backports to beta

Kirill Pimenov authored Nov 09, 2017 and Marek Kotewicz committed Nov 13, 2017

Make CLI arguments parsing more backwards compatible

Alexey authored Nov 10, 2017 and Marek Kotewicz committed Nov 13, 2017

Events in WASM runtime

Kirill Pimenov authored Nov 01, 2017 and Marek Kotewicz committed Nov 13, 2017

Windows fixes

[beta] Disallow builtin multisig deploy (only watch)

Nikolay Volf authored Nov 03, 2017 and Arkadiy Paronyan committed Nov 03, 2017

* Action params and embedded params handling

* fix namespaces

* v1.8.2

* Refactor static context check in CREATE. (#6886)

* Refactor static context check in CREATE.

* Fix wasm.

* Fix serialization of non-localized transactions (#6868)

* Fix serialization of non-localized transactions.

* Return proper SignedTransactions representation.

* Allow force sealing and reseal=0 for non-dev chains. (#6878)

Afri Schoedon authored Oct 20, 2017 and Arkadiy Paronyan committed Oct 20, 2017

* Add ECIP1017 setting to Morden config

* Convert spaces to tabs

* Update Morden bootnodes to match Geth

* Tweaked snapshot sync threshold

* Change keypath derivation logic (#6815)

While the standard defined by Trezor as the default derivation path here
https://blog.trezor.io/trezor-integration-with-myetherwallet-3e217a652e08
says that it should be `m/44'/60'/0`, in practice they don't have an
implementation of a wallet for Ethereum themselves and refer customers
to MEW.

MEW has a custom implementation of the path derivation logic that allows them to
generate multiple addresses by essentially adding `/0`, `/1` etc to the path.

In my initial implementation of Trezor I didn't take this into
consideration unfortunately and just used the keypath that Trezor
themselves recommended. However, given that it's seemingly standard
practice to append `/0` for a "sub-address" (and this is what we've done
for Ledger as well) it seems like a mistake on my part to not take that
into consideration.

Unfortunately, anyone who has used their Trezor device with Parity
previously would now see a different address when they connect the
Trezor device the next time. The only way they would have to access the
old address is to use an old version, or by going through MEW and
selecting the Ledger keypath.

Also see #6811

Jaco Greeff authored Oct 19, 2017 and Arkadiy Paronyan committed Oct 19, 2017

* Refresh cached tokens based on registry info & random balances

* Don't display errored token images

* Fixed kovan chain validation

* Fork detection

* Fixed typo

* CLI: Reject invalid argument values rather than ignore them

* Fix grumbles

Nicolas Gotchac authored Oct 12, 2017 and Jaco Greeff committed Oct 12, 2017

* Fix badges not showing up

* Always fetch meta data first [badges]

Nicolas Gotchac authored Oct 12, 2017 and Jaco Greeff committed Oct 12, 2017

* Update new token fetching

* Working Certifications Monitoring

* Update on Certification / Revoke

* Fix none-fetched tokens value display

* Fix tests

* Check vouch status on appId in addition to contentHash

* Simplify var expansion

Prevent going offline when restoring or taking a snapshot

Graceful exit when invalid CLI flags are passed (#6485)

Fixed RETURNDATA out of bounds check

* Remove .only

* Add vouch overlays to dapps

* Cleanup address

* Only run where we have a contentHash

* GitLab kickstart