Proposals

Learn how to create a proposal on Swipe Governance

Users who have the requires SXP staked on the Swipe Network or proper amount of SXP delegated to their address have the ability to create Swipe Improvement Proposals (SIPs)

To view the Governance main dashboard where you can click the Dashboard menu item as shown below which is where you may begin the process to Create Proposals.

Once you have entered the Governance Dashboard screen you can start a new proposal if you have enough SXP to create one either through units staked or units delegated from other stakers. To start press Create Proposal as shown below:

You will now see a proposal popup which you can use the interface to fill in the address and signatures required for the changes as shown below:

Please note: The Swipe Improvement Proposal can have up to 10 actions (based on proposalMaxOperations()). The proposer cannot create another proposal if they currently have a pending or active proposal. It is not possible to queue two identical actions in the same block (due to a restriction in the Timelock), therefore actions in a single proposal must be unique, and unique proposals that share an identical action must be queued in different blocks.

Please see the details below if you are using the smart contracts directly

Governor

function propose(address[] memory targets, uint[] memory values, string[] memory signatures, bytes[] memory calldatas, string memory description) returns (uint)

• targets: The ordered list of target addresses for calls to be made during proposal execution. This array must be the same length as all other array parameters in this function.

• values: The ordered list of values (i.e. msg.value) to be passed to the calls made during proposal execution. This array must be the same length as all other array parameters in this function.

• signatures: The ordered list of function signatures to be passed during execution. This array must be the same length as all other array parameters in this function.

• calldatas: The ordered list of data to be passed to each individual function call during proposal execution. This array must be the same length as all other array parameters in this function.

• description: A human readable description of the proposal and the changes it will enact.

• RETURN: The ID of the newly created proposal.