Fault report spike#341
Conversation
|
@rvagg I'm considering putting something like this into filecoin-pin datasets command. Any thoughts? |
| 3. `getMaxProvingPeriod()` - Length of each proving period | ||
| 4. `challengeWindow()` - Size of the challenge window |
There was a problem hiding this comment.
these two can and should be getPDPConfig() where they are both available on the returned struct; we've just been discussing removing these methods because they should have been cleaned up when we made it a single call to get everything.
|
Yeah, very nice. Would be good to have a nice filecoin-pin tool to do this, |
|
I'm going to shut this one down. If we want to work on this again we can potentially reference it, though the quality of the code is such that we may be better off just starting again from scratch |
5 participants
Not convinced we should commit this but here is a demo of how to interact with ethcalls to get a complete fault report. State viewer has a few basic methods which make checking this information simple.
This is a claude heavy PR so some mistakes are going to be in here and the writing is a little AI-y. But I've tested it out and it works pretty nicely.