Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using latest eosio.forum contract on mainnet #4

Open
7 tasks
DenisCarriere opened this issue Sep 18, 2018 · 1 comment
Open
7 tasks

Using latest eosio.forum contract on mainnet #4

DenisCarriere opened this issue Sep 18, 2018 · 1 comment
Assignees

Comments

@DenisCarriere
Copy link
Member

DenisCarriere commented Sep 18, 2018

Using latest eosio.forum contract on mainnet

contract => eosforumrcpp

Major Changes/Considerations

  • proposals are now immutable
  • have an expiration date (max 6 months)
  • a freeze "cool-off" period when expiration happens no vote are accepted and cannot be cleaned for 3 days after freeze.
  • Proposer can expire at anytime (before initial expiration), but is also subject to this freeze.

Basically you have 3 days where you can reliably get table in a stable state

  • Proposals are in flat namespace (not scoped under proposer)

this does mean that first come first serve for the proposal_name, but the title / content is still arbitrary

  • proposal_name can be reused after they've been fully cleaned (after expiration, after freeze, after cleaning)

don't assume proposal_name is a long term primary key. It's immutable during it's existence in the table.

  • If you want to keep an archive, the best primary key would be (proposal_name + proposer + created_at) I think.
@DenisCarriere DenisCarriere self-assigned this Sep 18, 2018
@fproulx-dfuse
Copy link

@DenisCarriere good! Let me know and @maoueh if you have any question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants