-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
Will add the above instructions to my auto-deploy tool as well. (So it just gets done by click of a button) https://github.com/ethcore/parity/pull/4726 |
return WalletsUtils | ||
.isWallet(api, address) | ||
.then((isWallet) => { | ||
if (!isWallet) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 Really happy with this approach. (For both deploy & estimate)
transaction.gasUsed | ||
? ( | ||
<span> | ||
<span>used</span> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would have made sense to i18n these additions, but no matter, busy with this actual file in my conversion branch, so will be ok.
if (!isEqual(localHashes, this.localHashes)) { | ||
@action setLocalHashes = (localHashes = []) => { | ||
// Use slice to make sure they are both Arrays (MobX uses Objects for Observable Arrays) | ||
if (!isEqual(localHashes.slice(), this.localHashes.slice())) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure which one is more performant from a MobX perspective - .peek()
or .slice()
(Typically do use the former when it is a known (i.e. on this.
) value
Ok, happy with it from a code perspective, it needs to go for 1.6 - full end-to-end scenario testing will happen once merged. |
* Update Wallet Version * Update Wallet Library * Update Wallets Bytecodes * Typo * Separate Deploy in Contract API * Use the new Wallet ABI // Update wallet code * WIP .// Deploy from Wallet * Update Wallet contract * Contract Deployment for Wallet * Working deployments for Single Owned Wallet contracts * Linting * Create a Wallet from a Wallet * Linting * Fix Signer transactions // Add Gas Used for transactions * Deploy wallet contract fix * Fix too high gas estimate for Wallet Contract Deploys * Final piece ; deploying from Wallet owned by wallet * Update Wallet Code * Updated the Wallet Codes * Fixing Wallet Deployments * Add Support for older wallets * Linting
* Update Wallet to new Wallet Code (#4805) * Update Wallet Version * Update Wallet Library * Update Wallets Bytecodes * Typo * Separate Deploy in Contract API * Use the new Wallet ABI // Update wallet code * WIP .// Deploy from Wallet * Update Wallet contract * Contract Deployment for Wallet * Working deployments for Single Owned Wallet contracts * Linting * Create a Wallet from a Wallet * Linting * Fix Signer transactions // Add Gas Used for transactions * Deploy wallet contract fix * Fix too high gas estimate for Wallet Contract Deploys * Final piece ; deploying from Wallet owned by wallet * Update Wallet Code * Updated the Wallet Codes * Fixing Wallet Deployments * Add Support for older wallets * Linting * SMS Faucet (#4774) * Faucet * Remove flakey button-index testing * Only display faucet when sms verified (mainnet) * simplify availability checks * WIP * Resuest from verified -> verified * Update endpoint, display response text * Error icon on errors * Parse hash text response * Use /api/:address endpoint * hash -> data * Adjust sms-certified message * Fix SectionList hovering issue (#4749) * Fix SectionList Items hover when <3 items * Even easier... * lint (new)
Updates the UI to use the new Wallet.
Now one can deploy contracts with a Wallet.
The Wallet Library should be deployed to any network where we want to have it.
The bytecode + ABI are in
js/src/contracts/code/wallet.js
:walletLibrary
andwalletLibraryABI
.The deployed address should then be added to the registry with
walletLibrary
as a key (the value ofwalletLibraryRegKey
). It has been done for Kovan already.