bvdon 𐤊 (@mrbvdon) header
bvdon 𐤊 (@mrbvdon) profile picture

All opinions/comments are my own, good and bad. I have no affiliation with any entity.

USA
Joined May 2016
Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)Photo by bvdon 𐤊 (@mrbvdon)
kUSDT Trestly calls kUSDT the first native USDT on Kaspa. Three signers can mint past the vault. 9,399 minted, 3,380 released Up to 100,000 in one mint Vaults sit on Ethereum and BNB Chain A bridge float with a mint switch, not a Tether line. theindustryspread.com/trestl…
2
7
26
574
bvdon 𐤊 retweeted
Major speed story in proof of work ⚡ @kaspaunchained uses blockDAG tech to process multiple blocks at once, with no premine or presale. Here's what makes $KAS one of the fastest open-source chains around. See why ⬇️ bsc.news/post/kaspa-blockcha…
4
23
122
1,693
bvdon 𐤊 retweeted
🚨 NEW Episode w Toby from @st0x_io "Kaspa is Getting Tokenized Stocks" Full Video - youtu.be/syZxEULJruc @st0x_io brininging $150 Trillion Market OnChain CC @AppKaskad + @AlpacaHQ making it happen. kaspa:native
2
34
6
117
2,843
bvdon 𐤊 retweeted
Kaspa will be the final currency to exist when DAGKnight ships, not because nothing else will launch, but because there will be nothing left to redesign. Bitcoin's 10-minute block and Kaspa's current GHOSTDAG are both built on a hardcoded guess about internet latency, while DAGKnight drops that parameter: it reads latency from the DAG itself, keeps 50% hashrate security, and gets faster as the internet does. Once it lands, Kaspa's consensus stops needing a next version. Let that sink in. End game.
3
73
7
302
4,496
so do you all see it now, or is it still sinking in? ;)
After playing around with my Argent compiler (multi-app multi-contract compiler to Silverscript) for several days now, my belief that interesting and rich partitioned-state defi with atomic composability is possible on pure L1 UTXO rails is growing stronger by the day
19
113
1
522
14,203
I've looked more closely at the Token Depot and AMEKAS vision. I like that their plans include not only technical infrastructure but also commercial opportunities, including online stores. This is an important direction. But I believe we need a clear strategy for turning these stores into entry points for ordinary people. Here is how I imagine it working: 1. A customer visits an online store and finds a product they actually need. 2. Prices are displayed in the local currency, with the equivalent in KAS. 3. The customer adds the product to the cart and clicks "Pay". 4. Payment is made exclusively in KAS. 5. If the customer doesn't have a wallet, they need an easy way to open one right there. If they don't have KAS, they need a simple way to purchase the required amount. 6. They complete the payment and receive their order. We could also offer an additional incentive: a 5% discount when paying in KAS, automatically applied at checkout. This gives customers an immediate financial reason to use KAS. The important part is that people don't need to know anything about Kaspa before visiting the store. They come to buy something they need. The payment process introduces them to KAS, helps them open a wallet and acquire their first coins. Start small. Offer affordable, useful products, keep prices competitive and build sales volume. Even if the first purchases are modest, this is how new wallets are opened, KAS is purchased and real transaction activity begins. Over time, customers return and bring others. One investor can bring capital. A thousand ordinary users can help build an economy and bring thousands more. We are approaching a time when cryptocurrency will become part of everyday life. There are still so many people who have heard about crypto but don't actually use it. Instead of waiting for them to find their own way into the ecosystem, we should build that road for them. Give people what they want, make it easy for them to come in, and in return, we get what we want: new users, wallets, purchases and real demand for KAS. #Kaspa #KAS #CryptoAdoption #MassAdoption #RealWorldUtility #KaspaEcosystem
6
12
1
46
911
This weeks Kaspa dev update from @kaspaunchained. $KAS xitter.gq/kaspaunchained/status/…
a few things you might’ve missed while the devs were busy this week. 1 / KOB @crono_walker launched a testnet order book built with SilverScript and Argent. lets people place buy and sell orders for tokens, with Kaspa L1 contracts enforcing the trading rules. open to try on testnet-10. xitter.gq/crono_walker/status/21… 2 / home nodes @OriNewman proposed a Rusty Kaspa update to help nodes behind home routers connect to each other without manually setting up port forwarding. still under review. github.com/kaspanet/rusty-ka… 3 / prediction markets @manyfest_ shared work with @maxibitcat on a permissionless prediction market built with Argent. predictions would be tradable tokens, with a voting system to settle outcomes. still in development. xitter.gq/manyfest_/status/21204… 4 / HardKAS @HardKASOfficial is building a practice environment for Kaspa app developers. it lets them send test payments and try out smart contracts on their own computer, using coins with no real value. the idea is to find bugs before real money is involved. still experimental. xitter.gq/HardKASOfficial/status… 5 / notes for coding agents @KasperoLabs published a free guide for AI agents building on Kaspa. covers wallets, payments, SilverScript and mistakes found while building real projects. xitter.gq/KasperoLabs/status/212…
3
17
68
783
bvdon 𐤊 retweeted
a few things you might’ve missed while the devs were busy this week. 1 / KOB @crono_walker launched a testnet order book built with SilverScript and Argent. lets people place buy and sell orders for tokens, with Kaspa L1 contracts enforcing the trading rules. open to try on testnet-10. xitter.gq/crono_walker/status/21… 2 / home nodes @OriNewman proposed a Rusty Kaspa update to help nodes behind home routers connect to each other without manually setting up port forwarding. still under review. github.com/kaspanet/rusty-ka… 3 / prediction markets @manyfest_ shared work with @maxibitcat on a permissionless prediction market built with Argent. predictions would be tradable tokens, with a voting system to settle outcomes. still in development. xitter.gq/manyfest_/status/21204… 4 / HardKAS @HardKASOfficial is building a practice environment for Kaspa app developers. it lets them send test payments and try out smart contracts on their own computer, using coins with no real value. the idea is to find bugs before real money is involved. still experimental. xitter.gq/HardKASOfficial/status… 5 / notes for coding agents @KasperoLabs published a free guide for AI agents building on Kaspa. covers wallets, payments, SilverScript and mistakes found while building real projects. xitter.gq/KasperoLabs/status/212…
Here's a library to help your AI agent build on Kaspa safely. github.com/kasperolabs/kaspa… Best practices, code snippets tested on mainnet, lessons learned and failure modes, from building wallets, covenants, an indexer, token launchers, payment flows and a red team tool. It's written for coding agents to read before they write code, whichever one you use. What's in it: - Wallet safety: drainer patterns, signature modes, wrong-network and wrong-account traps - Sending and signing KAS from code: the fee rule, storage mass, SDK calls that work - SilverScript covenants: syntax, design principles, worked patterns - KCC-20 tokens: identity by covenant ID, metadata, supply, lookalikes - Token launchers: name rules, safe metadata and images - Supporting Kasware, Kaspire, Kastle, hosted and phone wallets - Accepting a KAS payment and checking it on chain - Red-teaming a covenant before it holds money - An error lookup: the node's message, its meaning and the fix - A failures log, each entry with the rule it taught It scales to the project. A tip jar and a hosted wallet need different things, and the first file helps your agent pick how strict to be. To use it, tell your assistant: "Read github.com/kasperolabs/kaspa…, start with 00-agent-rules.md, then the files for what we're building." Free and MIT. Corrections and additions welcome as issues or pull requests.
10
112
9
412
21,208
bvdon 𐤊 retweeted
Kaspa went from promising project to serious Layer 1 contender! ⚡ @kaspaunchained runs a fresh take on Proof-of-Work, and $KAS has standout features most chains lack. Here's what really sets it apart. Read now ⬇️ bsc.news/post/kaspa-kas-anal…
2
33
189
2,963
bvdon 𐤊 retweeted
Here's a library to help your AI agent build on Kaspa safely. github.com/kasperolabs/kaspa… Best practices, code snippets tested on mainnet, lessons learned and failure modes, from building wallets, covenants, an indexer, token launchers, payment flows and a red team tool. It's written for coding agents to read before they write code, whichever one you use. What's in it: - Wallet safety: drainer patterns, signature modes, wrong-network and wrong-account traps - Sending and signing KAS from code: the fee rule, storage mass, SDK calls that work - SilverScript covenants: syntax, design principles, worked patterns - KCC-20 tokens: identity by covenant ID, metadata, supply, lookalikes - Token launchers: name rules, safe metadata and images - Supporting Kasware, Kaspire, Kastle, hosted and phone wallets - Accepting a KAS payment and checking it on chain - Red-teaming a covenant before it holds money - An error lookup: the node's message, its meaning and the fix - A failures log, each entry with the rule it taught It scales to the project. A tip jar and a hosted wallet need different things, and the first file helps your agent pick how strict to be. To use it, tell your assistant: "Read github.com/kasperolabs/kaspa…, start with 00-agent-rules.md, then the files for what we're building." Free and MIT. Corrections and additions welcome as issues or pull requests.
9
44
3
116
11,469
When vProgs fully land on Kaspa $KAS, it’s going to be a big deal. Most smart contract chains work the same way: every node re-runs every contract’s code, so the whole network is limited by what one node can execute. Kaspa is taking a different route. With vProgs (verifiable programs), the code doesn’t run on the network at all. It runs off-chain, and you can write real, general-purpose programs instead of squeezing logic into a cramped on-chain VM. What makes that trustworthy is zero-knowledge proofs. When a program runs, it produces a small cryptographic proof that the computation was done correctly. Kaspa doesn’t re-execute anything; it just checks the proof, which is fast and cheap no matter how heavy the original computation was. If the proof checks out, the result is accepted with the full security of Kaspa’s proof-of-work consensus. So the base layer stays lean. It orders transactions and verifies proofs, and the heavy lifting happens elsewhere. Each vProg keeps its own state, so apps don’t fight over one global pile of shared state, and each one only has to prove its own activity. The part I think sets it apart is where this is headed. Other ecosystems do off-chain compute with on-chain proofs too, but they end up with a pile of separate rollups, with liquidity split between them and bridges in between. vProgs are designed so programs can eventually call each other and compose in the same transaction, all sequenced by Kaspa itself, on a fast proof-of-work blockDAG. If they pull that off, I don’t know of anything else that combines all of that.
2
2
2
20
933
Kaspa ($KAS) developers (@maxibitcat, @Manyfestation) are designing an Argent-based, ownerless prediction market app on Kaspa’s base layer, aiming for a fully permissionless forecasting system by around end-2026. 1. The Argent app would let anyone create markets, trade outcome tokens, and vote on results in a decentralized Kaspa-native prediction system. 2. “Ownerless” means no protocol fees or treasury for a project team, with only Kaspa miners benefiting from transaction activity. 3. The design carries real manipulation and loss risks, and the 2026 mainnet target is still a development goal, not a guaranteed launch date.
1
140
🚨 Silverscript v1 is officially out! 🚨 ​This completes the 8 month journey that started with Toccata. We can finally write human and AI readable smart contracts on $KAS. ​What used to take thousands of lines of raw opcodes for an early token mechanism can now be written in just 60 lines of code. It grew from just "CashScript with loops" into a full smart contract language handling complex, stateful contracts. ​Massive step for UTXO programmability on Proof-of-Work. Silverscript is setting the foundation, and Argent is coming next to add higher layers of abstraction. ​Link to the Github release: github.com/kaspanet/silversc…
5
110
6
447
6,580
We only need 5000 people to donated 1000 kaspa to reach 5.000.000 I already did it. Will you help too?
4
12
5
53
886
Kaspa Order Book (KOB) is live on testnet, and it’s pretty amazing to see it in action. Kudos to @crono_walker for the excellent work! Want to try it yourself? Follow the step-by-step guide in the replies below and make your first testnet transaction in just a few minutes. Use $KAS today!
5
8
1
25
1,491
5. Familiarize yourself with the rest of KOB. Main tabs from left to right: • Market tab shows you all the coins that trade in the market. • Trade tab is where you execute and track your trades. • Portfolio tab shows all the assets you have. This includes what is in your wallet, as well as any pending orders that would show as Escrowed balances. So if you have a resting limit order waiting for a fill, that quote asset is escrowed until the order fills. • Activity tab give you all the market stats at a glance so you can see things like trade volume (in KAS), number of trades, orders place, traders active on the site, etc. • Create token tab lets you creat a new fixed-supply token. • Settings tab lets you customize your KOB experience.
2
44
4. Check the "Portfolio" and that should display your tKAS balance. Click on "Trade" and let's buy some TUSD. You will notice the interface looks very familiar, just like a centralized exchange. So, go ahead and place a few buy orders. Try out the numerous order types too. Limit, market, IOC, FOK, etc, stop markets, stop-limit. Feature rich order book! Once your order is placed you can track the status Balances, Open orders,Order history, Trade history. All the familiar features crypto traders expect.
2
57
3. Now that you have some tKAS, let’s try the Kaspa Order Book (KOB). • Go to the Kaspa Order Book. kob.kaspa.ag/ • In the upper-right corner, click Open the app. • Click Connect, then select Connect KasWare. • Enter your password when the KasWare wallet prompts you. Once your wallet connects, you’re ready to trade on the testnet. • Tip: KasWare locks after 5 minutes by default. I changed the timeout to 30 minutes in the wallet settings so I don’t have to unlock it as often.
3
97
2. Next, let’s get some free tKAS to use on KOB. Open your KasWare wallet and click the gear icon to open Settings. Select Kaspa Network, then choose Testnet 10. Click Receive and copy your testnet wallet address. Open the faucet, paste your receive address into the form, enter 10,000 as the amount, and click Submit. Kaspa Testnet Faucet faucet-tn10.kaspanet.io/ Check your KasWare wallet for the 10,000 tKAS. Once the tKAS shows up in your wallet, you’re ready to try the Kaspa Order Book (KOB).
3
112