We're studying seasons.
After Hot Wallet Rate, the next big question on the 369wallet roadmap is shape — not feature. We're exploring a season-based layer: themed chapters, limited rewards, and rotating drops sitting on top of the wallet's core experience. Nothing committed yet — but we want this on the record.
This is a roadmap note. Nothing here is a commitment — we're in study, not ship. We're publishing it because users have a right to know what we're thinking about, before it becomes a feature on a release calendar.
The question we're asking
369wallet is, structurally, a long-running surface — you open it on Tuesday, you'll open it on Saturday, and on the Tuesday after that. Most of what we ship behaves the same: it lands once and stays.
That has been the right default. But it leaves something on the table. There's no inherent rhythm, no narrative arc, no reason this month should feel any different from last month. The wallet has features. It doesn't have chapters.
What we mean by "seasons"
A season, as we're modeling it internally, is a defined window — measured in weeks, not days, not months — during which a curated set of rewards, drops, and themed activities sits on top of the wallet's regular features. When the season ends, that set retires. The next season opens with its own theme, its own rewards, and its own surface.
Concretely, we're studying:
- Themed reward curves. Different in-wallet actions weighted differently per season. One season might favor predict.fun positions; the next might favor staking or cross-chain swaps. The same user behavior earns differently depending on which chapter is open.
- Limited drops. Items, allocations, allowlists, or in-wallet status that only exist during a given season. Once retired, retired.
- Recurring rituals. Lightweight in-wallet activities that show up exclusively in-season — quests, leaderboards, milestones, claim windows.
- Inter-season scaffolding. Continuity that lets long-term users carry signal across seasons without flattening the freshness of a new chapter for new users.
How seasons would relate to Hot Wallet Rate
Hot Wallet Rate, announced last week, is the always-on accrual layer — it pays out to active users continuously, regardless of season. Seasons would sit one layer above: a periodic, themed multiplier and reward layer. You don't have to opt into seasons to earn Rate. You opt into seasons because you want the season-specific upside.
Both layers are designed to compose. Neither replaces the other.
Why we like the shape
Three reasons keep this concept on the table:
- Cadence creates anticipation. A predictable opening-closing rhythm gives users something to plan around. Anticipation is, quietly, one of the strongest forms of engagement we can design for.
- Scarcity is honest. A season that genuinely ends — with rewards that genuinely retire — is a clearer promise than an open-ended program that quietly inflates over time. We'd rather make small, sharply-edged commitments and keep them.
- It gives newcomers a clean entry. A new user joining mid-season-three doesn't feel like they missed the train. The next season opens for everyone.
What's still being studied
Most of it, honestly. We're not ready to share concrete answers on:
- Season length, opening cadence, and overlap rules.
- The reward and drop economy — what's earnable, what's purchasable, what's distributed.
- How seasons interact with cross-chain activity and partner integrations.
- The narrative direction of the first season.
These are the questions the product and engineering teams are working through. We will publish progress as decisions land, with the same level of detail we've used for every other roadmap note in this series.
The reason we're saying anything now
Two reasons. First, this work is starting to influence design decisions on adjacent features — and it would be wrong to ship them without acknowledging where they're pointed. Second, the most useful feedback we get on big shape-changes is the kind that arrives early, not the kind that arrives the week of release.
If you have a sharp opinion on how seasons should — or shouldn't — work, our preferred channel is @369Wallet. The team reads it.
"We don't want to add features. We want to add chapters." — 369wallet team
— The 369wallet product & engineering team