We’re building DarkHorse, a place to launch and trade RGB assets on Bitcoin.
From creating and launching an asset to trading it after graduation, the entire process will happen in one place.
We’ve already completed two core trading flows:
• Instant AMM swaps
• PSBT-based wallet-to-wallet orders
Users can trade directly from their own wallets, while DarkHorse handles order matching without taking custody of their assets.
Our goal is simple:
Make launching and trading assets on Bitcoin as seamless as using Uniswap on Ethereum.
Here’s the current build in action 👇
Follow us. DarkHorse is coming soon.
Turning Bitcoin into the world’s leading settlement layer for stablecoins is a mission worth building toward together.
We’ll keep building on RGB and helping bring more real-world use cases to life. 🤝
Some people have asked what this PR is for, so here’s a quick explanation.
WDK is Tether’s open-source wallet development toolkit. Developers can use it to build wallets where users control their own assets.
WDK’s existing examples mainly focus on app wallets. We got its core features running in a browser and submitted a working example and tests.
If the PR is merged, teams building browser extension wallets will have an example to follow. That could bring WDK to more use cases and help pave the way for RGB browser extension wallets.
Picked up some $PPRGB to try the buying process ourselves. 🐸
Buying an RGB asset still takes a few steps. At @RGBHorse, we’re testing what it would take to enable AMM trading for RGB assets.
Still early, but we’re making progress. 🐎
While building RGBHorse, we’ve been testing the full RGB flow from receiving assets to swaps.
Found an edge case in @KaleidoSwap’s WebRGB during testing and reported it on GitHub.
@KaleidoSwap team, sharing this as we keep building together. 🤝
https://t.co/Q3nnTmO8Ln
Found two edge cases in rgb-lib-wasm.
One is a JS/WASM deserialization issue: integer values can be rejected unexpectedly, while some optional fields are required when they shouldn’t be. We submitted a fix with tests.
The other is wasm32-specific: a signed PSBT is kept only in memory while waiting for the recipient ACK. If the session is locked or reloaded during that window, the transfer can no longer be broadcast.
No assets are lost in this case. They never left the sender, so the transfer simply needs to be resent.
One PR, one issue. Small contributions to making RGB better. 🐎
PR #28 👇
Issue #29 👇
https://t.co/DGLVVOQ4Gn
https://t.co/ZxrIYYense