Manage compliance rules
Compliance officers change transfer rules from the dashboard. Every edit is captured in an audit log, and changes apply on the next token operation — never a redeploy.
Where rules live
Each token configuration has exactly one rule set. Open Rules in the dashboard, choose the token configuration on the left, and its current rules load in the editor on the right.
Editing a rule
- Select the token configuration (for example
us_real_estate_fund_v1). - Adjust any field — required schema, allowed jurisdictions, minimum investment, max holders, or transfer lock.
- Save. The change is validated and persisted immediately.
When changes take effect
A saved rule applies to the next /token/mint or /token/transfer call. There is no on-chain transaction, no redeploy, and no downtime. In-flight transactions already built are unaffected; new builds use the new rule.
Reading the audit log
Every change writes an entry recording who made it, when, and the before and after values. Use the audit view to answer “who changed the minimum investment, and when?” with certainty. Entries are append-only — they are never edited or deleted.
Worked examples
| Goal | Change |
|---|---|
| Open an asset to a new market | Add the jurisdiction to allowed_jurisdictions. |
| Raise the holder cap | Increase max_holders. |
| Enforce a lock-up | Set transfer_lock_until to the unlock date. |
| Require accreditation | Set required_schema to kyc_accredited_v1. |
Last updated