Testinginprod
@tip_cosmos
Followers
64
Following
66
Media
0
Statuses
69
An article about the status of the cosmos ecosystem from a dev PoV, starting from CosmWasm. More to come around the SDK + IBC + all else:
medium.com
The status of Cosmos Development: CosmWasm TLDR: CosmWasm is a framework that, aside from allowing the addition of functionality without requiring upgrades, offers limited additional value. Creating …
1
1
11
I am so happy that I am seeing so many chains using the collections API ç_ç
0
0
1
Why instead of allowing direct contract calls we are still piling up on a design that does not make any sense and does not offer anything security wise that justifies the headaches it brings?
Got a slick CosmWasm 2 trick for you!⚡️ Use the CosmWasm 2 payload field to pass data via the message into the reply entry point. Say goodbye to: 1 Store to DB 2 Read from DB 3 Delete from DB 4 Risking overrides or double delete in complex compositions Check it out:
0
0
1
this is a fundamental problem of the AMM model being used and not of the liquidity. there's difference between slippage and spread. and if dexes were orderbooks (or highly precise CL pools), an MM could quote you better prices with much less liquidity.
@RandomCTGuy people pretend liquidity is this binary thing. that's the wrong framing. if arbitrum and base had their liquidity combined, users would experience half the slippage that they do today. that's a strict improvement that must exist, status quo is severely degraded
0
0
0
Module building is too verbose. Too much protobuf. A lot of components are not coherent with each other. But it's improving...
#Cosmos devs, if you were going to rebuild the Cosmos SDK from scratch, what would you change?
0
0
1
If you're using collections to handle your modules state (I hope you are!) you should prefer using "Walk" over "Iterate" when ranging state.
0
1
1
Imho almost all the infra currently being built in cosmos is useless. And it will find no use case. Combined tvl lower than top 20 eth protocol. Successful chains exist as independent silos. Solve this, no point in focusing in how to inflate unused block space even more.
6
0
11
With these changes, bank assets could be backed by cw contracts, enabling programmable denoms and unifying cw20 with bank coins across Cosmos chains.
1
0
2
The next version of the bank module will support arbitrary asset types with customizable transfer mechanisms, giving developers more flexibility. People will be able to implement custom ERC20 like denoms! And mint coins of different types as they need.
1
0
1
Challenges with the current bank module: Its transfer semantics are inflexible, often requiring developers to ask for changes in the bank module (Open source is slow!).
1
0
1
Appreciated features of the current bank module include its single entry point for checking and moving user balances across different assets, eliminating the need for separate indexers. One of the biggest UX struggles of ETH.
1
0
1
Today we had the first working group meeting for the cosmos-sdk's bank rework. We proposed enabling the bank to handle all fungible, transferable assets more generically. #Cosmos
1
3
14
Biggest mistakes made in cosmos-sdk: - Proto as first class citizen. - Using keepers to interact with other components of the system.
1
0
1
Biggest mistakes made in CosmWasm: - Actor model - Making enums a first class citizen for API definition
0
0
1