mikemey / mex Goto Github PK

• new and existing user

on startup: useraccount-/wallet-service need to update balances from past blocks that might have been missed (due to down-time)

after requiredConfirmations metadata

investigate + fix

• request from wallet-service
• wallet-service down

• broadcasts confirmation on new deposits until settled

avoid uWebSockets.js dependency - due to authors release issues

• add WalletService to orchestrator start
• live update transactions:
  • deposits to new address
  • wait for current deposit update
• existing user journey:
  • deposit to user balances
  • invoice settled against balances

• broadcast updates on chains, first supported: new btc blocks

subscriptions from a ws-client to a topic (on ws-server) aren't re-established when connection is going down and up again later (ie in cases of erroneous client call) - think through if automatic re-connect is feasable

• motivation + goals
• run requirements
• ws messages
• test requirements
  • describe e2ehelper.sh
  • describe orchestrator.e2e.js
  • describe btc-node.orch.js

replace websockets (server + client) with zeromq for network transport