Legal and risk information
SEAL is software for private balances and user-authorized transactions. Its purpose is to reduce unnecessary disclosure of financial activity and support personal safety. This page describes the design and its limits; it is general information, not legal advice, a regulatory determination or a substitute for jurisdiction-specific terms.
Privacy and personal safety
Public wallet histories can reveal balances and payment relationships. Reducing that exposure is a legitimate privacy objective, including for people concerned about targeted theft, extortion or kidnapping. Authorities have reported violent crimes targeting cryptocurrency holders; that does not establish that SEAL would have prevented them. See this US Department of Justice account of alleged cryptocurrency robberies and kidnapping.
SEAL does not guarantee anonymity, untraceability or physical safety. Deposits, withdrawals, swaps, submitting addresses and transaction timing remain public. Services can observe traffic metadata. Privacy software does not erase transaction history or remove legal obligations.
Permissionless protocol access
The pool's user entry points do not require a SEAL account approval or per-user allowlist. Anyone can submit a transaction that satisfies the contract's proof, asset, deadline and other execution rules. This is technical permissionlessness, not a promise that every use is lawful in every jurisdiction or that a hosted interface or intent service is always available.
Users authorize spending with their private note keys. Proof generation is local, and intent services receive the proof and authorized execution terms rather than the user's spending keys. Assets are held by smart contracts and their backing protocols. SEAL swaps execute the route and output limits authorized by the user's proof. General external call execution is excluded from SEAL. These statements describe functionality, not legal status.
The guardian controls asset admission, bounded fees and swap routes. It cannot pause user assets or recover them administratively. The guardian is also the immutable recipient of protocol fees. SEAL verification is fixed at deployment. A faulty or malicious verifier can threaten funds or prevent exits. Withdrawals also depend on valid proofs, available backing, token restrictions and recoverable note data. See Security.
Responsibilities and risk
Use SEAL at your own risk. Smart-contract, cryptographic, token, lending-market, infrastructure and key-loss failures can cause partial or total loss. Yield is variable; principal, returns and immediate withdrawals are not guaranteed. The current release is not approved for mainnet and has not received an independent audit.
Users and service operators are responsible for the laws applicable to their own activities, including sanctions, tax and financial-service obligations where applicable. Technical access is not permission to violate those rules. This page does not waive rights or duties that applicable law makes mandatory.
Regulatory status depends on activities
The absence of a pause function does not establish an exemption from money-transmission or other financial regulation. FinCEN distinguishes software development from operating services that accept and transmit value, and discusses decentralized applications separately. MiCA likewise distinguishes services without an intermediary from activities performed or controlled by identifiable persons. Applying either framework requires the actual facts, roles and jurisdiction; this documentation makes no exemption claim. FinCEN guidance, sections 4.4 and 4.5, MiCA, recital 22.
Protocol code, governance, a hosted interface, archives and intent services are distinct activities. Their legal treatment needs separate qualified review before a production launch. A descriptive name, risk disclaimer or permissionless design does not settle that analysis.