A full sovereign custodian implementation of risk-free transaction sending for web3 businesses and degens
-
Losing funds due wrong address input ( a huge pain currently in web3 as the action is not reversible after sending the transaction ).
-
Losings funds due wrong network selection while sending the transaction.
At some point the address can be correct but the choice of the network can result to loss of funds
vane act as a safety net for web3 users.
-
Receiver address confirmation
-
Transaction execution simulation
-
Receiver account ownership confirmation after transaction execution and network simulation.
As this is crucial to make sure that you control account provided ( receiver ) in X network/blockchain.
After all confirmation, vane will route and submit the transaction to X address to the Y network/blokchain.
vane_web3 is designed to be decentralized and locally run by users having complete control.
In itself is not a wallet, but can work with any type of wallet as it acts as an extension safety layer for web3.
-
DbWorker
- database worker is responsible for locally storing, user addresses, tx records, and peers that user interacted with
-
P2PWorker
- responsible for sending pinging tx to receiver for confirmation on address and network
-
TxProcessingWorker
- signature verification, creating tx payload to be signed, simulating tx, submitting tx
-
RpcWorker
- interface where users interact with, signing tx, initiating tx, sender confirmation, receiver confirmation
-
TelemetryWorker
- recording total volume of tx per user and reverted tx volume and number of peers(receivers) interacted with
-
MainServiceWorker
- orchestrating all workers and having a single run function to spawn all workers and control the flow of passing tx state machine processing updates
-
Remote Db (Airtable)
- a naive solution to dht ( peer discovery mechanism) as new users for vane will register their peer id along with account addresses to remote airtable server as a means to be discovered by other peers.