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.
While building DarkHorse, we tested WDK’s core features in the browser.
We submitted a working example and Chromium tests to @WDK_tether’s tetherto/wdk repo.
Our PR has passed the repo’s Socket security scan and is now awaiting review.
Back to building. 🐎
https://t.co/03SfItGfNU
While building DarkHorse, we tested WDK’s core features in the browser.
We submitted a working example and Chromium tests to @WDK_tether’s tetherto/wdk repo.
Our PR has passed the repo’s Socket security scan and is now awaiting review.
Back to building. 🐎
https://t.co/03SfItGfNU
Exactly.
There’s a lot to like about RGB, but getting started can still be hard for everyday users.
We’re working to make it easier, starting with trading.
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. 🐎
We’ve received many questions about when @RGBHorse will go live.
The truth is, building products on RGB takes more time than we initially expected.
The RGB ecosystem is still at an early stage, and many things need to be built, tested, and improved from the ground up.
Of course, we could launch something quickly.
But we believe building a solid foundation matters more than simply moving fast.
Thank you to everyone who has been following our journey.
We’re still building, and we’ll share more updates when the time is right.
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
@VIhnatiuk@MorganStanley@MergnerMs@utexocom Excited to see Bitcoin-native assets gaining more adoption. We’re building RGB asset launches and swaps at @RGBHorse, and looking forward to more possibilities together.
We found and reported two issues while testing @KaleidoSwap’s RGB infrastructure.
One affects first-time receives of RGB assets through WebRGB. The other can cause a transfer to disappear from status tracking after the asset is identified.
The second issue has already been confirmed by the KaleidoSwap team, with a fix submitted in PR #109.
Glad to see it moving quickly. We’ll keep testing and contributing as we build.
WebRGB #2 👇
Wallet Engine #107 👇
https://t.co/WivVGLkmTa
https://t.co/5jCxlrcKtK
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