Kaspagent retweeted
Kaspa Privacy Initiative — Development Update
Following my conversation with @michaelsuttonil, we set out to test whether Kaspa's Based Apps and KIP-21 could provide the foundation for a shielded native KAS protocol.
The feasibility PoC on TN10 is now complete!
Across PRs #31–33, we've demonstrated:
✅ Real Kaspa L1 lane ordering
✅ Execution with cryptographic ZK proofs
✅ Proof-based settlement accepted by Kaspa
✅ Rejection of deliberately omitted operations
✅ State reconstruction and successful native KAS withdrawal after executor downtime
This is a significant step forward. Rather than building our own transaction-ordering infrastructure, we can potentially build on capabilities already available in Kaspa.
We've also added a new design principle in PR #34: future protocol upgrades should preserve users' access to their funds and aim to enable privacy-preserving migration between versions.
Now comes the part we've been working towards: actual financial privacy.
Our next milestone is a shielded payment cycle: Alice deposits native test-KAS, privately pays Bob, and Bob withdraws native test-KAS.
We'll begin by designing the private notes, commitments, nullifiers and ZK proof rules needed to make that possible.
The Based App PoC demonstrates technical feasibility within its tested scope. It is not yet a privacy protocol, an independently audited system or a final architecture decision.
But we're moving from proving the infrastructure to building the privacy layer itself.
All research remains open source. Technical feedback and contributions are welcome!
github.com/olafweller/kaspa-…
Kaspagent 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.
👇
Kaspagent retweeted
Congrats to the team on the launch!
Good to see @AppKaskad taking on new markets.
We said we would expand, and now we just did.
Kaskad is LIVE on @RobinhoodApp!
Get your stocks ready!
Kaspagent retweeted
Zealous Swap X V2 is now live on @Igra_Labs ⚡
Better prices on every swap. Automatically.
Kaspagent retweeted
Update from KAT.
The Kasplex KRC-20 Indexer API is back online. See the quoted post below from Kasplex.
We have confirmed that ZEAL and NACHO are the only two assets affected by the KRC-20 Indexer exploit as it relates to bridge operations.
We still recommend that you do not trade KRC-20s until a recovery plan has been put in place and approved by the community. That choice belongs to the community, as it always has.
We are awaiting ZealousSwap’s recovery plan, and we remain committed to supporting that plan as best we can.
NachoNation will hold a series of calls and discussions over the next week or so to explore the options, formulate the best recovery plan, and approve it together.
KAT Bridge remains offline. We expect that to continue at least until a finalized recovery plan is structured and approved by the community. Igra’s DAO decision on the funds they recovered need to be considered as part of that plan.
Thank you for staying with this. The indexer is back, the scope is clear, and the community will decide the way forward.
Kaspagent retweeted
Hello @kasplex , could you please provide an update on the restoration of #KRC20 operations?
It has now been six days since the indexer exploit. The public mainnet API remains unavailable, and affected users and projects in the #Kaspa ecosystem still have no clear timeline for resuming their activities.
According to your latest update, the code fixes were complete, with state rollback verification expected to take 3–5 days.
However, we have not yet found a published fix or a new release in the official go-krc20d repository.
Could you please clarify:
- What has been completed, and what remains?
- When will the corrected source code and new version be published?
- When can users expect the public API and KRC-20 transfers to resume?
A thorough resolution should take priority. But after six days of disruption, clear communication on progress and next steps is a reasonable expectation.
If a reliable ETA is not yet available, please explain the remaining obstacles and let the community know when to expect the next status update.
KRC20 Incident Update:
A vulnerability in the underlying protocol has been confirmed. Code-level fixes are complete, and a hard fork will follow. A full-state revert verification must be completed prior to the hard fork; this process is expected to take 3–5 days.
Public node APIs will be disabled during this period; please do not perform any KRC20 token operations (such as transfers).
For self-hosted nodes, please wait for the release of the new "go-krc20d" version before upgrading.
Kaspagent retweeted
Trading on ZealousSwap is now reopened on Kasplex L2.
With the KRC 20 indexer paused and the affected bridge routes closed, we are comfortable reopening trading on the network.
Igra L2 trading remains open as well.
Kasplex L2 users can now resume trading normally.
Kaspagent retweeted
We want ZealousLaunch to become more than a place to create tokens.
The bigger goal is a creator economy on Kaspa L1 where creators can keep earning from what they build.
Launch an idea, build a community around it, and if the curve graduates, liquidity moves into ZealousSwap automatically. From there, creator royalties continue through swaps on that market.
We want creators to have a reason to keep building long after launch, because the markets they create can keep generating revenue for them.
A launch should not be the end of creator revenue. It should be the beginning.
Kaspagent retweeted
Trustless job submission is a strong direction for agent marketplaces.
The real unlock is making each task verifiable for both the human and the AI.
Excited to see what ERC8183 enables as these workflows move onchain.
Kaspagent retweeted
Replying to @kaspafanatic
Hi, thanks for your support. I will check this in the coming days to see how i can get properly those data with accuracy.
Actually working on ERC8183, to allow trustless and easy job submitting for human and AI Agents on Kaspagent, with great support from @emdin and @argonmining
Kaspagent retweeted
This is huge! Cost for running a node or attester on a VPS just decreased dramatically.
Turns out the full node can travel light: same full verification and 97% less storage.
We previously said substantially lower storage would require a separate light node with different security assumptions.
Well, we got one thing wrong.
Our upcoming upgrade delivers that reduction to the full nodes, with full transaction verification stays intact.
Igra node storage: 1TB -> 30GB.
Storage growth: 150GB -> 4GB per month at current activity.
Running a node and verifying Igra yourself is now practical for far more people.
Node operators and attesters: details and documentation coming shortly.
Decentralize the world!
Kaspagent retweeted
Here we go. Super proud of the team.
Turns out the full node can travel light: same full verification and 97% less storage.
We previously said substantially lower storage would require a separate light node with different security assumptions.
Well, we got one thing wrong.
Our upcoming upgrade delivers that reduction to the full nodes, with full transaction verification stays intact.
Igra node storage: 1TB -> 30GB.
Storage growth: 150GB -> 4GB per month at current activity.
Running a node and verifying Igra yourself is now practical for far more people.
Node operators and attesters: details and documentation coming shortly.
Decentralize the world!
Kaspagent retweeted
$KAS is the 2nd highest gainer in the last 24 hours and is officially back above $1B market cap
Kaspagent retweeted
Technical:
- 200D MA reclaimed (first time since March)
- 48% off July lows
- Silverscript v1 mainnet weekend
Fundamental:
- Real crypto: 6 of 100
- Fair launch + PoW + no corporation
Macro:
- $150T Global M2 record
- Debasement in mainstream vocabulary
Framework holds. kaspa:native
Kaspagent retweeted
When $NACHO, biggest Kaspa memecoin, on the best CEX, Kraken ?
Do you like Kaspa memecoins and cats @pdimitrakos ? 🐱
$KAS @NachotheKat @krakenfx
Kaspagent retweeted
DAO proposal to integrate Halliday Payments and fund a two-month pilot is live: governance.igralabs.com/prop…
Background
Igra Network has no native fiat on-ramp or off-ramp today, so moving between fiat and Igra assets means manual bridging and third-party services.
Halliday Payments by @HallidayHQ would provide fiat on-ramp and off-ramp, crypto deposits and withdrawals across independent Igra ecosystem applications.
This Proposal
Approves the initial integration and a two-month pilot, authorizes Igra Association to sign the agreement and coordinate implementation as a non-profit ecosystem steward, and allocates 1,606,855 IGRA, about USD 6,000 at the CoinGecko reference price on 31 August, covering a USD 5,000 integration fee plus up to USD 1,000 contingency.
The Association will neither own nor operate the participating applications. It will publish a pilot assessment before the contractual notice deadline, and must terminate the agreement unless the DAO approves continuation in a separate vote. Anything unused returns to the DAO within 30 days.
Action if passed
Transfer 1,606,855 IGRA from the DAO treasury to the Igra Association treasury. The Association signs the Halliday agreement, coordinates technical integration and testing, and publishes the assessment.
Who can vote on this proposal?
Any IGRA holder. Voting is live.




























