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

Deterministic Masternodes GUI + Bug Fixes #2791

Closed
wants to merge 84 commits into from

Conversation

Liquid369
Copy link
Member

Co-Authored with @panleone
Trying to follow up on work with Deterministic Masternodes, this was taken from furszy's repo and has been running regtest.
We found a few issues along the way trying to carry forward the current work, this PR will essentially supersede PR#2751 as it has the DMN GUI already and we are carrying forward the testing process.
This PR fixes two bugs we found in regard to Creating Masternodes with a Single Input, alongside allowing said input into mempool and causing the chain to stall.

Upcoming work to still do:

  • Continue Testing code
  • Add a new masternode type which will bridge between ipv4 and ipv6
  • Extend bip6 protocol with this new masternode type

We will update the list accordingly as we assess more work and features/functionality

furszy added 30 commits March 8, 2022 11:19
Decoupling the RPC server errors from the function.
And use the `PROTOCOL_VERSION` instead of the `CLIENT_VERSION`. Which should had never been used there as the serialization of inputs/spend_notes cannot be modified changing the `CLIENT_VERSION`, it's a hard-fork that needs a protocol bump.
Same validation is performed inside TryATMP.
…the network.

The transaction inputs are always from the wallet.
And remove duplicated available inputs validation. The code will perform the same check few lines after the signature inside ATMP.
Differentiating deterministic from legacy masternodes
…created locally).

Only useful when the owner generates the operator key, so the object can be securely stored inside the wallet.dat encrypted.

A future work could create an encryptable db for this specific object.
@Liquid369
Copy link
Member Author

Superseding PR #2804

@Liquid369 Liquid369 closed this Feb 9, 2023
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.

4 participants