NguyenDat-KASPA💎 (@NguyenDat_TSVN) header
NguyenDat-KASPA💎 (@NguyenDat_TSVN) profile picture

KASPA - BLOCKDAG SOLVED TRILEMMA BLOCKCHAIN . HYPE VỀ CÁC GIẢI PHÁP KHÁNG MEV , LỚP GIẢI TRÌNH TỰ , GIẢI PHÁP ORACLE , DEFI TOÀN DIỆN QUA VPROG #KAS

Joined April 2023
Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)Photo by NguyenDat-KASPA💎 (@NguyenDat_TSVN)
NguyenDat-KASPA💎 retweeted
Quantum resistant addresses are fully supported within @KaChat_ apps! Anytime you see a green shield on an address it means its quantum resistant. Be mindful that you lose resistance whenever $KAS leaves an address for the first time. Fun fact: quantum resistant addresses start with kaspa:p while non-resistant addresses start with kaspa:q
4
40
4
193
4,051
NguyenDat-KASPA💎 retweeted
kob.kaspa.ag has supported bots and AI agents from day one. 👀 Place, amend and cancel orders from the CLI or over MCP. No API keys, no accounts: your own key signs. Keep the feedback coming! ✨️
3
24
2
68
1,785
NguyenDat-KASPA💎 retweeted
Coming soon: Kozmic Bridge. USDC between Ethereum and Kaspa L1, both ways, verified by zero-knowledge proofs alone. Kaspa checks a proof of Ethereum’s finality; Ethereum checks a proof of Kaspa’s work after your burn. Nothing in the middle holds a key. Deposits land in about 25 minutes, exits in about an hour and a half. Small caps, real USDC, a few more rounds of testing before the door opens.
22
96
12
266
9,584
NguyenDat-KASPA💎 retweeted
I am excited to launch the testnet for the app I have been working on for a long time. It runs on Kaspa L1 and is written in Silverscript and Argent. It is an order book specialized in pure, decentralized characteristics. I look forward to your feedback! kob.kaspa.ag/
25
99
11
261
11,379
NguyenDat-KASPA💎 retweeted
Although "prediction markets" is the standard way people refer to such systems, it has a gambling connotation that I believe is very reductive. Contracts that pay when a specific event comes true can be extremely beneficial for all sorts of risk management activities. You want to open a bar but you're scared of a lockdown? You can buy a token that compensates you if that happens. You make wine and you're scared the summer is going to be too hot? You can protect yourself against that. Basically, you can turn off the risks you're not willing to take and only keep the ones that you're happy to handle. Traditionally such things have always required an intermediary, who decides what events are available, how much they cost and how they are resolved. But at the heart of it, it's just a bunch of people coming together and coordinating around a common need. I'm not completely sure what form this will take, but I don't really see this as an app or a product. It's fundamentally a protocol, a set of open rules that people can use to find themselves and agree on whatever terms they consider useful. Backed by a solid ordering backbone and a design offering some specific guarantees (with limitations that must also be understood).
TLDR- A fully open, decentralized and permissionless prediction market application on Kaspa. In the last few months I have been working with @maxibitcat mapping and coding his proposal for a permissionless prediction market into an Argent app. He proposed a voting resolution mechanism that utilizes a lottery to incentivize the losing side of a binary market to vote honestly (see more in his original post). It felt like a great use case for KCC20 tokens. A prediction is held as a tradable, fungible KCC20 token representing the prediction asset, with extended logic to support voting. A few things worth sharing: 1. Argent is a fantastic tool that enables coding this complex covenant system with ease. This idea could also be written as a single EVM program, but when mapping it to the state machine it actually is, it feels natural and obvious to implement it as a UTXO covenant application (image attached). 2. It’s exciting to draft an application that is completely decentralized and open. Everyone would be able to create and participate in any market they wish, while also running their own application code There will be no owner and no beneficiary. The system is completely open, would only benefit the network miners, and would encourage honest participation. 3. The system’s openness and current implementation tie the security of a market to its size. Small-cap markets could be manipulated more easily. Inevitably, people would lose money in this social experiment. 4. I aim to release a mainnet version around the end of this year.
12
47
2
172
3,436
NguyenDat-KASPA💎 retweeted
Kaspa is the greatest crypto ever built. But that alone is not enough. It’s the builders’ job to turn it into things ordinary people can use. Stablecoins and oracles will answer the liquidity question, or at least make room for it when adoption comes. But adoption itself is in our hands, no one else’s. I think everyone building on Kaspa knows this. I don’t build on Kaspa to get rich. I build on Kaspa because I love Kaspa. To me it is something pure: an alternative to an unstable system, one that already matches or beats that system in places, like programmable money on programmable rails. I believe Kaspa can break out of its small ecosystem and matter to the world at large. That happens the day someone can pay, get paid, and keep their money safe without ever learning what a blockDAG is. So I will build the best tools I can: safe, and written in words people already know. If I could, I would be paid only in KAS from now on. Until that day, my job is to help bring it closer.
10
25
3
74
1,539
NguyenDat-KASPA💎 retweeted
Replying to @asaefstroem
@asaefstroem wouldn't such an oracle service potentially even allow us to run something like NEAR's rainbow bridge, so we could directly onboard USDC ourselves by locking USDC in ETH that become available in KAS as soon as this deposit was attested?
Uhhhh, I like! Having miners include real time data about real world facts directly in their blocks and use them to provide decentralized oracle services, sounds like a really interesting idea. The oracles could become their own economic actors that collect fees for consuming their latest values that could then be re-distributed to the miners that update these values. That would not only create an incentive for miners to actually provide this data but it would also provide a completely new funding mechanism for PoW itself. And I don't even think that you have to constrain yourself to weighing these oracles by the amount of PoW - you could most probably also build an oracle that aggregates existing attestors in other chains like chainlink, or larger dexes to tap into another dimension of existing decentralization. Such a "merge-mining of data" would turn Kaspa into an aggregation layer for all kinds of forms of decentralized trust.
4
47
3
226
4,769
NguyenDat-KASPA💎 retweeted
KaspaDollar whitepaper is now live! Please find it under the /whitepaper page on our website. Do note, that this is a working document that is subject to both internal and external review! As part of this release we also want to talk about why KaspaDollar is not just a stablecoin and why $KAS is the only collateral possible. That is, in this post we want to go through some of the decisions that have been taken so far and the thinking behind them, because a few of them look strange from the outside until you see what they protect. KaspaDollar is not a business. There is no planned revenue that will be extracted from the community and there is neither any developer fee. The deployed contracts will not have an admin key and no central form of control at all. Our goal is to design it into a self-sustaining system that inherits the properties of the base layer itself. Therefore, it should be considered a product designed for the people of $KAS, owned by $KAS miners, if anything. Let’s backtrack a little bit to understand the motivations behind this. Why do we want decentralization and why do we resist censorship? Because there are countless examples of centralized entities abusing their power in their own favor. When it comes to stablecoins we can see this concretely with freezes. A concrete example is when Circle blacklisted the Tornado Cash contracts in 2022, every depositor in those pools had their USDC frozen with them. In addition, Tether blacklisted more than a billion dollars of USDT in 2025 alone. One can argue that most of the cases are in line with a criminal investigation but what prevents a centralized issuer from freezing without proper cause? What is the point of a decentralized PoW if a centralized stablecoin captures the majority of the TVL. Some might argue that this is why we should just stick to $KAS. But $KAS comes with a volatility not every holder can accept. Many people want to offload profits or losses into a stable asset knowing that the value of $KSD will with near certainty equal the same value tomorrow. Everyone in the Kaspa movement has their own reasons for being here, but we believe and hope that all of them are rooted in the core crypto ethos. Kaspa is a PoW-backed L1 with capabilities that exceed any other PoW network, and it is PoW for a reason, because this is the consensus mechanism that has proven to be the most decentralized way of agreeing on chain. Some people point out that mining hashrate on Kaspa, and on Bitcoin, is too concentrated in a handful of pools or miners. That is true, but the same is true of staking on PoS networks like Ethereum with one major difference. The difference is that PoW is actual hardware, an ASIC machine that took years and a tremendous amount of capital to develop that can do exactly one thing, mine $KAS. Attacking a PoW network with hardware you bought means attacking the only income your hardware will ever have. A PoS attacker’s stake can be slashed only for misbehavior the protocol can prove, and voting a false price or censoring a transaction is not one of them. Therefore in a PoS system, the stake could simply be retargeted. Now the reason why $KSD only uses $KAS for its collateral is to bind it to the success and health of the network. The price that $KSD runs on is voted by the miners themselves. So the only party that can attack $KSD is a large miner, and that miner would be doing it in public, against the asset that pays for its hardware. Therefore, the more of Kaspa’s economy settles in $KSD, the more an attack on $KSD is an attack on $KAS itself, and the reward would be in the very asset the attack is destroying. Some have suggested that we should use gold or $ETH as collateral. If we did this, $KSD would actually become more likely to be attacked and exploited. With $ETH or gold the reward would be paid in an asset the attack does not impact. It would also mean that the collateral is no longer on Kaspa at all. Gold on Kaspa is only a claim on gold that is held by a custodian, and $ETH on Kaspa is a claim on $ETH secured by PoS. $KAS is the only asset that exists natively on the base layer, with no issuer and no bridge in front of it. So ironically, through less diversification we get a stronger system, one that is closer to the security properties of $KAS itself. However, we can also not ignore the fact that centralized issuance is needed for adoption. That is why KaspaDollar also creates the infrastructure that any future issuer on Kaspa will need, including centralized ones like @circle or @tether if they ever come. The biggest piece is the oracle itself, a price feed voted by the miners that any Kaspa protocol can read, whether it is a lending market or a DEX. Simply put, providing technical rails that are built and verified by the core team can have a very beneficial stamp of approval, which could make issuance and building on Kaspa less daunting. Consider what Kaspa DeFi would look like if it were built on bridged stablecoins or on stablecoins that originate on an L2. A covenant on the base layer can have flawless security and still hold nothing more than a claim on money that lives somewhere else, with completely different security properties. If the dollar inside it is bridged, its value depends on the bridge’s multisig. If the dollar comes from an L2, its value depends on that L2’s sequencer and the L2’s security. If the L2 has any form of centralized control, then the security of Kaspa’s DeFi inherits the security of an external system, that can be completely disjoint from the original sought properties. Therefore, an important statement is that: the base layer implementation is only as secure as the weakest asset within the protocol. $KSD is the only dollar on Kaspa where both the collateral and the price are secured by the same miners that secure $KAS, and that is what makes it the foundation for Kaspa DeFi.
54
289
27
744
29,059
NguyenDat-KASPA💎 retweeted
Replying to @KaspaDollar
@KaspaDollar’s oracle will power so much more than just $KSD. Think bigger.
18
62
1
274
5,880
NguyenDat-KASPA💎 retweeted
From @IzioDev in Discord. "We encourage node operators who haven't yet upgraded to RK v2.1.0 to do so, especially those running production or mining infrastructure. Over the past three months, we've received roughly a dozen reports from independent security reporters, reflecting a growing interest in reviewing Kaspa's implementation. This is something we want to encourage. Having more independent eyes on the code, challenging assumptions, and finding edge cases is an important part of keeping a decentralized network robust. We're opening the first reward round for the RK v2.1.0 release. You can see the details of the release security-wise here as-well as the reporter credits. Maintainers estimated the following targets: - timestamp underflow: 6,000 Kas. - bech32 panic: 2,000 Kas. - compressed parent DoS vector: 4,000 Kas Totaling in 12,000 Kas. Here is the address for this funding round: kaspa:pzqpl8yauke670565xa2uhkzmg389w5h8x3x7d0fpj3vmy3mjx9y2x0l4vfl7, owned by @michaelsuttonil , @OriNewman and myself in a 2 on 3 multisig. 📆 Deadline is 14 days, 17th November 2026 is the last day after which funds will be proportionally distributed no matter how much has been filled as explained in the first linked message. Thanks to all the maintainers, contributors, and independent reporters who continue to dedicate their time to improving Rusty Kaspa." Links to discussion and details around rewards in thread.
3
34
136
2,145
NguyenDat-KASPA💎 retweeted
Website update! So many questions and so many unknowns yet we are completely blown away by how well the fundraiser has progressed so far, and we hope that the pace will keep increasing! A lot of feedback has been gathered, and the website now describes the proposed idea for how KaspaDollar will function as easy as possible. Most importantly, we would like to introduce our decentralized oracle design which with the help of $KAS miners, will secure the KaspaDollar stablecoin through KIP-21 sequencing commitments. We hope that other projects will follow along and utilize miner payloads as a means of improving miner economics. Let's build the first native PoW-backed stablecoin together!
22
112
9
363
12,664
NguyenDat-KASPA💎 retweeted
get utxos by covenant id, which was a long awaited node feature is now approved. you can build the node from source code and try this feature out now, or wait for upcoming release. WASM support and JS example provided, should be easy to use. just add "--covenant-index" to the arguments list. thanks to @Max143672 for the feature :) cc @kascovio
9
40
4
186
3,947
NguyenDat-KASPA💎 retweeted
Thank you for this tweet, @KaspaSilver. I am going to address your concerns, piece by piece. Concern 1 & 2: "Missing whitepaper, and no R&D" I understand your point about the missing whitepaper. This is still in progress as it needs to be written in a certain way and have the necessary proofs, statements in order to bring the value that a whitepaper does. It is totally acceptable to be wary of donating before you see a concrete spec. The reasoning behind opening the fundraiser before those are finished is primarily for brand awareness, the fundraiser progress so far has exceeded my expectations. It is not the case that no R&D has been done earlier, in fact I have been working on the stablecoin initiative for the last 6 months already, where primarily focus has been on communicating with centralized issuers. Unfortunately, centralized issuers are resistant to deploying on Kaspa for primarily two reasons: 1. because of the lack of anticipated volume. 2. because the needed infrastructure is missing. I, of course disagree with this statement as there can be no volume without DeFi, hence it is a chicken and egg problem. The implementation of @KaspaDollar, would therefore not be "just a stablecoin from scratch" but a: 1. fully decentralized stablecoin 2. build the needed infrastructure that centralized issuers need in order to operate 3. bring the first needed volume in order to validate Kaspa's DeFi potential that is needed for issuers to bring their assets. Therefore, @KaspaDollar is indirectly an effort to bring USDC/USDT onchain. Concern 3: "Decentralized stablecoins are problematic." Decentralized stablecoins utilize a decentralized asset as collateral, this means they are backed by whatever the collateral is most usually traded against, which for now is the U.S dollar. When it comes to regulation the situation is complex, however we can break it down: 1. Looking at EU, MiCA (Regulation (EU) 2023/1114), Recital 22 it is stated that: "where crypto-asset services are provided in a fully decentralised manner without any intermediary, they should not fall within the scope of this Regulation" and "where crypto-assets have no identifiable issuer, they should not fall within the scope of Title II, III or IV". 2. Looking at, US, GENIUS Act (signed July 18 2025), Sec. 2 defines a "payment stablecoin" as a digital asset whose issuer is obligated to convert or redeem it for a fixed amount of monetary value. In our case, @KaspaDollar has no identifiable issuer. 3. The freeze/blacklist requirement you are referring to is Sec. 4(a)(6) of the same act, and it applies to "permitted payment stablecoin issuers", i.e. centralized issuers like USDT and USDC. 4. Freeze and blacklist functions exist because a company holds USD in a bank and is a regulated entity. There is neither a bank account behind @KaspaDollar nor a company behind it. There will be no developer fees and no upgradability. This will also apply to the oracle itself. Concern 4: "Decentralized stablecoins are hard to list on exchanges" The current market situation says the contrary: 1. DAI/USDS is listed on Binance, Coinbase, OKX, Bybit, MEXC, Kraken etc. and has no freeze functionality. Now it is true that they have the possibility to enable this, but at its current stage it is still unfreezable yet listed on most major CEX's. But more importantly, a CEX listing is not the goal for @KaspaDollar and having this expectation, misses the point what it is for. DAI was not built to be traded on Binance, it existed so that Ethereum DeFi had a stable value of account that lived onchain. Following its creation, everything else was built on top of it. On Kaspa, we have the same gap today: 1. there is no dollar on L1, 2. no stable pair for a DEX, 3. no stable asset to lend or borrow against, 4. no way to take profit without leaving the chain, 5. no reason for anyone to build any of that. Every DeFi primitive starts with a stable unit of account, and there is not going to be one from a centralized issuer without having seen some kind of evidence that sufficient volume is to be expected. Therefore, @KaspaDollar is the first one to take on that risk. So the order that I believe in is not: "get USDT, then DeFi". It is "create a decentralized native stablecoin, build the DeFi, show the volume, and then the issuers come".
$KAS I just want to share why I personally have not donated to KaspaDollar yet and hoping I can get some more information. First off I think its not good to ask for funding without a whitepaper or much more guidance on how things will work. To me it appears as give us the money and then we will research and figure out how achievable the goals we want. Secondly, I truly believe we do not have time to be spending our resources on a brand new from scratch stablecoin. To me all efforts should be spent on getting native L1 support for already established USDT and USDC stablecoins. Third, from what I can tell the goal is to make this stablecoin trustless. This means there is no way to freeze or blacklist addresses. This is a problem. Stablecoins are backed by the dollar and typically require those features in order to prevent money laundering and follow regulation. This means that if development moves forward for this we will not see this come to life without a few years of wait time. The reason for this is because this stablecoin would not be easily listed on popular exchanges. The only way to obtain it will be via DEXs which for Kaspa as far as I am aware we do not have proper DEXs if they do exist they lack accessibility. These are my thoughts. Please if you have more information surrounding this leave them below.
51
149
21
475
27,878
NguyenDat-KASPA💎 retweeted
I made kaspa-redteam, a tool for builders: drop a .sil, it attacks every spend path it can reach with known exploits and reports what Kaspa consensus let through. Free to use, files aren’t stored. redteam.kasperolabs.com
11
30
6
99
6,208
NguyenDat-KASPA💎 retweeted
Kaspa Orderbook DEX has no central operator. It is decentralized, with competing "Executors" vying to process transactions. We are currently building an "Executor App" for Windows, Linux, and Android.
2
14
37
1,018
NguyenDat-KASPA💎 retweeted
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem. We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build. Come build with us.
25
277
39
736
74,558
NguyenDat-KASPA💎 retweeted
Kaspa Privacy Initiative — Another Exciting Step! 💚🚀 Just yesterday, we demonstrated private KAS payments on Kaspa TN10. Now we've tested something equally important: what happens if the original operator disappears? And it worked! 🎉 ✅ Original application controller disabled ✅ State successfully reconstructed from public blockchain history ✅ Alice and Bob restored their wallets from backups on a separate Linux computer ✅ Bob recovered and withdrew 4 native test-KAS ✅ Alice recovered and withdrew her remaining 6 test-KAS ✅ All 6 GPU-generated ZK proofs verified and accepted on TN10! All funds recovered. Nothing left stranded. This is another encouraging step toward optional, self-custodial privacy for native KAS. No new token, no custodians. Still experimental, with more decentralization and privacy work ahead, but we're getting closer! Full results: github.com/olafweller/kaspa-… Thanks to everyone supporting this open-source journey! 💚 Follow our progress or support KPI at kpi.cash Let's keep building! 🚀
8
112
10
380
7,036
NguyenDat-KASPA💎 retweeted
I believe we will eventually add native pqdsa support, but this is only the first step. (btw, it's possible to implement pqdsa with kaspa script, see github.com/biryukovmaxim/kas…)
2
16
49
660
NguyenDat-KASPA💎 retweeted
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending github.com/kaspanet/kips/blo…
40
194
15
541
27,742
NguyenDat-KASPA💎 retweeted
Kaspa Privacy Initiative — From ZK Proofs to Real KAS Payments! 💚🚀 This is getting really exciting! Just days ago, we celebrated generating our first complete zero-knowledge execution proof using a rented GPU. Now we've taken the next step. We've successfully completed a full private payment test on Kaspa TN10! And this time, real test-KAS moved on-chain. ✅ Alice started with 10 private test-KAS ✅ She privately sent 4 KAS to Bob, keeping 6 in change ✅ Four ZK proofs generated on GPU and independently verified ✅ All four TN10 settlements accepted ✅ Bob actually received 4 test-KAS! We also confirmed that invalid payments and attempts to spend funds twice are rejected. We're moving beyond proving individual components to making them work together on Kaspa. And that's pretty exciting! 👇
11
109
11
395
6,627