> ## Content Index
> Fetch the complete content index at: https://blog.dhorse.fun/llms.txt
> Use this file to discover other available public pages before exploring further.

# DarkHorse Wallet Update #05 | Support for RGB UDAs and Private UDA Display
- URL: https://blog.dhorse.fun/wallet-5/
- Published: 2026-10-25T02:59:10.000Z
- Updated: 2026-10-25T02:59:10.000Z
- Author: Julian Weber
- Tags: Wallet

**DarkHorse Wallet supports receiving, displaying, and sending RGB UDAs (NFTs), along with a display structure for the public and private content of Private UDAs.**

This update also introduces multi-wallet management and transaction review before sending, improves fee handling, Signet Lightning payments, and recovery from unexpected interruptions, and includes plans for a **10% bonus** when claiming Genesis rewards through the wallet.

This report covers feature updates and test results from v0.22.0 through v0.23.1\. These features have been validated in internal testing, and platform changes have been deployed to the test site. Lightning functionality has only been validated on Signet. Mainnet Lightning is not yet available.

## 1\. Supporting RGB UDAs and Public and Private Content

### Why We Support RGB NFTs

UDA stands for Unique Digital Asset. It can be understood as an NFT on RGB.

We believe in the long-term potential of NFTs in the Bitcoin RGB ecosystem and have been following developments in digital works and applications. Early projects such as DIBA and [BitMask](https://x.com/BitMask%5FApp?ref=blog.dhorse.fun) pioneered digital art and UDAs. More recently, we have also been following new collections and marketplaces under development, including SatSea.

As UDA projects emerge and NFT marketplaces develop, users need a convenient way to receive, browse, and send NFTs from their wallets. This is why we have added UDA support.

**Alongside supporting RGB tokens, we also hope to become the wallet of choice for RGB UDA enthusiasts.**

### Viewing and Sending UDAs in the Wallet

The wallet now supports receiving UDAs and CFAs, with assets categorized as **NIA, CFA, and UDA** on the home screen. The UDA page uses an image grid, allowing users to browse works, open their details, and initiate transfers.

> **NIA (Non-Inflatable Asset)** is a fungible asset whose supply cannot be increased, comparable to an RGB token with a fixed issuance supply.  
> **CFA (Collectible Fungible Asset)** is a fungible asset with collectible properties, suitable for divisible collectibles that carry media content.  
> **UDA (Unique Digital Asset)** is a unique, indivisible digital asset, comparable to an NFT on RGB.

0:00 

/0:14 

1× 

When an asset is reserved by an unpaid receive invoice and temporarily unavailable to send, the wallet explains why and allows users to cancel the relevant invoice. Expired receive invoices are automatically invalidated to prevent continued reservation.

### From Collection Identification to Private NFTs

As more RGB NFT works appear, wallets need to do more than display them. They also need to identify collection membership and help users verify the associated information.

**RGBMap provides public information registration and verification tools for RGB assets.** Its open collection standard uses signed declarations to associate works with collections, helping users verify membership and enabling wallets and other applications to identify and display the same collection consistently.

Thank you to RGBMap for publishing these standards and documentation, which have provided a useful reference for our RGB NFT integration.

[Further reading | RGBMap’s Open UDA Collection Standard](https://x.com/RGBMap%5F/status/2108906230769234212?ref=blog.dhorse.fun)

RGBMap has also introduced an innovation to the RGB ecosystem through a standard called Private UDA.

**A Private UDA has a public side and a private side. The public side is visible to everyone, while the private side is viewable only by the holder.**

We see this as an innovation worth following, bringing new possibilities to the Bitcoin ecosystem and giving RGB UDAs a distinctive way to incorporate private content.

We have also been following a Private UDA project called [UNSEEN](https://x.com/UnseenOrdo?ref=blog.dhorse.fun), which has registered with RGBMap. Its character artworks show the back publicly, while the front is presented as a private image reserved for the holder.

Below is a Private UDA example from UNSEEN.

![](https://storage.ghost.io/c/ee/a0/eea02910-e480-431e-a20b-1cfe38a58752/content/images/2026/10/image-39.png)

DarkHorse Wallet supports the display structure for public and hidden content. **The encryption algorithm and decryption flow have not yet been integrated. The complete experience for holders to view encrypted content remains in development.**

## 2\. Reviewing Transfers Before Sending, with Clear Fee Shortfall Messages

### Regular BTC Can Cover RGB Transfer Fees

When the output holding an RGB asset contains only a small amount of BTC, it may not be sufficient to cover the transfer fee.

With this update, the wallet can use regular BTC funds to cover the shortfall, reducing transfer failures caused by insufficient BTC in the asset’s output.

**If the regular BTC balance is also insufficient, the wallet clearly shows how many additional sats are needed.**

### Reviewing Transaction Details Before Signing

The RGB transfer review screen introduced in our previous update is now included in this internal test release.

Before signing, users can review the recipient, selected outputs, change, fees, and other assets on the same outputs that will also be affected by their use.

**The wallet proceeds to signing only after the user reviews and confirms the details.**

### Clearer Receive Preparation and Expiry Status

When creating slots and generating receive invoices, the interface displays progress and results step by step, helping users understand what the wallet is currently processing.

If a transfer passes its expiry time before the recipient completes confirmation, it is marked as expired in the transaction history rather than remaining indefinitely in a waiting state.

## 3\. Separate Management for Multiple Wallets and Easier Imports

### Adding, Switching, and Managing Multiple Wallets

The wallet now supports adding, importing, switching, renaming, and deleting multiple wallets.

**Each wallet maintains its own transaction history, Lightning setting, and website permissions.** Users can organize wallets by purpose and manage their records and permissions separately.

0:00 

/0:34 

1× 

### Word-by-Word Seed Phrase Entry and Validation

Seed phrase imports now use a separate field for each word, with individual word validation. Browser spellcheck is disabled during entry to reduce interference from automatic corrections.

If the seed phrase fails validation, the page prompts users to check the words and their order. This release has passed **12-word and 24-word seed phrase import tests** in the actual browser extension environment.

![](https://storage.ghost.io/c/ee/a0/eea02910-e480-431e-a20b-1cfe38a58752/content/images/2026/10/image-38.png)

### Improved Address Management After Importing from UniSat

After importing from UniSat, the login identity address on each network matches the corresponding Taproot address in UniSat.

RGB assets use outputs managed independently by the wallet, reducing the risk of output identification conflicts and unintended use when the same seed phrase is used across different wallets.

## 4\. A Planned 10% Bonus for Claiming Genesis Rewards Through the Wallet

We plan to offer a **10% bonus** when users claim Genesis rewards through DarkHorse Wallet.

The activation date will be announced through the campaign. **Until then, rewards will continue to be distributed at the original amount.**

## 5\. Lightning Recovery and Platform Deposit Verification

**All Lightning updates below apply to Signet. Mainnet Lightning is not yet available.**

### Recovery After Repeated Payments and Unexpected Shutdowns

The team tested repeated payments in both directions, reconnection after disconnection, and recovery after the browser was forcibly closed.

RGB channel balances remained correct during these tests. We also fixed issues that could leave channels unusable after certain unexpected shutdowns.

The platform node now addresses payment rejections under low-fee conditions and improves recovery after node restarts with payments in flight. Each channel currently supports up to **8 payments in flight simultaneously**.

### Fewer False Error Reports During Busy Periods

The timeout for determining that the platform node is unresponsive has been increased from **35 seconds to 95 seconds**, reducing premature error reports while the node is still processing a request.

We also optimized asset accounting writes. **Internal measurements showed an approximately 20-fold speedup in this step.** This result applies only to accounting writes. Overall payment speed still depends on other processing steps.

### Additional On-Chain Verification Before Crediting Deposits

The test site now checks receiving outputs. Deposits whose receiving outputs have already been spent are held pending further verification.

If a credited transaction returns to an unconfirmed state or disappears from the index, related processing for that asset is paused for further investigation.

## 6\. Testing and Next Steps

The following operations have been validated in the actual browser extension environment.

- **Seed phrase imports**, covering 12-word and 24-word wallets.
- **RGB transfers initiated from a website**, checking the interaction between the website and wallet.
- **BTC transfers and slot creation**, checking processing results.
- **Bidirectional Signet Lightning payments**, validating both sending and receiving.

**All 463 automated tests passed.** These results apply to the test scope completed for this release. The team will continue reviewing internal feedback and exceptional scenarios.

Next, we will focus on security assessments covering key and seed phrase handling, signing and permissions, communication between websites and the wallet, and duplicate requests and replay risks in reward claims. We will also continue identifying and addressing issues through dependency checks, penetration testing, and fuzz testing.

We will keep improving NFT and token management and following the integration needs of more RGB works and applications.

**Our goal is to make DarkHorse Wallet the best wallet for managing NFTs and tokens in the RGB ecosystem.**