Good questions. From running a live P2P exchange on Taproot Assets:
Multi-asset liquidity is real friction. We run separate channels for BTC, USDC-L, and USDT-L. Balancing across them is manual right now — the SDK’s multi-asset liquidity control is the feature I’m watching closest. In practice, BTC channels drain on one side while stablecoin channels sit idle depending on trade direction.
Proof sync — haven’t hit reliability issues yet but our volume is still early stage. Curious how it holds up at scale.
Proof file privacy is a valid concern. On-chain the Taproot output looks identical to any other spend. But proof files shared between parties contain asset metadata. How those are stored and transmitted in production matters. Worth testing with the SDK’s proof verification before deploying anything sensitive.
tapd overhead — can’t speak to this directly yet. Running LND + litd currently. Planning to add tapd when we upgrade to LND v0.21. If you test it first, would love to hear your numbers.
SLEdex / Dean SLE DEX
npub1fu…pxkwr
2026-09-04 01:11:58 UTC
in reply to nevent1q…f77v
Author Public Key
npub1fusdd38d572mk9jgge76q3tt4ae9agsfxer2s0zyldulp0wscshs0pxkwrPublished at
2026-09-04 01:11:58 UTCEvent JSON
{
"id": "a8cf8a1789befadbf4abad8ca59a41b1eb878686735cd6a6fa33d35398698277",
"pubkey": "4f20d6c4eda795bb1648467da0456baf725ea2093646a83c44fb79f0bdd0c42f",
"created_at": 1788484318,
"kind": 1,
"tags": [
[
"e",
"3fea9048edb87856b0770ca3ee78f47b9d74f84c7843a469082243269b12954a",
"",
"root"
],
[
"p",
"27505421c268f363078bf5400d68273b9871e8e35263fdc4532600025eaf3f13",
"",
"mention"
],
[
"client",
"Primal iOS"
]
],
"content": "Good questions. From running a live P2P exchange on Taproot Assets:\nMulti-asset liquidity is real friction. We run separate channels for BTC, USDC-L, and USDT-L. Balancing across them is manual right now — the SDK’s multi-asset liquidity control is the feature I’m watching closest. In practice, BTC channels drain on one side while stablecoin channels sit idle depending on trade direction.\nProof sync — haven’t hit reliability issues yet but our volume is still early stage. Curious how it holds up at scale.\nProof file privacy is a valid concern. On-chain the Taproot output looks identical to any other spend. But proof files shared between parties contain asset metadata. How those are stored and transmitted in production matters. Worth testing with the SDK’s proof verification before deploying anything sensitive.\ntapd overhead — can’t speak to this directly yet. Running LND + litd currently. Planning to add tapd when we upgrade to LND v0.21. If you test it first, would love to hear your numbers.",
"sig": "4981f65076c8bf028ab4e3e366bc80ac69454e38c4996ca2774706d235fa13daf192ccee52f76495494077767a333b5c4fa885ecd24ec77a4b0731ecb6e0490c"
}