# stablecoins — X 热门讨论 (2026-09-25 10:10 UTC)
## @dinhturin (dinhxomgon) · 09-25 06:21 · ♥41 ↻1 💬44 Bitcoin doesn't have to just sit in a wallet.
That’s probably the part of strkBTC I find most interesting.
Once BTC is brought into Starknet as strkBTC, it can become usable across the DeFi ecosystem.
You can:
→ Supply it to lending markets → Use it as collateral → Borrow stablecoins → Provide liquidity → Stake through Endur and receive xstrkBTC → Or simply hold it and keep the option to shield it when needed
And that last part matters. The goal isn't to force Bitcoin holders into one strategy. It's to give BTC more ways to be used while keeping the choice between public and shielded activity. @Starknet For me, that's a more interesting definition of BTCFi: Not just bringing Bitcoin onchain, but giving Bitcoin more things to do once it gets there. 🛡️₿ https://x.com/dinhturin/status/2103369231668785469
## @zordcrypt (ZORD CRYPT) · 09-25 08:27 · ♥55 ↻1 💬27 Public blockchains are great at settlement.
They’re not great at keeping your financial activity private.
Every deposit, transfer, vault position, rebalance, and balance can leave a permanent public trail.
For a normal wallet, that may not matter much.
For a treasury, trading desk, or autonomous agent managing capital, it can reveal position size, cost basis, and even strategy.
That is the problem Confidential Finance is trying to solve.
The goal isn’t to hide everything.
It’s selective privacy.
Keep addresses and transactions verifiable on a public chain, while keeping sensitive information like amounts, balances, and strategy size encrypted.
And importantly, institutions still need a way to prove reserves, satisfy audits, or take action when required by law.
That’s where @primus_labs comes in.
Primus, formerly PADO, isn’t building another L1.
It is building a privacy and verification layer around existing chains, using zkTLS to prove off-chain data without exposing the underlying information, and FHE / zkFHE to perform computations on encrypted data.
The idea is simple:
Keep the chain public. Keep the financial book private.
The first concrete implementation is already live on BNB Chain with Unitas and United Stables.
✦ The flow looks like this:
→ Shield a stablecoin into an encrypted version → Transfer it without revealing the amount or updated balance → Stake it into a confidential vault while keeping the position private → Unshield or redeem when you want the normal asset back
Your wallet remains visible on the public network.
Your dollar balance doesn’t.
That makes this different from a fully private chain, where liquidity has to move somewhere else, and different from a shielded pool that hides more of the transaction graph.
The technical side is also interesting.
@primus_labs says it built its FHE stack in-house, including the scheme, AutoHoG compiler, and GPU engine.
Its reported benchmarks show roughly 90ms per confidential transfer and 210+ TPS on an 8× RTX 5090 setup.
FHE is still more expensive than normal computation, but performance like this is what starts moving confidential finance from research into usable infrastructure.
There’s another important piece: proof of reserves.
Primus is using zkTLS to let products such as Unitas prove backing without simply publishing their entire financial data set.
That combination matters.
Privacy without a way to prove solvency is difficult for institutions.
Transparency without privacy exposes the entire book.
You need both.
✦ The bigger question is what happens next.
Can confidential finance support credit, agent execution, automated rebalancing, and cross-protocol strategies without leaking sensitive information at the edges?
That is where Primus gets interesting.
Its broader stack combines zkTLS for Web2 and agent proofs with FHE for encrypted computation.
The $BNB vault is simply the first place where that thesis meets real stablecoins and real yield.
If public chains are going to handle more treasury capital, payroll, and autonomous agents, they may need something in between full transparency and a completely private chain.
Not a darker blockchain.
A public blockchain that doesn’t have to publish your entire financial book. https://x.com/zordcrypt/status/2103400959443427579
## @0xWINNYx (Winny) · 09-25 09:18 · ♥52 ↻10 💬10 I’ve been looking at stablecoin data a little differently.
Stablecoin market caps are growing across multiple chains. 📈
But I don’t think market cap tells the whole story anymore.
➤ Arbitrum just added ~$180M in stablecoin market cap in 24 hours, with Avalanche adding another ~$92M.
That’s meaningful growth.
But recent on-chain data shows ~$203B in settled stablecoin volume, while only ~$30.5B is considered organic.
~85% comes from service-to-service activity.
So when stablecoin liquidity expands across chains, I think the more interesting question is what that liquidity is actually being used for.
Huge supply growth doesn’t necessarily mean huge economic demand.
➤ Base alone processed roughly $140B, almost entirely in USDC.
➤ Tron is processing billions primarily through USDT.
➤ Ethereum has multiple stablecoins competing for settlement and liquidity.
Different chains are building different rails around the same basic asset: digital dollars.
The same digital dollar can represent very different economic activity depending on where it sits and how it moves. > 引用 @cryptodotnews: JUST IN: Arbitrum leads the latest stablecoin market cap surge across major chains
Arbitrum added $180.7M in the past 24 hours, ahead of Avalanche at $92.5M, while Hyperliquid, Aptos and Base added $30.2M, $11.5M and $4.2M, bringing the top five’s combined growth to $319.1M. https://t.co/9J8izku8uH https://x.com/0xWINNYx/status/2103413940688482684
## @JaromirTesar (Cardano YOD₳) · 09-25 08:45 · ♥41 ↻4 💬1 Cardano Native Tokens just got a ticket onto the rails institutions already use.
The Cardano Foundation announced that Fireblocks will add full native support for CNTs.
It means hat banks, exchanges, payment firms, and fintechs on Fireblocks will be able to custody, send, and receive those tokens with the same policy controls they already use for everything else.
To be clear, it is more than an integration announcement.
Fireblocks is the institutional plumbing layer: MPC wallets, treasury ops, policy engines, and a transfer network that banks and fintechs sit on top of.
Clients include names like BNY, Revolut, Galaxy, and Worldpay.
If an exchange lists an asset, a bank issues a token, or a fintech moves stablecoins at scale, Fireblocks is often the system that actually signs and gates the transaction.
Until now, CNTs sat in a gray zone. ADA could move through Fireblocks. Tokens issued on the same chain needed extra manual steps or RAW-signing workarounds.
It was the kind of setup compliance teams quietly refused. Native support means CNTs become standard assets inside the existing console, not a special project.
For issuers, the practical meaning is simple: if you mint a stablecoin or a tokenized asset on Cardano, the desks that already run BTC, ETH, and USDC through Fireblocks can now treat your token as another line item, meaning same vaults, same approvals, same audit trail.
Long story short, this opens the doors to institutions for Cardano. > 引用 @Cardano_CF: Cardano Native Tokens (CNTs) will be supported on @FireblocksHQ.
That means every exchange, bank, and fintech using Fireblocks will be able to custody, send, and receive CNTs with the same policy controls they already use for every other asset.
Special thanks to @emurgo_io and the Pentad as well as @IagonOfficial for helping on this journey. https://x.com/JaromirTesar/status/2103405497395163479