TapRay

Peer-to-peer liquidity for RGB assets. Makers quote from their own inventory, you settle directly.
No pools, no custody.

[RGB Hub @RGB_Hub]

RGB Community Call: Meet @TapRayFi .

A live intro to the project and a demo of TapRay, the liquidity network for Bitcoin assets, in the wider RGB Protocol on Bitcoin ecosystem.

Guest: TapRay
Thu 23 July, 15:00 CEST
Live on Telegram + X, simultaneously.
Bring your questions.

[TapRay @TapRayFi]

A debugging and inspection tool for the RGB ecosystem.
https://t.co/dS1TykHsa9

[TapRay @TapRayFi]

RGB consignments are powerful, but not exactly human-readable.

Our decoder verifies the consignment, validates the Bitcoin commitment via SPV, reconstructs the anchor transaction, and visualizes the entire RGB state lineage from tip to genesis.

[TapRay @TapRayFi]

@TapRayFi vs @tap_protocol

TAP is closer to an asset protocol and programmable execution environment, while TapRay is a market-making and liquidity coordination layer built on top of Bitcoin asset protocols.

TAP is an Ordinals metaprotocol for issuing and managing Bitcoin-native assets through inscriptions and indexers. It supports transfers, authorities, locks, sales, AMMs, staking, and other programmable actions. NAT is one ecosystem built around that stack.

TapRay solves a different problem. We are building an RFQ liquidity network for Bitcoin assets, starting with RGB. Market makers quote directly from their own inventory, retain custody of their keys and funds, and compete to offer users the best price. TapRay coordinates quote discovery, inventory reservation, signing, and non-custodial settlement.

This fits naturally with RGB, where asset state and transfer history are exchanged only between the relevant parties rather than published and globally indexed. Bitcoin sees the commitment, not the full asset data. This makes the system private by default at the protocol-data layer and reduces the amount of data the wider network must store and process.

TAP vs TapRay

- TAP defines asset and account state
- TapRay coordinates liquidity, quoting, and trade execution

- TAP uses inscription-based state reconstructed by indexers
- TapRay currently settles RGB assets using client-side validation

-TAP includes native trading primitives such as sales and AMMs
- TapRay focuses on RFQs, competitive quoting, inventory-aware market making, and minimizing unnecessary information exposure

Supporting TAP assets on TapRay could make sense later if there is enough user and market-maker demand.

For now, we are starting with RGB because that is where we see the clearest liquidity infrastructure gap.

[BTCaveman. @TRACaveMan]

@TapRayFi why not just use @tap_protocol

Atleast research https://t.co/SBN64pL8nM

Silly

[TapRay @TapRayFi]

@Blockstream @adam3us Just borrow against it. Use @LiquidiumFi 's credit line. Lowest APY on the market!

[TapRay @TapRayFi]

@RGB_Hub Hey everyone!

[TapRay @TapRayFi]

@paoloardoino Looking forward to it!

[TapRay @TapRayFi]

@Prestonbox @PepeRgb20 @LnfiNetwork v0.12 FTW! We need an efficient way to run these wallets on resource-constrained devices.

For now, though, v0.11 will have to suffice.

[TapRay @TapRayFi]

@RGB_Hub @emilejellinek @kaleidoswap @dariusnostr @LnfiNetwork 👀🔥

[TapRay @TapRayFi]

@orbis1_ Hardware wallet: "I saved your keys."
RGB wallet: "Cool, where are the consignments?"
Hardware wallet: "The what?" 😅😂

[TapRay @TapRayFi]

@RGB_Hub @FedericoTenga Honestly beautiful tech. But the UX has to carry a protocol that basically says:

the blockchain is only the notary, your wallet is the accountant, and losing local state is financial dementia. 😂

[TapRay @TapRayFi]

@RGB_Hub @FedericoTenga TLDR: RGB is what happens when Bitcoin maxis discover tokens but refuse to let the blockchain know they did.

No global state.
No public token balances.
No EVM circus.

Just private off-chain asset history, Bitcoin commitments, and the sacred duty of not losing your consignment.

[TapRay @TapRayFi]

@BitlightLabs Hey!

[TapRay @TapRayFi]

@billgnofficial Hey!