Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP - Prometheus Fork Development/Testing - V3.0.1 #12

Open
wants to merge 23 commits into
base: master
Choose a base branch
from

Conversation

Dev-JamesR
Copy link
Member

WIP - Prometheus Hard-Fork

The Prometheus hard fork will enable a new decentralized node validation system. The new system utilizes a prioritized tx type allowing nodes with upcoming validation opportunities to gather signatures from peered/collateralized nodes in order to offer up proof of activity. The proof of activity is then recorded to an indexing contract allowing other nodes to pull in signed evidence of activity (utilizing zero-knowledge proofing/sigs) to accurately pay out node rewards during consensus finality.

Prometheus Hard-Fork - Deployment Schedule

Private Testnet

  • Finish/Test Consensus Finality/Reward Payments
  • Verify node communication systems are accurately signing/validating and sharing zk proofs
  • Test & Update node validation/proof tracking contract to replace existing contracts deployed on Xerom
  • Complete testing of fork from current DNP V2.0 to Prometheus hard-fork validating a successful transition from current reward payment system to Prometheus.

Xerom Deployment

  • Deploy validation/proof tracking contract to Xerom chain
  • Validate proof tracking/updating is fully functional
  • Select an upcoming fork block
  • Facilitate network wide update to Prometheus V3.0

Additional Updates/Testing Will Be Required to Eventually Facilitate Deployment to Ether-1

@Dev-JamesR Dev-JamesR self-assigned this Feb 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant