The Timewave era has come to a close. Timewave Inc. will be winding down. All code is now open source under Apache 2.0 on our Github. https://t.co/2RSEVIchaf
Sincere gratitude to all of our partners, collaborators, and supporters over the last 3 years.
Yours in time,
The next generation of crypto will be defined by natively cross-chain applications.
If you’re building at that frontier, let’s talk.
🧵 What we do at Timewave:
Did you know that Valence offers a developer interface that helps manage cross-chain programs?
The Programs UI tracks CosmWasm chains, with EVM support coming in a few weeks. Solana on deck.
To check it out, click the link below 👇
@brane_trix Valence handles retry logic and error handling so you can specify exactly what you want to have happen if/when you hit a given issue. If there's something specific you're hoping to achieve, we'd gladly connect you with one of our engineers
If you are interested in building something that will define the future of internet-native finance—let’s build it together.
DMs open.
Website: https://t.co/b3zann1Xvh
New blog post: Valence Powers the Networked Economy
Crypto today is fragmented.
Liquidity, users, and state are siloed across chains—forcing every protocol to act like its own island.
Valence is building something better:
A unified execution layer for the Networked Economy. 🧵
Hydro isn't the only team contributing to Valence.
@OrbitEarn also just contributed a valuable Valence library.
Here's what they built, how it works, and why it matters 🧵
🛠 Major milestone reached!
For the first time, external teams have contributed production-ready Valence libraries.
Here's what one of them built, how it works, and why it matters 🧵
Valence isn't just for protocols.
Valence also supports anyone seeking higher yields.
Here is how Valence offers cross-chain leveraged yield vaults that offer depositors higher risk-adjusted returns. 🧵
We could use @ValenceZone to not only automate operations between @cosmoshub and @StargazeZone, but to also automate operations between the Hub and any Hub-native DeFi.
For example, deploy the Hub's ATOM to Stride Swap, @stride_zone's IBC Eureka DEX
I do not have an opinion as to whether the should Hub move forward with the acquisition.
That said, if the Hub does move forward with an acquisition, I recommend
1) it does not try to do so in a single gulp
2) it minimizes the use of multisigs and maximizes automation