Launch status
BAAL is PRE-LAUNCH. The TGE has not occurred. TGE date: To be announced.
BAAL is not available for purchase or transfer. Liquidity and trading have not started. No token sale exists and no allocation is promised to anyone.
Summary
0 of 14 release gates met
- Website / community pre-launch
- This informational site; the waitlist is not open yet. It creates no token.
- Token generation event (TGE)
- Has not occurred. TGE date: To be announced.
- Liquidity creation
- Has not occurred. Not part of the TGE.
- Trading opening
- Has not occurred. Not part of the TGE.
- Token address
- [Mint address: Not published. Token generation has not occurred.]
- Vesting program audit
- NOT AUDITED
- Vesting program deployment
- BLOCKED
What has to happen first
The TGE will occur only after the remaining technical, security, audit and release gates below are satisfied, and then only on the explicit written approval of the project's founder. Satisfying every gate is necessary, not sufficient, and no gate may be waived to meet a date. No date has been approved, so none is given.
| Condition | Status | Requirement |
|---|---|---|
| Implementation complete | Not met | Every instruction in the spec is implemented, the glue is exercised against a real runtime (local validator or program-test), and no TODO remains in scope. |
| Local tests pass | Not met | cargo test, clippy, the mutation check and the TypeScript suite pass on the exact commit. |
| Security review complete | Not met | An internal review of the spec's questions is recorded and all findings closed, before the independent audit begins. |
| Independent audit complete | Not met | A written report from an independent auditor naming the exact commit and binary hash, with no open high or critical finding. |
| Exact source-to-binary build reproduced | Not met | Two independent builds of the audited commit produce byte-identical binaries that equal the deployed bytes. |
| Deployed program identity verified | Not met | Program id, deployed bytes and embedded constants match the deployment record, checked from chain data. |
| Upgrade authority verified | Not met | The program-data upgrade-authority field was read from the network and is empty (ADR-014), by two independent readers. |
| Devnet rehearsal completed twice | Not met | The rehearsal plan was run in full two times with every pass criterion met and recorded. |
| Independent operator reproduces the result | Not met | An operator who did not run the rehearsal reproduced it from the written plan alone with identical results. |
| BAAL mint verified | Not met | The production mint exists, is a classic 9-decimal mint with mint and freeze authority removed, supply 1,000,000,000 BAAL, address equal to the compiled constant. |
| Schedule accounts verified | Not met | Every schedule account and vault matches the approved schedule file, recomputed independently. |
| Treasury and signers approved | Not met | The creation-authority multisig exists with the approved threshold and at least three independent, verified signers. |
| Legal approval obtained | Not met | Written legal approval for the structure, the disclosures and the beneficiary terms. |
| Public documentation matches implementation | Not met | Every public statement about the program (schedule, limits, upgrade status, audit status) is checked against the implementation and on-chain state. |
The seven separate events
Token generation and trading are different events. Public trading or liquidity is never evidence that the token supply was created, and creating a token does not create demand, value, liquidity or an exchange listing.
| Event | Status | Meaning |
|---|---|---|
| 1. Token generation (supply minted) | Not occurred | The fixed supply of 1,000,000,000 BAAL exists in a mint account and the mint authority is permanently revoked. |
| 2. Allocation and vesting initialization | Not occurred | Each allocation is held by its approved wallet role and every required vesting arrangement exists and is publicly verifiable. Blocked while vesting enforcement is OPEN. |
| 3. Public announcement | Not occurred | The project publishes the verified mint address and facts through its official channels. |
| 4. Liquidity creation | Not occurred | A market pool or order book is funded by a person, with its own disclosures. Not part of the TGE. |
| 5. Trading opening | Not occurred | Holders can swap BAAL on at least one venue. |
| 6. Market-data submission | Not occurred | Token information is submitted to third-party data aggregators, which decide independently whether to list it. |
| 7. Public product launch | Not occurred | A Baalvion product or service that uses BAAL is made available. None is promised. |
The TGE is the combination of events 1 and 2 plus technical readiness. Events 4 to 6 are not TGE prerequisites. These tables are generated from the project's own records, so a condition appears as met only when the record is changed with evidence.
BAAL Launch Waitlist: not open yet Read Tokenomics Read Documentation