hello everyone, we see your questions on the v31 update, and I’ll answer them below.
Why the interop fees are not in this release:
The fees ran on Gateway-based public interop, and that is what was deferred. Over recent months the team worked directly with the institutions building on ZKsync. Their requirements were consistent: private execution, settlement direct to Ethereum, and atomic interop between their own environments, rather than public interop routed through Gateway. v31 was rescoped to the foundation that path depends on. The Gateway interop code, including the fee mechanics, is complete, audited, and remains in the codebase, inactive. It could be brought into production through a future governance proposal and any implementation steps required at that time. The full account of what changed and why is in the deprecation notice on the original post [deprecation notice].
On “dropped entirely” and whether the community is being sidelined:
Nothing here bypasses the community. The consultation is the governance vote, and it is still ahead. This rescoped proposal is live for review now, and nothing in v31 executes without passing that vote.
On the claim that fees were promised before the first TPP-18 minting:
That misrepresents what I wrote. My statement in the TPP-18 thread was that v31 was expected to ship ahead of the first minter activation. That was a timeline expectation as of that date. It contained no promise that fees would pass before minting and said nothing about dilution. The full exchange is on the record [TPP-18 thread reply]. Two things from that statement did not hold, and they are that: the timeline slipped, and the scope changed. Both are now documented in the rescoped proposal.
On token utility:
No decision to abandon anything has been made. ZK is the network’s native and governance asset. The fee mechanics exist in the codebase and are inactive. Whether any fee mechanism activates is a governance decision, not a team announcement.
On trust in the process:
TPP-18 went through the standard governance process: a public proposal, feedback from ZKsync delegates, open discussion, and an onchain vote, with the allocation visible to every voter. v31 goes through the same process. When the scope changed, it was published as a new proposal with a deprecation notice explaining the change, precisely so the record stays intact and delegates vote on what will actually ship.