Solana Mainnet Sees Transaction Size Limit Raised at Epoch 1035

Hosts Note the Activation

Hosts tracking daily protocol shifts opened recent spaces by walking through the details of Solana activating Transaction V1 at the start of epoch 1035. They described the move as a measured increase in capacity rather than a full overhaul of the network.

The change took effect around 01:00 to 01:20 UTC on September 15, 2026. Maximum serialized transaction size moved from 1,232 bytes to 4,096 bytes. That expansion gives developers space to include zero-knowledge proofs, larger multisig setups, and new signature schemes inside a single atomic transaction.

Backward Compatibility Stays in Place

Hosts stressed that legacy and version-zero transactions continue to operate at the prior 1,232-byte limit. Applications and wallets already in use remain functional without immediate changes. Protocols must opt into the new v1 format to take advantage of the higher ceiling.

The upgrade builds on earlier work that included a slot-time reduction in August and a disinflation vote at the end of that month. Commentators in the rooms treated the byte increase as another incremental step rather than a sudden break with existing operations.

Market Snapshot at the Time

CoinGecko data at approximately 12:20 p.m. ET on September 15 showed Bitcoin near 76,278 dollars, down 2.98 percent over 24 hours. Ethereum traded around 2,416.69 dollars after a 4.19 percent decline. Solana sat near 99.06 dollars, off 3.25 percent for the day. Dogecoin hovered at 0.081537 dollars following a 3.20 percent drop.

What the Change Unlocks

Participants in the discussions listed concrete use cases that now fit inside one transaction. Zero-knowledge proofs can travel without splitting across multiple calls. Large multisig approvals become simpler. Confidential transfer schemes and emerging signature methods gain room that previously required workarounds.

Hosts repeatedly clarified that the upgrade does not alter the status of other network proposals or external products. It stands apart from recent exchange-traded product flows and separate regulatory drafts mentioned elsewhere.

Developer Adoption Path

Spaces moderators noted that adoption will depend on individual teams choosing to update their code to the v1 format. No requirement forces immediate migration. The soft rollout allows testing at each protocol’s own pace while the network continues to support the older transaction structure.

Daily coverage of the change has centered on these practical distinctions. Hosts have returned to the same points across multiple sessions: the size increase itself, the continued operation of legacy transactions, and the opt-in nature of the larger limit. That steady cadence has kept attention on the engineering detail rather than broader market narratives.