dPoW
dPoW copied to clipboard
KomodoPlatform
Komodo delayed Proof of Work software
Commit: https://github.com/VerusCoin/VerusCoin/commit/07ff18aa5a51be8bb1abbb4f9093e24b71e04109 Release: https://github.com/VerusCoin/VerusCoin/releases/tag/v1.2.2-5
- Updates VRSC (contingent on sec review of https://github.com/VerusCoin/VerusCoin/compare/dee30f3...1d62f81) - Updates scoring epochs.json for KIP chains - Adds VOTE2024 - Updates Notary Node Bible with new dates
Commit: https://github.com/VerusCoin/VerusCoin/commit/dee30f36c31aa60dfd6cfbd5b5ebf21cfafa2169 Release: https://github.com/VerusCoin/VerusCoin/releases/tag/v1.2.2-2
Can we confirm which fields are unnecessary here? _Originally posted by @Alrighttt in https://github.com/KomodoPlatform/dPoW/pull/494#discussion_r1247035651_
These are only used for the notarystats and notarychains rpc methods, and could be removed entirely as I don't believe we use these methods. _Originally posted by @Alrighttt in https://github.com/KomodoPlatform/dPoW/pull/494#discussion_r1247070222_
Similar to https://github.com/KomodoPlatform/dPoW/issues/477 Once an update has been merged to master, this should trigger the creation of a draft PR to update the contents of https://github.com/KomodoPlatform/dPoW/blob/master/doc/scoring_epochs.json with an entry using...
To better manage seed node update announcements for NNs, we should be able to use actions + github API to: - create an issue in this repo to alert about...
>>Notarization counts to be determined from decoded notarization transaction OP_RETURN data on KMD block chain. The bible mentions above. Is there a reason we only count notarizations on the KMD...
A malicious actor could theoretically issue a notarization transaction by controlling a minimum of 13 NNs. I propose an additional validation layer where 13 NNs still issue the notarization TX...
