backasin retweeted
Privacy coming to $KAS 🤯
Bullish!
Major breakthrough for the Kaspa Privacy Initiative! 💚🚀
Yesterday, we hit a serious bottleneck: generating our full zero-knowledge execution proof on CPU was taking far too long.
So we rented an NVIDIA L40S GPU.
And it worked!
✅ Full cryptographic proof in just 4 minutes and 16 seconds
✅ Independently verified on CPU
✅ Invalid operations correctly rejected
✅ Estimated GPU rental cost: just $0.12
For the first time, we've demonstrated that our complete test-model execution can be cryptographically proven in minutes, at a surprisingly low cost.
And that opens up some exciting possibilities. 👇
backasin 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…
backasin retweeted
V3 pools are now live on the Igra network, with router support activating as liquidity deepens.
kaspa:native
backasin retweeted
ZEAL Recovery Update
The Kasplex KRC20 indexer is now operational again, and the custody balances now align across the independent indexers. This gives us enough clarity to publish the current ZEAL supply situation and the recovery measures we are moving forward with.
The original KRC20 supply remains 240,000,000 ZEAL. Of that, 167,187,982.93 ZEAL is held by the bridge custody address and backs ZEAL on the L2s, while 72,812,017.07 ZEAL is held directly by users on KRC20 L1.
On the L2s, Igra currently holds 216,275,848.19 ZEAL and Kasplex L2 holds 48,337,560.83 ZEAL, bringing the combined L2 supply to 264,613,409.01 ZEAL. Since only 167,187,982.93 ZEAL is backed by L1 custody, this leaves a 97,425,426.08 ZEAL supply gap created by the KRC20 indexer incident.
As part of the recovery plan, the first decision we have made is to permanently burn the entire 24,000,000 ZEAL team allocation.
We believe taking responsibility should start with us. Even though the incident did not originate from ZealousSwap, preserving a future team allocation while the community deals with the consequences of the incident is not the direction we want to take. The full allocation will be removed permanently, and there will be no future team unlock.
Farm rewards and Infinity Pool emissions will also remain paused.
On Igra, we will burn 43,794,947.23 ZEAL in Farm rewards that have not yet been distributed and 38,409,590.09 ZEAL in future Infinity Pool emissions. This brings the total Igra burn to 82,204,537.32 ZEAL.
On Kasplex L2, in addition to the full team allocation, we will burn 7,200,000 ZEAL from the Insurance Fund, 4,586,310.61 ZEAL in undistributed Farm rewards and 681,650.32 ZEAL in future Infinity Pool emissions. The total Kasplex L2 burn will be 36,467,960.94 ZEAL.
Altogether, 118,672,498.26 ZEAL will be permanently burned.
This is 21,247,072.18 ZEAL more than the 97,425,426.08 ZEAL supply gap, meaning the gap is covered approximately 1.22x. Following the burns, the maximum ZEAL supply will fall from 240,000,000 to 218,752,927.82 ZEAL.
We also want to be very clear about what these burns do and do not change.
They do not reduce the ZEAL already circulating today. The tokens sold during the incident are now held by users who purchased them legitimately, and those trades remain valid. We will not rewrite what happened onchain or treat those holders differently.
Circulating supply was approximately 118,087,936.62 ZEAL before the incident and is approximately 215,627,642.88 ZEAL today, an increase of roughly 97,539,706.26 ZEAL.
The supply we are burning comes from protocol reserves that had not yet entered circulation. Before the incident, approximately 121.9 million ZEAL was still scheduled to enter the market over time through Farm emissions, Infinity Pool emissions, the team allocation and the Insurance Fund.
After these burns, that future supply overhang is effectively removed.
Approximately 98.6% of all ZEAL that will ever exist is already circulating. The remaining portion consists primarily of Farm rewards that users have already earned but have not yet claimed.
This means there will be no future team unlock from the burned allocation, no future Insurance Fund allocation entering circulation, and no further Farm or Infinity Pool emissions from the reserves being removed. ZEAL’s future inflation from these allocations is effectively eliminated. Approximately 98.6% of all ZEAL that will ever exist is already circulating, with the remaining portion consisting primarily of rewards farmers have already earned but not yet claimed. There is no longer a large emission schedule or unlock overhang waiting to enter the market.
We are still waiting for Igra to provide an update regarding the future of the funds recovered from the attacker, and we will update the community as soon as there is more clarity there.
👇
backasin retweeted
hello again. the devs made things this week and i made a list.
1 / Rusty Kaspa v2.1.0
nodes now download sync data in smaller chunks to avoid bottlenecks and timeouts while catching up with the network. v2.1.0 also includes Stratum bridge fixes and moves the existing zero-knowledge proof tools into their own package.
github.com/kaspanet/rusty-ka…
2 / vProgs
@Max143672 announced the first vProg running on testnet. it’s a playable tic-tac-toe game with real execution and settlement. still a working proof of concept, with public code for devs to build from.
xitter.cf/Max143672/status/21034…
3 / Python SDK
@smartgoo_ released Python SDK v2.1.0. devs can now compile SilverScript contracts in Python and debug them without running a node. it also adds tools for using zero-knowledge proofs, examples and bug fixes. SilverScript support is still experimental.
github.com/kaspanet/kaspa-py…
4 / SilverScript Studio
@KasperoLabs announced SilverScript Studio is live on mainnet. build, compile and deploy covenants from your browser. write them yourself, describe what you want to its AI, or use the wizards for things like vaults, escrow, recurring payments and payroll.
xitter.cf/KasperoLabs/status/210…
5 / KCC23
@manyfest_ explained a proposal for linking details like token names, symbols and images to a covenant, without copying them into every holder’s coins. KCC23 is still a draft and open for review.
xitter.cf/manyfest_/status/21030…
6 / KCC standards
@asaefstroem’s proposal to finalize KCC0 was merged. it sets out how shared ecosystem conventions are proposed and reviewed. he also proposed moving KCC20 into last call review. that hasn’t merged, so KCC20 is still a draft.
github.com/kaspanet/kccs/pul… github.com/kaspanet/kccs/pul…
7 / DNS seeder
@supertypo_kas released DNS seeder v0.9.6, fixing a bug that counted some offline nodes as online.
github.com/supertypo/simply-…
thanks to everyone building. see you next week.
While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined.
On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state.
On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant).
This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it.
A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information.
The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity.
After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself.
Read more on Kas-Smiths:
kas-smiths.org/t/kcc-23-conv…
Or read the KCC draft:
github.com/kaspanet/kccs/pul…
backasin retweeted
⚠️ Status update: what to do if you received unexpected iKAS on 21 September.
Short version:
if you received iKAS from any address on this list, please send it to the Igra DAO Governance contract: 0xB3300fcC2F3EF3DeCdF8B1f710c21666f33Cbf18
explorer.igralabs.com/accoun…
Long version:
The attacker behind the KRC-20 incident sent amounts of 5,000 to 10,000 iKAS to around 35 wallets that seemingly have nothing to do with the attack. This was done to make uninvolved users look connected to it.
You are not under suspicion. Anyone can send to any address and you could not have refused it. Your own funds are unaffected, and exits covered by your own balance and deposits will settle normally.
Funds originating from the attacker cannot be bridged out. The exit settlement operators settle against amounts traceable to your own deposits, so anything traced to the attacker's wallets will not be paid out.
These are stolen funds. Returning them is voluntary, takes one transaction, and costs you nothing you could otherwise use.
If you already moved or spent it, email [email protected] and we'll help sort it out.
backasin retweeted
We are currently investigating a critical exploit affecting the Kasplex KRC20 indexer.
Based on what we know so far, the exploit allows an attacker to create unauthorized KRC20 balances, which were then bridged to Igra and Kasplex L2 and used to drain liquidity pools, including ZEAL and NACHO pools.
We strongly advise everyone not to buy or interact with KRC20 tokens until the issue is resolved, as the exploit may affect any KRC20 token.
We are in contact with the relevant teams and are working to block the exploiter from moving the remaining funds.
More details will be shared as soon as we complete our investigation.
backasin retweeted
To the Kaspa community: you catch more flies with honey than vinegar.
I know you’re passionate.
But you have to remember 2 things:
1. We’re on the same team as bitcoiners (I am both) we priotize and care about the same things. Kaspa is a spiritual successor to Bitcoin. Bitcoin is Kaspa’s ancestor. Yes, it is ossified into SoV only, and is not completing its initial goal as P2P cash, but that’s what Kaspa is for. Don’t hate on Bitcoin, it just is what it is.
2. Bitcoiners are extremely skeptical of any new project claiming to be equal to or better than Bitcoin. There are 10s of thousands of such projects. All trying to market themselves, and tons of people spamming how great it is. Give some grace if Bitcoiners don’t believe you immediately. They see and hear the same things all the time, and usually they’re right to dismiss it as BS. Jumping on them with insults and taunts doesn’t help convert them, it proves them right.
Stay calm, patient, and open. Prioritize education, and meet them where they’re at.
Exactly this isn't a replacing game. Its not zero sum. Its about what kaspa:native offers verses what bitcoin:native offers.
Kaspa offers more freedom so All my efforts are there that simple.
You can hold both. You can hold just one. Doesn't matter. Just hold what actually benefits your life the most and do your own research.
backasin retweeted
Start your KAS mining journey with KuMining! ⛏️💎
Complete daily tasks, purchase hashrate, or invite friends to win USDT, KAS, Nintendo Switch 2, iPhone 17 Pro Max, and up to 10,000 KAS!
Join the campaign now 👇
kucoin.com/campaigns/mining_…
#KuCoin #KuMining #Kaspa #KAS #CryptoMining
backasin retweeted
Questions worth putting to Chainlink Labs publicly regarding the $LINK token.
1. The v0.2 docs (2023) said staking "can" expand to secure CCIP and other services — is there a committed timeline for this, or is it still purely optionality with no roadmap date?
2. Why has the community staking pool cap stayed at 45M LINK since November 2023 despite TVS and CCIP volume both growing multiples since then?
3. Is there a technical or economic reason staking hasn't been extended beyond the ETH/USD feed pilot to other high-value feeds (BTC/USD, or now tokenized equity feeds like NVDA)?
4. What specifically is blocking a "per-service" or "per-feed" staking design, if the modular v0.2 architecture was built to support exactly that?
5. As Robinhood Chain and other tokenized-equity venues scale, is there a plan for staked LINK to economically back those specific feeds, or will feed security continue to rest solely on node-operator reputation with no staker capital at risk?
6. How much of current staking reward is genuinely fee-derived (from CCIP/Data Streams usage) versus still emissions-funded, and what's the trajectory to a fully fee-funded model?
7. Given CCIP's $18B+ quarterly volume, why hasn't slashing/staking been extended to CCIP lanes the way it has to the ETH/USD feed?
8. Is "Total Value Secured" still the right metric to market staking against, if the mechanism securing that value hasn't scaled in step — should the market instead be tracking "value secured per staked LINK" as a decay metric?
9. With LayerZero still moving the majority of cross-chain volume, what's Chainlink's actual timetable for CCIP to convert institutional design wins into comparable throughput share, and how does that connect back to staking capacity plans?
10. Does Labs have an internal target date for a v0.3/v1.0 staking upgrade that moves beyond the current architecture, or is the "modular, future-ready" framing effectively permanent messaging without a delivery deadline?
backasin retweeted
Chainspect posts BS posts (based on who pays them)
When we ask why $KAS isn't there, we get blocked
It's because of players like Chainspect with their "pay to play" model, the entire industry looks like a scam
This makes genuine, honest projects like #Kaspa look like a scam for those who don't understand this industry
Don't be like Chainspect
Replying to @chainspect_app @Algorand @AptosLabs @hedera @dfinity @KaiaChain @KeetaNetwork @MultiversX @RedbellyNetwork @SeiNetwork
What's your $KAS wallet address so we can send you money to post factual statements?
backasin retweeted
I present to you the Proof of Prints ecosystem built for Kaspa! Journey to proofofprints.com/ to get started.
Solo Mining Pool - No fees, no KYC
PoPManager - ASIC and Mobile Mining Management
PoPMobile - Mobile Kaspa Miner on Android
PoPMiner - Soon to come - ESP32 Miner/Companion
All Open Source with NO fees.
Keep in mind this are all Beta products. There still may be bugs. Telegram soon to come per community request.
Thank you for the support as always!
Happy testing!
backasin retweeted
Kaspa has gained a live connection to the broader crypto ecosystem.
Through @Igra_Labs , @hyperlane , and the teams building around them, $KAS now has an active pathway into major EVM networks like @ethereum.
What’s actually happening
-> Igra runs an EVM-compatible Layer 2 anchored to Kaspa
-> Hyperlane connects that environment to other EVM chains
-> Kaspa.com and @ZealousSwap are building applications and liquidity on top
-> @Kaspa_KAT connects Kaspa L1 and L2 for KAS and KRC-20 movement (@kasplex)
Together, this creates a working route between Kaspa and external ecosystems.
Assets can now move:
KAS ↔ Igra (iKAS) ↔ EVM networks
Already in use
Kaspa.com and @ZealousSwap have launched a USDC <> KAS L2 pool
#Stablecoins can bridge into Igra and be used immediately
K.A.T. enables movement between L1 and L2
This is live infrastructure supporting real activity.
Simply put
$KAS now connects into the wider crypto economy through Igra, with applications and liquidity already in motion.
So what
• Stablecoin liquidity can enter and move through the Kaspa ecosystem
• Builders can use familiar EVM tools while anchoring to Kaspa
• Applications, trading, and asset movement are already functioning
How this comes together
This is ecosystem-driven development around the Kaspa base layer:
• Kaspa Core advances real-time settlement at the base layer
• Igra extends that capability through an EVM-compatible L2
• Hyperlane enables cross-chain connectivity
Kaspa.com and Zealous bring applications and liquidity
• K.A.T. keeps value moving between L1 and L2
Where this is heading?
This is a working model built with today’s tools.
As Kaspa evolves with #covenants++ and #KvProgs through #Toccata, builders across this ecosystem may begin moving more logic, assets, and coordination directly onto Kaspa L1.
The roles of L2s, bridges, and integrations can evolve alongside that shift, as more capability becomes native to the network.
The bigger picture
Kaspa is becoming a system that connects, routes, and settles.
This is one working example.
Many teams across the Kaspa ecosystem are building in parallel, shaping how this network is used in practice.


























