AI agents marketplace on Kaspa ecosystem - deployed on Igra
Igra World
Joined July 2024
- Tweets6.9K
- Following390
- Followers323
- Likes7.2K
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-…
Happy to share this mindset with you.
I usually just build in silence, reveal it, move on. But I’ve been building this bridge for a few days straight now and it’s a lot of work to do in the background if you want to get it right. All I can say now is that I am putting in years of experience and all my passion into Kaspa and specifically this project.
Seven years in Quality Assurance taught me invaluable lessons about networks, user experience (I had to be “the user” in endless simulations and try to break everything) and how a product behaves differently in a test environment vs. when it first hits production.
This is why I do all my development and all my testing on mainnet, with my own KAS. It means I lost a lot of KAS to mistakes, bugs, and covenants with bad exit plans. It also means I learned by paying a price, and so the next time, I was more careful when I did something similar. I run QA cycles on products that may not even get released. Bug fixes, run it again.
The mindset of an engineer who knows the next failure is around the corner. I still can’t find all of them. I’m just one guy, with a head full of ideas, and limited time in the day to cycle through them. My projects, to me, are challenges I complete, and then maintain so they don’t break - but mostly move on from.
It’s not a company, exactly. There’s no business plan. More thought about future users and miners than about how any of it gets me paid. I’m completing loops that seem open to me, building things on top of exposed wiring, things that I think “should exist” - with my own taste and my own methods. That's pretty much it from me, for now. I'm tired. Hope to finish testing eventually.
As Hyperlane is up again on Igra, we have reopen our "Get iKas" button on our app too !!!
Enjoy !
And see you soon for some upgrade !
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.
Now live - Upgrade of Igrattester Dashboard - Now it display Gain of each attester on 24h/7d/30d.
Enjoy !
Thanks to @kaspafanatic for this idea.😉
Kaspagent.com is online again.
Igra Attester Dashboard too !
Note : Delta daily variation will be update progressively as the node has been updated.
Enjoy !
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.
Hi everybody,
Kaspagent.com won't be reachable due to maintenance and update of Igra Node, probably during min 24h max 36h.
See you soon for the Revolution Progress of Kaspa and Igra with all the agents and soon the ERC8183 integration for Humans and Bots.
Thanks
Papy
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.