Update ERC-2334: Move to Review

ERCS/erc-2334.md

@@ -1,16 +1,16 @@
 ---
 eip: 2334
 title: BLS12-381 Deterministic Account Hierarchy
-author: Carl Beekhuizen <carl@ethereum.org>
-discussions-to: https://github.com/ethereum/EIPs/issues/2338
-status: Stagnant
+author: Carl Beekhuizen <carl@ethereum.org>, Mamy Ratsimbazafy <mamy@numforge.co>
+discussions-to: https://ethereum-magicians.org/t/erc-2333-erc-2334-erc-2335-bls12-381-key-generation-deterministic-account-hierarchy-keystore/19566
+status: Review
 type: Standards Track
 category: ERC
 created: 2019-09-30
 requires: 2333
 ---
 
 ## Simple Summary
 
 This EIP defines the purpose of a given key, or family thereof, within a tree of keys. When combined with [EIP-2333](./eip-2333.md), the combination of a seed and knowledge of the desired purpose of a key is sufficient to determine a key pair.
 
@@ -20,13 +20,13 @@
 
 ## A note on purpose
 
 This specification is designed not only to be an Ethereum 2.0 standard, but one that is adopted by the wider community who have adopted [BLS signatures over BLS12-381](https://datatracker.ietf.org/doc/draft-irtf-cfrg-bls-signature/). It is therefore important also to consider the needs of the wider industry along with those specific to Ethereum. As a part of these considerations, it is the intention of the author that this standard eventually migrate to a more neutral repository in the future.
 
 ## Motivation
 
 Ethereum 2.0 alongside many other projects will use BLS signatures over BLS12-381, an [IETF proposed standard](https://datatracker.ietf.org/doc/draft-irtf-cfrg-bls-signature/). This new scheme requires a new key derivation mechanism, which is established within [EIP-2333](./eip-2333.md). This new scheme is incompatible with the current form of this specification ([BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki)) due to the: exclusive use of hardened keys, the increased number of keys per level, not using [BIP32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) for key derivation. It is therefore necessary to establish a new *path* for traversing the [EIP-2333](./eip-2333.md) key-tree.
 
 The path structure specified in this EIP aims to be more general than [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) by not having UTXO-centric features [which gave rise to the 4 different types of wallet paths being used within Ethereum 1.0](https://github.com/ethereum/EIPs/issues/84#issuecomment-292324521) and gave rise to (draft) [EIP-600](./eip-600.md) & [EIP-601](./eip-601.md)
 
 ## Specification
 
@@ -79,7 +79,7 @@
 
 ## Rationale
 
 `purpose`, `coin_type`, and `account` are widely-adopted terms as per [BIP43](https://github.com/bitcoin/bips/blob/master/bip-0043.mediawiki) and [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) and therefore reusing these terms and their associated meanings makes sense.
 
 The purpose needs to be distinct from these standards as the KDF and path are not inter-compatible and `12381` is an obvious choice.
 
@@ -95,7 +95,7 @@
 
 ## Backwards Compatibility
 
 [BIP43](https://github.com/bitcoin/bips/blob/master/bip-0043.mediawiki) and [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) are the commonly used standards for this purpose within Ethereum 1.0, however they have not been `Accepted` as standards as yet. Due to the use of a new KDF within [EIP-2333](./eip-2333.md), a new path standard is required. This EIP implements this, with minor changes.
 
 `purpose` `12381` paths do not support hardened keys and therefore the `'` character is invalid.