nakamoto consensus unchained. digital money traveling at internet speed. non-representative community account.
Joined November 2021
- Tweets2.3K
- Following0
- Followers235K
- Likes2.5K
this week in Kaspa dev. the devs were busy. i took notes.
1 / covenant indexing
@Max143672's covenant indexing, covered last week, is now merged. @michaelsuttonil also added a new query for inspecting the transactions behind those coins. both are awaiting a node release.
github.com/kaspanet/rusty-ka…
github.com/kaspanet/rusty-ka…
2 / KaspaDollar
@KaspaDollar released a working whitepaper for its proposed KAS-backed stablecoin, with vaults and a price feed using miners' votes.
teapaw.org/KaspaDollar/status/211…
3 / Argent
Argent now lets devs add checks when connecting contracts. for example, making sure a new trading pool is set up for the correct token contract.
github.com/argent-lang/argen…
4 / security reporters
@IzioDev shared a community funding round to reward the security reporters whose findings helped harden Rusty Kaspa v2.1.0.
teapaw.org/IzioDev/status/2117633…
5 / kaspa-redteam
@KasperoLabs continued work on kaspa-redteam, adding tests based on real transactions and analysis of deployed contracts without the original source.
github.com/kasperolabs/kaspa…
a community funding wallet has been opened to reward security reporters who contributed in the software hardening, something that should be encouraged further.
here are all the details: discord.com/channels/5991532…
if an app does a big calculation, making every kaspa node repeat it would be a lot of duplicated work.
with inline zk, each action carries its own proof that the calculation followed the programmed rules.
a kaspa covenant checks that proof without repeating the whole calculation, then makes sure the transaction matches what the proof says.
four things from this week in Kaspa dev. intern has kept the technical words to a minimum.
1 / kaspa-redteam
@KasperoLabs released kaspa-redteam, an open-source testing tool for SilverScript contracts. helps devs find bugs in their own contracts and reproduce them while building.
teapaw.org/KasperoLabs/status/211…
2 / Argent
Argent merged a fix so devs can use multiple contracts together without running into errors caused by clashing variable names.
github.com/argent-lang/argen…
3 / covenant indexing
work continued on letting apps ask a Kaspa node which coins belong to a particular covenant. useful for wallets and explorers tracking tokens. this week’s changes keep those searches from asking the node to do too much work at once. still under review.
github.com/kaspanet/rusty-ka…
4 / Mid-Chain talks
@hashdag spoke about “Opening the Strategic Pandora Box”, work with @OriNewman. @michaelsuttonil covered DAGKnight. both at Mid-Chain this week. recording linked in Michael’s post.
teapaw.org/michaelsuttonil/status…
i started here: youtube.com/live/brCCRgMkISw…
Kaspa 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 teapaw.org/i/broadcasts/1YGNrbwdZ…
five things from this week in Kaspa dev. i have numbered them to appear organized.
1 / KCC standards
KCC1, KCC2 and KCC20 are now Final. devs have shared conventions for how covenants, permissions and fungible tokens work together, ready for wallets and apps to adopt.
teapaw.org/kccforum/status/211292…
2 / wallet public keys
@OriNewman proposed a wallet convention that keeps public keys hidden until funds are spent, reducing their exposure to future quantum attackers. originally KIP22, it’s now under review as a KCC. spending still reveals the key.
github.com/kaspanet/kccs/pul…
3 / Kaspa Privacy Initiative
@WellerOlaf shared a private-payment experiment on testnet, followed by a recovery test. wallets were restored and the full test balance withdrawn with the original app controller disabled. the rest of the test infrastructure stayed available. still experimental.
github.com/olafweller/kaspa-…
4 / Kastle
@KastleWallet added support for dotK names. users can view, register and transfer their .k names inside the wallet. the mobile update is rolling out, with name support also available in the extension.
teapaw.org/KastleWallet/status/21…
5 / KaspaDollar
@asaefstroem is leading a new initiative to build an overcollateralized stablecoin on Kaspa, backing each dollar of tokens with more than a dollar of collateral. development, research and an independent audit are still ahead.
teapaw.org/KaspaDollar/status/211…
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.
Kaspa retweeted
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!
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.
come build with us.
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.
a little appreciation for everyone explaining kaspa in a language this intern can’t speak.
将来、十分に強力な量子コンピューターが登場すると、次のような攻撃が可能になる恐れがある
① ブロックチェーン上の公開鍵を取得
② 量子計算で公開鍵から秘密鍵を導出
③ 秘密鍵で取引署名し、資産を奪取
現在のKaspaの標準アドレスは公開鍵が露出しているため、将来的にこの攻撃の対象となり得る
そこでコア開発者Ori Newmanが、新たな改善提案「KIP-22」を公開
公開鍵をハッシュで隠し、送金時まで露出させないことで、量子攻撃のリスクを軽減する
しかも既存のP2SHを活用するため、ハードフォークなしで実現できる設計だ🔥
※ただし、送金時には公開鍵が露出するため、完全な耐量子化ではない
現在は提案段階で、ウォレット側の対応も必要となる
DAGKNIGHTがKaspaの「性能」を進化させるなら、KIP-22は資産の「安全性」を高める一歩
Kaspaは量子コンピューター時代を見据え、長期的な安全性の強化にも取り組んでいる
#Kaspa #KAS #KIP22
