Safety
Security
Audit status, non-custodial design, admin keys and timelock intentions, and the planned bug bounty.
Rind holds other people's assets in a contract. That is a serious responsibility. This page states what exists today and what is intended.
Audit status
| Item | Status |
|---|---|
| Vault contracts | In design, not deployed |
| External audit | Planned, none completed |
| Audit report | Intended to be public before mainnet deposits open |
| Bug bounty | Planned, intended for the vault beta |
No audit has been completed. The intention is that mainnet deposits open only after at least one independent audit is complete and its report is public. The auditor and report will be announced on @Rind_rwa.
Non-custodial design
The vault is designed so that only you can move your position.
- Withdrawals are callable only by the wallet that owns the position.
- Executions are callable by keepers, but only when the contract itself verifies that the trigger is hit and the output meets the slippage cap. Proceeds go to your position, never to the keeper.
- No admin withdrawal. There is no function that lets an admin move user deposits.
- No upgrade of user funds. Positions do not migrate to new contracts without the owner's action.
Admin keys and timelock
Some parameters need to change over time, such as adding a Stock Token, adjusting a slippage cap, or updating the venue whitelist. The intended controls:
| Control | Intention |
|---|---|
| Parameter changes | Behind a timelock, so users can react before they apply |
| Admin key | A multisig, not a single key, until governance is live |
| Emergency pause | Can stop new deposits and executions, never withdrawals |
| Governance handover | Parameter control moves to $RIND governance in Phase 3 |
The emergency pause is deliberately one-sided. It can stop the protocol from acting. It cannot stop you from leaving.
What the contract checks
Every execution is checked on-chain:
- The reference price is fresh, less than 60 seconds old during market hours.
- The market state and token state allow a trigger.
- The price is at or below the trigger level.
- The output is at least the minimum allowed by the slippage cap.
If any check fails, the transaction reverts and nothing is sold.
Bug bounty
A bug bounty is planned for the vault beta. Scope, reward levels and the disclosure process will be published with it. Until then, if you find an issue in this site or the demo app, contact @Rind_rwa by direct message and do not disclose it publicly.
Your own security
- Use a hardware wallet for meaningful amounts.
- Read every signature request. The demo app only asks you to sign plain, human-readable messages.
- Rind will never ask for your seed phrase.
- Verify the contract address on this site and on @Rind_rwa before you interact.
Smart contracts carry risk even after audits. Use at your own risk. See Risks and disclaimers.