New design implies that we avoid wallet API and all communication with blockchain(s) is performed from Web browser by means of web extensions ( Beam Web Wallet, Metamask). For this reason we need a background service which has to provide common functions both for web and for git-remote-sourc3, also it should give possibility for git-remote-sourc3 to communicate with web (for tx confirmations, for example).
This background service should be explicitly installed on the developer's machine, it should listen for web sockets.
New design implies that we avoid wallet API and all communication with blockchain(s) is performed from Web browser by means of web extensions ( Beam Web Wallet, Metamask). For this reason we need a background service which has to provide common functions both for web and for
git-remote-sourc3, also it should give possibility forgit-remote-sourc3to communicate with web (for tx confirmations, for example). This background service should be explicitly installed on the developer's machine, it should listen for web sockets.