Improve our transaction saving process.

[gianfra-t]

Context

Currently, we are storing all the signed transactions and information about the offramp on google sheets, right after those are created and before the offramp starts.

Since storing these transaction is critical to avoid loosing funds, we could potentially replace google sheets as a database with something that provides us with more assurances:

• That the transaction was stored correctly.
• Can't be accidentally deleted by manual manipulation.
• And potentially has replicas or backups.

Since we do not require large read/write counts (1 write, and < 1 read per offramp) as well as no need to keep this data after the offramp succeeds, we might be able to meet these requirements with very low cost. One potential alternatively very briefly explored was firestore.

TODO

• Briefly explore some cloud providers, aiming at NoSQL to avoid keeping a schema.
• Once the provider is selected, modify the signer-service or the ui to store the transactions object, with emphasis on ensuring it was commited.

[gianfra-t]

@prayagd this is more of a tech core and technical debt issue. A low hanging fruit to further decrease the chances of loosing funds.

[prayagd]

Hey team! Please add your planning poker estimate with Zenhub @ebma @gianfra-t @Sharqiewicz