Repo(s) organisation - Githubissues

revault / practical-revault

Version 0 specifications for a Revault deployment

Creative Commons Attribution 4.0 International

33 stars 9 forks source link

Repo(s) organisation #3

Closed darosior closed 4 years ago

darosior commented 4 years ago

I thought to go with one repo per entity:

Wallet
Watchtower
Cosig server
Sync server

The communication channel code will probably be part of another repo (not here).

edouardparis commented 4 years ago

revault-wallet will be a lib crate like https://github.com/MagicalBitcoin/magical-bitcoin-wallet and revault-gui will use revault-wallet as a dependcy ? I think it would be the cleanest way to do it in order to have a clean wallet implem without too much dependencies

darosior commented 4 years ago

I wanted to have revaultd and revault-gui talking to it via a socket, but now that we need Windows support... I need to give some more thoughts.

In any case yep, I think the core logic --revault-whatever-- would be in a lib.

darosior commented 4 years ago

We settled on this:

libs

revault_tx => Bitcoin Script and transactions primitives revault_net => Communication channels and practical-revault messages

bins

revaultd => "wallet" daemon watchtowerd, sync_serverd, cosignerd => servers daemons