Make a quantum transfer
Connect a relay, review exact transfer details, and confirm with your quantum password.
Choose a transaction connection
| Connection | What it does | What you provide |
|---|---|---|
| Browser gas payer | A connected extension relays the signed quantum operation through EntryPoint. It separately reviews/fronts the outer transaction fee. | An explicitly connected browser account on Robinhood Testnet |
| ERC-4337 bundler | A compatible service estimates and relays UserOperations. | Your HTTPS endpoint supporting chain 46630 and EntryPoint v0.7 |
Choose Browser wallet or HTTPS bundler in the connection panel, then connect the selected method. The quantum signing seed stays in Qozmo. Bundler endpoint details remain in this unlocked session and are cleared on lock. Provider CORS and service availability can affect browser access.
Prepare the asset and recipient
- 1
Choose ETH or ERC-20
For an ERC-20, enter its testnet contract and use Check token and balance. Symbols and decimals are read from the contract; the token remains labeled unverified.
- 2
Enter the destination
Use the full recipient address and a positive amount within the asset’s decimal precision.
- 3
Review the operation
Check the quantum sender, recipient, asset contract, exact amount, network, maximum account fee, and whether first-operation deployment is included.
- 4
Confirm your password
Qozmo rechecks account state, fee requirements, nonce, deployment, balance and execution before signing.
When a new review is needed
A review expires after two minutes. Changes in nonce, deployment or increased fee/gas requirements require a fresh review. Qozmo signs the originally reviewed operation rather than silently changing it.
For an undeployed account, balances are checked and account deployment is included. Explicit false-returning ERC-20 calls are rejected before signing when detected by the preview.
After submission
Qozmo checks the EntryPoint operation event and canonical receipt. A successful outer transaction alone does not establish successful transfer execution. The Activity view distinguishes verified execution from a merely consumed key.
If the service response is lost, follow pending operations. Do not create a new message with the exposed key.