Local readiness check
Check this browser before production use.
PayMoney needs two unusual browser capabilities: threaded Stwo proof generation and the PayMoney Chrome extension. These checks perform both operations locally with real cryptography.
This reference STARK is transparent, not zero-knowledge. Do not enter secret leaves. Passing confirms this reference profile only; it does not certify the final production circuits, bank integration, or settlement system.
01 · Browser prover
Generate a Poseidon2 Merkle proof
Every leaf carries 8 canonical M31 words. Choose a tree size and how many worker threads the prover may use, then prove it. The leaves and proof never leave this browser.
Each proof gets a fresh prover and thread pool. Changing either control changes the next measured proof.
- Load the prover
- Start the thread pool
- Prove
Proving runs entirely in this browser and gets slower as the tree grows. Keep this tab open and let it finish.
Proof generated
- Merkle root
- Circuit ID
- Leaves
- Threads
- Proving time
- Peak Wasm memory
- Proof size
02 · Chrome extension
Sign a fresh local challenge
Detection requires a real provider round trip. After approval, the extension returns its BIP-340 public key, signs a fresh challenge, and this page verifies the signature locally.
- Detect the provider
- Approve the connection
- Approve the signature
Install PayMoney 0.5.0
This is an unpacked developer-mode installation for Chrome 140 or newer. Chrome will keep using the extracted folder, so leave it in a permanent location. It runs on
https://paymoney.financeand onhttp://localhostat any port; other local hostnames and IP addresses are deliberately excluded.- Download paymoney-extension-0.5.0.zip .
- Extract the ZIP. It creates a folder named
paymoney-extension. - Open
chrome://extensionsin a new Chrome tab and turn on Developer mode in the top-right corner. - Choose Load unpacked.
- Select the extracted
paymoney-extensionfolder—the folder that directly containsmanifest.json. Do not select the ZIP or its parent folder. - Return to this page using
localhost, reload it, and choose Check extension.
If Chrome reports a manifest error, remove the extracted folder, download the ZIP again, and repeat these steps. When a newer version is published, replace the extracted folder and choose Reload on the extension card in
chrome://extensions.Signature verified
- Key fingerprint
- Public key
- Extension version