With the completion of the original @cosmos whitepaper (yes you read that right, a crypto project actually completed its whitepaper) a new roadmap for the Gaia (Cosmos Hub) is in process from @interchain_io under @shahankhatch in collaboration with core devs.

🧵👇⚛️🚀👨‍🚀👩‍🚀🧵
TL;DR Gaia is planning to pull in modules from other SDK chains as well as develop new ones.

AMM! Derivatives! CNS! BTC/ETH interop! Cross Chain Accounts and Staking! WOW! Strap in and let's take a ride through #ATOM2021, its going to be a great year! Lets take them one by one
An Automated Market Maker, built by @B__Harvest is coming to the Hub. Pools! Swaps! It will likely be ready for deployment in mid-Feb. Check out the demo below!

swap.bharvest.io
Bitcoin Interop is on the table. No team is currently working full-time on it but there is great prior work by the Nomic and Summa One to draw from. If you are looking for a good @cosmos project you can get funded to do this one.

github.com/summa-tx/relay…
github.com/nomic-io/nomic
@ethereum interop is coming via @AltheaNetwork's Peggy implementation. @getsomm_ plans to deploy this on a separate chain sometime in February. After a period of proving, expect to see it on the Hub this year.

FWIW This is what I'm working on right now.

github.com/althea-net/peg…
Interchain Accounts is a feature enabled by IBC. It allows one chain's validator set to control an account on another chain. This code will be ready after an audit sometime in the next month.

@billyrennekamp breaks down what it means for the hub below

forum.cosmos.network/t/cosmos-hub-a…
Cross Chain Staking (shared security @Polkadot) is currently being worked on by @informalinc and @Tendermint_Core. It is currently scheduled to be complete in Q4 with a deliverable to help new zones bootstrap liquidity in Q3. Expect to hear a lot more on this in the next months
Staking Derivatives, another extension of @cosmos PoS model scheduled for this year. They help $ATOM be a better collateral for DeFi. Completion in Q4. Prior work by @B__Harvest and @ChorusOne set to inform @iqlusioninc and @interchain_io on their final implementation.
And finally, Gaia will deploy a Chain Naming Service (CNS) to prevent collision in the Interchain naming space. Think DNS for IBC. I've done some prior work on this, but the @tendermint_team under @zcpeng will pick up development. Expected in Q2.

github.com/jackzampolin/c…
Expect these features to make their way to the hub as they ship. I anticipate roughly quarterly major upgrades (#stargate in Jan, then roughly April, July and October) facilitated by the upgrade module.
The vision of Gaia has always been as a continually evolving system, pulling in the best modules from the broader ecosystem. Many blockchains have tried this, but failed. The @cosmos community is making it a reality this year.
Final note: this is from where I sit and final roadmap may vary.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jack Zampolin

Jack Zampolin Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jack_zampolin

30 Dec 20
A thread on $DOT, $ATOM, @cosmos, and @polkadot
Both projects are predicated on the core idea that in order to have ETH like programmability/interoperability, applications need to have separate chains, preventing congestion on the overall network.
The difference comes in how they to achieve this. @polkadot's model is that all interactions between separate chains will be intermediated through a "relay chain" via a protocol called XCMP.
Read 10 tweets
9 Apr 20
A quick thread on the primitives that make up #ibc. There are four major ones:
1. Clients
2. Connections
3. Channels
4. Packets

🚀👨‍🚀🌔👩‍🚀👇
In IBC, a "Client" is an instance of a lite client for another chain that is committed to state. This piece is fundamental to the function of #ibc. All other primitives rely on clients to prove their data was included in the counterparty chain.

github.com/cosmos/ics/tre…
Once we have a client to prove data, we create a "Connection". This requires 4 transactions, 2 on each chain. The clients are updated throughout to prove the newly committed state on both chains.

github.com/cosmos/ics/tre…
Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!