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 MBB contract’s permission manager oversees the AI Processor and maintains the list of approved Processors.

AI Processor

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

1. Deploying ERC20 contracts.

2. Creating liquidity pairs on Uniswap V3.

3. Distributing initial token allocations to contributors.

4. Managing airdrops

Processor

The Processor is the only manually operated role within the MBB contract and serves two primary functions:

1. Claiming Uniswap LP Rewards: Collects liquidity provider rewards generated through Uniswap.

2. Managing the Airdrop Token List:

   1. Tokens issued by MBB are automatically added to the airdrop token list.

   2. User-donated tokens (e.g., cbBTC, USDC, USDT) must be manually configured in the MBB contract to enable autonomous airdrops for these tokens.

Keys

X API Key

X 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

A standard EVM address is used to interact with MBB’s on-chain contracts, including:

1. Deploying ERC20 contracts.

2. Creating liquidity pairs on Uniswap V3.

3. Distributing initial token allocations to contributors.

4. Managing airdrops.

Its private key is securely stored in the Service Key Manager.

Owner Private Key

The EOA wallet magnetlabs.eth, managed by Magnet Labs Inc..

Processor Key

The EOA wallet, managed by Magnet Labs Inc..