pc20

package

v0.0.42 Latest Latest Go to latest Published: Jul 23, 2026 License: MIT Imports: 7 Imported by: 0

Details

Valid go.mod file
Redistributable license
Tagged version
Stable version
Learn more about best practices

Repository

github.com/pushchain/push-chain-node

Links

Open Source Insights

Documentation ¶

Index ¶

Constants
func CreateUpgradeHandler(mm upgrades.ModuleManager, configurator module.Configurator, ...) upgradetypes.UpgradeHandler
func NewUpgrade() upgrades.Upgrade

Constants ¶

View Source

const UpgradeName = "pc20"

UpgradeName is the on-chain name of the pc20 upgrade. It MUST match the plan.name in the MsgSoftwareUpgrade governance proposal.

Variables ¶

This section is empty.

Functions ¶

func CreateUpgradeHandler ¶

func CreateUpgradeHandler(
	mm upgrades.ModuleManager,
	configurator module.Configurator,
	_ *upgrades.AppKeepers,
) upgradetypes.UpgradeHandler

This is a NO-OP state upgrade: the pc20 feature adds no new store keys, no module ConsensusVersion bumps, and no migrations — it is a binary-only change (new x/uexecutor pc20 handling + the VAULT_PC / VAULT_PC20 system-contract definitions in x/uregistry). The VAULT_PC (0xB0) and VAULT_PC20 (0xB1) contracts are deployed separately from the EVM side after the upgrade, so the handler does not touch EVM state. It only runs RunMigrations (a no-op here) so the chain swaps to the new binary and resumes producing blocks.

Types ¶