Skip to content

Latest commit

 

History

History
122 lines (77 loc) · 5.5 KB

README.md

File metadata and controls

122 lines (77 loc) · 5.5 KB
Raw

vane network

Implementation of risk free transaction sending for web3 businesses and degens

What are we solving?

  1. Losing funds due wrong address input ( a huge pain currently in web3 as the action is not reversible after sending the transaction ).

  2. 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

Our Solution

vane act as a safety net for web3 users.

  1. Receiver address confirmation

  2. Transaction execution simulation

  3. 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.

  4. After all confirmation, vane will route and submit the transaction to X address to the Y network/blokchain.

vane operate as a gurdian for the transaction. This is so needed as take for example sending funds to L2s in Ethereum. It is so easy loosing funds, choosing the network ( L2 ) and at somepoint the address you can only control in certain network and not the other, so the simulation part and confirmation is crucial.

We want to eliminate all fear while sending transactions in web3 and to make sure users have a room to make mistakes whitout costing them a fortune.

User flow

  1. Initiate sending transaction by providing a wallet address ( sender )
  2. A transaction data will be sent to receiver address as notification for receiver confirmation.
  3. The sender will check with the receiver to confirm they received the notification, ensuring the address is correct and they are the intended recipient. ( sender & receiver )
  • After simulation of transaction execution
  1. The receiver will have to confirm and verify that he can control the account which received the tokens.
  • After the confirmation
  1. The transaction will be routed and submitted to the confirmed wallet address and network/blockchain.

With this user flow the receiver and sender have only 2 interactions to make the whole transaction risk free.

And at any point of the confirmation, the sender can stop the transaction from progressing once noticed there is some incorrectness.

Technology

vane is an offchain & onchain solution. vane-flow

Offchain components

  1. AV-layer ( Address Verification Layer )

    • Accepts new transaction requests and put them in a queue per sender & receiver address
    • In the transaction message queue, each transaction object is checked for its state ( Pending Confirmation -> Confirmed ).
    • Confirmed transaction object will be propagated to the execution simulation layer
    • Reverted transactions will be dropped from the message queue

  2. Network Simulation

    • Spawn a parallel reality of the specified network chain ( Chopsticks & EthSim ( coming soon ))
    • Send the transaction to the spawned simulated network for execution
    • Receiver should verify that is able to control the deposited account in the chain
    • Record the proof of attestation
    • Propagate the transaction to network router layer

  3. Network Router Layer

    • Send the transaction to the verified and attested address and network.

Onchain component

  1. Smart contract

    • Store cached value for verified , confirmed and attested transaction object
    • Have tokens for incentivizing relayers
    • Wallet partnership revenue integration

Transaction pipeline

Potential problems

  1. Nonce control

    As transactions will be submitted by network router relayer, it is possible that the nonce it holds has already been invalidated by the target network.

    To mitigate this, the transaction will fetch the next valid nonce once it passes all vane checks ( address verification, simulation network execution and reciver deposited account ownership attestation) and once it is at network router relayer a new fresh nonce will be fetched and included in the submitted transaction

Product thesis

  • There will be one instance of the servers run by vane labs enabling users to connect to
  • vane should compile to wasm to enable embedding the backend with front end app, enabling users to run their own instance for decentralization

Network Supported

List of symbols:

  • ✅: means the network is currently supported.
  • 🏗️ means that the network is being actively implemented.
  • ❌ means that the network is currently not supported
  • AV layer - Address Verifcation layer
Supported networks layers Status
Polkadot AV layer & Simulation layer ✅ & ❌
Kusama AV layer & Simulation layer 🏗️ & ❌
Ethereum Av layer & Simulation layer 🏗️ & ❌
Solana Av layer & Simulation layer 🏗️ & ❌
BNB Av layer & Simulation layer ❌ & ❌
Base Av layer & Simulation layer ❌ & ❌
Arbitrum Av layer & Simulation layer ❌ & ❌
Optimism Av layer & Simulation layer ❌ & ❌
Bitcoin Av layer & Simulation layer ❌ & ❌
Sui Av layer & Simulation layer ❌ & ❌