The Ledger
TRON Activates Proposal 108’s Contract-Storage Setting
TRON says Proposal 108 took effect on November 2, enabling network parameter 102 for contract-storage optimization. The proposal called for operators to upgrade to GreatVoyage-v4.8.2.4 before activation.

“This proposal aims to activate the #102 network parameter, enabling TVM storage key optimization to further improve the stability and reliability of the TRON network.”
yanghang8612, proposal author
TRON switches on TVM parameter 102
TRON’s Proposal 108 has taken effect, enabling network parameter 102 on the mainnet, according to an update posted to the proposal discussion on November 3. The update says the proposal received 25 approvals and took effect on November 2, 2026. It also says parameter 102 is now enabled and closes the discussion because the governance activation is complete.
The proposal concerns the storage-key optimization identified as ALLOW_OPTIMIZE_TVM_STORAGE_KEY. Its voting request used the command createProposal 102 1: 108 is the proposal number, while 102 identifies the network parameter it changes. The proposal says the corresponding changes would activate only after approval and the proposal taking effect. The November 3 status update confirms that sequence has concluded on mainnet.
The proposal’s opening description states its aim directly. Its motivation says reliable smart-contract execution is important to network operation and that stronger TVM storage handling is intended to improve the reliability of contract-storage operations and support network stability. The proposal does not provide a measured throughput result or a transaction-fee change for the activation.
Empedocles was the recommended node version
During the discussion, proposal author yanghang8612 identified GreatVoyage-v4.8.2.4 (Empedocles) as the recommended node version for enabling parameter 102. The author called it a mandatory upgrade and said node operators, particularly block-producing Super Representatives, should upgrade before the proposal took effect. The proposal’s compatibility guidance also advised operators to use a version supporting parameter 102 ahead of activation.
The release page dates GreatVoyage-v4.8.2.4 to October 22, 2026, and marks it as a mandatory upgrade. Its listed changes include improving operation-execution consistency and stability in rare cases, and optimizing smart-contract storage and metadata handling in edge cases. Those release notes describe the software changes; the parameter activation itself was governed separately through Proposal 108.
The proposal discussion set October 30, 2026, as the estimated date for creating the voting request and November 2 as its estimated effective date. On October 30, yanghang8612 wrote that the on-chain proposal had been initiated and was open for voting. The subsequent status update records the outcome: approval with 25 approvals and an effective date of November 2. The issue was closed on November 3.
What the activation changes
ChainCatcher reported on November 3 that the contract-storage optimization introduced in GreatVoyage-v4.8.2.4 was enabled with the proposal’s implementation. Its report describes the intended benefit as improved processing consistency and stability in relevant execution scenarios, alongside greater contract-execution stability and node-operation reliability. These are stated aims and descriptions, not published benchmark results.
The change is therefore specific: a governance vote enabled parameter 102, which turns on the named TVM storage-key optimization. The release provided the recommended software version, while the proposal specified the voting command, preparation guidance and estimated schedule. With the activation complete, the proposal’s discussion page says any later implementation or tooling issues can be tracked separately.
Sources
- Original source TRON TIPs on GitHub github.com
Other pages read
- TRON java-tron release on GitHub github.com
- ChainCatcher h.chaincatcher.com