celestia

this issue is encapsulating the comment here that was not addressed in #331 per the request of #257

We need to make sure that large messages encode to shares properly. This could be hard coded, in that we know that a message of size X takes up Y shares when encoded, but preferably we should have some function that t

Summary

Add explanatory information inside config.toml

Impact on users

ATM, users need to navigate to the networks repo in order to find a guideline on config.toml
Having all the explanatory info inside config.toml eases this step for future users

Cost of not doing

Jumping back and forth from config.toml to networks repo guide is cumbersome

Evidence

A lot of users are aski

in the current cli integration test, we are checking to see that emitted events contain a multiple of the share size instead of checking for a direct size. We should update that test to check for a specific size.