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:
Receiver files where not published on time
Receiver files were not in consensus (more than 50% of them should provide same info)
Miner's node were not able to download the receiver files when generating a new block
Solution alternatives:
Implement Receivers 2.0 (and it should be a robust one)
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.
Satoshi0x
commented
2 years ago
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:
Solution alternatives:
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.