vector
vector copied to clipboard
↗️ Vector is an ultra-minimal state channel network implementation.
Right now the saveChannelStateAndTransfers method logic is inefficient. We are also deleting data of transfers that are no longer active. The method should be improved to (1) not delete then...
When getting transfers, the `channel` is no longer associated with the database entry if it is not an active transfer. To handle this, we separately query for the `channel` if...
When calling `BrowserNode.connect` the config schema is never validated Additionally when calling `.init()` the config is not validated
We now have an `initiatorSubmits` parameter for withdrawals. Instead of making the assumption that alice always withdraws, we should refactor the handler so that you can specify if you do...
Engine is missing several unit tests. Should go through and develop a test spec + implement the missing unit tests so we can easily refactor
Transactions associated with auto rebalancing are not stored since they are not associated with the server-node and are not submitted through the chain service. They are also not tracked in...
Some use cases immediately withdraw after a transfer (i.e. crosschain transfer). If we use a combined transfer, it might optimize and reduce the potential for errors.
There is no way to tell how long specific functions are taking, making it difficult to improve latency. Partially addressed by PR #398 but needs to be expanded to all...
Fix error on server node side.
Right now we use a custom `Result` type to prevent the `try`-`catch` syntax. This is nice, but has a *lot* of boiler plate. Instead, we should be able to refactor...