story: storage of parameters (dapp/lpms)

[xdaluca]

Problem
The smart contracts for videre are only concerned about enforcing settlement and term conditions - and in doing so the contracts only retain a the EIP712 state hash of the typed structured data that makes up the state of the stay.

To paraphrase, the only thing recorded on chain is a hash of the state - therefore there is NO readable "I check in on date dd/mm/YYYY and check out on date aa/bb/CCCC". This data MUST be stored somewhere, otherwise the state cannot be reconstructed, and therefore smart contract execution will be impossible.

Solution
Store the state data in a structure such that:

• feat: stub stage storage in lpms-server #100
• The stays dapp to maintain a copy of the state in local storage.
• After booking a stay, the stays dapp could generate QR code, as well as a signed hash in the structure so that the QR code could have all data embedded within to allow "no-wallet" check-in.