Uyên Nhi Ngx

#dusk $DUSK @Dusk

I used to think integrating Chainlink was routine—every chain does it to get a price oracle. But after reading the Dusk and NPEX announcement carefully, I realized this isn’t a typical price oracle. NPEX is a licensed MTF trading venue in the Netherlands; it has raised more than 200 million euros through its platform and has over 17,500 active investors. When a regulated venue like that needs financial data with high integrity to bring tokenized assets on-chain, the problem is no longer about getting a quick price—it’s about having data reliable enough to pass audits and regulatory oversight. Chainlink CCIP acts as a standardized interaction layer, connecting this data across multiple blockchain ecosystems instead of keeping it locked inside Dusk. This turns DUSK not just into a private infrastructure, but into a connection point between licensed traditional finance and public DeFi. The question is: as more and more regulated venues do the same, which data standard will prevail?

#binancep2pantoan @Binance Vietnam

One afternoon, after a buyer finished matching their USDT order, they immediately messaged, “My account is about to expire. Could you please ask a relative to transfer for me?” A few minutes later, the funds arrived exactly in the correct amount, but the name on the receipt was a completely unfamiliar one.

I stopped right away—not because I lacked money, but because the transfer name didn’t match the buyer’s registered name on the order. Paying using an account not in one’s own name is truly risky. It’s not just a matter of whether the amounts are correct; if that money comes from an unclear source, my own bank account could be implicated later.

I asked the buyer to explain immediately in the order chat who the account holder is, what their relationship is with the buyer—rather than me speculating and releasing just to get it over with.

The more evasive their answer is, the more certain I am to stop. I’ll report within the order, and I’ll keep the receipt image and the chat logs as evidence, so that Binance Support can verify before taking any further action.

Even if the name doesn’t match, and even if the money is sufficient, it remains a big question mark.

#binancep2pantoan @Binance Vietnam

There was a time when I was selling ETH, and near the end of the transaction, the buyer messaged me saying the system was "having an error". They asked me to cancel the order in the app so they could transfer the money directly via the bank to make it faster, and then I would send the ETH myself afterward. At first, it sounded reasonable, because sometimes the app really does lag.

But I paused, remembering that canceling the order means the collateral is released and the order is no longer protected by the platform. At that point, whatever amount they transferred would only rely on each other’s promises. I refused to cancel. I told them to leave the order as-is in the app, and if there was any issue, to wait or contact Support instead of handling it separately.

While waiting, I checked their profile and saw that the account had just been created. It had no completed orders yet—very different from the professional impression they gave when messaging. After a while, they still paid normally through the app, and there was clearly no error at all. I went to the bank to verify, and the money came in exactly the right amount, with the name matching the order. That’s when I unlocked everything.

After that, I still took screenshots of the order and the chat and saved them into a separate folder, in case I needed to cross-check later.

Looking back now, I’m glad that day I didn’t rush to cancel the order based on what they said.

#dusk $DUSK @Dusk

The first time I heard about Dusk Trade, I thought it was just another tokenized asset app—the market already had dozens of similar ones. But the more carefully I read the architecture, the more I realized it doesn’t compete on the interface layer; it competes on the legal layer behind it. Dusk Trade is an application layer running on DuskEVM, bringing MMF, ETFs, bonds, and RWAs into one place with real ownership, instant settlement, and DeFi-style composability. The difference is that it’s designed to operate as an MTF and a licensed investment platform, complying with EU regulations—not as a token wrapper laid on top of real-world assets and then hoping regulators will overlook it. Most other RWA platforms solve the technical problem first, and the legal one later. Dusk Trade does the reverse. That’s why I think this isn’t a product so much as a test to see whether regulated financial infrastructure can run natively on-chain. The question is: if this model works in the EU, who will be next to try it in other markets?

#dusk $DUSK @Dusk

I paid attention to DuskEVM since its testnet days—not because adding an EVM-compatible layer is something new, but because of how it handles a contradiction that most of today’s onchain financial infrastructure hasn’t been able to resolve: how to achieve both privacy and auditability at the same time. Hedger, DuskEVM’s module privacy, combines homomorphic encryption based on ElGamal with zero-knowledge proofs to encrypt balances and transaction amounts, while still allowing authorized parties to review them when needed. This
not absolute anonymity like old DeFi.

But this is when I see the real difference. Financial institutions don’t need anonymity; they need selective disclosure—private with the market, but transparent to regulators when required. That’s exactly something traditional EVM can’t do. With in-browser proving under 2 seconds, DuskEVM opens up familiar Solidity for builders, but runs on a compliance layer that native Ethereum doesn’t have.

The question is: how many currently regulated financial applications truly need this layer to exist onchain?

#binancep2pantoan @Binance Vietnam

Last week I guided my younger cousin to buy USDT for the first time on Binance P2P, because he messaged me asking why the price was cheaper somewhere else but he didn’t dare try. I told him to let me sit next to him and do it once so he could get used to it.

After placing the order, I noticed the seller’s profile had a completion rate slightly lower than the ones I usually choose, but the badge was still acceptable, so I decided to try. In the chat, the seller immediately sent the bank account number to transfer money to, but the name on it didn’t match the name shown on the order.

I paused and explained to my cousin that matching the account name is an important step; if you transfer to the wrong person, later there’s no basis to verify and you’ll have nothing to cross-check against.

I then asked directly in the platform’s chat. They replied, "Company account, just transfer," and their tone was quite rushed. That made me even more certain I should cancel the order rather than keep arguing.

After that, I placed a different order. The account name matched perfectly. Once my cousin finished transferring the money, I told him to take a screenshot of the receipt with the order code—consider it a habit of keeping records from the very first time.

Only after I saw him finish did I realize: those steps that seemed like pointless hassle turned out to be exactly what saved me at the right moment.

#binancep2pantoan @Binance Vietnam

When I first started learning P2P trading, I once almost made a pretty silly mistake. At the time, I needed to sell some BNB, so I chose an order from someone who looked familiar—because they had matched an order with me once before. Thinking “we’re familiar,” I became a bit careless and didn’t re-check their profile the way I usually did.

While waiting for payment, they messaged me asking if I had Zalo so we could “exchange faster, no need to type through the app.” I was about to agree right away because I thought, “Anyway, we’re familiar,” but then I remembered that if anything is exchanged outside the platform, later if problems arise there’s nothing to provide proof—so I kept the conversation in the app.

After that, they transferred the money and sent a payment confirmation photo, but this time I still opened my banking app myself to verify instead of trusting the photo immediately like before. The funds really did arrive, the match name was correct—only then did I unlock.

Only after everything was done did I realize that “familiar face” doesn’t mean you can skip verification steps. Their profile or transaction history could change over time. I still saved the order code as usual, treating it like a habit I shouldn’t abandon.

#binancep2pantoan @Binance Vietnam

Once I sold USDT to a buyer who messaged very politely, and their profile looked fine, so I didn’t think too much about it. The issue only happened after they transferred the money.

I opened my banking app to check and saw the payment went through—correct amount, everything matched. But the transfer memo/content field contained some sentence unrelated to the order, like "repay a debt on behalf of A," with no mention of the order ID at all. When I asked again in the platform chat, they said they used the wrong template by mistake; it was nothing, and I should just release the order.

I still felt it was strange, so I didn’t act right away. Unusual transfer content is also a sign I had read before—something to be careful about. I messaged back that I would keep the order status unchanged for a bit to check further. Then they started spamming me, urging me to release urgently because "time is running out." The more they pressured me, the more certain I became that I should slow down.

I screenshot the entire chat and the receipt, then filed a complaint directly in the app instead of making the decision myself. Support checked and handled it properly—so I didn’t lose anything.

After that incident, I realized that sometimes the feeling that "something isn’t right" is worth trusting more than rushing to release the order just to get it over with.

#binancep2pantoan @Binance Vietnam

There came a time when I urgently needed to buy a small amount of USDT in order to transfer money on time. On P2P, I just picked an order with a good price without paying close attention to the seller’s profile. As soon as I entered the chat, they suggested that I transfer directly through their phone number. Then they claimed that they would “report” to the system that the transaction was completed, and in return the price would be a little cheaper.

It sounded tempting, but then I remembered that for any transaction done outside the platform, Binance collateral would effectively no longer work. The money I transferred wouldn’t be protected if they failed to deliver enough. I refused, kept the order in the app, and only paid through it.

Before transferring, I also took the time to review their profile. I noticed the completion rate was quite low compared to what I usually choose, so I carefully cross-checked the name of the account receiving the money with the name shown on the order. Luckily, they matched, so I proceeded to transfer.

After the transaction was done, I still saved the order ID along with a screenshot of the order, just in case later I needed to contact Support to verify and match the details.

#binancep2pantoan @Binance Vietnam

Last month, I sold ETH for the first time to a newly created account with no much transaction history. Normally I’m hesitant about accounts like that, but since the badge looked fine, I still accepted the order—just a bit more carefully in the later steps.

After the order was matched, I was relieved that my ETH was locked in Binance’s margin account and hadn’t been transferred anywhere. That way, if anything happened, there would still be a place to file a complaint instead of having to handle it alone. The buyer messaged me to say they’d transferred the money, along with a photo of a receipt that looked very real. But I kept to my old rule: I wouldn’t unlock it just because of that photo. I opened my banking app to check, and the balance hadn’t moved by a single dollar.

I then replied in the platform chat, making it clear that I needed to see the money credited to the account first, not rely on a screenshot. A few minutes later, the funds came in for real—the sender’s name also matched the name on the order—so only then did I unlock it.

After finishing the order, I still saved the order code and the chat as usual. It’s a small habit, but now I feel it’s worth keeping.

#binancep2pantoan @Binance Vietnam

There was a time I bought BNB on Binance P2P. I chose a seller with a verified badge and a high completion rate, so I felt reassured. But right after I entered the chat, they urged me to transfer money quickly because “someone else is about to place an order.” That felt strange, because the order had already matched for me—so how could anyone else jump in.

I still made the transfer as usual, but when I was almost finished, they switched to a different account number, which didn’t match the name on the original order. That’s when I stopped, because changing the payment account midway is one of the suspicious signs I had read about before. They also suggested messaging me separately through another app to “handle it neatly,” but I refused and kept all communication within the platform’s chat. Once you move outside the system, if a dispute happens later, there’s nothing left to cross-check.

I took screenshots of the entire chat, saved the order code, and then filed an appeal right in the app. Binance Support stepped in to handle it, and the order was safely canceled—my money wasn’t lost.

Since then, I’ve realized that sometimes, just slowing down by a beat can help you avoid a lot of things.

#binancep2pantoan @Binance Vietnam

The first time I sold USDT on Binance P2P, I was also a bit nervous because I wasn’t used to it yet. But looking back, the system has already prepared the hardest part for me: as soon as the order is matched, my crypto amount is locked in escrow, not directly handed over to the buyer. So if anything goes wrong, I still have an official channel to file a complaint, rather than having to handle it all on my own.

Before confirming the order, I have a habit of quickly reviewing the counterparty’s profile—checking their badges, completion rate, and transaction history—then matching the recipient account name with the order details to ensure they match. That day, the buyer even suggested transferring money outside the app to make it faster, but I refused and kept all communication within the platform chat. If it moved outside the system, the escrow and chat history would also be gone, and in case of a dispute there would be nothing to compare or verify.

When they sent a screenshot claiming they had transferred the money and urged me to unlock it immediately, I still opened my banking app to check on my end—and indeed, the money hadn’t arrived. I replied that I would wait until I actually received the payment, and after that they went silent.

I’ve kept the order ID and all the chat from that day, just in case I need to contact Support. If I had been in a rush back then, I probably would have lost the funds.

#binancep2pantoan @Binance Vietnam

P2P trading is like placing a deposit to buy a house through a mediator: you don’t send money directly to the seller. Instead, someone holds the assets in the middle until both parties confirm everything is done. That’s exactly the escrow mechanism of Binance P2P. The crypto is locked, and chat within the platform logs every exchange. So if anything goes wrong, you always have an official channel to file a complaint.

Many people think trading outside the platform is faster, but in fact, once you leave the system, escrow disappears, the chat disappears, and if a dispute arises, there’s almost nothing left to verify. Therefore, the platform isn’t just tedious paperwork—it’s the only layer of protection you have.

Before confirming an order, review the counterparty’s profile: badges, completion rate, transaction history. Then cross-check the name of the account receiving the payment with the order details. Also, don’t rely only on screenshots—open your banking app yourself to verify that the money has been deposited into your account, and only then unlock the crypto.

If you’re not sure, just pause and ask Binance Support—there’s still time.

#baby $BABY @BabylonLabs_io

I ran into something odd while testing the TBV flow through Aave v4 on testnet, my borrowed USDC balance did not update for almost ten minutes after the transaction confirmed on my end. My first instinct was that I had found a real problem worth writing about.

I posted about it in Babylon's community channel expecting either silence or a generic canned reply, which is usually what happens when you flag something on a fresh testnet. Instead someone from the team asked for my wallet address and transaction hash within minutes, then came back explaining it was an indexer delay on their side, not a vault issue, and that a fix was already queued.

That exchange told me more about Trustless Bitcoin Vaults (TBV) than the documentation did. Anyone can write clean marketing copy about native BTC collateral, no wrapping, no bridging. Fewer teams respond that directly when a random user flags something messy on testnet, before there is any incentive to look good for a bigger audience.

I still do not fully trust any protocol based on one good interaction, but it moved my baseline from skeptical to willing to keep testing.

#baby $BABY @BabylonLabs_io

I have a habit with projects I plan to write about long term, I keep an old note where I log what they promised and when, then check back later to see if it actually shipped. Most projects fail this quietly, dates slip, features get renamed, nobody follows up.

Going back through my own notes on Babylon was more interesting than I expected. The BTC staking network through finality providers went from testnet talk to something people were actually using, and now Trustless Bitcoin Vaults (TBV) showed up as a natural next step rather than a scramble to announce something new. Native Bitcoin-backed borrowing through Aave v4 landing on public testnet lined up close to the timeline they had floated earlier in the year, which is rarer than it should be in this space.

I am not saying that proves anything about mainnet execution, testnet delivery is a lower bar. But my own tracking, not their marketing, is what convinced me Babylon tends to ship things close to when they say they will.

That track record is the only reason I am willing to actually test TBV with attention instead of skepticism.

#baby $BABY @BabylonLabs_io

I started following Babylon a while back mostly for the staking story, BTC securing other chains through finality providers. I did not expect to end up spending a weekend reading through their docs on Trustless Bitcoin Vaults instead, but that is where the project pulled me.

What struck me first was how much the documentation assumes you already understand Bitcoin's UTXO model and script limitations. I had to stop twice and go read background material just to understand why native BTC collateral is technically hard in the first place, wrapping exists because Bitcoin was never designed to talk to other chains. Once that clicked, Trustless Bitcoin Vaults (TBV) made a lot more sense as a real engineering answer rather than a marketing label.

I also spent time in their community channels, asking basic questions about how TBV differs from earlier BTC bridge products. The answers were technical, sometimes more technical than I wanted, but nobody dodged the harder questions about liquidation or oracle risk.

That is not something I can say about every project I have covered here.

Still forming my full opinion, but the depth behind TBV earned more of my attention than I expected going in.

#baby $BABY @BabylonLabs_io

Someone in a risk chat brought up 2022 unprompted, not the token collapses everyone remembers, but the quieter cause underneath them, collateral getting reused across multiple protocols at once until nobody could tell how much real backing actually existed. That pattern tends to repeat whenever an asset becomes popular collateral.

That is the angle I have not seen anyone raise about Trustless Bitcoin Vaults (TBV) yet. TBV lets native BTC serve as collateral without wrapping or bridging, and the first product live on public testnet, native Bitcoin-backed borrowing through Aave v4, is exactly the kind of integration that invites composability. Once BTC sits as collateral inside Aave v4, the borrowed USDC or USDT does not have to stop there, it can get redeployed into another position, another protocol, another loop.

None of that is unique to TBV, it is just how DeFi works. But TBV's specific selling point is trust minimization, and rehypothecated leverage built on top quietly reintroduces the counterparty and liquidity risk that native BTC collateral was supposed to avoid in the first place.

The vault itself can be trustless while the ecosystem built on top of it is not.

Watching whether that gap becomes a real conversation once TBV volume grows past testnet.

#baby $BABY @BabylonLabs_io

Every lending protocol I have ever seen fail collapsed the same way, not because the collateral was bad but because the price feed lied for a few critical seconds. Terra, Mango, half the smaller exploits from the last few years, the story is almost always an oracle problem dressed up as something else.

That is the question I keep coming back to with Trustless Bitcoin Vaults (TBV). TBV lets native BTC be posted as collateral without wrapping, with native Bitcoin-backed borrowing through Aave v4 live on public testnet right now. Removing the wrapping step and the bridge custodian genuinely removes two real attack surfaces. It does not remove a third one, the BTC price oracle that decides when a position gets liquidated.

Native BTC does not live on Ethereum natively, so somewhere in this system a price feed has to translate Bitcoin market conditions into a number Aave v4 can act on. Whatever secures that feed becomes just as important as the vault logic itself, maybe more so, since a bad price update can trigger liquidations even when the actual collateral is perfectly fine.

Trustless collateral still needs a trusted price, and that part of the design has not been the headline yet.

#baby $BABY @BabylonLabs_io

I went into the Aave v4 testnet expecting the usual first day mess, half broken buttons, a faucet that does not work, three tabs open just to figure out which network to switch to. That is normally the real barrier to native BTC DeFi, not the security model.

Testing Trustless Bitcoin Vaults (TBV) through Aave v4 changed that expectation a bit. Depositing testnet BTC as collateral and borrowing USDC took one wallet connection and one signature for the deposit, then a second for the borrow, no wrapping step in between, no separate bridge interface to bounce through first.

But the part that actually slowed me down was not the vault, it was waiting on Bitcoin confirmation times before the collateral showed as usable on the Ethereum side. Native BTC security means native BTC block times, and that tradeoff is invisible in the marketing copy but very visible the moment you are staring at a pending screen.

A clean interface cannot hide the fact that Bitcoin finality is slower than the chain you are borrowing on.

Curious how Babylon plans to make that wait feel acceptable once real money, not testnet BTC, is sitting in the queue.

#baby $BABY @BabylonLabs_io

I keep seeing "self-custodial" used as a marketing word rather than a technical claim. Plenty of products say your keys, your crypto, then quietly add a recovery service, a guardian wallet, or a support ticket process that makes the custody promise softer than it sounds.

So I actually went looking at how Trustless Bitcoin Vaults (TBV) handles this. TBV lets native Bitcoin be posted as collateral without wrapping or bridging, and the first live use is native Bitcoin-backed borrowing through Aave v4 on public testnet, where you borrow assets like USDC or USDT against BTC you never hand over to anyone.

The detail that matters here is what happens at signing. If self-custody is real, the user's keys should be the only thing that can move the collateral, no multisig committee, no bridge validator set sitting quietly in the middle.

I tested the borrow flow on testnet and did not see a hidden custodian step, which is a better sign than most projects give at this stage.

Still, testnet behavior under calm conditions is not proof the self-custody promise holds during a liquidation cascade.