rmrkdao/rmrkdao-spec

Issues

• CUSTODIAN voteFee should be consolidated in the PROPOSAL

  #21 opened 2 years ago by spenweb
  0

• RESULT validation

  #20 opened 2 years ago by spenweb
  1

• PROPOSAL id schema should be explicit

  #19 opened 2 years ago by spenweb
  0

• Specify RESULT count object keys schema

  #15 opened 2 years ago by spenweb
  4

• RESULT id should be unique

  #14 opened 2 years ago by spenweb
  1

• PROPOSAL options should be a dictionary to decrease resources and potential validation bugs

  #13 opened 2 years ago by spenweb
  3

• Specify expected time format

  #12 opened 2 years ago by spenweb
  1

• Replace datetime types with Epoch seconds

  #11 opened 2 years ago by spenweb
  2

• How should REGISTER with same custodian be handled?

  #10 opened 2 years ago by spenweb
  1

• Rename CUSTODIAN's `custodian` property to `owner`

  #9 opened 2 years ago by spenweb
  1

• Custodian's address is unnecessary for REGISTER interaction

  #8 opened 2 years ago by spenweb
  2

• Consider the case of a tie result

  #4 opened 2 years ago by spenweb
  1

• New entity: RMRK::DAO::RESULT

  #1 opened 2 years ago by spenweb
  1

• New interaction: RMRK::DAO::RECERTIFY

  #3 opened 2 years ago by spenweb
  2

• Custodian reputation needs to be easily known

  #2 opened 2 years ago by spenweb
  1