docs/CHANGELOG-1.2.md
Note: Parity 1.2 reached End-of-Life on 2016-11-07 (EOL).
Parity 1.2.4 Is a maintenance release that fixes a few issues related to mining and peer synchronization. This release is marked as stable.
Parity 1.2.3 is a patch release that addresses network stability issues for both Ethereum HF and Ethereum classic chains and brings a few changes to the transaction tracing API.
CALLCODE, DELEGATECALL and SUICIDEtrace_call returns traces in flat formattrace_rawTransaction and trace_replayTransactionNote that to continue using tracing features in this version you need to re-sync the blockchain. This can be done by using parity export $HOME/ethereum-chain-backup.rlp , deleting the database usually located at ~/.parity/906a34e69aec8c0d followed by parity import $HOME/ethereum-chain-backup.rlp.
DAO hard-fork implementation conforms to the specification and is enabled by default.
--reseal-on-txs defaults to own.--db-cache-size consuming too much memory.
eth_getWork RPC response additionally includes the block number.Full changelog
--author is now required for mining.--reseal-on-txs Specify which transactions should force the node to reseal a block. By default parity updates the seal on incoming transactions to reduce transaction latency. Set this option to none to force updates on new blocks only.--reseal-min-period Can be used to control how often a new pending block is generated if none is not selected on prior option.--work-queue-size Controls how many pending blocks to keep in memory.--relay-set Can be used to enable more strict transaction verification.--remove-solved Move solved blocks from the work package queue instead of cloning them. This gives a slightly faster import speed, but means that extra solutions submitted for the same work package will go unused.--notify-work Accepts a list of URLs that will receive a POST request when new work package is available. The body of the POST message is JSON encoded and has the same format as eth_getWork RPC response.eth_getWork RPC response additionally includes the block number.
DAO soft-fork control options have been replaced by the single --fork option which disables the soft-fork by default.
This is a new framework for signing transactions. It fulfills three requirements:
The feature is enabled through the --signer flag. When enabled, the user must ensure at least one "Signer UI" is set-up for managing transaction confirmation. There are two such UIs available; one through a Google Chrome Extension, separately installable and the second through a special web page hosted locally. Set-up must be done once for each such UI, through copying and pasting a token from the output console of Parity into the UI. Specific instructions are given in the UI.
From this point on, no transaction may ever be signed by Parity except through one of these allowed Signer UIs, and no password should ever be entered anywhere else.
Should be started with --geth to ensure Mist compatibility.
Numerous improvements and optimisations have been added to our mining implementation. A large "active queue" ensures that late-included transactions are included in the mined block without sacrificing older results from latent-reported ethminer results.
We're happy to announce full Windows support with 1.2!
This release includes support for the proposed DAO soft-fork. Upon upgrade, all mining nodes can vote for or against the soft fork (this is done through altering the block gas limit; a gas limit of at most 4M results in the soft-fork being triggered).
By default, nodes vote "for" the DAO soft-fork (and try to reduce the gas limit to 3.1M). To vote against the soft-fork (keeping it at 4.7M), run with --dont-help-rescue-dao. Not upgrading is not recommended; if the majority votes with a soft-fork, an upgrade will be necessary to mine on the correct chain.
-off renamed to GNU-consistent prefix --no-.Full changes:
ethcore by default, adding x-frame-options header to dapps. #1197die_with_error use fmt::Display rather than Debug #1116