kumavis
970d4fd695
metamask - add missing diskState and memState subscriptions
8 years ago
kumavis
9e4ef45b6a
migration #9 - break out CurrencyController substate
8 years ago
kumavis
8b5e3aa287
migration #8 - break out NoticeController substate
8 years ago
kumavis
73edfc9f31
eth-store - convert to obs-store subclass
8 years ago
kumavis
f08f40aee2
txManager - depend on preferencesStore
8 years ago
kumavis
0c6df24ecf
metamask - introduce networkStore
8 years ago
kumavis
99fa9ab13a
migration 7 - break off TransactionManager substate
8 years ago
kumavis
bcb86f38cb
messageManager - move view state to obs-store
8 years ago
kumavis
79ed2e902f
keyring - replace getState with memStore
8 years ago
kumavis
5c5aa6ea01
keyring - rm config dep
8 years ago
kumavis
4c0cb9d92e
metamask - memState - adopt configManager.isDisclaimerConfirmed from keyring controller
8 years ago
Frankie
1b16b46241
code clan up and tests
8 years ago
kumavis
1cb730144d
metamask - adopt isInitialized from keyring controller
8 years ago
kumavis
ad060e2678
metamask - inherit some configManager state from keyring controller
8 years ago
kumavis
c0d3db6a8c
keyring - synchronous getState
8 years ago
kumavis
7ccaa263d2
inpage - set web3.eth.defaultAccount correctly
8 years ago
kumavis
2fa60cfcbf
continue rename selectedAccount to selectedAddress
8 years ago
kumavis
f9b31fe2c3
rename selectedAccount to selectedAddress
8 years ago
kumavis
b1de2cdefa
metamask - rename getSelectedAccount to getSelectedAddress
8 years ago
kumavis
4dafb09db2
metamask - move selectedAccount set/get to preferencesController
8 years ago
kumavis
0a1918f71a
preferences - introduce preferences controller
8 years ago
kumavis
dd528d886f
metamask - lookup selectedAccount via keyringController
8 years ago
kumavis
6480c2d8a6
public config - get selectedAccount from keyring controller substate
8 years ago
kumavis
13e2003469
metamask - subscribe metamask store to keyringController substate
8 years ago
Frankie
8be68575bb
Clean up message manger includes:
...
Provider egine bump
Remove presence of message manger in keyring controller
Change the status wording fom conf to approved
make Message manager a class
fix messages not being apart of the badge
re write message manger to better reflect controller pattern
8 years ago
kumavis
e9cdbf4f89
keyring - add and initialize obs-store
8 years ago
kumavis
1fd1746744
metamask - adopt shapeshift txs from keyringController
8 years ago
kumavis
ad9531d521
metamask - organize methods
8 years ago
kumavis
efcd22905a
metamask - fix setupProviderConnection
8 years ago
kumavis
9ab8362843
metamask controller - cleanup remote api
8 years ago
kumavis
fc1b11e373
metamask - organize into sections
8 years ago
kumavis
832772414e
metamask - use web3-stream-provider/handler instead of manual wiring
8 years ago
kumavis
2113979be7
metamask controller - adopt setup*Communication from background
8 years ago
kumavis
2f79781ab9
metamask controller - adopt clearSeedWords from keyring controller
8 years ago
kumavis
dc86ddebb7
background - graceful publicConfigStore connection teardown
8 years ago
kumavis
af115aa4c1
background - organize metamask instantiation
8 years ago
kumavis
76ce348a04
obs-store - use published module
8 years ago
kumavis
463a56ff54
background controller - extract KeyringC.placeSeedWords to MetamaskC
8 years ago
Frankie
48ffea0142
Move the assumption of their only being one hd keyring when requesting seed words to metamaskController
8 years ago
Frankie
8642ced310
Fix issue where generating a new account would put it in loose keys
8 years ago
Dan Finlay
b52346388b
Added new modular private key import system
...
Now any strategy for importing a private key that can be described as a pure function can be very easily turned into a MetaMask import strategy.
I've created a generic and reusable UI action called `importNewAccount(strategy, args)`.
The `strategy` is a unique identifier defined in `app/scripts/account-import-strategies`, and the `args` will be passed to the member of the `strategies` array whose key matches the strategy string.
Strategies return private key hex strings, and are used by the metamask-controller to create a new keyring, and select that new account, before calling back.
This also implements @frankiebee's idea of showing the imported account when it's been imported (my oversight!).
This commit only moves us to this architecture, keeping feature parity for private key import, but has some untested code for importing geth-style JSON files as well!
8 years ago
Dan Finlay
1ff4894b67
Allow importing of private key strings
...
Fixes #1021
A top-right menu item now allows `Account Import`. It has a menu (with one item for now) that allows importing a private key string.
Errors are displayed, and a success navigates the user to their account list, where the imported account is labeled `LOOSE`.
8 years ago
kumavis
c3d491a37c
background - return txHash to provider-engine on done
8 years ago
kumavis
d755b66e20
background - metamask controller - fix 'this' ref
8 years ago
kumavis
29e83d71a8
background - handle tx finalization in controllers instead of provider-engine
8 years ago
kumavis
3bc996878b
background - move pojo migrator to outside of metamask controller
8 years ago
kumavis
8012ede126
background - introduce ObservableStore
8 years ago
Frankie
0fae263a9a
Take some of the tx Logic out of the UI and create a visble state for pending and unaproved transactions
8 years ago
kumavis
26e4ff40e1
rpc - fix sync account cache setting
8 years ago
kumavis
61637c738b
web3 provider - override eth_syncing and web3_clientVersion
8 years ago