Sign in to your FYNX workspace. Connect your own wallet, verify ownership, and test each step before launch.
Use your existing owner account. You can add a passkey after signing in. FYNX never asks for wallet recovery words.
Connecting securely…
Loading your dashboard…
Follows what you do on this page. Nothing here signs, sends or saves anything except your own test results in this browser.
Record each result here as you go. It is the same list as Launch readiness, saved only in this browser. For steps with a transaction, add its ID to the note as evidence.
Connect an Ethereum browser wallet. A Ledger account can connect through a compatible wallet extension; approval stays on your device.
Test assets have no monetary value. Never send real money to a test network.
No wallet connected
A connection alone does not prove wallet ownership.
— USDC
Check the full address and selected network on your wallet device. Only send the selected asset on that same network.
Connect and verify your wallet first.Recovery belongs to your wallet. For Ledger, keep the 24 words offline and enter them only on your Ledger device. An email password reset cannot recover wallet funds.
Your wallet shows the final network fee. No FYNX service fee applies to this test.
Quotes come directly from Uniswap v3 pools. FYNX charges no service fee for these tests. Pool fees and blockchain fees apply. Quotes expire after one minute.
An approval only permits the displayed amount; it does not complete a swap. After approval confirms, request a fresh quote. On Base the wallet may add an L1 data fee to the estimate.
Transactions you submit from this page appear below. “Check status” reads the network and tells you if one is waiting, confirmed (with a confirmations count), failed, replaced by a sped-up or cancelled version, dropped, or moved by a block reorganisation. Checking never signs or resends anything. This is not a complete wallet history: use the block explorer for older activity.
FYNX will use a regulated payment provider for card and bank checkout. A Transak sandbox adapter is prepared; it needs your partner account and approved connection before testing. No real card or bank payments are enabled.
Open Transak sandbox ↗Use only the provider's test credentials in its sandbox. Payment and KYC information stays with the provider. Opening or returning from checkout never confirms payment. Transak staging ETH buys do not deliver ETH; use this to test the checkout only.
Off · Base is read-only
When on, Crypto tools can prepare ETH and USDC transfers on Base up to your limits, with the same review, simulation and checks as on the test networks. Your wallet still asks you to approve every transfer. Swaps with real money stay off. Turn this on only after the security, legal and pilot gates in Launch readiness are done.
Needs a sign-in within the last 5 minutes. Every change is written to the security audit log. Turning off takes effect at once, also for a transfer you were reviewing.
Read by your FYNX server for the wallet you verified, on every supported network. Read-only: nothing is signed or sent. Test-network assets have no money value and are never added to your total.
| Network | ETH | USDC | Value (USD) |
|---|
Every ETH and USDC transfer in and out of your verified wallet, newest first (up to 100), from the history provider.
Compares this history with the transactions you submitted from this page and with the balances above. Read-only. Used for the pilot / rollback launch step: see the rollback and reconciliation plan ↗.
| Asset | Received | Sent | Net | Balance | Check |
|---|
Checked in this browser from your signed-in account. Nothing is sent or saved.
Losing every way in means waiting for a manual owner recovery. Keep at least two.
Do each test, then record Passed, Failed or Not applicable here. It is the same list as Launch readiness, saved only in this browser. Add a short note to each (browser, device) with Add a note.
Use your device’s biometric or PIN verification to sign in to FYNX. A FYNX passkey protects account access; your connected wallet still approves each signature.
Sign in again if your login is more than five minutes old. Keep Google or email access as a backup.
Load registrations to see the latest entries.
Browse 50 entries at a time, or search for an exact email. Expand a status to inspect consent and retention. Remove a record only after verifying a deletion request. Test addresses at example.com are not subscribers.
Likely typos, throwaway inboxes, shared mailboxes and the same inbox signed up twice, from the loaded rows.
Figures use the registrations loaded on this page and leave out test addresses. The CSV file contains email addresses: keep it private and delete it when you no longer need it. The copied summary has counts only.
A draft built from this registration. Check it, then paste it into your reply from fynxteam5@gmail.com. Nothing is sent from here and the draft is cleared on sign-out.
| Registered | Status & consent | Action |
|---|
Keep track of every access, removal or correction request so none is missed. Each one is due 30 days after it arrives (your own target; your lawyer confirms the legal deadline for each country). Do not type email addresses here: a ticket number or the email subject is enough to find the message. Saved only in this browser.
Join from your phone with an address ending in @example.com, then press Find registration with that address here. The sign-up check below confirms what was saved; after you remove it, you can record the test in one press. Results are shared with Launch readiness and saved only in this browser.
These are release gates, not certification checkboxes. Test evidence and remaining work are maintained in your GitHub repository.
FYNX is built to use these the moment their keys are added. Keys go into Google Cloud Secret Manager, never into this page, chat or GitHub. Press Check my services after each step of the setup guide.
Mark each of your steps Passed, Failed or Not applicable and add a short note. Results stay in this browser only and are never sent anywhere. Copy the report and share it so the checklist evidence can be updated.
Tested on your phone or iPad? On that device, open Launch readiness and press Copy test report (or Download report). Then paste the report here or choose the downloaded file. It is read in this browser only and nothing is uploaded. For each step, the most recently recorded result is kept. Your answers in “Decisions only you can make” come along too (the most recently saved answer is kept), as do the waitlist privacy request log (dates and answers only; the most recently changed version is kept) and finished incident practice runs with their follow-up tick-offs.
Twelve launch steps are business decisions rather than tests. Answer each one here; a complete answer marks that step done in the checklist above and goes into your test report. Answers stay in this browser only.
The decision record is a short table for your engineer or Claude. The lawyer sheet is a first-call list of questions for U.S. counsel, filled in with your answers so far. Neither contains keys, passwords or email addresses you did not type.
Sit down with your team for about 30 minutes. Pick a made-up incident, then talk through the seven stages of the incident procedure ↗ one at a time. For each stage, agree what you would do, then compare with the procedure. A finished run with at least two people marks the practice-run step done in the checklist above. Nothing is sent anywhere; the run stays in this browser.
Every follow-up written during a finished practice run lands here. Tick each one off when it is done, so nothing agreed in the room is forgotten.
Backups: once a backup policy is chosen, the restore test follows the backup and restore guide ↗.
Check owner access, the private database and any connected wallet’s network. This check does not request a signature or send funds.