ALPHA WITHIN GOVERNED RAILS
UtilityInfrastructure
ALPHA supports access, settlement and incentives within Becoming Alpha’s ecosystem, with defined terms, eligibility requirements and governed transfer routes.
Becoming Alpha’s omnichain bridge is designed around LayerZero V2’s Omnichain Fungible Token (OFT) standard. It connects ALPHA’s Solana origin to configured EVM routes through source burning, verified messages and destination minting.
Omnichain bridge
How it connects
TransferControl
ALPHA has a fixed supply of 100 billion tokens, with Solana as its canonical origin. Using LayerZero V2’s OFT standard, the ALPHA Omnichain Bridge is designed to extend access to Ethereum, BNB Chain, Base and further EVM networks as each route is approved and configured. Every transfer is designed to conserve the global supply; cross-chain transfer is currently exercised on public test networks.
SourceRecord
A transfer identifies the amount and configured route. The source burn removes that amount from circulation on the source chain.
VerifiedMessage
The route’s verifier and execution requirements govern the message. Its identifier connects the source action to subsequent states.
DestinationRecord
Destination minting credits the corresponding amount after the required checks. Interrupted transfers follow the applicable recovery process.
Connected context
RecordedUtility
A utility transaction has an operating context: the service or activity it supports, the conditions that apply, and the evidence of what occurred. The architecture connects these elements so participants can examine the basis of access, settlement or program participation. Cross-chain routes add their own verification and recovery requirements.
Activity and conditions
Explore the detail
PlatformUtility
Start with the activity being supported. Each use depends on its terms, permissions and operating controls.
Access Utility
ALPHA’s access role connects token utility to defined services and intelligence capabilities within the platform design. The relevant terms identify the activity being supported and the conditions that apply to its use. Participant eligibility and information permissions remain part of that context. This gives a reviewer a way to examine how a proposed token use relates to an identifiable platform function and its governing requirements.
- Applicable activity
- Use of an eligible platform capability
- Governing record
- Access terms and participant permissions
Service Settlement
The settlement design connects payment to the scope, delivery and acceptance conditions of a service engagement. The engagement record identifies the expected work, the material used to assess delivery and the party responsible for acceptance. ALPHA’s role sits within those terms and the applicable operating controls. Preserving the delivery, acceptance and payment context supports reconciliation and review of how the engagement was fulfilled.
- Applicable activity
- An accepted service or platform engagement
- Governing record
- Delivery, acceptance and payment conditions
Verified Contribution
The incentive design links an eligible contribution to its supporting evidence, acceptance conditions and program rules. A release needs a recorded basis identifying the work, recipient, relevant reserve and permitted use. That trace allows reviewers to follow recognition back to the contribution and examine subsequent use. ALPHA Incentive Credits retain their separate non-transferable, spend-only conditions throughout the applicable credit process.
- Applicable activity
- An eligible contribution under a program
- Governing record
- Evidence, eligibility and permitted use
ALPHA Incentive Credits have separate non-transferable, spend-only conditions.
Chain Transfers
The transfer design connects a source-chain action to a destination-chain action through a configured route and a traceable message. Source burning and destination minting serve the movement of the corresponding amount under the global supply design. Route approvals, verification requirements, operating limits and recovery states provide the control context. A reviewer can examine those settings and the transfer record when assessing the mechanism.
- Applicable activity
- Transfer between enabled chains
- Governing record
- Route configuration, transfer states and recovery
Designed for accountability
GovernedRoutes
The governance model calls for an accountable owner, documented approval, a versioned route registry, operating limits and pause controls. Security depends on the contracts, verifier configuration and operating controls applied to each route.
Progress & RoadmapQuestions & context
FurtherDetail
How does the OFT protocol support the bridge?
LayerZero V2’s Omnichain Fungible Token (OFT) standard connects token transfers across configured chains. The design burns the bridged amount at the source and mints the corresponding amount at the destination. Decentralized Verifier Networks (DVNs) verify messages; an Executor handles delivery. Route configuration governs applicable fees, precision, limits and pause controls.
How does transfer minting relate to the supply cap?
Transfer minting serves the movement of an existing amount between chains. The conservation design accounts for circulating and in-flight amounts against the defined global supply.
Where can I review allocation and release information?
The reference tables below retain the published allocation amounts and illustrative release conditions. Schedules remain subject to governance and applicable terms.
Where is the current build position recorded?
Progress & Roadmap and Security & Assurance provide the published build and review context. Production activation depends on the required deployment, configuration and security gates.
Allocation & release reference
The allocation amounts total 100 billion ALPHA. Release conditions are illustrative and subject to governance and applicable terms.
| Allocation | Supply share | Amount | Unlocked at listing | Lock-up | Linear vesting |
|---|---|---|---|---|---|
| Seed | 10% | 10B | 10% | 3 months | 12 months |
| Private | 12.5% | 12.5B | 20% | 3 months | 9 months |
| Public | 5% | 5B | 50% | 3 months | 6 months |
| Founding Team & Early Backers | 11% | 11B | — | 12 months | 12 months |
| Elevate to Alpha | 13% | 13B | — | per program | per emissions |
| Alpha Visibility | 7% | 7B | — | per program | per emissions |
| Social Impact | 2.5% | 2.5B | — | per program | per emissions |
| Operations & Dev. | 14% | 14B | — | 1 month | 14 months |
| Marketing & Growth | 9% | 9B | — | 1 month | 9 months |
| Staking Rewards | 11% | 11B | — | metered | capped ≤1B / mo |
| Exchange Liquidity & MM | 5% | 5B | 50% at DEX | staged | + CEX & MM |
ContinueExploring
Continue into contribution programs and review the terms governing token utility.