Dokora independent recovery

Base Sepolia · Test USDC only. This static tool uses your chosen RPC and connected wallet directly. It does not sign into Dokora, contact its account service, use its hosted RPC, or load CDP.

Keep the original browser's transaction records. Another origin cannot read them. Resolve pending transactions before using a separate recovery copy. Never enter a private key or recovery phrase.

Connection

The URL stays in this page's memory. Use an RPC that allows requests from this origin; no fallback is selected automatically.

Wallet disconnected

Withdraw or revoke

Checks the actual controller and both supported controller journals. Your root wallet approves the exact transaction. No wallet migration is performed.

No action prepared

Direct protocol actions

Use the bundled protocol selected above. Direct sends use the connected EOA root and its balances. For a contract wallet or assets held in a different trading wallet, export the exact call and use that wallet's verified execution interface. This panel does not impersonate its owner or switch to CDP.

Allowance and trade are separate, explicitly confirmed transactions. Approval alone does not buy or sell. Check an earlier approval before preparing a trade; no automatic batch or infinite approval is used. Use zero to revoke an allowance before changing an existing nonzero allowance. The pinned canonical router is selected for a graduated market; the curve is selected before graduation.

For contract-wallet assets, enter the actual asset-holding wallet here. Export verifies its balances, ownership and exact simulation. The connected wallet does not send this export.

No protocol action prepared

Permissionless validator enrollment

For a separately reviewed fresh Base Sepolia deployment. The hosted legacy registrar is not changed. Anyone may register with consent from both wallet owners; there is no committee signature. The linked addresses are public and permanent. New registration does not go on duty or reset an existing score, cooldown or ban.

The paired root above is the explicit transaction relayer and pays native gas. Both participant wallets sign identical typed consent. Use the same address for both roles to self-enroll with one reusable signature. Approved protected Coinbase validator wallets can use the verified paired EOA root for replay-safe consent. Other contract-wallet owners must import a signature from their verified interface; this page does not impersonate them.


    
Read the exact versioned validator consent
No consent prepared

A separate wallet owner can review the downloaded typed consent in their verified signing interface and return its exact signature. Signature requests never ask for a private key or recovery phrase. Enrollment signatures may be relayed until the displayed deadline.

No enrollment prepared

  

Independent validator workflow

Duty requires an existing eligible validator registration. This client does not bypass admission rules. Inspect the onchain proposal and its deadlines before deciding.

Direct claim must be mined within the original eight-second offer. It does not obtain the operator's acceptance grace. This route supports a connected EOA validator or an EOA paired root of an approved restricted wallet. Contract roots should use their own verified execution interface.

Keep the downloaded secret private until reveal. The secret stays local when committing; only its commitment is sent. You are responsible for revealing the same vote within the onchain window. A missed reveal can incur penalties. Imported backup text is parsed locally.

No action prepared

Public referral ledger

For a separately reviewed fresh Base Sepolia deployment. Selecting a published public-ledger protocol prefills its reviewed pins. Other deployments require explicit published runtime hash and bindings; the tool verifies them before preparing any transaction. Historical private referral records are not migrated.

Registration and enrollment use the connected root as profile. Links and referrals are public and permanent. If using a separate trading wallet, link it before enrollment or either wallet's first trade. You cannot attach it later after enrollment. This registry does not change wallet custody.

Mutual wallet link consent and exact call

Review the same typed consent with both wallet owners using their verified signing interface. This tool does not request a blind signature. The nonce and deadline are fixed in the displayed consent.

No referral action prepared

Enter an RPC URL and connect your wallet to start.