BUILD.
RELEASE.
EXPAND.

A 3D gallery environment is live as a public-facing component of the ecosystem. Intended as a virtual space where NFT artworks can be showcased and, where applicable, made accessible for acquisition.

A custom transfer interface helps move $21K between wallets, including cases where token visibility may not be immediate in standard wallet interfaces. Users remain responsible for independently verifying destination addresses, wallet compatibility, and transaction conditions before use.

A lightweight experimental game live inside the ecosystem. Wallet-connected, with arcade-style progression: shoot rug pullers, ghost devs, and shitcoin mutants — avoid BTC, SOL, ETH. Skill unlocks maps and gear. $21K token holders get progression bonuses. Leaderboard stored on-chain via GitHub. Scope, mechanics, and release format may evolve.

A messaging system is currently in active beta testing. It allows $21K token holders to send end-to-end encrypted messages directly between wallets — no email, no phone number, no account. The wallet is the identity.

Technical architecture: NaCl box encryption (X25519 / XSalsa20 / Poly1305), messaging keypair generated and stored locally in-browser, messages stored on encrypted servers, small SOL service fee per message sent directly to the project wallet.

Access is gated: a minimum of 1 $21K token is required to connect. Terms of Use are signed cryptographically via wallet signature before access is granted.

A dedicated OTC system has been developed and remains available as internal project code. Its public deployment is currently deferred: current priority is directing resources toward stronger liquidity conditions rather than activating this branch immediately.

Following successful beta testing, 21K Mail is planned for broader public release to all $21K token holders. The public launch phase will include improved onboarding, clearer UX, and potentially integration of permanent Arweave storage to replace current server-side storage. Fee model and access conditions may evolve.

The immediate phase is focused on releasing, stabilizing, and showcasing what has already been built. Short-term efforts prioritize public visibility, clearer presentation of available tools, and incremental ecosystem polish rather than unnecessary expansion.

The next growth phase is intended to progressively open the ecosystem to partnerships and active contributors — artists, developers, and community members who want to participate in code, creative direction, or initiative building.

The long-term vision is to move toward a more community-driven model: continued support, building, and technical contribution remain possible, but the broader direction of the ecosystem is intended to become less dependent on a single public operator and increasingly shaped by the wider community.