A community-centric channel amplifying the real-world impact, everyday benefits, & the people powering adoption. Kaspa: Empowering People | Powering the Planet
The Earth
Joined March 2025
- Tweets2.7K
- Following841
- Followers5.4K
- Likes4.6K
Kaspa Commons retweeted
hashdag (“Opening the Pandora box” with Ori Newman) & myself (DAG Knight), speaking here next
Mid-Chain @ BGU · Part 2: Sessions 3–4, Noam Nisan & Yehuda Lindell xitter.cf/i/broadcasts/1YGNrbwdZ…
Great PR, @cryptosione !
Crypto is back in Israel’s national conversation. ⚡️
Earlier this year, KaspaCom CEO @cryptosione appeared on national economic TV to talk Kaspa, its technology, and adoption.
Tune in. 👇
Drifts like a dream, @ExTriage !
Hello, Kaspians! 🏁💚
Today we tested the new ECU tune on the Kaspa Rally Car, and the difference I felt was huge: much more low-end torque and a much sharper response!
Before, the engine only seemed to wake up at high revs. Now it pulls from low revs all the way to the limiter. When left-foot braking, as soon as I release the brake, the car pulls straight away. We’re still fine-tuning everything, but today’s testing definitely put a big smile on my face! 😁
Tomorrow there’s more work to do: adjust the hydraulic handbrake and realign the car, reviewing the rear camber and toe to make the rear end more predictable when it starts sliding.
I didn’t push too hard today… this clutch has definitely seen better days 😅
If we manage to complete the StagHunt, it’s going to be a real race against time: remove the gearbox for an overhaul, replace the clutch while it’s out, and strip down the differential to switch to a 4.44 final drive. Even with the 3.91, the gearing still feels too tall for what we need.
Every test shows us what has improved and what still needs work. We’re getting closer, and none of this would have been possible without you.
A heartfelt thank-you to everyone donating, sharing, helping and continuing to believe in this project. 💚🏁
If you’d like to follow, share or support the project:
🏁 StagHunt:
staghunt.app/bounties/bnty-m…
☕ Support the team:
kas.coffee/kasrallyteam
💳 Revolut:
revolut.me/extriage
🌐 Project website:
kasparally.com
Built by the community. Driven by purpose. 🏁
#Kaspa #KaspaRally #PoweredByKaspa
💵 KaspaDollar
15 Questions for the Development Team!
The new @KaspaDollar initiative, led by Kaspa core developer @asaefstroem, with support from the core team as described in its announcement, is exciting news for the Kaspa ecosystem!
#Stablecoins will play an important role in bringing decentralized finance, payments, lending and other financial applications to Kaspa.
Most of us are familiar with $USDT and $USDC, which rely on centralized issuers and reserves of traditional financial assets to maintain their dollar backing.
KaspaDollar is proposing something different: a decentralized, overcollateralized stablecoin.
Closer comparisons are existing DeFi stablecoins like $DAI, Liquity's $LUSD and its newer $BOLD. Each takes a different approach to collateral, stability, redemption and governance. DAI also incorporates centralized stablecoins and real-world assets into its backing.
The KaspaDollar team has already published its initial roadmap, including a 5 million $KAS development fundraiser, testnet plans, independent auditing and a targeted September 2027 mainnet launch.
At @Kaspa_Commons, we're excited to follow this development and help our fellow Kaspians understand how it could work, what makes it different, and what opportunities it might create.
We've put together 15 questions covering the technology, economics, funding, decentralization and adoption.
These aren't demands for answers or assumptions about decisions the team has already made. We're genuinely interested in digging deeper, learning alongside the community and understanding the thinking behind what's being built.
We recognize that some answers may still be taking shape through research and development. We'd love to hear from the team as that work progresses, and hopefully turn their responses into an ongoing Q&A that everyone can learn from.
No rush! Excited for this next year!
And of course, we'd love to hear what questions our fellow Kaspians have too!
🧵 1/5
kaspadollar.com
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
⚙️ BUILDING KASPADOLLAR ON KASPA
Kaspa's BlockDAG, UTXO architecture and expanding L1 programmability offer a different technical foundation from the account-based smart contracts used by Ethereum stablecoins.
We're particularly interested in how the team intends to put these capabilities to work.
8. How will KaspaDollar operate on Kaspa's L1?
Kaspa's UTXO architecture differs significantly from Ethereum's account-based model.
How will KaspaDollar manage collateral positions, stablecoin issuance, redemptions and protocol accounting?
Will these functions operate directly through L1 transactions and covenants, or will certain operations require additional infrastructure?
How might the architecture handle increasing numbers of users and collateral positions without creating unnecessary shared-state bottlenecks?
9. What advantages could Kaspa's technology provide?
Toccata brings capabilities including covenants, introspection, covenant IDs and ZK verification.
Which of these will be essential to KaspaDollar's initial implementation?
Could Kaspa's BlockDAG architecture and L1 programmability offer meaningful advantages in transaction processing, security, scalability or operating efficiency compared with existing decentralized stablecoins?
Looking further ahead, how might technologies such as vProgs provide additional capabilities?
And separately, could future consensus improvements through DagKnight have any practical impact on how KaspaDollar operates?
10. How decentralized can the system become?
One attraction of crypto-backed stablecoins is the possibility of operating without a central issuer controlling the underlying assets.
Will minting, collateral management, redemptions and liquidations be permissionless, allowing participants to interact with the protocol without requiring approval from an operator?
Who will control protocol upgrades, collateral policies and emergency procedures?
Could KaspaDollar eventually operate through largely fixed protocol rules, or will some governance and administrative functions remain necessary?
11. How will users independently verify the system?
The published roadmap includes independent security auditing, which is encouraging.
Will anyone be able to verify circulating supply, collateral backing, outstanding obligations and overall protocol solvency directly on Kaspa?
How will ongoing monitoring, security reviews and transparency be handled after launch?
🧵 4/5
🚀 FUNDING, PARTICIPATION AND BUILDING THE ECOSYSTEM
KaspaDollar has a published development roadmap and a 5 million KAS fundraising target.
Getting the protocol onto mainnet is one objective. Establishing a sustainable and useful financial ecosystem around it will be just as important.
12. How will development funding be managed?
The 5 million KAS fundraiser is described as funding for research, development, auditing and integrations, not the collateral backing the stablecoin or the liquidity required to trade it.
The team has also outlined refund provisions if the fundraising target isn't reached by January 1, 2027.
How will the use of funds, development milestones and progress be reported to contributors?
Once initial funding has been used, what mechanisms might sustain the protocol's ongoing development and supporting infrastructure?
13. What opportunities might exist for financial participation?
Beyond donations to development, could users eventually participate as collateral providers, liquidity providers or through stability pools that help protect the system?
Might the protocol generate fees or other economic incentives for those supporting its operation?
How could these opportunities work, and what risks would participants need to understand?
14. How will KaspaDollar connect with the wider financial ecosystem?
The roadmap already mentions wallet integrations and cooperation with other stablecoin providers.
Could KaspaDollar become a common unit of account for Kaspa-based trading, payments, lending and commerce?
What integrations with wallets, exchanges, merchants and existing DeFi applications might be priorities?
And what would an everyday user actually be able to do with KaspaDollar when it launches?
15. What will make KaspaDollar worth choosing?
DAI, LUSD and BOLD have already demonstrated different approaches to decentralized dollar-denominated assets, each with its own benefits, limitations and tradeoffs.
What design choices might KaspaDollar make differently, and where could Kaspa's architecture provide meaningful advantages?
What might distinguish KaspaDollar for developers, businesses and everyday users?
Beyond a successful launch, what would meaningful adoption look like in its first year?
We recognize that many of these answers will develop through research, testing and experience.
At Kaspa Commons, we'd love to keep following the work and sharing what we learn from the team in a way that helps more people understand the technology and the opportunities it could create.
We're excited about what a decentralized dollar could bring to Kaspa and the world, and appreciate the work being undertaken to make it possible. Well done, @asaefstroem and team!
To the @KaspaDollar team, we'd welcome your thoughts on any of these questions as the project develops!
And to our fellow Kaspians, what else would YOU like to know?
🧵 5/5
kaspadollar.com/docs
KD Donation Address
kaspa:qpy0rvs9mkfa66vnhre4dwsc4c0nu8jhvk0jlfzvq7x8pejjezpujpyrwecl6
Bring it.
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
Think of WETH as a claim ticket for ETH held in a shared vault.
With Kaspa’s approach, the actual KAS stays together with its matching token record, 1:1. There’s no shared wrapper vault needed.
If we’re swapping kaspa:native, paying a merchant or moving funds between apps, we want it to work without a pile of extra steps. We also want it to keep working smoothly when everyone else turns up.
@ethereum uses WETH to let ethereum:native work with apps built around the ERC-20 standard. @michaelsuttonil is explaining how KAS could get that same compatibility while keeping the actual KAS with each individual holding, rather than pooling the backing in one wrapper contract.
A potential example - say thousands of people are depositing, withdrawing and transferring funds across different apps. Keeping their holdings independent could help that activity move without adding a shared wrapper bottleneck. There will still be limits in the network and the apps themselves, but this design could help preserve Kaspa’s ability to handle unrelated activity independently.
For someone trading, the hope is less waiting when things get busy. For a business, bank or enterprise market processing lots of payments, it could help keep transactions moving as customer numbers grow.
Developers would also have a common way to work with KAS and other tokens. A swap service could handle KAS through the same basic system it uses for other assets. A merchant app could potentially accept KAS and convert it into a supported #stablecoin at checkout. Customers could pay with what they hold, while the business receives what it needs.
Those services still have to be built, funded and tested. A simpler integration could make them easier to develop and maintain, and give users more places to put their KAS to work.
There’s a liquidity benefit to aim for, as well. If apps agree on one common KAS20 implementation, they could connect to the same trading markets instead of scattering funds across different versions. With enough liquidity, that could mean better prices and less slippage, so users receive closer to the amount they expected when making a swap.
In a nutshell: Individual holdings remain independent, avoiding an additional shared wrapper bottleneck. That could help financial apps handle growing activity while remaining responsive for users.
That gives developers simpler plumbing to build with, which could mean smoother experiences for users as activity grows.
yup. on eth it’s called WETH--an ERC-20 wrapper for ETH. the difference is that all the backing ETH is held under one contract address, while individual WETH balances are tracked in the contract’s storage.
on kaspa, each UTXO simply holds the actual KAS together with the KAS20 state representing it 1:1. there’s no shared wrapper vault or wrapper-level contention. it’s just native KAS managed by a KAS20 contract through the common KCC-20 interface, so the design is more streamlined and there’s no real reason to add a “w”
cc @elperorr
Well done, @AlbertaHashX !
Thanks for helping to secure the network!
DYK?
Canada is one of the world's most prominent hubs for cryptocurrency mining, ranking as the fourth-largest $BTC mining destination globally (trailing behind the United States, China, and Kazakhstan)
And all hail the Canadian 🇨🇦 Kaspains!
Who else is a proud Canuck in here!?
This is a really important milestone because it allows developers to finally start building "composable" apps.
KCC means "Kaspa Calls for Conventions" and it is an effort to define standards that can be shared across the ecosystem.
For apps to be composable, it is not enough that they can call each others functions and observe the results, but they also need to be able to "understand" the data they see.
Instead of having each app manually implement the "proprietary language" of all the other apps, these KCC's establish a "common language" that is understood by everybody.
So while this doesn't introduce new "on-chain" features, it enables developers to write apps that can be composed without the apps having to know about each other.
There will of course be additional standards in the future but these three are arguably the most important ones because they cover the foundations and how tokens / assets are modeled (which is essential for DeFi and anything related to decentralized governance).
Kaspa is growing up so fast! 😱
PS: If you are building on Kaspa, please drop me a DM - I would love to hear about your project!
Come build with us. 👨💻👩💻⚙️ #KCC20
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.
KASPA FIXES THIS is a series from @Kaspa_Commons examining important news developments in technology, finance and industry, the challenges they reveal, and how Kaspa's technology could help address them.
Our goal is to help you look beyond the headlines, understand the real-world problems, discover where Kaspa could offer practical solutions, and recognize opportunities to build, innovate and bring those solutions to market.
👨🔧KASPA FIXES THIS: Centralized Banking Infrastructure
❌ THE PROBLEM
On October 20, a Google Cloud power failure in London disrupted banking services at Revolut, Lloyds, HSBC and others.
Customers experienced problems with payments, transfers, withdrawals and account access.
The incident exposed how dependent modern banking remains on a handful of centralized infrastructure providers.
Interestingly, Revolut is already investing in blockchain-based financial services, including stablecoins and crypto payments. Its EURR stablecoin, issued through Stripe-owned Bridge, is designed to move euro-denominated value on blockchain networks.
Yet access to these services can still depend on centralized applications and infrastructure.
✅ THE KASPA SOLUTION
Kaspa could provide the foundation for financial infrastructure designed to operate independently of any single bank, company or cloud provider.
• Decentralized PoW: Independent nodes maintain a permissionless network without a central operator.
• 10 BPS: Rapid transaction inclusion could support payments and financial settlement.
• Programmability: Covenants and developing vProgs could enable automated payments, conditional transfers and new financial services.
• Institutional resilience: Banks and payment providers could integrate Kaspa while building independent access routes and redundant infrastructure to reduce reliance on individual cloud providers.
• Financial independence: Developers could build wallets, payment applications and financial services that allow people and businesses to transact directly, without traditional banks acting as intermediaries for every transfer.
• Institutional settlement: @KaspaKii's WarpCore initiative is exploring how Kaspa could support decentralized settlement for financial institutions.
Existing financial institutions could use Kaspa to improve the resilience of their services.
Developers could (and are!) building entirely new financial applications that operate without those institutions acting as intermediaries. 👈
Both approaches would require resilient applications, independent access infrastructure and, where necessary, connections to traditional financial systems.
With Kaspa, people and businesses could have more ways to move and manage value, even when individual service providers go offline.
Kaspa Fixes This.
Learn more links below.
👀 whatchya building here, @OverBuildLabs ?
