web3-provider-engine

Web3 ProviderEngine

Web3 ProviderEngine is a tool for composing your own web3 providers.

Status: WIP - expect breaking changes and strange behaviour

Composable

Built to be modular - works via a stack of 'sub-providers' which are like normal web3 providers but only handle a subset of rpc methods, specified via subProvider.methods = ['eth_call', 'etc...'].

The subproviders can emit new rpc requests in order to handle their own; e.g. eth_call may trigger eth_getAccountBalance, eth_getCode, and others. The provider engine also handles caching of rpc request results.

const ProviderEngine = require('web3-provider-engine')
const StaticProvider = require('web3-provider-engine/subproviders/static.js')
const FilterSubprovider = require('web3-provider-engine/subproviders/fitlers.js')
const VmSubprovider = require('web3-provider-engine/subproviders/vm.js')
const LightWalletSubprovider = require('web3-provider-engine/subproviders/lightwallet.js')
const RpcSubprovider = require('web3-provider-engine/subproviders/rpc.js')

var engine = new ProviderEngine()
var web3 = new Web3(engine)

// static - e.g.: web3_clientVersion
engine.addSource(new StaticProvider({
  web3_clientVersion: 'MetaMask-ZeroClient/v0.0.0/javascript',
  net_version: '1',
  net_listening: true,
  net_peerCount: '0xc',
  eth_protocolVersion: '63',
  eth_hashrate: '0x0',
  eth_mining: false,
  eth_syncing: true,
})

// filters - e.g.: eth_newBlockFilter
engine.addSource(new FilterSubprovider({
  rootProvider: engine,
}))

// vm - e.g.: eth_call
engine.addSource(new VmSubprovider({
  rootProvider: engine,
}))

// id mgmt - e.g.: eth_signTransaction
engine.addSource(new LightWalletSubprovider({
  rootProvider: engine,
}))

// data source - e.g.: eth_getBalance
engine.addSource(new RpcSubprovider({
  rpcUrl: 'https://rpc.metamask.io/',
}))

// start polling for blocks
engine.start()

Built For Zero-Clients

The Ethereum JSON RPC was not designed to have one node service many clients. However a smaller, lighter subset of the JSON RPC can be used to provide the blockchain data an Ethereum 'zero-client' node would need to function. We handle as many types of requests locally as possible, and just let data lookups fallback to some data source ( hosted rpc, blockchain api, etc ). Categorically, we don’t want / can’t have the following types of RPC calls go to the network:

• id mgmt + tx signing (requires private data)
• filters (requires a stateful data api)
• vm (expensive, hard to scale)

Current RPC method support:

static

• web3_clientVersion
• net_version
• net_listening
• net_peerCount
• eth_protocolVersion
• eth_hashrate
• eth_mining
• eth_syncing

filters

• eth_newBlockFilter
• eth_newPendingTransactionFilter
• eth_newFilter
• eth_uninstallFilter
• eth_getFilterLogs
• eth_getFilterChanges

accounts manager

• eth_coinbase
• eth_accounts
• eth_sendTransaction
• eth_sign ( not used in web3.js )

vm

• eth_call
• eth_estimateGas

db source

• db_putString
• db_getString
• db_putHex
• db_getHex

compiler

• eth_getCompilers
• eth_compileLLL
• eth_compileSerpent
• eth_compileSolidity

shh gateway

• shh_version
• shh_post
• shh_newIdentity
• shh_hasIdentity
• shh_newGroup
• shh_addToGroup

data source ( fallback to rpc )

• eth_gasPrice
• eth_blockNumber
• eth_getBalance
• eth_getBlockByHash
• eth_getBlockByNumber
• eth_getBlockTransactionCountByHash
• eth_getBlockTransactionCountByNumber
• eth_getCode
• eth_getStorageAt
• eth_getTransactionByBlockHashAndIndex
• eth_getTransactionByBlockNumberAndIndex
• eth_getTransactionByHash
• eth_getTransactionCount
• eth_getTransactionReceipt
• eth_getUncleByBlockHashAndIndex
• eth_getUncleByBlockNumberAndIndex
• eth_getUncleCountByBlockHash
• eth_getUncleCountByBlockNumber
• eth_sendRawTransaction
• eth_getLogs ( not used in web3.js )

( not supported )

• eth_getWork
• eth_submitWork
• eth_submitHashrate ( not used in web3.js )