You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some initial exploration into updating the block explorer and the network stats dashboard and some helpful hints from @travisperson it looks like decoding the values output from dag get on the front end will be more onerous than it is worth. More importantly that decoding is really go-filecoin's job so the node's API should do that for us.
Acceptance criteria
Three new pieces of CLI functionality
(1) a --full flag on show block which returns the block header with messages and receipts embedded directly in it. We'll use this flag to keep the old behavior
(2) a show messages command that returns a properly decoded SignedMessage array given the Messages cid from a block header
(3) a show receipts command. Ditto (2) for receipts
These three userfacing endpoints will rely on the following internals:
(a) a new FullBlock type which may be useful elsewhere
(b) GetMessages function on the chain state plumbing/porcelain
(c) GetReceipts function on the chain state plumbing/porcelain
b & c are very close to being done because the prep work already piped a message store to the chain state.
Risks + pitfalls
Where to begin
start with the internals
The text was updated successfully, but these errors were encountered:
Description
After some initial exploration into updating the block explorer and the network stats dashboard and some helpful hints from @travisperson it looks like decoding the values output from
dag get
on the front end will be more onerous than it is worth. More importantly that decoding is really go-filecoin's job so the node's API should do that for us.Acceptance criteria
Three new pieces of CLI functionality
(1) a --full flag on
show block
which returns the block header with messages and receipts embedded directly in it. We'll use this flag to keep the old behavior(2) a
show messages
command that returns a properly decoded SignedMessage array given theMessages
cid from a block header(3) a
show receipts
command. Ditto (2) for receiptsThese three userfacing endpoints will rely on the following internals:
(a) a new
FullBlock
type which may be useful elsewhere(b)
GetMessages
function on the chain state plumbing/porcelain(c)
GetReceipts
function on the chain state plumbing/porcelainb & c are very close to being done because the prep work already piped a message store to the chain state.
Risks + pitfalls
Where to begin
start with the internals
The text was updated successfully, but these errors were encountered: