Document status: Pre-Mainnet / Infrastructure Build
Network: Solana
Token standard: SPL Token
Symbol: COH
Fixed supply target: 1,000,000,000 COH
Decimals: 9
Token-level tax: 0%
Canonical website: https://cohibameme.site
Source repository: https://github.com/Roberhood314/COHIBA
Official X: https://x.com/hunhkcgy
This document separates VERIFIED facts, PLANNED architecture, and POST-MAINNET data. No Mainnet mint, market pair, liquidity, holder count, price, market capitalization, or trading volume is treated as official until independently verifiable.
COHIBA is a Solana-based community and cultural crypto project centered on human agency in the age of artificial intelligence. Its core narrative is “Fear the Machine. Defend the Human.”
The project is not positioned as an anti-AI protocol. Its purpose is to create an internet-native cultural asset whose technical design emphasizes transparent issuance, public verification, fixed-supply controls, machine-readable project data, and observable market evidence.
The project is currently in PRE-MAINNET state. The engineering objective is to complete all reversible infrastructure, verification, observability, security, documentation and market-data plumbing before the irreversible Mainnet release.
Contains non-secret data only: project identity, token specification, public wallet addresses, block/slot data, mint address after launch, explorer URLs and market data after verification.
Contains launch orchestration logic and read-only public APIs.
Contains SYSTEM_WALLET_SECRET_JSON, COHIBA_MAINNET_LAUNCH_KEY and infrastructure credentials. These values must never be committed to GitHub, returned by public APIs, embedded in frontend JavaScript, or placed in listing forms.
Solana becomes the canonical post-launch source of truth for mint existence, supply, balances, authority state and transaction signatures.
| Field | Value |
|---|---|
| Name | COHIBA |
| Symbol | COH |
| Network | Solana |
| Standard | SPL Token |
| Total supply | 1,000,000,000 COH |
| Max supply | 1,000,000,000 COH |
| Decimals | 9 |
| Base units | 1,000,000,000,000,000,000 |
| Token-level tax | 0% |
| Post-launch mint authority | null |
| Post-launch freeze authority | null |
| Metadata standard | Metaplex Fungible Token |
| Metadata target | immutable |
pTEH7pYratL14VFPQ9i5JMvPYDCpCQ773cHQZ3DdW3t
| Allocation | % | COH |
|---|---|---|
| Public launch & liquidity | 75% | 750,000,000 |
| Community | 10% | 100,000,000 |
| Marketing | 5% | 50,000,000 |
| Development | 5% | 50,000,000 |
| Treasury | 3% | 30,000,000 |
| Team | 2% | 20,000,000 |
This is a planning model, not a circulating-supply claim. Final circulating supply must be derived from actual post-launch wallet balances, locks, vesting and liquidity positions.
PRE_MAINNET → MINT_CREATED → ATA_READY → SUPPLY_MINTED → METADATA_READY → FREEZE_REVOKED → MINT_REVOKED → LOCKED_VERIFIED
Core invariants:
Mainnet remains disabled during infrastructure construction.
Required release conditions:
Launch state is stored on persistent Railway volume storage so container restarts and browser resets cannot cause a duplicate mint.
Canonical endpoint: https://cohibameme.site/token-metadata.json
Metadata includes name, symbol, description, image, official website, network, supply, decimals and token-tax specification.
Dashboard: https://cohibameme.site/blockchain.html
APIs:
Published fields include network, slot, block height, epoch, Solana core version, mint, supply, decimals, authorities, destination account/balance, largest token accounts, recent signatures, explorer links and verification booleans.
Dashboard: https://cohibameme.site/infrastructure.html
API: https://cohibameme.site/api/infra-readiness
Readiness gates cover website, verification, blockchain dashboard, token metadata, machine-readable project/market data, Devnet verification, signer configuration, Mainnet RPC, Mainnet safety lock and non-launch state.
Canonical file: https://cohibameme.site/project-data.json
Canonical file: https://cohibameme.site/market-data.json
Pre-market values remain null. Expected POST-MAINNET fields include venue, pair, pool address, market URL, price, liquidity, 24h volume, holders, circulating supply, source and timestamp.
After verified Mainnet launch, the mint will be linked through Solscan, Solana Explorer, the verification page, token page, blockchain dashboard and listing evidence pack.
Candidate first venue: Raydium.
Candidate pairs: COH/SOL and COH/USDC.
A market is considered live only when a pool exists on-chain, assets are actually deposited, direct pair URL is public, independent swaps can occur and liquidity is observable.
Relevant measurements:
No LP lock/burn claim may be made without cryptographic verification.
Prohibited project practices:
Only independently observable market activity may be published as evidence.
Total supply is deterministic by design. Circulating supply is not assumed from total supply.
Post-launch circulating supply must account for treasury, team, development, marketing, liquidity positions, locked/vested balances and non-circulating reserves.
Launch stops before unverified irreversible transitions.
Launch remains blocked.
Readiness fails.
Persistent state allows recovery from the last successful state rather than minting again.
Launch aborts.
Launch aborts before authority revocation.
Hard failure requiring operator investigation.
Operational telemetry should cover deployment health, API health, RPC connectivity, signer balance threshold, launch transitions, verification failures, HTTP errors, latency, volume availability and public endpoint availability.
Secrets must never enter logs.
Freeze application changes, verify production commit, metadata, signer address, funding, RPC and safety controls, then capture a readiness snapshot.
Explicit owner approval, enable Mainnet gate, execute guarded launch, validate every transition.
Verify mint independently, supply and authorities, capture transactions, publish explorer URLs, disable launch path after completion, update project data, Whitepaper status and listing evidence.
COHIBA is primarily a cultural/community cryptoasset. Product/market fit is intended at the intersection of AI-era cultural anxiety, internet meme distribution, human-first identity, transparent token engineering and verifiable project operations.
COHIBA does not claim novel consensus or cryptography. Engineering differentiation focuses on lifecycle states, public readiness APIs, automated blockchain evidence, machine-readable transparency and clear separation of planned vs verified market data.
Current governance is founder-led. No decentralized-governance claim is made.
Post-launch transparency should publish category wallet, amount, percentage, lock/vesting status and unlock schedule where applicable.
Risks include extreme volatility, total loss of value, liquidity failure, wallet compromise, infrastructure failure, RPC outages, Solana incidents, integration risk, third-party manipulation, regulatory change, brand disputes, community attrition and execution failure.
COHIBA provides no guarantee of price, returns, exchange listing, liquidity, adoption or profitability.
Documentation is technical and informational, not legal, tax or investment advice. Users are responsible for local compliance.
COHIBA is independent and does not claim affiliation with unrelated companies, cigar manufacturers or trademark owners.
Brand, website, repository, token architecture, security controls.
Devnet issuance, supply verification, authority-revocation testing.
Blockchain API, infrastructure API, Whitepaper, machine-readable data, listing evidence, monitoring and release runbook.
Fund signer, authorize release, mint fixed supply, verify, revoke authorities, publish explorer evidence.
Create real liquidity pool, publish pair, measure organic market activity.
CMC/CoinGecko/market-data submissions using live evidence.
Continuous development, community, transparency updates and ecosystem participation.
Material changes to supply, authority design, wallet allocation, market structure, governance or security architecture require a version increment, dated changelog, Git commit, website update and clear explanation.
Mainnet remains the final irreversible operation.
Required final gate:
Only then should Mainnet minting occur.