Jan 9 - Jan 9, 2025
The primary justification for this feature is to prevent pools from providing false information about share indexes within a slice during challenges. However, this concern may be mitigated by the fact that the path itself suffices to determine the index of a leaf, a task for which the pool is already responsible for providing the necessary data. This suggests a potential redundancy in requiring the share_index to be committed and returned, given that the path information alone accomplishes the objective of index verification without the need for additional mechanisms.
Thread Summary (0 replies)
Jan 9 - Jan 9, 2025
1 messages
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback