Post-quantum encrypted key storage. Solana’s on-chain signatures remain Ed25519. Launching and automatic fee distribution are not active yet.
EB / CREATOR SYSTEM 01
YOUR TOKEN ↗
⋈
entangled bitYOUR BUNKERKEYS / OFFLINE
01 / THE MISSIONCREATION FUNDS CUSTODY
One launch. An ongoing source of fuel.
01 / CREATE
You create the token.
Define your token and choose your own offline vault as the creator-fee destination.
02 / LAUNCH
The curve goes live.
The planned launch uses pump.fun’s bonding curve, approved by your creator wallet.
03 / ACCRUE
Trading generates fees.
Eligible trades accrue creator fees under Pump’s current fee rules, on the curve and after graduation.
04 / AUTO-FUND
Your bunker receives.
A planned background service triggers on-chain distributions to your configured vault. Its private key stays offline.
Automatic means recurring on-chain distributions, not a separate vault deposit after every trade. Network availability, minimum balances, and transaction costs affect timing. No trading volume or fee income is guaranteed.
02 / PREPARE YOUR LAUNCHLOCAL DRAFTS / AVAILABLE NOW
Start with a plan. Launch when it’s ready.
Name your token, connect a public vault account, and preview its automatic fee route. Your draft stays in this browser unless you export it. No token is created and no funds move.
03 / BUILT WITH CLEAR BOUNDARIESSELF-CUSTODY FIRST
Your vault owns the fees.
The initial design assigns 100% of creator fees to your verified public vault address. Entangled coordinates the launch and distribution service; the creator keeps the keys. The planned worker pays its own transaction costs and cannot redirect the configured recipient.
Quantum resistance, precisely.
Your encrypted key backup uses ML-KEM-768, HKDF-SHA256, and AES-256-GCM. Your USB stores the backup; funds stay on Solana. This does not make Pump tokens, trading, or Ed25519 withdrawals quantum-resistant.
The public launch planner works today. Token deployment, permanent fee-route approval, automatic distributions, and live fee history are planned. Your existing vault tools stay free; Plus monitoring remains a separate future service.
What needs to happen before launches go live?
The Pump integration needs verified transaction builders, an on-chain recipient check, simulation and wallet approval, and tested handling of partial launches. The background distributor needs durable job records, confirmation tracking, a funded gas budget, and a completed security review. There is no launch date yet.
Can I change the vault later?
Pump’s documented fee-sharing flow finalizes the recipient list and revokes further admin updates. The launch flow must show the full destination and its fingerprint before you approve. A saved local draft can be edited; an on-chain fee configuration has different rules.
Does Entangled create every token under one shared wallet?
The planned flow uses each creator’s own approving wallet and a separate vault recipient for that token. Entangled provides the launch experience and automatic distribution service. It does not need a shared wallet holding every creator’s revenue.