Official Public Record
AKSU Launch & Tokenomics Record
The canonical public record of AKSU token parameters, constitutional allocations, Founder vesting, Genesis policy, launch liquidity, Treasury accounting, deployment state, and verification fields.
- Version
- 1.0
- Status
- Active
- Article type
- TOKENOMICS
- Publication mode
- Full document
- Identifier
- AKSU-LAUNCH-TOKENOMICS-RECORD-V1
- Adoption date
- Not applicable
- Effective date
- Not applicable
- Last updated
- Not recorded
- Issuing authority
- Aksumite, by Founder Approval
- Scope
- Aksumite institutional scope
Purpose
This Record preserves Founder-approved AKSU policy separately from deployment evidence. It does not represent pending mainnet identifiers, funding, balances, transactions, or verification timestamps as complete.
Current launch state: PREPARING. Policy and build artifacts are in preparation. No mainnet deployment, funding, or on-chain verification is claimed.
Definitions
- “Allocation”
- A constitutional accounting category. An allocation is not, by itself, circulating supply, Treasury ownership, liquidity deployment, or LP-position custody.
- “Verified evidence”
- A mainnet identifier, transaction, authority state, balance, or timestamp independently checked before publication as official.
- “Final quote contribution”
- The actual quote-side amount locked before mainnet pool creation. It may exceed, but may not fall below, the approved minimum.
Network and Token Parameters
Canonical parameters
- (1)Network: Solana mainnet-beta.
- (2)Token program: Original SPL Token Program.
- (3)Maximum supply: 100,000,000,000 AKSU.
- (4)Decimals: 6.
- (5)Official mint: Pending deployment.
- (6)Creation transaction: Pending deployment.
- (7)Metadata URI: Pending deployment.
- (8)Metadata hash: Pending deployment.
- (9)Mint authority: Pending deployment.
- (10)Freeze authority: Pending deployment.
- (11)Verified at: Pending verification.
Policy and deployment distinction
Approved policy is not evidence of deployment. Mint, transaction, metadata, authority, and verification fields remain pending until verified mainnet evidence is published.
Citation: AKSU Launch & Tokenomics Record, § 1.02 (1.0)Constitutional Allocation Accounting
Maximum supply allocation
The maximum supply is 100,000,000,000 AKSU. The six constitutional allocations total 100 percent of maximum supply.
- (1)Founder: 10,000,000,000 AKSU (10%). Deployment state: FOUNDER APPROVED TRUSTED THIRD PARTY NOT DEPLOYED.
- (2)Genesis: 2,000,000,000 AKSU. Deployment state: PENDING DEPLOYMENT.
- (3)Launch Liquidity: 10,000,000,000 AKSU. Deployment state: PENDING DEPLOYMENT.
- (4)Operational Treasury: 10,000,000,000 AKSU. Deployment state: PENDING DEPLOYMENT.
- (5)Strategic Treasury: 20,000,000,000 AKSU. Deployment state: PENDING DEPLOYMENT.
- (6)Locked Milestone Treasury: 48,000,000,000 AKSU. Deployment state: PENDING DEPLOYMENT.
Accounting boundary
Founder allocation, Genesis, launch liquidity, Operational Treasury, Strategic Treasury, and Locked Milestone Treasury remain constitutionally separate. Allocation is not circulation, and LP-position ownership does not convert Liquidity Allocation into Treasury.
Citation: AKSU Launch & Tokenomics Record, § 2.02 (1.0)Founder Vesting and Genesis
Founder vesting policy
- (1)Provider: Streamflow.
- (2)Allocation: 10,000,000,000 AKSU (10%).
- (3)Schedule: 5 calendar years · daily periods.
- (4)Start rule: 00:00 UTC on the calendar day after verified mainnet launch.
- (5)Program ID: strmRqUCoQUgGUan5YhzUZa6KqdzwX5L6FpUxfmKg5m.
- (6)Configuration hash: 0394d2bb36b50dabaa5459efe5f8b59bcaefec65ac868c32e1c2a21471b1aacf.
- (7)Vesting account: Pending deployment.
- (8)Beneficiary: Pending deployment.
Genesis policy
The Genesis allocation is 2,000,000,000 AKSU, equal to 2 percent of maximum supply. Day-one Genesis circulation is zero. Account creation alone does not establish eligibility. Any later distribution requires a separately approved mechanism and public record.
Citation: AKSU Launch & Tokenomics Record, § 3.02 (1.0)Launch Liquidity
Founder-approved launch allocation
The full canonical Liquidity Allocation is intended for initial liquidity deployment. No AKSU remains undeployed within the Liquidity Allocation after the approved initial deployment.
- (1)Canonical allocation: 10,000,000,000 AKSU.
- (2)Approved launch amount: 10,000,000,000 AKSU (100% of allocation).
- (3)Minimum quote-side funding: $3,000 USD equivalent.
- (4)Final USD-equivalent funding: Pending final ceremony lock · may exceed minimum.
- (5)Initial price rule: Final quote-side USD value ÷ 10,000,000,000 AKSU.
- (6)Final quote asset: Pending selection.
- (7)Final quote quantity: Pending final ceremony lock.
- (8)Initial token-per-quote ratio: Pending pool creation.
- (9)Initial AKSU price: Pending pool creation.
- (10)Implied fully diluted valuation: Pending pool creation.
Mainnet creation record
- (1)Venue: Pending selection.
- (2)Pool address: Pending deployment.
- (3)Creation transaction: Pending deployment.
- (4)LP ownership or custody: Pending final custody record.
- (5)Verification timestamp: Pending verification.
Treasury Accounting and Chain Evidence
Treasury accounting
Operational Treasury, Strategic Treasury, and Locked Milestone Treasury are recorded independently from the Liquidity Allocation. Each allocation address, published balance, and verification timestamp remains pending until verified deployment evidence exists.
Citation: AKSU Launch & Tokenomics Record, § 5.01 (1.0)Required verified evidence
The public evidence record supports the official mint, creation transaction, metadata, mint and freeze authority states, Founder vesting account, Treasury and allocation addresses, liquidity pool, creation transaction, LP custody, explorer links, balances, and verification timestamps. Prelaunch null values remain pending and are not official chain claims.
Citation: AKSU Launch & Tokenomics Record, § 5.02 (1.0)