Role and Key Management

MBB utilizes multiple services and accesses on-chain contracts, incorporating a multi-layered permission and private key management mechanism for different services and contracts. These include:

Roles

Owner

The Owner is responsible for deploying:

1. MBB Token Creator Contract

2. MBB LP Locker Contract

• MBB Staker Contract

The Owner also configures role permissions:

• In MBB Token Creator Contract: assigns AI Processor and setlocker roles

• In MBB LP Locker Contract: assigns Token_creator and Staker roles

• In MBB Staker Contract: assigns AI Processor role

AI Processor

Responsible for invoking most AI-controlled autonomous methods within the MBB contract, including:

1. Deploys ERC20 token (Memecoin)

2. Creates liquidity pairs on Uniswap V3

3. Permanently locks LP NFT in MBB Locker Contract

4. Claims token creator revenue

Operator

1. Claims transaction fees from unstaked tokens to magnetlabs.eth

2. Configures some contract parameters:

   • CreatorRevenuePercentage

   • MaxStakersPerPool

   • MinimumStaking

Keys

Twitter API Key

Twitter API Key is primarily used for MBB’s posting and commenting activities. It is authorized under the @magnetaixyz account and securely stored in the ActionVM Service Key Manager.

OpenAI API Key

The OpenAI API Key serves as the foundational access key for MBB’s underlying LLM capabilities. It is owned by Magnet Labs Inc. and securely stored in the ActionVM Service Key Manager.

AI Processor Private Key

• Wallet: memeblindbox.base.eth

• Management: Securely maintained in the Service Key Manager

Owner Private Key

• Wallet: magnetlabs.eth

• Management: Controlled by Magnet Labs.

Operator Private Key

• Wallet:

• Management: Controlled by Magnet Labs.