Proposal#
Proposals represent a formal request submitted by a PWR token holder to initiate changes within:
- Mother DAO: Overall governance rules, treasury allocations, or strategic direction of the protocol.
- Or Child DAO: Specific project goals, resource distribution, or operational decisions.
Each proposal:
- Is subject to voting to confirm alignment with the community's consensus before implementation.
- Has a set of Properties.
Properties#
The proposal properties:
- Title.
- Status.
- Proposal Details:
- Proposal ID.
- Proposal Sender.
- Proposed By.
- Tx Timestamp.
- Proposal Height.
- Current Height.
- Voting Information:
- Voting Start.
- Voting End.
- Voting Metrics.
- Description.
- Payload.
Title#
The title of a proposal.
Status#
The current state of a proposal:
- discussion: First hour after proposal creation, open for discussion.
- voting: Voting is in progress from the start until the end of the voting period.
- noQuorum: Proposal fails due to insufficient votes.
- votingFailed: Proposal rejected due to the majority voting No.
- waitingForTx: Proposal approved by majority voting Yes, awaiting execution.
- inBlockchain: Proposal successfully implemented on the blockchain.
Proposal ID#
The unique identifier of a proposal.
Proposal Sender#
The wallet address associated with the PWRDAO.
Proposed By#
The proposal creator's wallet address.
Tx Timestamp#
The date and time a proposal was submitted in the DD/MM/YYYY, HH:MM format.
Proposal Height#
The blockchain height when a proposal was created.
Current Height#
The current height of the blockchain.
Voting Start#
The time voting begins in the DD/MM/YYYY, HH:MM format.
Voting End#
The time voting ends in the DD/MM/YYYY, HH:MM format.
Voting Metrics#
The voting metrics include the parameters:
- Activity for quorum: vPWR token amount needed to approve the proposal by voting in favor.
- Activity: Total amount of PWR tokens staked for the proposal.
- Yes: Total vPWR tokens voting in favor.
- No: Total vPWR tokens voting against.
Description#
The proposal description.
Payload#
The set of properties that represent a transaction to broadcast if the proposal receives sufficient votes.
The supported payload properties:
| Property | Transaction Type | Description |
|---|---|---|
| type | All | Supported transaction type: - Transfer: 4.- Data: 12.- Set Script: 13.- Invoke Script: 16. |
| timestamp | All | Transaction timestamp per the Unix time in milliseconds. |
| senderPublicKey | All | Public key of the transaction sender in the base58-encoded byte array format. |
| fee | All | Transaction fee in the smallest unit.Example: A 0.001 WAVES fee is shown as 100000, since 1 WAVES = 10^8 WAVELET |
| feeAssetId | All | Base58-encoded token ID or null for WAVES. |
| version | All | Transaction version in the binary format. |
| recipient | Transfer | Base58-encoded recipient address or recipient alias in the alias:<CHAIN_ID>: prefix format.Example: alias:T:merry |
| amount | Transfer | Transaction token amount. |
| assetId | Transfer | Base58-encoded token ID or null for WAVES. |
| attachment | Transfer | Arbitrary binary data. Typically, a base58-encoded comment of up to 140 bytes. |
| data | Data | Data property including key-value pairs: |
| script | Set Script | Base64-encoded compiled script: - Account script: Up to 8192 bytes. - dApp: Up to 163,840 bytes. - null: Delete script. |
| dApp | Invoke Script | Base58-encoded dApp address or dApp alias in the alias:<CHAIN_ID>: prefix format. Example alias:T:merry. |
| call | Invoke Script | Call property including key-value pairs: |
| payment | Invoke Script | Payment property including key-value pairs: |
| chainId | Invoke Script | Waves blockchain network ID: - Mainnet: W or 87.- Testnet: T or 84.- Stagenet: S or 83. |
Operations#
The supported operations with proposals:
- Add: Add a proposal.
- Edit: Edit the proposal's title and description.
- Retract: Retract the proposal.
- Vote: Vote on the proposal.