|
|
|
const Dnode = require('dnode')
|
|
|
|
const ObjectMultiplex = require('./lib/obj-multiplex')
|
|
|
|
const eos = require('end-of-stream')
|
|
|
|
const combineStreams = require('pumpify')
|
|
|
|
const extend = require('xtend')
|
|
|
|
const EthStore = require('eth-store')
|
|
|
|
const PortStream = require('./lib/port-stream.js')
|
|
|
|
const MetaMaskProvider = require('web3-provider-engine/zero.js')
|
|
|
|
const IdentityStore = require('./lib/idStore')
|
|
|
|
const createTxNotification = require('./lib/notifications.js').createTxNotification
|
|
|
|
const createMsgNotification = require('./lib/notifications.js').createMsgNotification
|
Made configuration migrateable
Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case).
Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need.
By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code.
All the restructuring and data-type management is kept in one neat little place.
This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more!
I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
|
|
|
const configManager = require('./lib/config-manager-singleton')
|
|
|
|
const messageManager = require('./lib/message-manager')
|
|
|
|
const setupMultiplex = require('./lib/stream-utils.js').setupMultiplex
|
|
|
|
const HostStore = require('./lib/remote-store.js').HostStore
|
|
|
|
const Web3 = require('web3')
|
|
|
|
|
|
|
|
//
|
|
|
|
// connect to other contexts
|
|
|
|
//
|
|
|
|
|
|
|
|
chrome.runtime.onConnect.addListener(connectRemote)
|
|
|
|
function connectRemote(remotePort){
|
|
|
|
var isMetaMaskInternalProcess = (remotePort.name === 'popup')
|
|
|
|
var portStream = new PortStream(remotePort)
|
|
|
|
if (isMetaMaskInternalProcess) {
|
|
|
|
// communication with popup
|
|
|
|
setupTrustedCommunication(portStream)
|
|
|
|
} else {
|
|
|
|
// communication with page
|
|
|
|
setupUntrustedCommunication(portStream)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
function setupUntrustedCommunication(connectionStream){
|
|
|
|
// setup multiplexing
|
|
|
|
var mx = setupMultiplex(connectionStream)
|
|
|
|
// connect features
|
|
|
|
setupProviderConnection(mx.createStream('provider'))
|
|
|
|
setupPublicConfig(mx.createStream('publicConfig'))
|
|
|
|
}
|
|
|
|
|
|
|
|
function setupTrustedCommunication(connectionStream){
|
|
|
|
// setup multiplexing
|
|
|
|
var mx = setupMultiplex(connectionStream)
|
|
|
|
// connect features
|
|
|
|
setupControllerConnection(mx.createStream('controller'))
|
|
|
|
setupProviderConnection(mx.createStream('provider'))
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// state and network
|
|
|
|
//
|
|
|
|
|
|
|
|
var providerConfig = configManager.getProvider()
|
|
|
|
var idStore = new IdentityStore()
|
|
|
|
|
|
|
|
var providerOpts = {
|
Made configuration migrateable
Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case).
Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need.
By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code.
All the restructuring and data-type management is kept in one neat little place.
This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more!
I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
|
|
|
rpcUrl: configManager.getCurrentRpcAddress(),
|
|
|
|
// account mgmt
|
|
|
|
getAccounts: function(cb){
|
|
|
|
var selectedAddress = idStore.getSelectedAddress()
|
|
|
|
var result = selectedAddress ? [selectedAddress] : []
|
|
|
|
cb(null, result)
|
|
|
|
},
|
|
|
|
// tx signing
|
|
|
|
approveTransaction: addUnconfirmedTx,
|
|
|
|
signTransaction: idStore.signTransaction.bind(idStore),
|
|
|
|
// msg signing
|
|
|
|
approveMessage: addUnconfirmedMsg,
|
|
|
|
signMessage: idStore.signMessage.bind(idStore),
|
|
|
|
}
|
|
|
|
var provider = MetaMaskProvider(providerOpts)
|
|
|
|
var web3 = new Web3(provider)
|
|
|
|
idStore.web3 = web3
|
|
|
|
idStore.getNetwork(3)
|
|
|
|
|
|
|
|
// log new blocks
|
|
|
|
provider.on('block', function(block){
|
|
|
|
console.log('BLOCK CHANGED:', '#'+block.number.toString('hex'), '0x'+block.hash.toString('hex'))
|
|
|
|
})
|
|
|
|
|
|
|
|
var ethStore = new EthStore(provider)
|
|
|
|
idStore.setStore(ethStore)
|
|
|
|
|
|
|
|
function getState(){
|
|
|
|
var state = extend(
|
|
|
|
ethStore.getState(),
|
|
|
|
idStore.getState(),
|
Made configuration migrateable
Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case).
Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need.
By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code.
All the restructuring and data-type management is kept in one neat little place.
This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more!
I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
|
|
|
configManager.getConfig()
|
|
|
|
)
|
|
|
|
return state
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// public store
|
|
|
|
//
|
|
|
|
|
|
|
|
// get init state
|
|
|
|
var initPublicState = extend(
|
|
|
|
idStoreToPublic(idStore.getState()),
|
|
|
|
configToPublic(configManager.getConfig())
|
|
|
|
)
|
|
|
|
|
|
|
|
var publicConfigStore = new HostStore(initPublicState)
|
|
|
|
|
|
|
|
// subscribe to changes
|
|
|
|
configManager.subscribe(function(state){
|
|
|
|
storeSetFromObj(publicConfigStore, configToPublic(state))
|
|
|
|
})
|
|
|
|
idStore.on('update', function(state){
|
|
|
|
storeSetFromObj(publicConfigStore, idStoreToPublic(state))
|
|
|
|
})
|
|
|
|
|
|
|
|
// idStore substate
|
|
|
|
function idStoreToPublic(state){
|
|
|
|
return {
|
|
|
|
selectedAddress: state.selectedAddress,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// config substate
|
|
|
|
function configToPublic(state){
|
|
|
|
return {
|
|
|
|
provider: state.provider,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// dump obj into store
|
|
|
|
function storeSetFromObj(store, obj){
|
|
|
|
Object.keys(obj).forEach(function(key){
|
|
|
|
store.set(key, obj[key])
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
// handle rpc requests
|
|
|
|
function onRpcRequest(remoteStream, payload){
|
|
|
|
// console.log('MetaMaskPlugin - incoming payload:', payload)
|
|
|
|
provider.sendAsync(payload, function onPayloadHandled(err, response){
|
|
|
|
// provider engine errors are included in response objects
|
|
|
|
if (!payload.isMetamaskInternal) {
|
|
|
|
console.log('MetaMaskPlugin - RPC complete:', payload, '->', response)
|
|
|
|
if (response.error) console.error('Error in RPC response:\n'+response.error.message)
|
|
|
|
}
|
|
|
|
try {
|
|
|
|
remoteStream.write(response)
|
|
|
|
} catch (err) {
|
|
|
|
console.error(err)
|
|
|
|
}
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
//
|
|
|
|
// remote features
|
|
|
|
//
|
|
|
|
|
|
|
|
function setupPublicConfig(stream){
|
|
|
|
var storeStream = publicConfigStore.createStream()
|
|
|
|
stream.pipe(storeStream).pipe(stream)
|
|
|
|
}
|
|
|
|
|
|
|
|
function setupProviderConnection(stream){
|
|
|
|
stream.on('data', onRpcRequest.bind(null, stream))
|
|
|
|
}
|
|
|
|
|
|
|
|
function setupControllerConnection(stream){
|
|
|
|
var dnode = Dnode({
|
|
|
|
getState: function(cb){ cb(null, getState()) },
|
|
|
|
setRpcTarget: setRpcTarget,
|
|
|
|
setProviderType: setProviderType,
|
|
|
|
useEtherscanProvider: useEtherscanProvider,
|
|
|
|
// forward directly to idStore
|
|
|
|
createNewVault: idStore.createNewVault.bind(idStore),
|
|
|
|
recoverFromSeed: idStore.recoverFromSeed.bind(idStore),
|
|
|
|
submitPassword: idStore.submitPassword.bind(idStore),
|
|
|
|
setSelectedAddress: idStore.setSelectedAddress.bind(idStore),
|
|
|
|
approveTransaction: idStore.approveTransaction.bind(idStore),
|
|
|
|
cancelTransaction: idStore.cancelTransaction.bind(idStore),
|
|
|
|
signMessage: idStore.signMessage.bind(idStore),
|
|
|
|
cancelMessage: idStore.cancelMessage.bind(idStore),
|
|
|
|
setLocked: idStore.setLocked.bind(idStore),
|
|
|
|
clearSeedWordCache: idStore.clearSeedWordCache.bind(idStore),
|
|
|
|
exportAccount: idStore.exportAccount.bind(idStore),
|
|
|
|
revealAccount: idStore.revealAccount.bind(idStore),
|
|
|
|
saveAccountLabel: idStore.saveAccountLabel.bind(idStore),
|
|
|
|
})
|
|
|
|
stream.pipe(dnode).pipe(stream)
|
|
|
|
dnode.on('remote', function(remote){
|
|
|
|
|
|
|
|
// push updates to popup
|
|
|
|
ethStore.on('update', sendUpdate)
|
|
|
|
idStore.on('update', sendUpdate)
|
|
|
|
// teardown on disconnect
|
|
|
|
eos(stream, function unsubscribe(){
|
|
|
|
ethStore.removeListener('update', sendUpdate)
|
|
|
|
})
|
|
|
|
function sendUpdate(){
|
|
|
|
var state = getState()
|
|
|
|
remote.sendUpdate(state)
|
|
|
|
}
|
|
|
|
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// plugin badge text
|
|
|
|
//
|
|
|
|
|
|
|
|
idStore.on('update', updateBadge)
|
|
|
|
|
|
|
|
function updateBadge(state){
|
|
|
|
var label = ''
|
|
|
|
var unconfTxs = configManager.unconfirmedTxs()
|
|
|
|
var unconfTxLen = Object.keys(unconfTxs).length
|
|
|
|
var unconfMsgs = messageManager.unconfirmedMsgs()
|
|
|
|
var unconfMsgLen = Object.keys(unconfMsgs).length
|
|
|
|
var count = unconfTxLen + unconfMsgLen
|
|
|
|
if (count) {
|
|
|
|
label = String(count)
|
|
|
|
}
|
|
|
|
chrome.browserAction.setBadgeText({ text: label })
|
|
|
|
chrome.browserAction.setBadgeBackgroundColor({ color: '#506F8B' })
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// Add unconfirmed Tx + Msg
|
|
|
|
//
|
|
|
|
|
|
|
|
function addUnconfirmedTx(txParams, cb){
|
|
|
|
var txId = idStore.addUnconfirmedTransaction(txParams, cb)
|
|
|
|
createTxNotification({
|
|
|
|
title: 'New Unsigned Transaction',
|
|
|
|
txParams: txParams,
|
|
|
|
confirm: idStore.approveTransaction.bind(idStore, txId, noop),
|
|
|
|
cancel: idStore.cancelTransaction.bind(idStore, txId),
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
function addUnconfirmedMsg(msgParams, cb){
|
|
|
|
var msgId = idStore.addUnconfirmedMessage(msgParams, cb)
|
|
|
|
createMsgNotification({
|
|
|
|
title: 'New Unsigned Message',
|
|
|
|
msgParams: msgParams,
|
|
|
|
confirm: idStore.approveMessage.bind(idStore, msgId, noop),
|
|
|
|
cancel: idStore.cancelMessage.bind(idStore, msgId),
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// config
|
|
|
|
//
|
|
|
|
|
|
|
|
// called from popup
|
|
|
|
function setRpcTarget(rpcTarget){
|
Made configuration migrateable
Abstract all configuration data into a singleton called `configManager`, who is responsible for reading and writing to the persisted storage (localStorage, in our case).
Uses my new module [pojo-migrator](https://www.npmjs.com/package/pojo-migrator), and wraps it with the `ConfigManager` class, which we can hang any state setting or getting methods we need.
By keeping all the persisted state in one place, we can stabilize its outward-facing API, making the interactions increasingly atomic, which will allow us to add features that require restructuring the persisted data in the long term without having to rewrite UI or even `background.js` code.
All the restructuring and data-type management is kept in one neat little place.
This should make it very easy to add new configuration options like user-configured providers, per-domain vaults, and more!
I know this doesn't seem like a big user-facing feature, but we have a big laundry list of features that I think this will really help streamline.
9 years ago
|
|
|
configManager.setRpcTarget(rpcTarget)
|
|
|
|
chrome.runtime.reload()
|
|
|
|
idStore.getNetwork(3) // 3 retry attempts
|
|
|
|
}
|
|
|
|
|
|
|
|
function setProviderType(type) {
|
|
|
|
configManager.setProviderType(type)
|
|
|
|
chrome.runtime.reload()
|
|
|
|
idStore.getNetwork(3)
|
|
|
|
}
|
|
|
|
|
|
|
|
function useEtherscanProvider() {
|
|
|
|
configManager.useEtherscanProvider()
|
|
|
|
chrome.runtime.reload()
|
|
|
|
}
|
|
|
|
|
|
|
|
// util
|
|
|
|
|
|
|
|
function noop(){}
|