-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Miner] chore: scaffold create-claim message #43
Conversation
acfdf18
to
7f7c544
Compare
InvalidationHeight doesn't seem to be used |
Nice catch! 👍 I had already removed it from the code but forgot to update the scaffold command in the description. |
`ignite scaffold message create-claim session_header:SessionHeader root_hash --signer SupplierAddress --module supplier` (NB: generated a temporary SessionHeader duplicate in the supplier module so the above would work; subsequently, removed and updated protobuf import and usage.)
7f7c544
to
d6ce316
Compare
The base branch was changed.
Co-authored-by: Daniel Olshansky <[email protected]>
a68e595
to
20c6373
Compare
- supplier address | ||
- session header | ||
- claim | ||
2. [ ] last block height commitment; derives: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this more relevant to the proof flow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is, but it must be committed to already at the point. IIRC, the point was to have the client commit to some block to say, "this is the latest block I'm aware of, so please use it's block hash" (or something similar; off-by-one, etc.). Then it's up to the on-chain logic to decide if that block is too old to be used as the pseudo-random input for the msg distribution logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Not to be confused with the pseudo-random input for the proof path.) 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@red-0ne 👆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@red-0ne I saw your comments but believe it's okay to merge it in without resolving them. I see them as guidelines for the reviewer to document and share what the next step is, but not anything set in stone.
I think it's a great example of why we need to keep these PRs small because we can potentially have a whole day of discussion on each of the bullet points, but need to keep things moving in smaller chunks.
* pokt/main: [Miner] chore: scaffold create-claim message (#43)
* pokt/main: [Service] Added the `Service` type Updated the command for unit tests in the PR template Updated PR template [Miner] chore: scaffold create-claim message (#43) [E2E] Add basics of the E2E suite (#62) [Gateway] Scaffold the unstake gateway message and nothing else (#67) [Gateway] Scaffold the gateway stake message and nothing else (#66) Add placeholder for auto-generated packages
* chore: scaffold create claim message `ignite scaffold message create-claim session_header:SessionHeader root_hash --signer SupplierAddress --module supplier` (NB: generated a temporary SessionHeader duplicate in the supplier module so the above would work; subsequently, removed and updated protobuf import and usage.) * refactor: use `bytes` type for `MsgCreateClaim#root_hash` field * chore: add TODO comment in msg handler * chore: add TODOs Co-authored-by: Daniel Olshansky <[email protected]> --------- Co-authored-by: Daniel Olshansky <[email protected]>
Summary
This message type is a nested dependency of the
Miner
via theSupplierClient
.MsgCreateClaim
message types, handlers, etc.:MsgCreateClaim#root_hash
type fromstring
to[]byte
& refactor usages.Issue
Related to:
This message type is a nested dependency of the
Miner
via theSupplierClient
.Type of change
Select one or more:
Testing
make go_test
Sanity Checklist