Kaspa is about to get a L1 bridge to Ethereum with no signers, approvers or admins anywhere in the path. Already proven on mainnet with a test token: deposit an ERC-20 into an Ethereum vault, mint a KCC-20 on Kaspa from a ZK proof of Ethereum’s own consensus.

Standard Chartered's crypto custody subsidiary Zodia Custody offers institutional custody for Kaspa's KAS. Zodia added KAS support in November 2024. @kaspaunchained

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. 👇

Kaspa.

Today the team is working on building out the API endpoints to make it as easy as possible for @coingecko to list covenant tokens on #kaspa Layer1 This will make it easy for all tokens launched on Kron to apply for a CoinGecko listing.

@dotk_name will be added next week Thanks to @supertypo_kas for testing it out Covenants really enables programmability on chain Looking forward for vProgs and zK stuff. Keep the good work @IzioDev @michaelsuttonil @Max143672 @OriNewman and more!

Buy Kron -> Stake Kron -> Earn Kaspa -> Buy More Kron -> Stake Kron -> Earn more Kaspa -> Repeat kaspa:native @KASPAglobal @kaspaunchained @KronTechnology

Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday. You can play it here: vprogs-tt.izio.fr/ (Requires private key and some testnet funds) We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top For Devs: this is the invitation. Play the game, read the code, build your own vprog. Game code: github.com/biryukovmaxim/vpr… vprogs framework: github.com/kaspanet/vprogs/t…

With $KAS at $0.0385 and a 28.7B max supply, spending ~$52 gets you 1,367 KAS…. 1367 KAS is the exact same percentage share of the network as holding 1 whole $BTC. Now, if you could go back to buy 1 BTC for $50, how many would you buy?

time to lock in

Today we applied a major update to the website and buy/sell transactions now confirm on chain in ~1 second. kaspa:native #defi