Integrate the intermediate states #76
Description
What is the problem or limitation you are having?
Currently, the intermediate states during the derivation process from Sa1 to Sa2 (represented as Sa1i) are not being exposed in a way that they can be easily stored or accessed outside the protocol. This makes it difficult to resume or manage the derivation process, particularly when we need to store intermediate states for resuming derivation.
Describe the solution you'd like
We would like to integrate the intermediate states (Sa1i) from the derivation of Sa1 to Sa2 into the GreatWall protocol, so they can be exposed to the application. The intermediate states should be accessible in a manner that allows them to be stored and later retrieved or resumed. This would enable applications to persist the derivation process, track intermediate steps, or resume from any given point in the derivation sequence.
The solution could involve emitting intermediate states through a stream or callback mechanism, so that each intermediate state can be captured as it is generated during the derivation process. This would allow the protocol to expose these states to the application in a usable format for storage.