BANK OF YAN · ROADMAP · 2026-09-09
One yen is a milestone.
Build what comes next.
Our ambition is a lasting Bank of Yan: a Japanese-rooted global community, useful tools and the resources to keep building. We are still at the beginning.
The community is the driving force.
As HyperEVM builders, we look to Hyperliquid as a reference for technical ambition and earning users’ confidence. We are an independent project with our own purpose, not affiliated with or endorsed by Hyperliquid.
Our team believes a strong community is the greatest long-term driving force: people who return, create, contribute ideas and hold us accountable. Our responsibility is to earn that participation through useful work and visible progress.
Priorities, not promised dates. Community and maintenance continue throughout. Future steps depend on evidence, resources and review; the ¥1 ambition is not an execution gate.
AVAILABLE PARTICIPATION
More than a future promise.
Staking and snapshot voting are already implemented. They give participants access to funded YAN rewards and a defined role in project decisions. Holding YAN in a wallet alone does not earn staking rewards or create voting weight.
Funded staking rewards
Rewards use deposited YAN, without minting. The scheduled annual payout is capped at 2M YAN and 6% of staked principal, and can fall as funding or total stake changes. Claim or compound explicitly.
After collection, the fee router sends 70% of the YAN it receives from the configured LP positions to the reward fund. This supports funding duration; it does not bypass the payout caps. WHYPE goes to treasury. Collection requires a transaction.
Unstaking has a 7-day wait; the requested amount stops earning rewards. Rewards are paid in YAN and do not guarantee a gain in yen or dollars. See staking for the current on-chain rate and funding.
View staking & current rate →A defined voice in decisions
Stakers can vote directly or delegate their voting weight. Passed listing-removal and restoration decisions can be executed on-chain after the notice period. Treasury proposals record community advice; they do not control the treasury wallet.
Making proposals requires delegate registration with a 1M YAN self-stake bond locked for 365 days. Ordinary voting does not require that bond. A proposal needs 20% participation, two-thirds support among For + Against and at least 1M YAN in support.
Early participation can be too small to pass proposals, and large stakes carry more weight. Governance is a participation mechanism, not a promise of equal influence or full community control.
View proposals & voting rules →The practical connection: participation can improve curation and accountability; collected LP YAN can replenish funded rewards. Neither voting nor staking creates external revenue by itself. There is no independent external audit, and these features do not remove token-price or smart-contract risk.
Live · ongoing work
Give people a reason to stay.
YAN’s token, website and community are live. Our continuing work is to improve the tools, resolve problems and build a culture people can make their own.
- Maintain the live tools and publish meaningful progress updates.
- Create Japanese-inspired art, monetary-history content and community activities.
- Make liquidity custody, treasury movements and spending understandable.
Explore YAN’s foundations →Execution conditions & limits
This work continues alongside later goals. Published tools and records are evidence of delivery; community size and market price are not completion criteria.
Next objective · not scheduled
Bring YAN to HyperCore.
Our next major technical objective is to connect the existing HyperEVM token to HyperCore through HIP-1, opening a path to native spot trading. Compatibility and funding still need to be established.
- Verify supply accounting, decimals and transfers in both directions using the exact proposed setup.
- Publish a deployment, liquidity and ongoing-operation budget before committing funds.
- Preserve the existing one-billion-token economic supply across both environments.
Why HyperEVM →Execution conditions & limits
Proceed only after a successful rehearsal and sufficient funding, while preserving operating reserves. The official HIP-1 auction currently has a 500 HYPE floor, before liquidity and other costs—well above the original 30 HYPE launch budget. No listing date is announced.
Future evaluation
Build the capacity to last.
Essential operating reserves come first. As resources grow, we intend to evaluate eligible tokenized assets, beginning with short-term government debt, as a possible source of treasury income.
- Assess legal eligibility, custody, redemption, liquidity and currency exposure.
- Publish exposure limits and an exit policy before any allocation.
- Keep commitments affordable during periods of low activity or investment losses.
Current treasury rules →Execution conditions & limits
No asset allocation is approved by this roadmap. Treasury income is uncertain. Government debt retains issuer and currency exposure; tokenization does not remove those dependencies.
Future proposal
Define how progress benefits holders.
We will compare ways to use realised net surplus after expenses, obligations and essential reserves. Existing staking rules remain separate from these future proposals.
- Compare buybacks, additional staking funding, liquidity support and legally feasible distributions.
- Explain who benefits, the trade-offs and how losses or zero surplus affect the mechanism.
- Publish a proposal and seek holder feedback before adopting a verifiable implementation.
Existing staking rules →Execution conditions & limits
No new payout or treasury claim is created here. A future mechanism needs explicit rules, legal review and funding. Existing immutable contracts cannot be changed by a roadmap or a vote; treasury votes remain advisory under the current structure.
Judge the work by its record.
The team will publish material progress, delays and changes of direction. This roadmap records our priorities as of 9 September 2026; it does not claim that future work has begun or passed verification.
Technical reference (checked 9 September 2026): Hyperliquid · HIP-1