Safety and transparency

The rules are in the contracts

The fees and their split, the guardrails, the hourly windows, the token-seconds and the claims are enforced by Mandate’s contracts on Robinhood Chain, not by a server. Their addresses are published in the app’s footer and on its docs page at launch, with their sources verified on the explorer.

• Fees to the wei. What the trade panel shows before you sign is what the contract takes.
• The pools’ price. The stocks are bought on Robinhood Chain’s pools at their price of the moment, with no other price to match; the protocol’s purchases set a minimum from a quote taken just before.
• Logged decisions. Every agent proposal, executed or refused, is recorded with the hash of its reasoning file.
• Checkable $MAND drops. Each Merkle root is published with its file; anyone can recompute it.

What the protocol owner can do

• Update the protocol’s contracts, to fix a bug or add a feature, such as plugging in other launchpads. The tokens themselves and the liquidity lock cannot be changed.
• Pause, in case of a bug. On the contracts that hold funds, the owner can pause what goes out (claims, stock purchases, buybacks) while trading goes on, and move the funds to safety while a fix is prepared. The app shows a banner as long as anything is paused. What you are owed stays recorded.
• End a liquidity lock, only after announcing it 30 days in advance.

Risks

• Smart contracts can have bugs.
• Memecoins are volatile: you can lose what you put in.
• Drops depend entirely on volume: no volume, no stocks.
• Stock Tokens follow their stock, trade with its market’s hours, and are not available everywhere.