Send & Receive
Send assets between SEAL accounts without publishing the private transfer's asset or amount. The recipient needs a SEAL account for the same network; a public wallet address alone cannot receive a private transfer.
SEAL addresses and contacts
Open Receive → My address to copy your complete checksummed seal.… payment address. You can share a payment-request link or save it as a contact, such as Alex, for future payments.
Human-readable names such as alex.seal are not supported by this version. The current seal.… address contains the recipient's payment information and network. Its checksum catches copying errors; it does not prove who owns it. Verify the full address with the recipient through a trusted channel.
Send a payment
- Open Shielded transfers → Send, or Send privately from Overview.
- Choose the asset, amount and recipient's SEAL address or saved contact.
- Review the recipient, submission method and any intent service charge.
- Generate the privacy proof locally and submit the reviewed payment.
- Wait for confirmation. Share the encrypted transfer file if the app asks you to.
For example, choose the saved contact Alex, enter 500 USDC, and review the payment. The asset and amount are visible to you and Alex, but not published as the private transfer's values onchain.
Receive and use funds
When encrypted delivery is available, incoming payments appear after synchronization. Otherwise, open Receive and import or paste the sender's seal-tx-….json transfer file. The blockchain transaction alone cannot recreate missing delivery information.
Claim an incoming payment or use Claim & combine to collect several payments. A valid incoming payment can also fund a withdrawal directly. Claiming and combining leave the lending backing in place.
A transfer file is a payment receipt, not an account backup. Its filename can expose the date, asset and amount to anyone seeing the file. Store your account backup separately.
Pending payments and reclaiming
The sender can reclaim an unclaimed payment after its inclusion has aged seven days. After that delay, both claim and reclaim can be valid; the first confirmed action wins. Contact the recipient before reclaiming. A recipient cannot claim an already reclaimed payment.
A confirmed transfer cannot simply be reversed. When a response is lost, check its saved status before creating another payment. See Backup & Recovery.
Completion and privacy
Proof generation, file delivery and onchain confirmation are separate steps. A completed proof does not mean money moved. Multi-transaction batches confirm independently; earlier confirmed payments remain complete if a later one fails.
SEAL hides the balance, transferred asset and transfer amount, but transaction timing, submitting addresses and grouping metadata remain observable. See Privacy and Fees & Costs.