Live financial news intelligence

Track market-moving stories before they get noisy

Real-time pulse of financial headlines curated from 5 premium feeds.

Latest market signal Czech Filtered by asset ZK
Coverage 239,812 Raw stories ingested 36,376 rewritten in CS_CZ • 0 to rewrite (last 7 days).
Agents 7 Live Pipeline agents
  • FMP Stock News Fetch every minute running now
  • FMP Forex News Fetch every 5 min 5m ago
  • CoinGecko News Fetch every 5 min 5m ago
  • FIO Stock News Fetch every 10 min 7m ago
  • Patria Stock News Fetch every 10 min 7m ago
  • Editorial rewrite Rewrite every minute 1m ago
  • Asset sync Assets every 1 hour 54m ago

Latest coverage

Market News Feed

Scan headlines quickly, then expand any story for source context.

View
Language
Relevance
Clear
Details Date Content Source Relevance
2026-10-17 22:43 7d ago
2026-10-17 15:41 7d ago
ZKsync ověřuje bloky Etherea pomocí jediné GPU
ZK zkSync
CoinGecko News 90
Original source text
ZKsync’s new prover keeps pace with Ethereum using one graphics card instead of a GPU cluster.
Vitalik Buterin says the speed race is over and the next fight is about proving these systems are correct.
Nothing changes on Ethereum yet, and there is no date for adopting this technology.
The ZK token has more than doubled since August, but the prover gives holders no direct revenue.

In mid-2025, the fastest systems for proving an Ethereum block in about 12 seconds needed somewhere between 50 and 160 graphics cards. On October 13, Matter Labs, the company that builds ZKsync, announced that its new Airbender Prime prover does the job on one. Across 7,200 consecutive Ethereum blocks, a single NVIDIA RTX PRO 6000 Blackwell card produced proofs for 99% of them in under 10 seconds, fast enough to keep up with the chain itself. Two days later, Vitalik Buterin congratulated the team and said the speed race is effectively won. For Ethereum, that moves the debate to a slower and far less exciting question: can anyone show these systems never make a mistake?

7,200

consecutive Ethereum blocks in the test

99%

proven in under 10 seconds

1 GPU

no data center, no cluster

<12 sec

slowest block, still within one Ethereum slot

The finish line was crossed last year. ZKsync shrank the machine
A proof, in this context, is a small cryptographic file confirming that every transaction in a block was processed correctly. Today, each Ethereum node checks a new block by running all of its transactions again on its own hardware. With a proof, a node could check that file instead, which takes very little computing power. The expensive work shifts to whoever generates the proof.

Speed alone is not the headline. In December 2025, the Ethereum Foundation said the industry had already hit its real-time target, after proving times fell from 16 minutes to 16 seconds within a year and costs dropped about 45 times. What ZKsync adds is the size of the setup. Its timings also include the data-gathering step before proving starts, which some earlier benchmarks left out.

June 2025

The first Airbender version proves a block in about 35 seconds on one GPU. Rivals need 50 to 160 cards for roughly 12 seconds.

July 2025

The Ethereum Foundation sets the rules: 99% of blocks in 10 seconds, on hardware under $100,000 using no more than 10 kW.

December 2025

The Foundation says the speed target has been met and shifts its focus to security.

October 13, 2026

Airbender Prime hits the target on a single graphics card and tops the public ETHproofs leaderboard.

October 15, 2026

Buterin calls the speed race won and names three security problems still unsolved.

Why the Ethereum Foundation put a $100,000 cap on proving hardware
The Foundation’s real-time proving rules were never only about speed. They also capped hardware at $100,000 and power use at 10 kilowatts, so that some of the people who already run validators from home could generate proofs too. A million-dollar machine that proves blocks in five seconds would fail that test, because it would leave proving to a handful of large operators.

One workstation card sits far below that budget. That is why the result matters more for decentralization than for raw performance. If a single card can keep up with Ethereum, then producing proofs stops being a job only well-funded companies can do.

The numbers come from ZKsync’s own tests. The code is open, and the ETHproofs leaderboard lets outsiders follow live results, but no independent team has published a full reproduction yet.

Buterin’s congratulations came with a three-item to-do list
Buterin did not stop at praise. He argued that the industry should now put its effort into making these provers trustworthy, and he named three specific gaps.

The first is formal verification, a set of mathematical checks showing that the prover follows Ethereum’s official rules exactly, including rare edge cases that normal testing can miss. The second is a hard ceiling on proving costs, so that no block can be made deliberately expensive enough to prove that it stalls the network. The third is the security of the proof system itself, meaning confidence that the cryptography underneath cannot be tricked into approving something false.

A slow prover only delays things. A fast prover with a bug can approve something false. If a flaw lets an invalid block pass as valid, nodes that only check proofs would accept it, on a network holding hundreds of billions of dollars. The Foundation has already said it wants validators to check several independent proofs for each block, so that a bug in one system cannot slip through alone. That work tends to take years, not months.

For people using Ethereum today, nothing changes yet
Airbender Prime is a ZKsync product, not an Ethereum upgrade. Validators still check blocks the traditional way, and no one has set a date for proofs to replace that. The Foundation’s plan starts with optional software that validators can choose to run, and only later could it become standard.

If it does arrive, the main gain would be room to grow. Ethereum could handle more activity per block without forcing everyone who runs a node to buy stronger hardware. Faster proofs would not make transactions final faster, though, because the rest of the network process follows its own timing.

ZKsync is already using Airbender on its own chains that run the Atlas upgrade, and it is pitching the same technology to banks and companies through Prividium, its system for private blockchains that settle on Ethereum. For now, those private chains are where the prover makes money for ZKsync, well before Ethereum mainnet could use it.

The ZK token doubled, but the prover does not pay its holders
ZK is mainly a governance token. Fees on ZKsync Era are paid in ETH, and proposals to give ZK more economic uses still depend on governance votes. A better prover can raise ZKsync’s profile without creating direct demand for the token.

Market trackers recorded a gain of about 6% after Buterin’s post. Traders have seen this pattern before. In November 2025, Buterin’s praise for ZKsync’s work sent ZK up more than 50% in a single day. The token now trades well below where that rally peaked.

ZK Doubled Off Its Lows, but Sellers Are Waiting Near $0.019
ZK bottomed at $0.00704 in mid-August, close to its all-time low, and now trades around $0.0160 on Binance, about 127% higher. The turning point came around October 9, when one daily candle added roughly 27% and lifted the price above its 200-day average, a long-term trend line that had blocked every rally since May. The price has stayed above it since, and the August-to-October pattern of higher lows near $0.0080, $0.0088 and $0.0108 shows buyers stepping in earlier each time.

ZK/USDT daily chart. Source: TradingView / Alexander Stefanov
The top of the move tells a different story. Long upper wicks at $0.0175 and $0.0189 mean the price pushed higher during the day and then got sold back down. The heaviest trading volume of the whole rally came on the day ZK touched $0.0189 and reversed, which points to large sellers waiting at that level. The RSI, a gauge of buying strength, has slipped to 61 from the low 70s, and its peaks have flattened while the price kept rising. Buyers are still in control, but each push is weaker.

ZK/USDT price ladder · daily chart

$0.0189

Resistance

This week’s high, where the heaviest selling appeared

$0.0175

Resistance

Several daily candles rejected here

$0.0161

Testing now

First support, with the price ($0.0160) sitting right on it

$0.0144-$0.0145

Key support

The 200-day average and a common pullback level meet here

$0.0130

Support

Top of the late-September trading range

$0.0116-$0.0118

Last line

The rising 50-day average

The $0.0144-$0.0145 zone decides what happens next. A dip into it on lighter volume than the rally, followed by a bounce, would keep the breakout alive and set up another attempt at $0.0175-$0.0189. A daily close back below the 200-day average would turn October’s move into a failed breakout, with $0.0130 the next likely stop. ZK also held its breakout even as a liquidation wave pushed Bitcoin under $81,000 this week. Saturday’s red candle is forming on much lighter volume than last week’s green days, which so far looks more like a pause than a wave of selling.

About 10 billion ZK tokens are still waiting to enter the market
Only around 52% of ZK’s 21 billion maximum supply circulates, according to market data aggregators, which leaves roughly 10 billion tokens to be released over time. Every recovery has to absorb that extra supply, whatever happens with the technology. On the development side, the next signals worth watching are outside teams reproducing ZKsync’s results on ETHproofs and the first published formal verification work Buterin asked for. Those would show whether Airbender Prime is ready for Ethereum itself, or only fast.

Alex is a financial markets journalist and co-founder of Millennial Media Group, and he's spent close to ten years trying to answer one stubborn question: what's really driving this?
It started in 2016, when Bitcoin refused to make sense to him - and rather than shrug, he stayed with it until it did. That patience became his method. He's less interested in what an asset is doing today than in the plumbing behind it: how liquidity flows, where risk hides, what a chart is quietly telling you that the headline isn't. That lens eventually stretched well past crypto into traditional markets, because the same forces - fear, leverage, incentives, timing - show up everywhere once you know how to look.
Most coverage, in his view, insults the reader by stopping at the surface. Price up, price down, moving on. He'd rather leave someone genuinely understanding a move than merely informed that it happened.
His path into markets ran through a Tourism degree at New Bulgarian University - proof, maybe, that curiosity beats credentials. With more than 200 deep analyses and over 10,000 articles behind him, he still walks away from most trading days having learned something he didn't know that morning.

Full Profile
2026-10-15 06:38 9d ago
2026-10-15 03:42 10d ago
ZKsync Airbender vygeneroval důkaz pro bloky Etherea za méně než 10 sekund
ZK zkSync
CoinGecko News 93
Original source text
ZKsync says it has built the first Ethereum prover that can generate proofs in real time on a single GPU. Ethereum co-founder Vitalik Buterin responded two days later with praise, and with homework.

The system is called Airbender Prime, and ZKsync announced it on October 13, 2026. Buterin publicly commended the team on October 15, 2026. He also argued that the focus should now move toward verifying zkEVM security, including system correctness and limits on how much proving can cost.

What Airbender Prime actually did ZKsync’s headline numbers come from a single NVIDIA RTX PRO 6000 Blackwell GPU. Across 7,200 Ethereum mainnet blocks, Airbender Prime proved 99% in under 10 seconds. Every block in the set was proved within 12 seconds.

The result places Airbender at the top of the ETHproofs.org public leaderboard, where it leads on proving time, GPU efficiency and cost-effectiveness.

A prior iteration of Airbender posted 21.8 MHz of throughput on an H100 GPU. The new version moves the conversation from raw throughput figures to something more tangible: keeping up with live Ethereum blocks on hardware you could plausibly buy.

Under the hood, Airbender relies on hash-based STARKs, a family of proof systems that ZKsync describes as secure against quantum attacks. It is built on RISC-V, an open instruction set standard, and its components are open source.

Buterin’s verdict: speed is solved, safety is next Buterin did not hedge on the performance side. He framed the race to make proving fast as effectively over.

“Speed battle… definitively won”

Then he pivoted. According to his comments, the next priority should be formal verification that the prover faithfully matches Ethereum’s specifications. He also called for bounds on prover costs tied to gas fees.

How Airbender fits into ZKsync’s roadmap Airbender is not arriving in isolation. It follows ZKsync’s earlier Atlas upgrade, part of a broader push to expand what Ethereum can handle.

The prover is already running across ZKsync’s supported chains. It was designed to operate efficiently on commodity hardware, with both institutional operators and independent participants in mind.

What this means for Ethereum and its scaling race On trust, Buterin’s comments effectively reset the scoreboard. The things to watch from here are fairly clear: progress on formal verification of Airbender against Ethereum’s specifications, any published work on prover cost bounds relative to gas, and whether rival zkEVM teams close the gap on the ETHproofs.org rankings.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.
2026-10-12 23:59 12d ago
2026-10-12 18:30 12d ago
ZKsync navrhuje veto upgradů s 630 miliony ZK
ZK zkSync
CoinGecko News 92
Original source text
Summary: Activate optimistic governance for ZIPs by deploying the council, veto, and supermajority contracts created by Scopelift, and set parameters outlined in the Specification section.

Field
Details

Title
Activate Optimistic Governance for ZIPs

Proposal Type
ZIP

One Sentence Summary
This ZIP activates Optimistic Governance for ZIPs which allows Security Council members to propose protocol upgrades and for the Token Assembly to veto any ZIP prior to execution.

Proposal Author
ZKsync Association

Proposal Sponsor
[TBC]

Date Submitted
[TBC]

Version
1

Summary of Action
Activate optimistic governance for ZIPs by deploying the council, veto, and supermajority contracts created by Scopelift, and set parameters outlined in the Specification section.

Abstract
This proposal activates Optimistic Governance for ZIPs. Security Council members will propose protocol upgrades and the Token Assembly will have the opportunity to veto any ZIP before it can proceed to execution. This removes the requirement for the Token Assembly to affirmatively approve every ZIP and focus voting on Token Program Proposals and Governance Advisory Proposals, while preserving its ability to veto a proposal.

Motivation
ZIPs are technical proposals that can upgrade the ZKsync protocol, its core contracts, and the governance system. The Security Council currently has responsibility for reviewing and approving protocol upgrades before they are executed. Allowing Security Council members to propose ZIPs places responsibility for driving upgrades with the governance body best positioned to assess them.

Under the current process, every ZIP must receive at least 630 million ZK in affirmative votes and a simple majority of votes cast. This means a proposal can fail because it does not reach quorum, even where there is no material opposition. It also requires the Token Assembly to approve technical changes before the Security Council completes its review.

Optimistic Governance shifts the Token Assembly’s role from approving every ZIP to having the ability to veto any ZIP, as well as increasing their focus on token programs, mechanics, and governance advisory. Once adopted, optimistic governace means protocol upgrade proposals can proceed without an affirmative Token Assembly vote, but 630 million ZK can stop it. A veto can only be overridden if at least 1.26 billion ZK votes For and there are more For votes than Against votes. This allows technical experts to drive protocol upgrades while keeping the Token Assembly as a check on whether they proceed.

This ZIP only changes the Protocol Upgrade path. The Token Governor (TPPs) and GovOps Governor (GAPs) are unchanged.

Specification
This proposal deploys a council token, a Council Governor, a Veto Governor, a Supermajority Governor, and a dedicated supermajority timelock on ZKsync Era. It reuses the existing Protocol Timelock so that successful proposals continue to reach the existing ProtocolUpgradeHandler on Ethereum.

Changes Proposed
1. Security Council proposal process
Each of the eight Security Council member entities will receive one non-transferable and non-delegable seat through CouncilERC20. Each seat will be held by that member entity’s SAFE multisig on ZKsync Era.

A seated member of the Security Council may submit a proposal through BasicCouncilGovernor. Any Security Council member entity can submit a protocol upgrade onchain. This submission equates to that entity sponsoring the ZIP. It is expected that the sponsor of the ZIP then casts a vote ‘FOR’ the proposal. One Security Council member entity voting FOR is sufficient to forward the proposal to the Token Assembly veto stage. The Security Council voting delay will be one day, enabling proposals to be cancelled and resubmitted if there is an error in the initial submission. The council voting period will be a maximum of three days. A one-seat super-quorum allows a proposal to advance as soon as the first valid FOR vote is cast.

The ZKsync deployment will use council vote-counting logic under which a valid FOR vote from one seat satisfies sponsorship regardless of Against votes. This preserves the intended one-member sponsorship model and prevents the council stage from becoming a separate majority-approval gate.

A successful council proposal is forwarded to the Veto Governor. It cannot be queued directly for execution through the Council Governor.

Council Members:

Matter Labs: 0xe38dc029623f0af56BdC46E5318610E257d6b760
Nethermind: 0x870Ec9631E28ee6C8b304e238E9b6890a99ab8aA
Open Zeppelin: 0x305798C076B64Be35Aa6367C6632b79e29D0113A
Spearbit: 0x356cF4Ac9fA86F0a9dDdc62e48082FE5Cd14bE7b
Chainlight: 0x3043bF9c9A512d20Dda2c2b2C3D69AF6f7Fcd5B1
Cyfrin: 0x9BC8d216d63b38c390e465D664FEb63B67659c13
Dedaub: 0xdbc2E250cBA867D6619Bed342Ca3Eca7b71e8b82
Peckshield: 0x46fc9a8A72456c84F42c5c9e5df46984c0078B15

2. Token Assembly veto process
Every proposal forwarded by the Council Governor will enter a Token Assembly veto process through BasicCouncilVetoGovernor. Delegated ZK voting power may cast veto votes during the configured veto period.

A proposal succeeds by default unless veto votes reach 630 million ZK. If the threshold is reached, the proposal is defeated unless the Token Assembly subsequently approves an override through the process described below.

The veto threshold will be set at a fixed threshold of 630 million ZK.

The veto vote will remain open for seven days. Once the veto votes reach 315 million ZK—50% of the veto threshold—the voting period will be extended by two days.

3. Token Assembly Supermajority Vote
A veto may be overridden by a Token Assembly supermajority:

at least 1.26 billion ZK voting For, equal to twice the 630 million ZK veto threshold; and
more For votes than Against votes.

The Supermajority Governor [ZKsync Supermajority Governor] will use the existing ZK token and the same fractional-counting model as the current Protocol Governor. It will have a proposal threshold of 21 million ZK, a one-day voting delay, a seven-day voting period, and a three-day late-quorum extension.

Successful supermajority proposals will execute through a dedicated self-administered TimelockController with a one-day minimum delay. That timelock will hold the Veto Governor’s vetoOverrideRole. No externally owned account, Security Council Safe, Foundation Safe, or general governance administrator will hold the supermajority role.

The supermajority vote must execute within 14 days after the veto deadline. This window accommodates the override vote, possible late-quorum extension, and supermajority-timelock delay.

Under the proposed implementation, the supermajority may apply to any proposal in the Defeated state, including a proposal stopped through the Foundation’s safety veto. This prevents the Foundation from becoming a unilateral denial-of-service point, but means its veto acts as a delay rather than an absolute stop when at least 1.26 billion ZK supports a proposal proceeding.

Following a successful supermajority vote, anyone may queue the proposal on the Veto Governor and, after the applicable timelock conditions are satisfied, execute it through the Council Governor. The existing L1 approval process still applies.

4. Foundation safety veto
The ZKsync Foundation will retain veto power in the Veto Governor’s vetoGuardian role via its L2 multisig, 0xF197677d63BF6E2841F5108b8dFd2FD6eCEff74B.

The Foundation may stop a proposal while it is Pending or Active by calling vetoByGuardian() on ZKsync Era. The Foundation cannot use this role to originate, affirmatively approve, queue, or execute a proposal.

A Foundation-vetoed proposal may be restored through the 1.26 billion ZK Token Assembly override described above.

5. Standard ZIP process
The standard process will be:

One Security Council member submits a ZIP through the Council Governor.
The proposing Security Council member, or any other council member, casts one FOR vote to advance the proposal to the Token Assembly veto stage.
The proposal enters the Token Assembly veto process.
The Foundation may exercise its safety veto while the proposal is Pending or Active.
If no veto occurs, the proposal succeeds at the end of the veto period.
If a veto occurs, the proposal proceeds only if the Token Assembly approves an override with at least 1.26 billion ZK voting For and more For votes than Against votes.
The Veto Governor queues and executes the proposal through the existing Protocol Timelock.
The Protocol Timelock sends the L2-to-L1 message to the ProtocolUpgradeHandler.
The upgrade proceeds through the existing L1 approval, delay, and execution stages.

Every standard ZIP is subject to the Token Assembly veto process. Only a higher-threshold Token Assembly vote may reverse a veto on L2.

6. Council Governor parameters

Parameter
Initial Value

Name
ZKsync Protocol Upgrade Council

Council Veto Governor
Deployed Veto Governor

Governor admin
0xf41eca3047b37dc7d88849de4a4dc07937ad6bc4

Voting delay
86,400 seconds (1 day)

Voting period
259,200 seconds (3 days)

Proposal threshold
1e18 (one seat)

Quorum fraction
12% (one of eight seats)

Super-quorum fraction
12% (one of eight seats)

Vote-success rule
One FOR vote is enough

7. Veto Governor parameters

Parameter
Initial Value

Name
ZKsync Protocol Upgrade Veto Governor

Token
ZK at 0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E

Voting delay
86,400 seconds (1 day)

Voting period
604,800 seconds (7 days)

Proposal threshold
0 (propose() is restricted to the Council Governor)

Veto Guardian
0xF197677d63BF6E2841F5108b8dFd2FD6eCEff74B

Veto override duration
1,209,600 seconds (14 days)

Voting-period extension
172,800 seconds (2 days)

Extension threshold
50% of veto threshold (315 million ZK)

Veto threshold
630 million ZK

Protocol Timelock
0x085b8B6407f150D62adB1EF926F7f304600ec714

Governor admin
0xf41eca3047b37dc7d88849de4a4dc07937ad6bc4

Council
Deployed Council Governor

Veto override role
Deployed Override timelock

8. Council token parameters

Parameter
Initial Value

Name
ZKsync Protocol Upgrade Council Seat

Symbol
ZKPUC

Admin
0xf41eca3047b37dc7d88849de4a4dc07937ad6bc4

Maximum tokens per member
1e18

Initial members
Matter Labs: 0xe38dc029623f0af56BdC46E5318610E257d6b760; Nethermind: 0x870Ec9631E28ee6C8b304e238E9b6890a99ab8aA; Open Zeppelin: 0x305798C076B64Be35Aa6367C6632b79e29D0113A; Spearbit: 0x356cF4Ac9fA86F0a9dDdc62e48082FE5Cd14bE7b; Chainlight: 0x3043bF9c9A512d20Dda2c2b2C3D69AF6f7Fcd5B1; Cyfrin: 0x9BC8d216d63b38c390e465D664FEb63B67659c13; Dedaub: 0xdbc2E250cBA867D6619Bed342Ca3Eca7b71e8b82; Peckshield: 0x46fc9a8A72456c84F42c5c9e5df46984c0078B15

Tokens per initial member
1e18

Transferability
Non-transferable and non-delegable

9. Supermajority Governor parameters

Parameter
Initial Value

Name
ZKsync Supermajority Governor

Token
ZK at 0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E

Proposal threshold
21 million ZK

Fixed For-vote quorum
1.26 billion ZK

Success condition
At least 1.26 billion ZK FOR and more FOR than AGAINST

Voting delay
86,400 seconds (1 day)

Voting period
604,800 seconds (7 days)

Late-quorum extension
259,200 seconds (3 days)

Override timelock minimum delay
86,400 seconds (1 day)

Override timelock proposer and canceller
Veto Override Governor

Override timelock executor
Open (address(0))

Override timelock administration
Self-administered

10. Existing Protocol Timelock migration
This design requires no changes to the existing ProtocolUpgradeHandler and continues to use the existing Protocol Timelock at 0x085b8B6407f150D62adB1EF926F7f304600ec714.

The migration will:

grant PROPOSER_ROLE, EXECUTOR_ROLE, and CANCELLER_ROLE on the Protocol Timelock to the new Veto Governor; and
revoke those roles from the current ZkProtocolGovernor at 0x76705327e682f2d96943280d99464ab61219e34f.

The Veto Governor requires EXECUTOR_ROLE because it calls executeBatch() itself. The Protocol Timelock is self-administered and currently has a minimum delay of zero. This ZIP does not change that delay.

11. Administration and council membership
The governorAdmin roles for the Council Governor and Veto Governor, as well as the CouncilERC20 admin role, will be assigned to the L2 alias of the ProtocolUpgradeHandler, 0xf41eca3047b37dc7d88849de4a4dc07937ad6bc4.

As a result, parameter changes and council seat changes must pass through the full ZIP process, including the L1 approval and delay stages, before the ProtocolUpgradeHandler sends the corresponding L1-to-L2 call.

The L1 Security Council membership and the L2 council-seat list are separate. A change to one does not automatically update the other. Any membership change must update both systems where applicable.

12. Prerequisite Guardian-dissolution ZIP
This proposal assumes that a separate ZIP has already:

assigned the ZKsync Foundation Safe to the ProtocolUpgradeHandler Guardian role;
deployed and activated an Emergency Upgrade Board that is composed of the Security Council plus Foundation, requiring both bodies; and
retired the prior three-body Emergency Upgrade Board.

That prerequisite ZIP must execute before this optimistic-governance migration. Any corresponding changes to Guardian roles in the Token Governor and GovOps Governor must be handled separately through the applicable TPP and GAP processes.

13. Scope
This proposal applies only to the Protocol Upgrade Governor and its timelock. It does not change:

the Token Governor or the affirmative Token Assembly vote required for TPPs;
the GovOps Governor or the affirmative Token Assembly vote required for GAPs;
the L1 ProtocolUpgradeHandler approval thresholds established by the prerequisite ZIP;
the Security Council’s existing freeze powers; or
the Emergency Upgrade Board established by the prerequisite ZIP.

Execution Impact
Security Council
Each Security Council member entity will receive one seat held through its Safe on ZKsync Era. Any one member may sponsor a proposal and forward it to the Token Assembly veto stage. The Security Council will continue to act collectively during the L1 approval stage.

L2 seat custody is operationally separate from the existing L1 Security Council membership. The signer sets and membership records must be kept aligned.

Token Assembly
The Token Assembly will no longer need to reach affirmative quorum for every ZIP. Instead, every standard ZIP will enter a public veto period.

Delegates may stop a proposal with 630 million ZK in veto votes. A disputed veto may be reversed only through a separate Token Assembly vote with at least 1.26 billion ZK voting For and more For votes than Against votes.

This proposal does not change Token Assembly approval rights for TPPs or GAPs.

ZKsync Foundation
The Foundation may veto Pending or Active proposals through an L1-to-L2 transaction. Under the proposed implementation, the Token Assembly may reverse that veto through the same 1.26 billion ZK override process.

The Foundation retains the L1 fallback approval and legal-veto-extension functions established by the prerequisite Guardian-dissolution ZIP.

Governance interfaces and monitoring
The governance interface must support council proposal, council sponsorship, Token Assembly veto, veto extension, override proposal, override execution, Protocol Timelock, and L1 approval states.

All council proposals and vetoes should trigger public notifications to delegates, Security Council members, the Foundation, and the wider community. Interfaces should display the 630 million ZK veto threshold, the 315 million ZK extension threshold, the 1.26 billion ZK override requirement, and the applicable deadlines.

Governance Procedures
The ZKsync Governance Procedures must be amended to reflect Security Council proposal rights, the Token Assembly veto and override processes, the Foundation safety veto, and the revised role of the current Protocol Timelock and Protocol Governor.

Backwards Compatibility
This proposal changes the governance process for future ZIPs and is therefore not procedurally backwards compatible with the current affirmative-vote model.

After activation:

ZIPs must be originated through the Council Governor;
delegated ZK voting power will ordinarily be used to veto rather than affirmatively approve ZIPs;
a separate higher-threshold Token Assembly process will govern veto overrides;
the new Veto Governor will replace the current Protocol Governor as proposer, executor, and canceller on the existing Protocol Timelock; and
governance interfaces and indexing services must support the council-to-veto and override lifecycles.

The proposal does not change application-facing transaction formats, smart contract interfaces, or validity rules for ordinary ZKsync transactions. The Token Governor and GovOps Governor proposal processes remain unchanged.

Any ZIP pending in the current Protocol Governor at the activation boundary must be handled under a published transition plan. No proposal should remain dependent on roles that are revoked during migration.

Security Considerations
The optimistic model allows a proposal to advance without affirmative Token Assembly participation. This improves liveness but makes public notice, monitoring, accessible technical materials, and a meaningful veto period essential. The seven-day veto period, late-veto extension, Foundation veto, Token Assembly override process, collective Security Council L1 approval, and existing L1 delays provide defense in depth.

The 1.26 billion ZK override protects against veto griefing and a unilateral Foundation denial of service, but it also means that a veto is not absolute. The override remains a Token Assembly decision: neither the Security Council, the Foundation, nor the administrator can invoke it without the required token vote. The feasibility of reaching 1.26 billion ZK in For votes should be assessed against historical participation before deployment.

As proposed, the override can reverse both a token-holder veto and a Foundation safety veto because both place the proposal in the Defeated state. Restricting the override to token-holder vetoes would require additional state tracking and a further modification to the audited code. The final implementation and documentation must make the selected behavior explicit.

If the Security Council cannot satisfy the L1 approval threshold, the Foundation may use the fallback approval path established by the prerequisite ZIP. If both bodies refuse or are unavailable, the upgrade will not execute. This is the intended two-body blocking property of the design.

The governorAdmin and council-token admin may change parameters and membership. Assigning these roles to the aliased ProtocolUpgradeHandler subjects their use to the full ZIP and L1 approval path, but also makes correct L1-to-L2 aliasing and cross-domain execution critical. All aliases and administrative calls must be tested on a fork.

The existing Protocol Timelock is retained because the ProtocolUpgradeHandler accepts messages only from that address. Incorrectly revoking the current governor’s roles before the Veto Governor is fully configured could make protocol governance inoperable. The role migration must be atomic where possible and verified against the final execution manifest.

The generic council-governance contracts were reviewed by Certora in December 2025 at commit 6680eb4, according to the supporting technical materials. The ZKsync-specific council counting, fixed veto-supply base, deployment parameters, override-governor integration, L1-to-L2 administration, and complete role migration require their own review before submission.
2026-10-11 11:18 13d ago
2026-10-11 07:00 13d ago
ZKsync plánuje expanzi do Japonska s NextBridge
ZK zkSync
CoinGecko News 78
Original source text
ZKsync [ZK] remained one of the few tokens to gain more than 10% as the cryptocurrency market regrouped after recent declines.

Its bullish performance coincided with a NextBridge partnership, expected to bring Prividium, its self-governed private ledger for institutions, to Japan.

Even so, the rally faced a test. AMBCrypto analyzed trader activity and found reasons to question whether ZK could sustain its upward movement.

Could ZKsync’s rally face a pullback? The Bollinger Bands chart showed ZK reaching the upper band, where its advance faced resistance. The indicator plots three bands around price. Its outer bands can help identify potential resistance and support, depending on market conditions.

Previous approaches to the upper band had preceded declines. This time, a red candlestick suggested selling pressure had started to emerge.

Source: TradingView If the pullback continues, ZK could approach the blue middle band at $0.0125, near horizontal support at $0.0124. That puts the $0.0124–$0.0125 zone in focus as a potential landing point.

Further selling could push ZK toward the lower band around $0.011, making it another potential support area.

Can ZK bulls defend the next support? Despite the emerging pullback, Bull Bear Power (BBP) suggested bulls retained the upper hand. The chart recorded consecutive positive green bars on the 9th and 10th of October, supporting the bullish momentum reading.

The Parabolic Stop and Reverse (SAR) offered a similar outlook, with dots positioned below ZK’s price.

Source: TradingView That positioning supported the prevailing upward trend, even as the red candlestick signaled near-term selling pressure. Taken together, these indicators leave room for a rebound if ZK retreats toward the middle band.

For bulls, holding the nearby $0.0124 support could help keep that recovery scenario alive.

What does ZKsync’s record holder count suggest? Meanwhile, ZK’s price gains coincided with an increase in its Holder Count. The number reached approximately 186,820, marking an all-time high. The upward trend had developed since mid-September.

Source: CoinMarketCap The growing Holder Count supported the adoption picture, although it did not establish how much those addresses bought.

ZK therefore faced competing signals: resistance near the upper band, bullish trend indicators, and a growing holder base. A pullback toward $0.0124–$0.0125 could test whether that bullish momentum translates into buyers defending support.

Final Summary ZKsync gained more than 10%, but upper-band resistance left a pullback toward $0.0124–$0.0125 in play. Bullish indicators and a record Holder Count supported the recovery outlook, with support holding key to a rebound.
2026-10-08 00:37 17d ago
2026-10-07 17:12 17d ago
Matter Labs otevřela modul Prividium, Deutsche Bundesbank jej testuje
ZK zkSync
CoinGecko News 92
Original source text
Matter Labs, the company behind the ZKsync protocol, has open-sourced the core permissioning engine of Prividium, its enterprise blockchain platform. The code went public on September 8, 2026, under the Apache 2.0 license.

Germany’s Deutsche Bundesbank is the first organization testing a self-hosted instance. The Bundesbank is collaborating with Matter Labs on both design and testing for its self-hosted deployment.

The release does not hand over everything. Matter Labs is keeping its enterprise tooling, including user interfaces and deployment tools, proprietary. The engine is open. The polished dashboard around it still comes with a bill.

What’s actually in the repo The release covers one main app and six packages. All of it lives in a public GitHub repository called matter-labs/prividium-core.

The permissioning engine is the part that decides who can do what on a private chain. For a regulated institution, that layer matters a lot. Permissions and auditability are the features compliance teams actually lose sleep over.

Advertisement

This piece completes a broader stack that was already public. ZKsync OS, the Atlas sequencer, the Airbender prover, and the interoperability contracts were all open-sourced before this announcement.

With the permissioning engine added, institutions can now independently build permissioned chains using publicly shared code. Previously, the gatekeeping layer was the missing puzzle piece.

The Apache 2.0 license lets institutions inspect and modify the engine without signing a commercial agreement for that specific component. A bank can read every line, change what it needs, and run it in-house without needing Matter Labs’ permission to do so.

Why a central bank cares about vendor lock-in Prividium is built for validium-style chains. In this model, transaction data stays off-chain, which keeps sensitive financial activity private. The chain still anchors to Ethereum through zero-knowledge proofs.

Matter Labs framed the open-source move as a response to institutional feedback. Large organizations told the company they were wary of depending on a single vendor for critical technology.

Opening the permissioning engine addresses that worry at the layer where it bites hardest. If the gatekeeping logic is public, an institution can verify it does what it claims and keep it running regardless of what happens to the vendor.

What this means The business model here is a familiar one: give away the engine, sell the car. Matter Labs keeps control over the commercial services that make deployment easier, while removing the biggest objection institutions raise in procurement meetings.

The Bundesbank test is the clearest signal of where this is aimed. A German central bank running a self-hosted Prividium instance is a meaningful credibility marker for ZKsync’s enterprise ambitions, though it remains a test rather than a production rollout.

Prividium chains anchor to Ethereum through zero-knowledge proofs, so institutional adoption of this model would route more enterprise activity back to Ethereum as the settlement layer.

There are also open questions about how far an open engine goes on its own. Institutions that self-host still need the skills to run and maintain the stack. The proprietary deployment tools exist precisely because that work is not trivial.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.
2026-10-08 00:37 17d ago
2026-10-07 21:25 17d ago
Oneiro představilo Revolution Network V2 na ZKsync OS
ZK zkSync
CoinGecko News 95
Original source text
WILMINGTON, DE, October 7th, 2026, FinanceWire

V2 starts from a new genesis on open Ethereum standards. Validity proofs on every batch begin with the public testnet.

Oneiro NA, Inc., a Delaware corporation, today announced Revolution Network V2. V2 is a full rebuild of the Revolution Network Ethereum Layer 2 for digital ownership and identity. It starts from a new genesis on ZKsync OS.

From the public testnet onward, every batch will carry a validity proof from the Airbender prover. Transaction data will be published to Ethereum in blobs. Anyone will be able to reconstruct the chain from Ethereum alone.

V2 replaces Libertas, the V1 testnet. Libertas runs on the EraVM stack, which ZKsync has announced it will retire. Oneiro chose to rebuild on open standards rather than migrate custom features.

“Our value is programmable staking and a trust layer for agentic commerce,” said Rob Frasca, Director, Oneiro NA, Inc. “Everything underneath should be standard, proven, and boring. V2 is that foundation. We published what V1 taught us, fixed every issue at the root, and built on the standards wallets, bundlers, and auditors already use.”

V2 Technical and Economic Changes

Validity proofs. Airbender proofs on every batch from the public testnet onward. Data settles to Ethereum. Standard Ethereum development. ZKsync OS is EVM equivalent. Contracts compile with standard Solidity. Foundry, Hardhat, viem, and ethers work unchanged. Same economics. The published emission total and curve are unchanged: 250M REVO over about ten years. Status

The ZKsync OS stack, the staking contract, smart accounts, and the Cornerstone Paymaster are built and tested on a devnet. 51 contract tests pass. Phase 1 is in progress. It delivers the real prover, verifying nodes, explorer, bridge, and Virtus, the V2 public testnet. Oneiro will announce the Virtus opening date separately.

For Libertas Holders

There is nothing to do today. At migration, Libertas will be frozen at a published block. Balances will be snapshotted and credited on V2. Names will move from .rev to .revo. Revolution will never ask for a seed phrase or a fee to migrate.

Details on V2 are at revolutionnetwork.io/v2. Developers can sign up for Virtus launch details at revolutionnetwork.io/developers.

About Oneiro NA, Inc.

Oneiro NA, Inc. is a Delaware corporation and a global provider of advanced, high-performance blockchain solutions. Oneiro is a core developer of the Revolution Network and also Amped.bio, the web3 link-in-bio application.

About Revolution Network

Revolution Network is a zero-knowledge Ethereum Layer 2 for digital ownership and identity. It combines programmable staking, onchain identity through the Revolution Name Service, compliant real-world asset rails through licensed partners, and a trust layer for agentic commerce. Learn more at revolutionnetwork.io.

Important Information

This release contains forward-looking statements about planned features, phases, and timing. They are plans, not guarantees, and may change or not occur. REVO is a utility token used for staking, network fees, and onchain identity registration. This release is for information only. It is not an offer to sell or a solicitation to buy any token or security. Nothing in it is investment, legal, or tax advice. Network rewards are variable and not guaranteed. REVO and related software, products, and services are not available in Prohibited Jurisdictions.
2026-09-09 17:41 1mo ago
2026-09-09 08:13 1mo ago
Matter Labs otevřel zdrojový kód Prividium pro regulované firmy
ZK zkSync
CoinGecko News 78
Original source text
Matter Labs, the company behind ZKsync, has open-sourced the core permissioning engine of Prividium, its distributed ledger technology platform built for financial institutions. The move is designed to give regulated firms greater control over their blockchain infrastructure and reduce their dependence on any single vendor.

Why Matter Labs Made the Change The decision was driven directly by feedback from the institutions Prividium is built to serve. Regulated firms told Matter Labs they needed to run critical infrastructure themselves rather than depend fully on a vendor. Matter Labs CEO Alex Gluchowski was direct about the rationale: he said.

That said, the open-source release does not cover every part of the product.

It is also worth noting that several Prividium components were already publicly available, including the ZKsync OS core, the Atlas sequencer, the Airbender prover, the interoperability contracts, and the block explorer. The permissioning engine, which governs roles and access controls, is the latest addition to that list.

Bundesbank Leads the Way Matter Labs added that it will continue collaborating with the Bundesbank on the platform's design and testing going forward.

Prividium is designed around a technical model that keeps sensitive data off public networks while still anchoring transactions to Ethereum. For regulated institutions navigating strict data residency and compliance requirements, that combination is increasingly attractive.

Sources:
The Block: ZKsync developer Matter Labs open-sources Prividium permissioning engine; Bundesbank tests platform
Crypto Economy: Matter Labs Releases Prividium Permissioning Code With Bundesbank Running Infrastructure Trials
Matter Labs: The Company Behind Prividium
2026-09-07 00:04 1mo ago
2026-09-06 23:00 1mo ago
Matter Labs posiluje EraVM před ukončením podpory
ZK zkSync
CoinGecko News 78
Original source text
Table of contents

ZKsync developer Matter Labs has outlined a security-hardening program for chains running its EraVM execution environment, which will be retired within six months, according to a September 4 announcement on the project blog. The company said funds held in ordinary externally owned accounts require no action, while assets in smart contracts will need steps and dates that will be published in the coming weeks.

Five Security Measures The post lists five changes. ZKsync recommends that public EraVM chains raise their execution delay from three hours to 24 hours, giving teams more time to detect and respond to an exploit before finalization, with an onchain proposal expected in the coming days. It is also working with every active EraVM chain to run an independent second node that confirms each executed batch, so an attacker would need to compromise two separately hosted infrastructures at once.

Matter Labs will publish covered Era protocol code three months after an upgrade ships, instead of immediately, to avoid handing attackers an advantage on frozen code, while independent auditors keep continuous access. On 24 August the Token Assembly approved GAP-5, which renames Emergency Upgrades to Instant Upgrades and requires a notice on the ZK Nation forums after each one. The company is also developing EraBender, an Airbender-based prover that would run alongside Boojum, so a flaw would have to exist in two independently built proving systems.

Why EraVM Is Retiring The company said artificial intelligence has changed the threat landscape, and that the public, permissionless nature of blockchains makes them attractive targets for autonomous exploit discovery. ZKsync introduced EraVM in 2023 as the first production zkEVM, but its successor, the Atlas upgrade, runs EVM natively and is where new protocol development will take place.

EraVM chains will keep settling value through the transition, but new protocol capabilities will ship on Atlas. The retirement does not apply to chains already running Atlas, and permissioned chains such as GRVT will communicate steps to their users directly.

What Comes Next ZKsync framed the work as ongoing rather than one-time, adding new monitoring layers, internal security reviews, and tooling to assert safety properties. The company said technical details may be temporarily withheld where disclosure creates a material security risk. The move builds on the project’s earlier protocol upgrade as it consolidates development around Atlas.

AUTHOR

Blockchain analyst specializing in the regulatory impact of government policies on the crypto industry. Known for his thorough research and clear, engaging writing, Emmanuel provides insightful analysis on the latest trends, market shifts, and emerging crypto innovations. His work aims to educate and inform both novice and experienced readers, offering expert perspectives on the fast-evolving world of digital assets. With a passion for staying ahead of the curve, Ogwu is a trusted voice in the cryptocurrency and blockchain space.
2026-07-15 20:57 3mo ago
2026-07-15 14:11 3mo ago
Tradable přesouvá 1 miliardu USD na Stellar
XLM Stellar Lumens ZK zkSync
CoinGecko News 78
Original source text
Tradable, the ParaFi-backed private credit tokenization platform, has begun migrating $1 billion in institutional-grade private credit assets to the @StellarOrg blockchain, shifting its portfolio away from ZKsync. The firm is deploying $XLM to handle the full deal lifecycle, including compliance controls and investor onboarding, for alternative assets that were previously held in opaque, siloed legacy systems.

From ZKsync to StellarTradable has been building its private credit infrastructure on ZKsync, where its on-chain technology allowed institutional asset managers to migrate investment strategies on-chain and access a broader investor base. The pivot to Stellar signals a strategic shift toward a network with deeper institutional roots and a more established compliance architecture. Tradable operates as a private credit tokenization and liquidity platform, providing deal ownership management and access to institutional-grade private credit deals.

The move also reflects Stellar's growing pull in the real-world asset space. In the first half of 2026, Stellar crossed $3 billion in tokenized real-world assets, hitting the $1 billion, $2 billion, and $3 billion marks all within six months. That momentum has attracted a roster of well-known institutional names. A growing number of regulated financial institutions, including Franklin Templeton, PayPal, WisdomTree, and MoneyGram, have chosen the Stellar network for settlement, tokenized assets, and global payments.

Why Stellar for Institutional Private CreditTradable's choice of Stellar is consistent with the network's positioning as a compliance-first blockchain for regulated asset issuance. Franklin Templeton pioneered tokenized treasuries on Stellar, enabling 24/7 trading of U.S. government securities with under 6-second settlements and near-zero transaction costs. WisdomTree, with over $100 billion in AUM, offers 13 digital funds on Stellar through WisdomTree Prime, seamlessly integrating fiat, digital assets, and tokenized investments.

The compliance infrastructure underpinning these deployments is built directly into the protocol. Nearly a decade of work with Securrency, now DTCC Digital Assets, helped embed compliance tools such as clawbacks, transfer restrictions, and identity controls directly into the Stellar network. That foundation has made Stellar the preferred venue for institutions that need more than speed. For regulated firms, moving assets on-chain requires compliance with securities laws, sanctions requirements, and investor protections, creating demand for blockchain infrastructure that can support identity checks, transfer restrictions, and other compliance controls.

Tradable's migration adds further institutional weight to a network that is increasingly becoming the default rail for tokenized private markets. With $1 billion in private credit moving from ZKsync to Stellar, the deployment is one of the larger chain migrations in the private credit tokenization space to date.

Sources
Markets Media: Tradable Tokenizes $1.7bn of Institutional-Grade Private Credit Positions
CoinDesk: How Stellar Became Part of DTCC's Tokenization Push for Wall Street Securities Onchain
Messari: State of Stellar Q1 2026
2026-07-01 14:16 3mo ago
2026-07-01 11:14 3mo ago
REAL spustil soukromou vrstvu pro tokenizovaná aktiva
ETH Ethereum ZK zkSync
CoinGecko News 78
Original source text
REAL launches a confidential execution layer using ZKsync's Prividium tech, letting banks and funds manage tokenized assets onchain with privacy controls and Ethereum settlement.

REAL, a blockchain infrastructure provider focused on tokenized real-world assets, has rolled out a confidential execution layer aimed at regulated financial firms that want to operate onchain without broadcasting every move.

The new layer runs parallel to REAL's public Layer 1 network and uses ZKsync's Prividium technology, which gives banks, asset managers, and funds privacy controls over positions, allocations, and counterparty data. Settlement still happens on Ethereum, so institutions retain access to public liquidity even while keeping sensitive activity off the open network.

For years, regulated firms have faced a structural tradeoff. Public blockchains offer global reach, near-instant settlement, and composability, but they also expose treasury strategies, portfolio positions, and trading relationships to anyone watching the chain. That visibility has kept many of the largest potential participants out of the tokenized real-world asset market, even as issuance volumes climbed.

REAL is positioning the confidential layer as a direct response to that gap. The architecture lets firms keep privacy and public settlement together, with the confidential chain handling sensitive activity while the public chain provides access to onchain liquidity.

"Institutions shouldn't have to choose between public liquidity and operational privacy. We're building infrastructure that delivers both," said Ivo Georgiev, CEO of Real Finance. 

The company's view is that issuance volumes alone will not define the next phase of tokenization. What matters is whether institutions can run their daily operations on these systems.

The new layer is designed around workflows where confidentiality is a baseline requirement: wealth and asset management mandates, balance sheet operations, tokenized deposit structures, and selective disclosure to auditors, compliance officers, and regulators when a review calls for it. Firms still get blockchain-native settlement and distribution, but their portfolio activity does not sit in plain view.

The release extends REAL's broader pitch around the lifecycle of tokenized real-world assets, which spans issuance, risk assessment, insurance, trading, and institutional execution under one compliance-aware architecture. The company has been building toward an environment where regulated capital can move onchain without forcing operators to rebuild reporting and oversight processes from scratch.

"This is about giving institutions a practical path into onchain finance," Georgiev added. "Real-world assets onchain require infrastructure that reflects how regulated finance actually operates. That's what we're building."

Tokenized real-world assets have drawn growing interest from major banks, asset managers, and other regulated firms over the past two years. The pitch is straightforward: blockchains can move money and assets faster and at lower cost than legacy rails. The friction has come from infrastructure that does not match how institutional desks actually operate, especially around confidentiality of positions and counterparties.

REAL is built on Cosmos Tendermint and uses a dual-validator model that includes both technical validators and business validators such as tokenizers, risk scorers, insurers, and credit agencies. Prividium, the underlying privacy infrastructure for the new layer, is ZKsync's product for regulated entities seeking configurable confidentiality and Ethereum settlement.

The company is headquartered in Sofia, Bulgaria.

Author

BSCN

BSCN's dedicated writing team brings over 41 years of combined experience in cryptocurrency research and analysis. Our writers hold diverse academic qualifications spanning Physics, Mathematics, and Philosophy from leading institutions including Oxford and Cambridge. While united by their passion for cryptocurrency and blockchain technology, the team's professional backgrounds are equally diverse, including former venture capital investors, startup founders, and active traders.