Official contact
The public email address will be published here.
Project information
Bitlurium is taking shape.
The website and X account are live. The private Bitlurium codebase is now in creation. No official token, sale, or wallet connection is active.
View roadmapCurrent status
Private code creation
Official website and X account: active. The codebase is being assembled privately for Bitlurium.
No official token, contract address, sale, or purchase link has been released. Any claim otherwise is unofficial.
Official channels
Contact and community.
@Bitlurium
Official Bitlurium account.
In creation
The official Telegram channel will be linked here once created.
Bitlurium roadmap
A verifiable path from design to transparency.
Each phase is activated only when its verifiable prerequisite is complete. The current focus is protocol design and local technical validation.
Project presence & identity
The visual system, public website and X presence establish a single reference point for project updates.
- Public information site online
- Recognisable visual identity
- Community channels prepared progressively
Protocol architecture
The technical candidate defines a capped supply model, controlled allocations and rules intended to reduce discretionary control.
- Fixed-supply candidate design
- No post-deployment minting target
- Burn, vesting and rewards logic documented
Local technical validation
The contract candidate is compiled and exercised locally before any public network action is considered.
- Integrated contract components
- Scenario testing for refunds and controls
- Configuration template prepared for independent review
Independent security review
A third-party specialist must assess the final code and configuration. No audit outcome is assumed or promised.
- Access-control and fund-flow review
- Findings remediated and retested
- Scope and report shared only when published
Deployment readiness
Before deployment, every chain-specific value must be independently checked and recorded in a public deployment manifest.
- Network, USDC and router verification
- Three designated CEX-vault signers
- Final parameter and address checklist
Public deployment
Addresses, verified source code and launch information are released only after pre-launch checks are complete.
- Public contract reference published once verified
- Clear distinction between verified and unverified links
- No price or market outcome promises
On-chain transparency & lifecycle
Post-deployment actions should be independently visible on-chain, with progress reported through evidence rather than marketing claims.
- Publicly verifiable contract events
- Scheduled burn interactions when eligible
- Utility and community features only when ready
No date, token sale, audit outcome, price, liquidity level or market result is promised on this page.