Skip to content

Commit c260ac5

Browse files
Update docs/reference/token-reference.mdx
Co-authored-by: carsonfarmer <[email protected]>
1 parent f5c0698 commit c260ac5

File tree

1 file changed

+0
-28
lines changed

1 file changed

+0
-28
lines changed

docs/reference/token-reference.mdx

Lines changed: 0 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -41,31 +41,3 @@ The Recall Security Council is responsible for pausing token operations in emerg
4141

4242
The Recall Foundation manages contract upgrades and token minting across all networks.
4343

44-
#### Description
45-
46-
Secured by a 3-of-5 multisig wallet, where four signers are independent parties outside the core
47-
team.
48-
49-
#### Capabilities
50-
51-
- Can upgrade token contracts across all networks
52-
- Can mint new RECALL tokens as needed for network operations
53-
- Acts as both the Admin and Minter roles for all RECALL token deployments
54-
55-
#### Risks
56-
57-
- Compromised Foundation could upgrade token contracts to introduce malicious functionality
58-
- Malicious actors could mint arbitrary amounts of RECALL tokens, diluting token holders
59-
- Compromised Foundation could modify contract logic to lock or remove tokens
60-
61-
#### Mitigations
62-
63-
- Secured by a 3-of-5 multisig wallet, requiring at least three signers to approve any action
64-
- Four of the five signers are independent parties outside the core team, providing external
65-
oversight
66-
- Upgrades and minting operations are subject to multisig approval, preventing unilateral actions
67-
68-
#### Foundation multisig address
69-
70-
- **Base**:
71-
[`0x05634A50F64F9be0FdEb944a6A5eC40eD1068A60`](https://app.safe.global/home?safe=base:0x05634A50F64F9be0FdEb944a6A5eC40eD1068A60)

0 commit comments

Comments
 (0)