Closed
Description
Why
In order to optimize the signer memory usage on the SPO infrastructure when signing Cardano transactions, we need our Merkle tree library to support multiple/custom store implementations optimized for:
- Proving in the aggregator: fast but memory intensive (serves both signature and proving)
- Signing in the signer: slower but memory optimized (serves only signature)
What
Implement a Merkle tree store with optimized memory usage in the signer.
How
- Upgrade the Merkle tree implementation to support multiple stores
- Implement a store for the signer with optimized memory usage based on SQLite
- Benchmark the new signer store
- Update the signer footprint in documentation