BASE SEPOLIA Test assets only · No real dollar valueAbout testnet ↗

Wallet access & recovery

Use test assets only. Dokora cannot reverse a transaction or recover a lost login wallet for you.

Independent wallet access

Use the static recovery client with your own Base Sepolia RPC and connected wallet. It supports verified recovery and direct protocol actions without signing into Dokora. Keep your original browser’s transaction records and resolve pending requests before sending another transaction.

Test USDC only. The client cannot replace a lost wallet key. Never enter a recovery phrase or private key.

Open independent recovery client

Earlier testnet markets

Select the earlier gateway deployment in the independent client's protocol selector for its token trades, badge activity, fee claims, refunds and validator recovery. The older admin-scoring deployment is also retained. Use the original wallet and resolve saved transactions and vote secrets before sending another request.

Deploying the new stack does not transfer old tokens or badges. Earlier market values are excluded from the current portfolio view.

Returning on a new device

  1. Restore or unlock your original login wallet using that wallet provider’s official instructions. Never enter a recovery phrase into Dokora.
  2. Open Dokora, choose Sign in, then select that same wallet and approve the sign-in message. Check the site address and the message before signing.
  3. Your trading wallet stays paired with your account and restores automatically. If sign-in has expired, approve the sign-in request for your original wallet. No funds move during sign-in.
  4. Compare the full trading-wallet address with your saved address or a previous deposit’s recipient. If it differs or access cannot be restored, stop. Do not fund a new address to recover old funds.
Login wallet vs trading wallet

Your login wallet proves ownership of your profile. Your trading wallet is a separate Coinbase CDP smart account used for one-click trading. A public address, a screenshot or a deposit receipt does not prove signing authority.

Save the public addresses of both wallets and the original sign-in method privately. An account-data export, browser settings or remembered wallet address is not a recovery key.

If you used an older email or Google sign-in, use that original method and the same CDP project. The current wallet-only screen cannot recover an unrelated legacy account. Do not sign out of a funded legacy session until recovery is arranged.

Lost or compromised access

If your login wallet is lost, follow its provider’s recovery process. Dokora support cannot replace its recovery phrase or assign its account to a new wallet. If you still have a verified trading session, review withdrawal options before ending it.

If compromise is suspected, stop using the affected device. From a trusted device, follow your wallet provider’s instructions to secure access and review permissions. Signing out of Dokora ends its local sessions; it does not revoke existing token allowances or cancel onchain transactions.

Never send a recovery phrase, private key, wallet QR pairing URI or sign-in code to support. Support will not ask you to transfer funds to “verify” or “unlock” an account.

Open support

Still need help?

Email support@dokora.xyz · No sign-in needed.

Describe where you are stuck. Never attach wallet backups or recovery credentials.

Support can troubleshoot access, but email cannot prove ownership or authorize moving funds or reassigning a profile.

Become a validator

Review proposals when you’re available. Anyone can sign up without committee approval. Signup starts off duty.

Before you start

  • Your profile and validator wallets become publicly and permanently linked.
  • Be ready: accept within 8 seconds, vote within 90 seconds, then reveal during the 90-second reveal window.
  • Keep your vote backup and pay network gas. This signup route does not provide automatic reveal.
  • Missing an accepted review costs Trust Credits. Repeated misses or votes against the final outcome can cause cooldowns; repeated misses can permanently ban your validator.
Read full validator rules
  1. Enroll with both wallets

    I authorize this exact engine and permissionless registrar to bind my validator wallet and profile wallet using the same versioned consent, nonce and deadline. Both wallets must consent; anyone may relay their signatures. Admission requires no committee credential, operator attestation, identity verification, deposit or stake. Network gas and transaction confirmation are still required.

  2. Understand the permanent public link

    Enrollment publicly and permanently links these wallets in this engine. A registered validator cannot register again, and its bound profile cannot be reassigned to another validator to clear a ban or reset history. I start with 100 Trust Credits and off duty. I must deliberately opt in before receiving work. Fresh wallets and profiles are not proof of a new human, and open enrollment does not prevent one person from controlling many validators.

  3. Accept only when ready

    An invitation must be accepted onchain before its 8-second deadline. After accepting, I have 90 seconds to review and commit Approve or Reject, or submit Pass if I cannot confidently decide. I must check the actual proposal, subject, category, description and source, including duplicates and misleading or harmful claims. Researching or waiting for a wallet does not pause the timer.

  4. Keep and reveal the exact secret

    Before committing, I must keep a complete scoped backup of my decision and salt and acknowledge saving it. Only the commitment is public at this stage. I must reveal that exact vote when the engine opens the 90-second reveal window, including when a retained manual outcome permits reveal. I must verify transaction confirmation and keep the secret until my accepted work is complete. This permissionless route does not promise a server backup, automatic reveal, gas sponsorship or inclusion before a deadline.

  5. Keep the existing automatic penalties

    A missed accepted decision or reveal costs 1 Trust Credit. Two consecutive unfinished accepted reviews trigger a 24-hour cooldown; one more unfinished accepted review triggers a second 24-hour cooldown, and another triggers a permanent validator-wallet ban in this deployment. A timely reveal or Pass breaks the initial streak. Gaining 10 net score points above the latest timeout-cooldown score resets the pre-ban escalation, without shortening an active cooldown or reversing a ban. Three consecutive decisions against the final outcome trigger a 24-hour cooldown. Two expired unaccepted invitations clock me out without a Trust Credit loss.

  6. No discretionary reinstatement

    The new stack freezes validator administration with zero validator-admin members and no credential eligibility guard. No operator or committee can grant eligibility, raise my score or restore my banned wallet/profile through an appeal. Existing automatic scoring and cooldown recovery remain; a permanent ban does not expire. Creating new keys can evade a wallet-level ban and is not evidence of a different person.

  7. Manual launches and rewards remain separate

    The manual reviewer still approves or rejects launches under the existing fallback rules until its owner explicitly retires that power. A revealed vote matching the final community or manual outcome gains 1 point and 1 Trust Credit; an opposing vote loses 1 of each. Only eligible completed community-panel work earns the existing weekly fee-funded rewards; Passes, timeouts, cancelled panels and manually decided reviews earn no reward work. Badge transfer rights, fee rates and fee allocations are unchanged. Rewards and profitable outcomes are not guaranteed. The currently bundled live deployment uses Base Sepolia, test USDC and mock exchange dependencies; this new source does not activate real USDC or change that deployment.

1. Review your wallets

Connect the wallet you use for your Dokora profile.

Advanced

Use these options for external wallet signatures, a previous request, or technical verification.

Manual signatures

Start with Review signup and agree to the rules above. Request each signature separately, or paste signatures from your wallet’s verified signing interface.

Recover a previous request

Check what happened to a request you already sent. Checking never sends it again. Paste its transaction hash only if the saved request is missing that hash.

Accept a review directly

Accepting a review is separate from signup and duty. It must confirm onchain within the original eight-second offer.

Technical details
Consent version
2026-10-16-permissionless-v1
Consent hash
0xd5db24e86d03366009b6f3e1d2aa96b53e930659272bf2564d7242759a6903dc
Enrollment contract
0xA1b79C852D5234D80Dd122dd55631a2B9b1Ba759
Validation engine
0x8403574980f851aAA23B57448Aa73140b737E500

Protected Coinbase wallets use their approved controller and paired wallet owner. Unsupported wallets can use the independent client with externally reviewed signatures.

Request details

Details appear here after you review or check a request.