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.
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.
- SDK v0.47, Tendermint 0.37
- IBC v5/6, ICA v3 (optional)
- Using Skip's MEV Tendermint fork by default
- Native Liquid Staking
- IBCTest (optional)
- Faster Block times (with respect to oracle)
- Improving the Nakamoto Coefficient
Links:
The V12 update is Juno's largest update, bringing many new features for developers, users, and relayers.
- x/FeeShare (CosmWasm)
- x/TokenFactory
- x/Oracle
- x/GlobalFee
- x/inter-tx
- More ICA Messages
- Governance Spam Prevention
- x/wasmd 30
- x/ibc V4
- x/ibc-fees
V12 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.
The oracle brings the ability to query external data sources, such as the price of JUNO or ATOM. This is a powerful tool for De-Fi applications on Juno like trading games, perpetual swaps, and more.
Governance can now also deny and allow IBC-based denominations (tokens) via GlobalFee, bringing massive User Experience improvements with it. First, all nodes will be required to accept the minimum fee. Given this, a user can query the required fee for gas, improving front-end UX. Second, it reduces operational costs for Validators and Relayers by whitelisting select IBC and ORACLE transactions. Now, these transactions will be free and take the strain off all parties.
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.
Juno is now a controller chain via inter-tx, which will allow it to control accounts on other chains. HERE.