revaultd
revaultd copied to clipboard
revault
The "wallet" daemon for participants under the Revault architecture
See https://github.com/revault/revaultd/pull/218#discussion_r653979415
We currently have the assumption that presigned transactions are always stored in database if the state is >secured for revocation txs and >active for Unvault transaction. This assumption is violated...
#### If the user decides to send funds to the same address as the change, we should merge the two outputs Example: Vault is 10 BTC User wants to send...
They are pulling a lot of dependencies, and we don't need their complexity. However, the derive feature is really nice to use and it would be nice to keep something...
We start using `secure_vault` and `active_vault` a lot and waiting synchronously wastes some considerable time. We should either make use of the `executor` fixture, have plural versions of the above...
We denote vaults for which all revocation transactions are signed as being "Secure". That's poor terminology and we should find then use a new one..
We currently have a basic queue which can fills until a certain limit. A very basic threadpool-like logic could help.
As it's exposed in a single `server` module, it think we could fuzz the `mio_loop`: https://github.com/re-vault/revaultd/blob/3141908c8c1e847b2e76f9240c109734d1324599/src/daemon/jsonrpc/server.rs#L121-L125 We could use a custom `MetaIoHandler` that would not process the actual command but...