Skip to content

Governance Design v1.1.0 Release Notes

Compare
Choose a tag to compare
@quocle108 quocle108 released this 24 Mar 03:34
· 43 commits to master since this release
57fc0a9

Community contract

Config Badge (#11 )

Config badge code has been added to the community contract . For now each badge will has separated code ( create badge, issue badge and config badge) based on badge ID. This feature allow issuer can config different Right Holder for each Badge ID

Community Reader (#13 )

To define who can read the community information in Code in Force UI, Community contract has been added the access table right holder . Remember this feature only prevent users to access from UI. If users access blockchain directly they can read all public information without limitation.

Verify Other Right Holder (#18 )

In the last version, it only verify for right holder based on badge ID, account name, position ID. For now, it has more option for right holder:

  • is_anyone: anyone can be a right holder
  • is_any_community_member: any community member can be a right holder
  • required_tokens: required at least token amount to become right holder

Community Name Rule (#19 )

To distinguish between community name and account name, Community contract only allow to create community account name from 6 to 12 characters and must include ".c" in the last name.

Other Changes

(#6 ) Fixed cannot config for amendment code
(#7 ) Allow execute proposal and approve position automatically through deferred transaction
(#8 ) Fixed requires community permission to create a position
(#12 ) Pass rule is no longer needed in position election. instead of it will select the candidate based on the voted weight until it has enough member to fill in the position

Dependencies

This release depends on eosio.cdt v1.7.x and (optionally) on can v1.0.x. To compile the contracts in this release, first install eosio.cdt v1.7.0.