Indexers

The protocol JSON can be inscribed using any text inscription service. However indexers needs to be developed to parse the vote inscriptions and tally them by the deadline.

Here we propose a model for indexers:

• Authenticate valid proposal

  • propose op JSON format is valid

  • expiry block height is in the future

  • pid for DAO is unique

  • id matches either input or output of tx as well as inscription owner

• Verify valid vote inscription

  • vote op JSON format is valid

  • vote inscription corresponds to dao and pid

  • vote inscription is received before expiry and after proposal

  • id matches either input or output of tx as well as inscription owner

• Tally the vote inscriptions

  • quorum met (quo % * mem)

  • total valid vote inscriptions cast aye

  • total valid vote inscriptions cast nay

  • total abstains

  • total invalid vote inscriptions

• Display the results

  • if quorum is met, system is majority, and more than 50% cast aye, then display pass result

  • if quorum is met, system is majority, and less than 50% cast aye, then display fail result

  • if quorum is met, system is majority, and exactly 50% cast aye and 50% cast nay, and proposer cast aye, then display pass result

  • if quorum is met, system is majority, and exactly 50% cast aye and 50% cast nay, and proposer cast nay, then display fail result

  • if quorum is met, system is unanimous, and 100% cast aye, then display pass result

  • if quorum is met, system is unanimous, and less than 100% cast aye, then display fail result

  • if quorum is not met, then display null result

  • Results can optionally be displayed by inscribing the tally op for the pid or published on a website or explorer