Callum Waters
Callum Waters
What do we imagine blob submitters need to sign over other than PFBs and other Celestia state transactions. I just want to make sure we're focused on providing DA or...
I see. Thanks for the context! I agree that it should really be it's own module. To be clear, I was thinking that the key manager should be something independent...
Yeah I think we can just close this. We may have forgotten to extend it to this long-lived branch anyway
> Or we should remove init altogther in favor of lazy init from start That can be done as a separate issue. We should make sure that the user has...
Just that we should store the node id and jwt secret
Can this target something like `feature/fibre`?
I think there needs to be information in docs.celestia.org as well for the actual developers that may want to know how to use it
Note that the specs are hosted in celestia-app and should be updated only after v2 has been released and `main` is now targeting v3
Note we already have: https://github.com/celestiaorg/celestia-app/blob/2e49d665b3275e769dfe0371b1ca41e39dc3f5f5/test/txsim/blob.go#L41
What exactly are we trying to assess here. Is it that we can still validate headers even if there's been a validator set change greater than 1/3