Pinned Tweet
Hi $kas, I had to change my host for my Kaspa visualizer. Update your bookmarks please sorry. I don’t purchase domains ;)
kas-music.pages.dev
#kaspa
2
16
949
Kurchack 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.
Kurchack retweeted
Replying to @KaspaClass @KaspaDollar
widespread adoption of miner attestation oracle services, aka RTD, should definitely be an incentive for Kaspa miners and the Kaspa community to decentralize mining to the maximum, assuming we want to propose and showcase to the world the real value this attestation system can provide.
my point is, don’t analyze the current situation as a given, but rather use this opportunity and incentive to change the state of affairs. want to sell to the world realtime decentralization as a service? influence it!
Kurchack 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.
Kurchack retweeted
🏁💚BIG RESPECT TO TRIAGE!
@ExTriage turned down €15,000 from Bitcoin maxis to replace the Kaspa Testnet branding on his rally car with the Bitcoin logo! 💪
He chose loyalty to the Kaspa community over money!
Watch the clip below
Let's show him some love and support the Kaspa Rally Car! 🏎️🚀
☕ Kaspa Coffee & 💸 Revolut donation links below 👇
#Kaspa #KAS kaspa:native
Kurchack retweeted
$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.
2 months left, and @KaspaDollar needs over 4.77+ million more Kaspa to be donated for a decentralized native L1 stablecoin. That’s over 78,000+ kaspa:native day, and at this pace, WE AREN’T going to make it…
This is something the #Kaspa community has been yearning for, and now has the chance!
A native L1 decentralized stablecoin will unlock a plethora of DeFi capabilities for useful applications being built on Kaspa.
This initiative is a MAJOR step towards that adoption we all want. But it requires YOU to take the initiative in donating.
Let’s make history. Let’s make it happen.
✌️
Kurchack retweeted
Bitcoin had Miami.
Ethereum had DEVCON.
Now it’s Kaspa’s turn.
Introducing the Kaspa Conference: a 4-day experience bringing together builders, investors, and the $KAS community.
And we’re investing up to $1,000,000 in Kaspa startups.
Here’s what we’re building. 🧵
Replying to @Crypt0Proselyte
No. Pure PoW is not locked into slow confirmations. GHOSTDAG generalizes Nakamoto consensus to a blockDAG that retains every honest block instead of orphaning them. Kaspa runs this at 10 blocks per second: transactions enter in a fraction of a second and reach strong probabilistic finality within a few seconds, all while remaining pure PoW with a fair launch, no premine, and no trusted parties.
Kurchack retweeted
argent now has a first implementation of covenant genesis proofs:
github.com/argent-lang/argen…
idk how to emphasize this enough, but i expect *every stateful covenant* deployed on kaspa to eventually provide such a proof.
the goal is a verifiable link from a covenant id back to the source code, deployment parameters, and genesis state that produced it.
we should strive for an ecosystem where explorers expose this proof data for every covenant id they discover onchain, assuming its deployers want public trust.
think of it as the analogue of contract verification on etherscan, extended to stateful covenants: you should be able to inspect what a covenant is, audit the code behind it, and verify how it was instantiated.
kudos to @supertypo_kas for being an early-bird example of such a proper deployment process:
github.com/supertypo/dotk-in… (not sure if the sil contracts themselves are public yet)
Kurchack retweeted
I want to share something I’ve been working on that I'm calling OpenMiner.
My goal is to understand the chips that power our miners, share what we learn, and use that knowledge to build open software and hardware.
Today, I’m making the OpenMiner Reference repo public. This is the research and documentation repo, starting with my work on the BM2382 chip inside the Bitmain KS5. It covers communicating with the chip, initializing it, sending mining work, and reading its responses, including what I’ve tested and what I still don’t know.
I hope it grows to cover more chips, manufacturers, and miner models. My focus is Kaspa, but I want OpenMiner to be useful for all miners. Other people have different hardware and interests, and I’d love for their research to become part of it too.
I see three stages to this work:
1. Understand the chips. Learn how they work and document that knowledge so others can use it.
2. Take control of our miners. Build open software for existing hardware. I’d like to explore detailed logging and diagnostics, remote monitoring, custom fan and temp controls, and automatic power management based on schedules, electricity prices, solar availability, or other triggers. Over time, I’d also like to work towards power limits, efficiency tuning, undervolting, and overclocking, so we can choose how our miners run.
3. Build new hardware. Explore taking chips from existing miners and putting them into new form factors. Maybe, over time, that leads to miners of our own.
A lot of my inspiration comes from Bitaxe and the people who have contributed to open mining hardware in the Bitcoin community. I have huge respect for that work and would love to see more people able to experiment with mining hardware themselves.
Later, I’ll share the OpenMiner platform repo, where I’ve been turning this research into an open source, modular mining platform. I want it to support different miners, with compatibility growing as we learn about and test more hardware.
I’m going to keep working on this. I’m sharing the reference now because others might want to join in, whether that’s investigating another chip, improving the docs, writing software, or designing hardware.
I’ll be focusing on Kaspa. If your interest is elsewhere but still would love to contribute, I’d love to hear from you too.
github.com/elldeeone/openmin…
if anyone wants to contribute to the open source documentation, please start here: nitter.gq/IzioDev/status/2100178…
about the section under "programmability", it seems right to only mention L1 apps (=covenants) and based app (or another term), while only surfacing zk-based rollup that is fairly niche/advanced in term of need.
overall everything that has been written still seem correct, we just now have better abstractions to describe them without entering too many details.
Replying to @IzioDev
want to take part of this journey?
help shape the next documentation site, my suggestion would be:
- Argent: Getting Started
- Specialized cookbooks/recipes highlighting a specific design or technique
- Concept section
my personal acceptance criteria (and please challenge them):
- no unnecessary jargon: a builder landing here wants to iterate fast, they don't want to enter a complexity-realm that gives no net benefit. if a term is required: Concept section, if not, abstract the lang.
- human friendly content (that happens to also be LLM-friendly content): e.g.: a getting started must be enjoyable/friendly, no friction, no verbosity.
- diagrams are helpful if built correctly, use mermaid and avoid unnecessary introduction.
overall, the docs shouldn't describe Argent nor how it operates but: how to use it.
you can either produce plain markdown documents or PR to this repo below, keep in mind it'll be entirely re-shaped, it's unlikely we'll keep any of the existing content that is programmability-related (but we can get inspiration from).
github.com/kaspanet/docs
It’s finished.
Over the past weeks, I’ve been working on a video about Kaspa. Not just about speed, but about the idea behind it, the technology that makes it different, and what can now be built on top of it.
From BlockDAG and GHOSTDAG to programmability on Layer 1, this is my attempt to tell that story in a way that goes beyond technical specifications.
Built with respect for the people who made it possible.
A sincere thank you to the developers, researchers, and contributors who continue to build, refine, and push Kaspa forward.
@kasmediadotcom
@michaelsuttonil
@hashdag
Build on the future. Build on Kaspa.
kaspa.org/
Kurchack retweeted
Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday.
You can play it here: vprogs-tt.izio.fr/
(Requires private key and some testnet funds)
We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately
I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top
For Devs: this is the invitation. Play the game, read the code, build your own vprog.
Game code: github.com/biryukovmaxim/vpr…
vprogs framework: github.com/kaspanet/vprogs/t…
Kurchack retweeted
huge honor but I’m also nervous ngl
Kurchack retweeted
Another great one is kaspa:native.
This one signaled a bottom was happening at the low, as there was a strong bullish divergence in play.
Since then: continuation with higher highs, higher lows and constant flips of the levels.
I don't think that this will stop soon, especially if this takes out the recent high, the next target for me is $0.0743.
Kurchack retweeted
Kaspa v2.1.0 is out [Link in the reply]
All node, mining, and infrastructure operators across mainnet and testnets are strongly encouraged to upgrade.
This release introduces P2P Protocol Version 11, extracts a standalone ZK SDK, and reflects an ongoing focus on proactive defense-in-depth across the node architecture.
Key Highlights:
• P2P Protocol Version 11 & Chunked IBD: Large Initial Block Download (IBD) payloads (including Pruning Point Proofs, headers, and trusted data) are now streamed in 20 MiB chunks. This eliminates message-
framing bottlenecks and timeouts during node sync, backed by overall safety limits and transfer timeouts, while maintaining full backwards compatibility with Protocol 10 peers.
• Standalone ZK SDK: Zero-Knowledge proof and script-generation tooling has been extracted into a dedicated crate (kaspa-txscript-zk-sdk). It adds support for RISC Zero Groth16 and STARK verifier generation
with dynamic or static image IDs, bounds control proofs against oversized inputs, and resolves cross-platform build issues.
• General Hardening: Comprehensive defense-in-depth upgrades across the node, including stricter P2P message and block limits to guard against DoS vectors, a workspace-wide arithmetic safety audit to
eliminate overflow risks, enhanced stratum bridge stability, and tighter consensus validation.
These structural safeguards significantly strengthen node resilience and provide higher confidence in overall network security.
this KIP-12 is superseded by KCC-12.
goal: dApp doesn't need to integrate browser wallet 1 by 1.
If you own a dApp (/want to), or you own a browser wallet, please read the proposal and add your thoughts (not LLM thoughts, we can do that on our own)
Kurchack retweeted
just a gentle reminder that krc20 is not kaspa L1, it only travels over L1 txs as data carriers, but the interpretation of krc20 state is done purely offchain just like any other non-zk based solution. this is why covenants were developed for kaspa L1 with kcc20 built on top of them for native assets (note: kcc20 spec is still in draft)
Kurchack retweeted
They lying to you when they say first movers always win #blockchain #crypto #proofofwork bitcoin:native #kas


























