Skip to content

Receivers v2.0 or DAO? #98

@DevElCuy

Description

@DevElCuy

Current implementation of receiver files describe how many Devcoins the beneficiaries should be paid on every block generation within a given round. Those payments didn't happen 100% of time for different situations:

  1. Receiver files where not published on time
  2. Receiver files were not in consensus (more than 50% of them should provide same info)
  3. Miner's node were not able to download the receiver files when generating a new block

Solution alternatives:

  1. Implement Receivers 2.0 (and it should be a robust one)
  2. Migrate into DAO model

Both involve more than just coding, since File custodians are on charge of mirroring the receiver files that are downloaded by every single Devcoin wallet and node.

Regarding the DAO, we could either have our very own NEVM or relay on Syscoin's.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions