- JRNY CLUB is launching $JRNY with a community-first approach, distributing tokens across both its own ecosystem and major NFT collections to create a shared Web3 network.
- Core allocations prioritize JRNY CLUB, FUKU, and XOLO holders, while external collections will receive 69 $JRNY per NFT, with distribution scaling based on supply.
- The token is built around real utility, featuring a declining tax model, burn mechanics, and upcoming staking and liquidity rewards to drive long-term participation
JRNY CLUB is doing something a little different with its upcoming $JRNY token launch. It’s not keeping it locked inside its own ecosystem. Instead, it’s opening the doors and letting in a wide range of major NFT communities from across Web3.
This turns $JRNY from just another ecosystem token into something more like a shared layer, a way for different communities to plug into the same network from day one. Not just holders on the inside, but people across the space.
Core Distribution: The JRNY Ecosystem
Most of the token supply is still going to the core JRNY ecosystem, which makes sense. These are the communities that have been there building and participating from the start.
Current allocations look like this:
- JRNY CLUB NFTs: 6,969 $JRNY per NFT
- FUKU: 6,969 $JRNY per NFT
- Planet XOLO Villagers: 2,069 $JRNY per NFT
- XOLO Crates: 420 $JRNY per NFT
- JRNY on Cardano: 20,000 $JRNY per NFT
One important detail, JRNY CLUB NFTs are the only ones getting a staking pool, tying extra rewards to long-term participation. That’s where the deeper utility starts to show up. For more information on collection details, join the JRNY CLUB Discord HERE
Built Around Use, Not Just Hype
At the core of it, the token design leans more toward usage than speculation. Instead of a typical launch, JRNY CLUB is rolling out a declining tax model, starting high to discourage early sniping, then dropping fairly quickly to a steady 5% swap tax. That final tax isn’t just sitting there either, it feeds into burn mechanics tied to both the token and NFTs over time.
They’re also looking at adding liquidity mining and staking shortly after launch, which means users can earn a share of trading fees alongside $JRNY rewards. It’s not perfect, still evolving, but the idea is to build utility directly into the system instead of bolting it on later.
Expanding Beyond: External NFT Claims
Here’s where it gets interesting. JRNY CLUB is extending claims to a long list of external NFT collections, not something you usually see done at this scale.
Each NFT from these collections will receive 69 $JRNY per NFT
And the list is pretty stacked:
CryptoPunks, Meebits, BAYC, Pudgy Penguins, Azuki, Good Vibes CLUB, HV-MTL, Moonbirds, Doodles, Quirkies, VeeFriends, Nakamigos, World of Women, Mocaverse, Rektguy, NeoTokyo (S1 & S2), Chimpers, Captainz, CyberKongz, Kodas, Normies, Gobs On Ape, Gs on Ape, Zards, Nouns, Final Bosu, BEARISH, fwogs, My Pet Hooligan, Milady, Mars Cats Voyage, Goblintown
There’s no fixed cap per collection either. Allocation scales with how many NFTs exist, keeping things proportional while maintaining that same per-NFT claim.
A More Connected Token Model
Zooming out a bit, the strategy here is pretty clear. This isn’t just about rewarding one community, it’s about connecting multiple ones.
By spreading $JRNY across both internal and external collections, JRNY CLUB is trying to build a network where different NFT holders can all participate in the same ecosystem. Tools, content, metaverse experiences, all tied together through one token.
Add in burn mechanics, staking, and future integrations, and it starts to look less like a passive asset and more like something people actually use.
What Comes Next
The token contract is nearing completion, with audits and final details still being worked through. More information around claim mechanics, utility, and integrations is expected soon.
But the direction is already pretty clear.
$JRNY isn’t being built just for JRNY CLUB. It’s being positioned as something bigger, a token that tries to connect communities across Web3, not just sit inside one.
