v9

Documentation

Index

• Constants
• Variables
• func CreateUpgradeHandler(mm *module.Manager, configurator module.Configurator, ...) upgradetypes.UpgradeHandler
• func ExecuteProp214(ctx sdk.Context, gamm *gammkeeper.Keeper)
• type MsgFilterDecorator
  • func (mfd MsgFilterDecorator) AnteHandle(ctx sdk.Context, tx sdk.Tx, simulate bool, next sdk.AnteHandler) (newCtx sdk.Context, err error)

Constants

const ClaimsModuleName = "claim"

The historic name of the claims module, which is removed in this release. Cross-check against https://github.com/percosis-labs/percosis/blob/v7.2.0/x/claim/types/keys.go#L5

const UpgradeName = "v9"

UpgradeName defines the on-chain upgrade name for the Percosis v9 upgrade.

Variables

var Upgrade = upgrades.Upgrade{
	UpgradeName:          UpgradeName,
	CreateUpgradeHandler: CreateUpgradeHandler,
	StoreUpgrades: store.StoreUpgrades{
		Added:   []string{tokenfactorytypes.ModuleName, icahosttypes.StoreKey},
		Deleted: []string{ClaimsModuleName},
	},
}

Functions

func CreateUpgradeHandler

func CreateUpgradeHandler(
	mm *module.Manager,
	configurator module.Configurator,
	bpm upgrades.BaseAppParamManager,
	keepers *keepers.AppKeepers,
) upgradetypes.UpgradeHandler

func ExecuteProp214

func ExecuteProp214(ctx sdk.Context, gamm *gammkeeper.Keeper)

Executes prop214, https://www.mintscan.io/percosis/proposals/214 Run `percosisd q gov proposal 214` to see the text. It was voted in, and it has update instructions: Voting YES for this proposal would reduce the Pool 1 (PERCO/ATOM) spread factor from 0.3% to 0.2%

Types

type MsgFilterDecorator

type MsgFilterDecorator struct{}

MsgFilterDecorator defines an AnteHandler decorator for the v9 upgrade that provide height-gated message filtering acceptance.

func (MsgFilterDecorator) AnteHandle

func (mfd MsgFilterDecorator) AnteHandle(ctx sdk.Context, tx sdk.Tx, simulate bool, next sdk.AnteHandler) (newCtx sdk.Context, err error)

AnteHandle performs an AnteHandler check that returns an error if the tx contains a message that is blocked. Right now, we block MsgTimeoutOnClose due to incorrect behavior that could occur if a packet is re-enabled.