Wallet logic that makes API calls to the server to get the data necessary to feed the Vue elements that allow for click-based interaction with meta-data tables about Trade Channel dealers and one's live TCs and part/fully signed tx. Additionally the logic for co-signing trades will be encoded a boolean function, which would inspect a data-element generated during the session prior to the API calls returning. The dealer who co-signs trades 2nd would usually be the user there, but some dealers may go the other way and offer people trades partially-signed in advance, and thus the user would do it, the code should be mirrored for any given client node. Finally an API to dbl. check that a string decodes to the right tx, with a secondary source of truth (a simpler express app with just the decode call running on a separate server). In the future p2p wallets should be able to provide these API services to each other, with a WebRTC implementation, but until then...
Wallet logic that makes API calls to the server to get the data necessary to feed the Vue elements that allow for click-based interaction with meta-data tables about Trade Channel dealers and one's live TCs and part/fully signed tx. Additionally the logic for co-signing trades will be encoded a boolean function, which would inspect a data-element generated during the session prior to the API calls returning. The dealer who co-signs trades 2nd would usually be the user there, but some dealers may go the other way and offer people trades partially-signed in advance, and thus the user would do it, the code should be mirrored for any given client node. Finally an API to dbl. check that a string decodes to the right tx, with a secondary source of truth (a simpler express app with just the decode call running on a separate server). In the future p2p wallets should be able to provide these API services to each other, with a WebRTC implementation, but until then...