At Obsidian, we take ideas from advanced programming, type theory, and declarative systems design out of the lab and into production.
We're pleased to announce the release of reflex-vty 1.0, bringing declarative, functional-reactive UI programming to terminal applications.🧵
Time really flies..
It’s been seven years since the first release of reflex-vty, our Haskell TUI framework that uses functional reactive programming. I had no idea what I was getting myself into.
Proud of how the framework looks now that it’s mature. Retro in the link below.
@Olarewa67856602@tradecraftfi No signup is required!
You can just visit the site and start trading.
Here's a quick walkthrough:
https://t.co/wcGSv63nLi
@BlazarLabs@obsidian_llc Great summary of Hydra projects!
Just one minor tweak: The initial phase of Hydra for Payments wasn't associated with any Catalyst proposal. Its development was a partnership between Obsidian Systems and IOG.
@StakeWithPride No direct P2P yet. As we conclude this phase, we'll release a thorough rundown of current architecture and next steps.
There are some exciting possibilities that open up later as hydra itself moves through some of its major upgrades. Ex: https://t.co/7G1dYBeXtq
@cardano_whale No worries! The team appreciates the mention.
We're heads-down integrating the latest improvements in Hydra itself (great to collab with IOG's Hydra team), bringing the open-source library together (hydra-pay), and validating it all in our standalone mobile app (stay tuned!)
@SimonSallstrom End-users don't have to stay online. In the video, you'll notice the channel UI includes Previous Transactions I received with my app closed.
50 separate open heads is already trivial. If you need all participants connected to *each other*, look ahead to: https://t.co/7G1dYBeXtq
@SimonSallstrom Fungible native tokens should work without too much trouble but- with Hydra for Payments- it's something we'll validate after we're absolutely solid on ADA workflows.
Benchmarking for hydra itself: https://t.co/VUz6tERYva
@877PSBYTE6@conraddit I'm still focused on payments so I don't have much to add! Constraints may change in future updates to hydra itself but it will also require a pioneering project to try to ship something.
It's also great to see more people conversant in hydra now! @Northern_ADA@The_cryptobear
@_KtorZ_ 🫀
For the team, it's been a real pleasure collaborating with @ch1bo_ & team at IOG, learning from you & the CF team tackling voting, seeing the creativity from @SwiftlyUnmoving & team on auction design.
And it's all open-source!
@IlluviumGamer@cardano_whale Hah!
Right - Hydra for Payments is focused on send/receive for now. Though some of our tooling and infra may help improve the dev experience on use cases that require scripts.
Other teams have begun work on such use cases: MLabs collab with IOG on auctions & CF on voting.
@jcampus1111 @regisg A user will be able move funds between L1 and an open hydra head without closing the head.
In the meantime, we'll accumulate a lot of experience operating long-living heads so that part of the system is robust when it's time to add incremental de-/commit.
@regisg We'll integrate external commits:
https://t.co/dApZv5i331
The current system works like this:
https://t.co/eaPkHqoQTQ
We'll maintain support for both options, as they offer different tradeoffs to builders.
Then we'll integrate incremental de-/commit as soon as it's ready.
@KiriakosKappa There's a hydra node for each user.
For Hydra Head in general, you can learn more here:
https://t.co/FfYfI1uPju
For our tooling specific to payment channels, you can learn more here: https://t.co/84KgYKWbj1
You can also expect future blog posts.