Eric Choo

🎉 Officially made it to the Top 100 CreatorPad!

Big thanks to everyone who's been reading my posts, engaging, and supporting me all this time 🫶
From simple market insights to mindset tips and personal takes, I never thought I'd hit this milestone.

15489 $PIXEL is not just a reward, but a motivation to keep pumping out high-quality content for the community 🚀

The journey is still long, gotta stay in the zone and push even further 💛
For those building content, stay persistent; opportunities are always there for those who put in the work.

#CreatorpadVN #BinanceSquare

Didn’t think I’d get lucky enough to land in the top 4 CreatorPad VN on Binance Square 🥹
The prize of 0.12 $BNB isn’t huge, but it’s a solid motivation to keep writing and sharing more.

Honestly, I see that Binance Square still has plenty of opportunities for those who love creating content, analyzing, or just engaging daily.
Just give it a shot, who knows, your next post might just go top 👀

If anyone wants to join but doesn’t know where to start, needs tips on writing, building engagement, or hunting events, just hit me up. I’ll support however I can 🤝

Congrats to everyone who scored some goodies this round 🫶

#dusk $DUSK @Dusk

I used to think that “big partners” in crypto were just marketing tactics—until I looked closely at the numbers behind the relationship between Dusk and NPEX.

NPEX isn’t a typical crypto exchange. It’s a trading venue licensed by the AFM (the Dutch financial regulator), and it also holds MTF, Broker, and ECSP licenses. An organization with this level of compliance wouldn’t choose infrastructure arbitrarily—and they’re planning to bring more than €300 million in assets on-chain via Dusk.

At the same time, Dusk has partnered with Chainlink to connect data and cross-chain infrastructure for regulated financial products. This isn’t two unrelated events. It points to a pattern: EU-licensed institutions are choosing Dusk as their infrastructure backbone—not because of hype, but because the real compliance puzzle is being solved.

The question I ask myself is: as more and more regulated organizations enter the space, who will they trust as their first infrastructure?

#binancep2pantoan @Binance Vietnam

The Number I Almost Skipped Reading

I matched with a seller whose completion rate I glanced at but didn't actually read — saw a badge, assumed that was enough, moved on to the payment step. Something made me scroll back up before I sent funds. The rate was fine, but the order count was low, barely a dozen trades. Not a red flag by itself, just a reason to be more careful than usual.

I confirmed the name on my transfer matched the order exactly before sending, which it did, and paid. The seller then asked me to confirm receipt "so they could speed things up on their end" — a small request, but not theirs to make, since only I control release timing based on what I actually see in my own account.

I waited until the crypto showed in my wallet, not their message, before marking the order complete. Kept the Order ID and full chat afterward, same as always, even though this one closed without any issue.

Reading the numbers, not just the badge, is the part I skip when I'm rushing. It's usually the part that mattered.

Web3 has a $50k reward pool split evenly among anyone who gets PnL +10 on BSC
Tip: deposit 1-200u to the web to buy 1 top coin that is currently trending (choose from top futures)
And short hedge on the exchange using the volume bought on Dex using the volume bought on web3

** everyone click the join link to get the refund/free fee nhé **
THAM GIA TẠI ĐÂY !!!

$H so beautiful, so good. If you don’t place a bet on the long lottery, it’s a bit of a waste. Go place the lottery bet, guys—small stakes only

#dusk $DUSK @Dusk

There’s a concept in crypto that’s often confused: tokenization and native issuance sound similar, but they’re fundamentally different.

Tokenization simply wraps an existing asset with a token—bonds are still issued the old way, and the token is only an on-chain representation. Native issuance is different: the asset’s entire lifecycle, from issuance to settlement, is put on-chain from the very beginning.

This is where I see how Dusk is designed differently from other Layer 1s. Dusk doesn’t just provide infrastructure to wrap assets—it also has the capability to run native issuance workflows for regulated securities, provided the issuing organization has sufficient authorization and the necessary product setup.

This isn’t a generic solution. It directly targets the problem that licensed exchanges and financial institutions in the EU are truly facing: how to move the entire issuance process on-chain while still complying with regulations.

The remaining question is how many organizations are ready for this shift.

#binancep2pantoan @Binance Vietnam

The Card I Almost Trusted

I matched with a seller whose merchant badge made me relax more than I should have. Badge or not, I still checked their completion rate and order count before confirming, mostly out of habit, and it held up fine. What didn't hold up was the payment I got minutes later — a screenshot of a transfer confirmation, sent proactively, before I'd even asked.

I didn't release off that. I opened my own banking app, saw nothing pending, and told the seller I was still waiting. They pushed for a faster release twice in the same message, which is the kind of pressure that usually means slow down, not speed up.

The funds landed about ten minutes later than the screenshot claimed. Once I confirmed it myself, I released, kept the chat entirely on Binance the whole time, and saved the Order ID and thread afterward like I do for every trade now, uneventful or not.

Nothing went wrong that day. But the screenshot alone would've said otherwise, and that gap is exactly where trades go bad.

#dusk $DUSK @Dusk

I’ve been following Dusk since not many people were talking about it—not because “privacy blockchain” sounds good, but because of one specific number: NPEX, a trading venue licensed by the AFM, is planning to bring over €300 million in assets on-chain via Dusk.

But the more I read, the more I realize the issue isn’t whether there are big partners or not. It’s that most current chains force a choice: either fully transparent, or fully private. Real regulated finance needs both at the same time.

Dusk solves this by separating four layers: privacy when needed, transparency when useful, selective disclosure for authorized parties, and deterministic settlement. That’s why Chainlink, NPEX, and EU-licensed organizations choose to build on Dusk instead of a typical public chain.

The question isn’t whether RWA will go on-chain—that’s already happening. The question is which infrastructure is truly compliance-ready for financial institutions to actually trust.

#binancep2pantoan @Binance Vietnam

The Wrong Amount That Stopped Me

I was mid-trade when a payment came in for slightly less than the order amount — small enough that I almost released anyway, chalking it up to a bank fee. Something told me to check first. I logged into my own account instead of trusting the notification preview, and the shortfall was real, not a fee, just an incomplete transfer.

I messaged the buyer in Binance chat rather than letting it go quiet, and asked them to send the remainder before I'd release anything. They pushed back a little, said they were "in a rush," which only made me slower, not faster. That's usually the tell.

Before matching with them I'd checked their completion rate and order count, which looked solid, so the badge alone wasn't the issue — the payment itself was. I've learned those are two separate checks, not one.

Once the full amount landed and I confirmed it in my banking app, I released, and kept the Order ID and chat thread afterward like always, even though the trade closed cleanly in the end.

Rushed doesn't mean wrong. But it's always worth counting twice.

#binancep2pantoan @Binance Vietnam

The Fee I Almost Ignored

I once picked a P2P offer purely because the rate looked slightly better than the others on the list. Small margin, but I was trying to be efficient. Midway through, the seller asked me to send payment to a different account than the one on the order, saying the first was "temporarily blocked." I said no and asked them to update it properly or I'd cancel.

That pause made me look closer at their profile — completion rate was fine, but their history showed the same excuse on an older cancelled order. I hadn't checked that before matching, only after something felt off, which is backwards from how I trade now.

I confirmed the payment landed in my actual bank app before doing anything else, ignored the screenshot they'd already sent, and kept the whole exchange inside Binance chat instead of the WhatsApp number they offered "just in case." Saved the Order ID and chat log afterward too, out of habit more than need.

Nothing dramatic happened in the end. But the version of me who didn't check order history first would've had a very different story to tell.

$LUNA resurrection, guys—buying power looks really strong; enter the lottery and skim gently up to 0.06, touching the EMA 200 is perfect

#binancep2pantoan @Binance Vietnam

The Chat I Almost Deleted Too Soon

I used to clear old P2P chats the moment an order closed, thinking there was nothing left to keep once the crypto had already changed hands. That habit almost cost me weeks later, when a buyer disputed a trade claiming we'd agreed on different terms. I hadn't kept my own copy, and I was relying on Binance's order history to still have the full thread — which it did, since the chat stays tied to the order, but I'd spent a stressful hour assuming I'd lost my proof.

I check counterparty history more carefully now too. That buyer's completion rate was fine, but the account was only a few weeks old, which wouldn't have stopped me from trading, just would've made me slower and more deliberate about confirming payment before release.

What actually resolved things was simple: everything relevant lived inside Binance, chat, order details, payment confirmation, so support could review it directly instead of taking either side's word for it. I opened the dispute while the order was still active, not after.

I still don't delete anything now, even when a trade feels completely uneventful.

#binancep2pantoan @Binance Vietnam

The Name That Didn't Match

I was two trades away from a personal best streak — fast releases, good ratings — when a payment came in from an account whose name didn't match the order at all. Close, but not exact. Middle name missing, one character off.

I almost let it go. The amount was right, the timing was right, and I was moving fast. Instead I asked the buyer directly in chat why the names differed. The answer was reasonable — a shared family account — but I only got that answer because I asked before releasing, not after.

That's become my actual rule now: match the name on the payment against the order details every single time, no exceptions for trades that feel routine. I also stopped trusting completion badges alone. I check the number behind them — how many orders, how consistent the history looks — because a badge tells me less than a track record does.

I saved the chat thread and the Order ID anyway, even though nothing went wrong. If I'd ever needed to explain that trade to support, I wouldn't have wanted to rely on memory.

Small mismatch, real pause. That's usually all safety costs.

#binancep2pantoan @Binance Vietnam

The Time I Actually Needed a Dispute

I trade P2P often enough that I'd never opened a dispute — until a seller confirmed payment received in chat, then went silent when I asked about the release delay. My first instinct was panic. My second was relief, because everything I needed was already sitting in the order: the escrow was still holding my crypto, the entire conversation was logged in Binance's chat, not on some app that could disappear.

I opened the dispute right there, while the order was still active, instead of waiting to see if things resolved on their own. That timing mattered — support could see the full chat history and the payment confirmation immediately, no reconstructing anything from memory.

What struck me was how much faster it moved because I'd kept my own records too: Order ID, screenshots of the chat, my bank confirmation. I didn't need most of it, but not needing it is different from not having it.

The seller had asked earlier to "just chat on Telegram instead." I said no. That one decision is probably why the dispute had anything to stand on at all.

#binancep2pantoan @Binance Vietnam

The Order I Almost Let Slide

I once matched with a seller whose account was brand new — three completed trades, no badge. I almost skipped checking, since the price was good and I was in a hurry. I didn't skip it, and I'm glad, because when I looked closer, the order history showed one cancelled trade with a note about a "wrong payment name." Small detail, but it made me pause.

I asked more questions in chat before paying, kept the conversation entirely inside Binance so there'd be a record, and confirmed everything matched before sending funds. Nothing went wrong that day, but I still saved the Order ID and chat log afterward, the way I do for every trade now, not just the ones that feel risky.

Escrow already protects the crypto on Binance's side. What I've learned is that my side of the protection is just as real: check who I'm trading with, notice small inconsistencies early, and keep a paper trail I'd actually want if I evcer needed support.

#binancep2pantoan @Binance Vietnam

The Screenshot That Almost Fooled Me

I once had a buyer send me a payment screenshot that looked flawless — right amount, right bank, right timestamp. I almost released. Then I remembered the one rule I'd promised myself never to break: open my own banking app, not theirs. Nothing had landed. The screenshot was fake.

That trade taught me more than any guide did. I now check the counterparty's completion rate and order history before I even agree to trade, not just their badge. I match the payer's name to the order details every time. And when a buyer suddenly asked to "finish this on Zalo, it's faster" — that was my cue to slow down, not speed up. A legitimate trade never needs to leave the platform.

I still keep every Order ID and chat log after closing, even on trades that felt completely routine. The one time I needed it, having everything saved turned a stressful dispute into a same-day resolution.

Trust the platform's checks, not a screenshot.

#binancep2pantoan @Binance Vietnam

The Ten Seconds I Almost Skipped

My first P2P trade felt instant. Escrow locked the seller's crypto before I paid a dong, chat logged every message, and a dispute channel sat one tap away if anything went wrong. None of that exists off-platform — no escrow, no chat record, no support access. That's not a rule, it's a deletion.

I check three things now. Counterparty: badge, completion rate, order history, not just a name. Payment: my own bank app confirming funds landed, never a screenshot. Pressure: rushed release, a mid-trade account swap, a request to "move this to Zalo" — any one is a reason to pause, two together is a reason to dispute.

I keep Order IDs, receipts, and chat transcripts after every trade. Never needed them, until once I did.

The real question isn't whether P2P is safe. It's which of these checks you'd skip when you're in a hurry.

#baby $BABY @BabylonLabs_io

Long before any of this, I'd written about people defaulting to the top finality provider without checking. I never actually checked the real distribution numbers myself, I was working off the anecdote. So I went and pulled the actual stake breakdown across providers to see how bad it really is.

It was worse in one way and better in another than I expected.

The top handful of providers do hold a disproportionate share, that part matched what I assumed. What surprised me was how quickly the concentration curve flattens after the top few, a long tail of smaller providers each holding meaningful, non-trivial stake, not the "everyone piled onto one name" picture the group chat anecdote implied. The problem isn't a single dominant provider, it's a moderately concentrated top layer sitting on top of a genuinely long tail that most delegators never scroll down to see.

Technical point: that distinction matters for what "fixing" this actually means. If it were one dominant provider, the fix is obvious, break up that concentration. With a flattening curve, the system is already more decentralized than casual observation suggests, the real gap is between what exists and what delegators perceive exists, since almost everyone I've talked to describes it as more concentrated than the data shows.

Self-critique: I wrote the original piece from a single anecdote and general sentiment, not from pulling real numbers, and I should have checked this earlier instead of assuming the worst-case version was the accurate one. The actual data changes the story, not into "no problem," but into a narrower, more precise one.

$BABY 's security narrative would be stronger leaning on this actual distribution data instead of leaving people to assume based on which names get mentioned most.

I'd want Babylon to surface this distribution curve directly in the staking interface, since right now you have to go dig for it, same as I just did. #baby

⚠️ Not financial advice. DYOR.

#baby $BABY @BabylonLabs_io

After writing about emission tapering and whether fee revenue can fill the gap it leaves, I went looking for the actual numbers instead of leaving the concern abstract. I wanted to find where Babylon publishes the emission curve and, ideally, some projection of usage-driven revenue against it.

I found the emission schedule without much trouble, tables with per-period issuance, decay rates, all laid out clearly.

What I couldn't find was the other half of the equation. Nothing crossing that emission curve against projected TBV borrowing volume or staking fee revenue, nothing modeling the point where one is supposed to hand off to the other. I checked governance posts, blog updates, even searched for any team commentary on the topic. Plenty of discussion about growth and adoption, none of it framed as "here's what usage needs to look like by the time emissions drop to X."

Technical point: publishing an emission schedule is a transparency baseline, almost every token does that much. What actually tells you whether a network survives its own subsidy phase is the second half, the revenue side meeting the emission side at a specific point in time. Its absence doesn't mean Babylon has no internal model for this, teams often work these numbers out privately before committing to public projections. But from where I'm sitting as someone trying to evaluate it, silence on that half reads the same whether the answer is reassuring or concerning.

Self-critique: I went in expecting to either confirm or dismiss my own concern with real numbers, and I came out with neither, just confirmation that the number isn't public yet. That's a different, weaker finding than what I set out to get, and I'd rather say that plainly than stretch the emission table into a conclusion it doesn't support.

$BABY holders are effectively underwriting that transition without being shown the model for it.

I'd want that crossover point published, even roughly, before treating current participation levels as anything more than emission-subsidized. #baby