-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support for hard-fork contract #93
Labels
enhancement
New feature or request
Comments
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 3, 2023
agaffney
added a commit
that referenced
this issue
Dec 4, 2023
agaffney
added a commit
that referenced
this issue
Dec 4, 2023
agaffney
added a commit
that referenced
this issue
Dec 4, 2023
agaffney
added a commit
that referenced
this issue
Dec 4, 2023
agaffney
added a commit
that referenced
this issue
Dec 4, 2023
agaffney
added a commit
that referenced
this issue
Dec 4, 2023
This was done partially in #98 |
This was finished in #192 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's a TUNAv2 contract with some changes. We want to be able to support both.
I've looked through the TUNA hard-fork contract, and I've noticed a few differences:
TargetState
object (used by the miner internally) has its fields reordered and a newminer
bytestring field addedminer
bytestring is a blake2b hash of either a public key hash or a NFT (for mining pools, I think)miner
field, the contract will verify that it matches one of the signers on the transactionextra
(message) last instead of before the interlinkIt's harder to determine what changes we'll need in the TX building (extra redeemers or whatever) from looking at the smart contract, so we may need to wait until Fortuna is updated to see what's needed
The text was updated successfully, but these errors were encountered: