This document contains the roadmap for the Juno project. It is a living document and will be updated as the project progresses. For the most update to date information, please follow the Notion and tracking issue links in each section.
- Long term Tracking Issue
- SDK v0.47, Tendermint 0.37
- IBC v5/6, ICA v3 (optional)
- Native Liquid Staking
- Improving the Nakamoto Coefficient
- Wasm based oracle
This upgrade focuses entirely on moving Juno's block times from 6 seconds to 3 seconds.
- 3 second block times (from 6 seconds)
This update will focus more on upgrading the base layer of the Juno stack, bringing new features and pushing us to the latest versions of the software.
- IBC-Hooks
- CosmWasm v0.31
- WasmVM v1.2.1
- Global Minimum Fees (governance controlled)
- Feeless IBC Relaying
- TokenFactory: burnFrom, burnTo, ForceTransfer
- Interchain test
- Using Skip's MEV Tendermint fork by default
Links:
The V13 update is Juno's largest update, bringing many new features for developers, users, and relayers.
- x/FeeShare (CosmWasm)
- x/TokenFactory
- Packet Forward Middleware
- x/GlobalFee
- More ICA Messages
- Governance Spam Prevention
- x/wasmd 30
- x/ibc V4
- x/ibc-fees
V13 is targeted at developers with relayer and user experience improvements as well.
FeeShare will allow contract developers to receive 50% of gas fees executed on their contract. Providing an alternative income source for new business use cases. This also enhances current business models to support developers & grow the ecosystem further.
The TokenFactory will make developers' lives easier, and also make querying users' DAO tokens via MintScan and Keplr possible. By default, CosmWasm smart contracts accept native tokens. However, the only initial native tokens are the staking demons for most chains. This gives the ability for a user to create their token, and manage the tokenomics behind it. Then accept it just as they would any other denomination via the standard x/bank module.
Speaking of relayers, IBCFees now helps to fund those who relayer your packets! In the above paragraph, we mention how IBC transfers are feeless for relayers. Fees can still be sent with these packets and bring some income for relayers, thus maintaining public goods infrastructure. The relayers still have to pay the fee on the other chain's token, but this is a positive step in the right direction for variables we can control.