Permission Management

To ensure security, compliance, and transparency in on-chain asset management, the BlockRock platform employs a multi-signature authorization (Multi-Signature) and hierarchical access control framework.

1. Multi-Signature Verification (Multi-Sig)

• Applicable Scenarios: All high-sensitivity operations, including fund transfers, asset allocation changes, and smart contract upgrades.

• Execution Process:

  • Critical transactions require multi-party independent authorization (e.g., platform security officers, third-party auditors, user representatives).

  • Operations proceed only after all authorized parties complete signature verification (e.g., 3/5 signature threshold).

• Advantages: Eliminates single-point failure risks and prevents internal/external malicious tampering.

2. Hierarchical Permission Management

• Role Definitions:

Role Tier	Multi-Sig Required?	Permission Scope	Example Operations
Super Administrator (Owner)	Yes	Global system configuration	• Upgrade smart contracts, adjust underlying protocols • Set/Modify administrators and operators • Transfer token ownership • Modify reward tokens
Administrator (Admin)	Yes	Fund withdrawals and token minting	• Release subscription cycles • Withdraw invested funds • Mint reward tokens
Operator (Operators)	No	Subscription cycle creation and configuration	• Create new subscription cycles • Configure cycle parameters
Web3 Users (Users)	No	Investment and trading	Subscribe, redeem, query holdings

• Permission Isolation: Each tier operates independently; cross-tier access is prohibited.

3. Technical Implementation Flowchart

Permission Management

RWA Fund Workflow Example: