# Solana Bridge Project

Announcement by Bishop9773

• : 1. Rust RPC Server
  • 1.1 Handle API calls from the Verus Daemon
  • 1.2 Serialize and deserialize data
  • 1.3 Interact with Solana smart contract endpoints
  • 1.4 Host a wallet to pay for Solana state change transactions
  • 1.5 Solana utility functions for Notarizers
• 2. Solana Smart Contracts
• 3. Daemon modification to accept Solana Proofs
• 4. Website to interact with Smart contract
• 5. Mobile app to interact with Solana and Verus

%%{init: { 'theme': 'forest' }}%%
graph LR
    A[Verus Daemon \n With modifications\n to handle\n solana proofs] -->|API Calls| B(Bridgekeeper)
    B --> C{API Call \n smart contract}
    C --> submitImports
    C --> getInfo
    C --> getExports
    C --> submitAcceptedNotarization
    C --> getNotarizationData
    C --> getBestProofRoot
    C --> getLastImportFrom
    C --> revokeidentity
    subgraph Solana
    submitImports
    getInfo
    getExports
    submitAcceptedNotarization
    getNotarizationData
    getBestProofRoot
    getLastImportFrom
    revokeidentity
    end

Verus Daemon

Verus Ethereum Contracts

Verus Bridgekeeper

Verus Ethereum Website

Verus Mobile App

Verus TS Resources

• @Monkins - provided information for developers to be able to understand what is involved with the bounty.
• @Monkins - provided an initial concept on how a sub chain can be kept in a solana smart contract in order to provide a stateroot Verus needs.

This Idea has been discussed with the Lead developer of Verus and would serve as the basis for a viable solution.

MVP 1

Define What needs to be built

• In the Daemon (How to solve the EDCSA Issue)
• Define and choose programming language to be used for each module
• Smart Contracts
• Apps

MVP 2.1

Create serializing libraries

MVP 2.2

Create RPC API for DAemon to connect to