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: Adds Proof of Possession verification during node registration #301

Closed
wants to merge 11 commits into from

Conversation

joshuahannan
Copy link
Member

https://github.com/dapperlabs/flow-go/issues/6284

Adds a parameter to the addNodeRecord method in the staking contract for the proof of possession.
In the NodeRecord init function, this is verified with the staking key.

Also updates the locked tokens contract, staking collection, and all of their transactions to include this parameter

@joshuahannan joshuahannan requested a review from tarakby July 29, 2022 18:07
@tarakby tarakby force-pushed the proof-of-possesion branch from 6bb3b88 to 964d1ba Compare August 8, 2022 19:51
@tarakby
Copy link
Contributor

tarakby commented Aug 8, 2022

I've started to add the tests on top of your work, but eventually hit some issues with the contracts. They issues should be easier for you to solve.
My work is on this PR (against your branch), feel free to review it and merge it.

* update manifest.go and manifest files

* add POP generation helper and add extra parameter to transactions

* update contract comments

* update to newest overflow and fixed tests (#306)

* fix dependencies

* add correct number of arguments to transactions

* fix placeholds PoPs

Co-authored-by: Bjarte S. Karlsen <[email protected]>
Co-authored-by: Josh Hannan <[email protected]>
@joshuahannan joshuahannan marked this pull request as ready for review August 19, 2022 19:29
@tarakby
Copy link
Contributor

tarakby commented Aug 19, 2022

This PR is ready but will wait for the Ledger integration to be merged. This would simplify the contract updates during the future network sporks, while Ledger updates are being developed.

@tarakby
Copy link
Contributor

tarakby commented May 3, 2024

Next step for this PR is to rebase on the stable Cadence branch

@tarakby
Copy link
Contributor

tarakby commented May 7, 2024

Rebasing the PR on the stable-cadence branch is done in separate PR #425. The current PR won't be merged to Cadence v0 and will be used directly with Cadence v1

@tarakby tarakby closed this May 7, 2024
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.

2 participants