Meteor extension: open this page in the Chrome browser where you installed it. Choose a testnet account (for example 0xcaptain888.testnet). An extension in Chrome is not available inside the Codex browser. MyNearWallet remains available in the wallet menu.
YOUR APPROVAL. ON CHAIN.
Proof before payout.
Inspect a deployed treasury, review an exact action, and approve it in your wallet.
Loading wallet component…
Archived account setup · read only
This earlier plan is blocked by Meteor's Full Access Key policy. It cannot create accounts or send funds. Keep it only to inspect the six proposed accounts. A separate developer-account deployment is required before treasury verification. All development reviewer identities belong to the same tester, not independent operators.
1. Verify your treasury
Load the project's public configuration and verify bytecode, participants and timing against one final testnet block. This read-only step does not request wallet authorization.
Use another public configuration
Verification boundary
This trusts the FastNEAR testnet RPC. It is not a light client or a proof of reviewer independence. A connected wallet is not authentication to the private workspace. Public configurations contain account IDs and commitments, never keys.
2. Prepare an action
Each operation is checked against your wallet role and current contract state. Browser funding is capped at 0.01 testnet NEAR per treasury. Wallet gas is separate.
0.001 testnet NEAR. No transaction until wallet confirmation.
Compare the receiver, method, amount and arguments with your wallet. No delegated function-call key is requested.
3. Verify the outcome
A wallet return is not proof of payment. Check the final transaction and every execution receipt. If signing timed out, inspect wallet history and verify its hash here before attempting a new transaction.