jaros1
commented
7 years ago - a chat message can have one or more money transactions included. Use chat level transaction id or one id for each money transaction? Seen from UI it should be all or nothing but that is hard to ensure on a distributed network like ZeroNet and using external money APIs. Maybe a transaction id with line number 1..n where n = number of transactions in chat message.
- either MN or W must add an unique transaction id when starting a money transaction from chat.
- maybe receiving MN or W should also add unique transaction id when receiving a money transaction in chat? Could be reverse transaction id + line number.
- keep track of transaction status for each transaction id.
- the two wallets should if possible agree on transaction status. That iis one transaction status for each wallet.
- transaction done if both wallets agree on done transaction.
- approved and done transactions could be distributed to a small numbers of peers on ZeroNet in a non reversible way.
- from MN UI: use transaction id in approve, reject, cancel and status requests.
- public transaction id or hidden transaction id? public transaction id is bad for privacy. maybe used same model for optional filenames as in MoneyNetworkAPI. Derived from a secret sessionid.
- transaction id = sessionid. shared between the two wallets and the two MN sessions.
-
.0000000000000 - special file with offline transactions. maybe not needed. all W2W transactions should maybe be offline transactions. cannot expects two wallets to be open at the same time.' -
.0000000000001 - special file with transaction status. encrypted with sessionid only. All 4 sessions (2*MN and 2*W) can read transaction status. A code and a test. code used be wallets. text displayed in MN chat - wallets may add extra encryption in W2W communication. For example ekstra public/private key sets. Use same encryption model as in MoneyNetworkAPI (3 layers encryption)