WEB3 Infrastructure
MHA Token · Tokenomics · L1/L2 Network · Smart Contracts · Audit · Seasons
MHA Token Overview
Use Case Framework
MHA is positioned across six functional areas in the MAGNE.AI ecosystem:
- Device: MAGNE.AI Phone Gen1 (MAG1) hardware participation incentives
- AI Agent: AI Agent economy settlement and incentives
- Network: MAGNE.AI network governance and value transfer
- Staking: Staking rewards and eligibility qualification
- Ecosystem: Ecosystem partners, liquidity incentives, Builder programs
- Future Expansion: Cross-chain bridging and Layer 2 settlement
Eligible Allocation Pool: 35,000,000 MHA allocated to eligible MS2 stakers based on effective staking weight.
Tokenomics (Distribution)
| Category | Allocation | Amount (MHA) |
|---|---|---|
| Mining | 30% | 3,000,000,000 |
| Staking | 15% | 1,500,000,000 |
| Ecosystem / DAO | 15% | 1,500,000,000 |
| Team | 10% | 1,000,000,000 |
| VC | 10% | 1,000,000,000 |
| Early Supporters | 8% | 800,000,000 |
| MM (Market Making) | 7% | 700,000,000 |
| Public | 3% | 300,000,000 |
| Agents | 1% | 100,000,000 |
| Exchange | 1% | 100,000,000 |
| Total | 100% | 10,000,000,000 |
L1 / L2 Network Architecture
| Layer | Type | ChainID | RPC | Explorer |
|---|---|---|---|---|
| L1 | Testnet | 20250810 | https://rpc.testnet.magicalhash.com |
Explorer |
| L2 (OP Stack) | Testnet | 20250827 | https://l2-rpc.testnet.magicalhash.com |
Explorer |
| Mainnet | Production | Planned | Target Q3 2026, subject to official announcements and technical progress. | — |
Cross-chain mapping from BSC (initial deployment) to L1 and L2 is planned. Testnet data should not be relied upon for formal economic activity.
MAGNE L1 / MHash L2 Capabilities (Public Reference)
- MAGNE L1 — base layer for the MAGNE.AI ecosystem
- MHash L2 — second-layer for scalable operations
- Wallet / swap / stake / bridge / identity / ecosystem access
- Web3 Portal as public reference source (token disclosure, network, developer and transparency materials presented as public references, not guaranteed launch claims)
Smart Contracts
| Contract / Asset | Address | Status / Source |
|---|---|---|
| Season 1 Lottery Contract (Proxy) | 0xb14426893ADb6601b9e6397afa10527B66297bc1 |
Publicly visible on BscScan |
| Season 1 USDT Pool | BSC USDT token holder / transactions | Publicly visible on BscScan |
| Season 2 Lottery Contract (Proxy) | 0x6DE61D8438176741fc8150Aef53256830a6Dd635 |
Publicly visible on BscScan |
| MS2 Staking Contract (Proxy) | 0xB6Ed72808fb34a3Ac118D397f49332abBAA484D8 |
Publicly visible on BscScan |
| MS2 Token | 0xC46A54BBD2716C436Aaaed6Ed2f555a9b054ebD1 |
Publicly visible on BscScan |
| MagneLotteryS2 Implementation | 0x877f5C053F3F3b43063572b432fF7B7F7B08226B |
Publicly visible on BscScan |
| MS2Staking Implementation | 0x9a7d5E82aB8bb64e279D02F80FF87aD42397532C |
Publicly visible on BscScan |
Audit Status
| Audit Scope | Status |
|---|---|
| Smart Contract Audit (overall) | Pending |
| Token Contract Audit (MS2) | Pending |
| Lottery Contract Audit | Pending |
| Staking Contract Audit | Pending |
| L1 Testnet Audit | Publicly visible in Season 2 Activity Center |
| L2 Testnet Audit | Publicly visible in Season 2 Activity Center |
| Mainnet Launch Readiness | In Progress |
Audit reports are categorized as Available under NDA upon completion.
Public Sale OG
Reported Public Sale OG Amount denominated in MHA · Dune Query 7924103 · 2025-10-29 to 2026-03-14 · lock-up 6 months after listing, then continuous release over 24 months
Public Sale OG — Round Summary
Pricing · lock-up · vesting · subject to applicable listing arrangements, exchange procedures, and compliance review
Prior to listing, an early-supporter public sale is planned at the lowest public-sale price. At the time of listing, the intended listing reference price will not be below this public-sale level, subject to applicable listing arrangements, exchange procedures, and compliance review.
Tokens from the Public Sale OG round will be locked for six months after listing and then released continuously over twenty-four months.
Public Sale OG Purchase History
MHA-denominated purchase records · 6 rows · 2025-10-29 to 2026-03-14
Disclaimer: This public sale chart reflects Dune query results denominated in MHA and should be reconciled with internal sale records, treasury records, refund records, and compliance review. It does not constitute investment advice, a guaranteed listing outcome, or a guarantee of future market performance.
Season 1 Activity Data
MAGNE.AI Phone Gen1 (MAG1)
Latest Season 1 metrics can be reviewed through the MAGNE.AI Season 1 Dashboard. MHA-related distribution records are subject to TGE timing, eligibility review, and official campaign rules.
Season 1 Historical Reference
On-chain participation evidence · Dune Query 7913639 · Cumulative Participating Wallets (daily cumulative snapshot, Apr 17 – Jul 06, 2026)
Disclaimer: Wallet addresses are not verified unique individuals.
Historical reference only. This chart is a historical Season 1 on-chain reference and does not represent current Season 2 participation.
Metric name: Season 1 Cumulative Participating Wallets. This figure reflects on-chain wallet activity recorded during Season 1 and is provided as historical reference only. It is not a measure of verified users, real users, KYC users, or otherwise confirmed unique human participants.
Public Dashboards & Links
Dashboards
- MAGNE.AI Season 1 Dashboard (Completed)
- MAGNE.AI Season 2 Dashboard (Beta)
- Dune Analytics (Community-maintained)
Public Reference Sources
- Official MAGNE.AI Site — Product, compliance, supply chain, campaign and contact information
- MAGNE.AI Web3 Portal — Web3 infrastructure, token disclosure, network, developer and transparency materials
payment.magne.ai Public API Status
| Endpoint | Status |
|---|---|
| /api/v1/lottery/dashboard | Public readable |
| /api/v1/lottery/list | Requires login |
| /api/v1/lottery2/dashboard | Requires login |
| /api/v1/lottery2/list | Requires login |
| /api/v1/lottery2/leaderboard | Public but empty / pending |
For the most reliable data, use the public dashboards linked above rather than direct API integration.