The Governance feature enables you to define and manage organizational policies for all platform operations. Set up approval groups, configure transaction policies, establish quorum requirements, and maintain complete control over who can perform what actions.
Changes to general policy quorums require review by the Crocante team. Submit a request to modify these core rules.
Transaction policies for withdrawals from Crocante-managed wallets:Policy Structure:
Order: Priority order (policies evaluated top to bottom)
Name: Descriptive policy label
Initiator: Who can initiate (All or specific users)
Destination: Where funds can go (All or specific addresses)
Asset: Which cryptocurrencies (specific or All Assets)
Range: Amount thresholds in USD or quantity
Quorum: Required approval groups and counts
Example Policy:
Name: Policy BTC1Initiator: All InitiatorsDestination: All Destinations Asset: BTCRange: 0 to 20 USD (Equivalent in USD)Quorum: Master Group (2)
Transactions that don’t match any policy will be denied by default. Ensure your policies cover all legitimate use cases.
Transactions are evaluated by the first matching policy in priority order. Order your policies from most specific to most general.
Policies for withdrawals from exchanges, OTC desks, and other counterparties:Policy Structure:
Order: Priority sequence
Name: Policy identifier
Initiator: User roles that can initiate
Origin: Source account type (Exchange, Internal OTC, Whitelist)
Destination: Target account type (Parfin Wallet, Whitelist, All)
Asset: Supported cryptocurrencies
Range: Amount limits
Quorum: Approval requirements
Example Policy:
Name: iOTC ALLInitiator: All InitiatorsOrigin: Internal OTCDestination: All DestinationsAsset: All AssetsRange: 0 USD or higher (Equivalent in USD)Quorum: Master Group (1)
Use counterparty policies to enforce different approval requirements based on where funds are coming from and going to.
User groups responsible for approving activities:Group Properties:
Name: Group identifier (e.g., “Master Group”, “OPs Team”)
Members: Number of users in group (e.g., “23 Users”)
Last Update: When group was modified
Rules: Number of policies using this group
Status: Active or Inactive
Example Groups:
Master Group: 23 Users, 27 Rules, Active
OPs Team: 6 Users, 0 Rules, Active
Teste de Grupo: 20 Users, 2 Rules, Active
Only admins can create, edit, or remove groups. Changes require approval according to “Approval Group Management” policy.
{ order: string, // Priority name: string, // Policy name initiator: string, // Who can initiate destination: string, // Where can send asset: string, // Which assets assetIcon: string, // Display icon range: string, // Amount limits quorum: string // Approval groups}
Counterparty policies add:
{ origin: string, // Source account type // ... other fields same as wallet policies}
Approval groups:
{ name: string, // Group name members: string, // Member count lastUpdate: string, // Last modified rules: string, // Policy count using this group status: string // Active/Inactive}
Policy Ordering Matters: Place specific policies (e.g., “BTC withdrawals 0-20 USD”) before general policies (e.g., “All assets, all amounts”). The first match wins.
Use Descriptive Names: Name policies clearly (“Policy BTC - 15-30” instead of “Policy 3”) for easier management and auditing.
Balance Security and Usability: Higher quorum requirements increase security but slow operations. Match quorum to transaction risk level.
Avoid Policy Gaps: Ensure legitimate transactions have a matching policy. Unmatchable transactions are automatically denied.
Test with Low Amounts: When adding new policies, test with small transactions first to verify the policy matches correctly.
