18 Trust
Risks
The honest list: what is built, what is not, and what can go wrong for users and for the token.
Not financial advice. $OOPS is a memecoin and may go to zero. Buy only what you can afford to lose. Nothing here is an offer to sell or a solicitation to buy any asset.
#Status
| Piece | State |
|---|---|
Escrow contract (Oopsend.sol) | deployed at 0x7B530e91D9dc24C78Ca2eEE2B494E7dE1B680AC0, tested |
| JavaScript engine and lab | running, but a simulation: it runs the contract's rules on a local ledger and a simulated clock, it does not touch a chain |
| Docs | written |
| Relayer | design only |
| Undo from X | design only |
| Automated on-chain buyback | design only, V1 burns are run by hand from a public wallet |
#Product risks
- Smart-contract risk. The code is new. A bug can lose funds. Per-link caps (2 ETH and 1% of a token's supply by default) exist to limit the damage.
- Admin risk. The admin can raise the fee for new links up to 1%, lower the caps, or pause new links. It cannot move escrowed funds or change open links. It can renounce its role.
- Link leakage. A leaked link can be claimed by anyone until it is undone. A link is a bearer instrument, so share it like cash.
- Token risk. Tokens that can blocklist, freeze, pause or rebase can make payouts revert or lose value inside an escrow. See Security and limits.
- Front-end risk. Phishing copies of the site are possible. Check the domain and the contract address before connecting a wallet, and never paste a seed phrase anywhere.
- Device risk. The secret lives in the browser that creates the link and in the URL. Malware or an unsafe extension on that device can read it.
- Dependency risk. The chain's RPC, wallets and any relayer can go down or change. The on-chain functions still work without the website: you can call
undoandexpireRefunddirectly. - Ordering risk. If an undo and a claim race, the transaction ordered first wins. A recipient who is slow can lose to an undo, and a sender who is slow can lose to a claim.
- Chain risk. Robinhood Chain is a young network. Outages, reorgs or policy changes by the chain's operators are outside Oopsend's control.
- Privacy. Senders, amounts, tokens and expiry are public events. The recipient is public when the claim lands.
#Token risks
- Memecoin volatility, thin liquidity, bonding-curve dynamics, bots and snipers.
- The buyback and burn depend on actual usage, which may be small or zero. They also depend, in V1, on people running the fee wallet doing it.
- $OOPS is not a security, a share or an investment contract. It gives no rights, no dividends and no claim on fees or escrows.
- Fakes will appear. The real contract address is published once, in the site config.
#Legal
Escrow and payment services can be regulated in some places. Check the rules where you live before using Oopsend or buying the token. The software is provided as is, with no warranty.
#What would reduce these risks
A deployment with a published and verified address, a running relayer that has been tried in public, and a period of use with the caps kept low. The Roadmap lists them in order.