<unnamed>

Public Key

npub1m2qdpyegdf7ngacxplrxcspr4dr24c6759mrjk309caamj8an0pq8vvdel

Profile Code

nprofile1qqsd4qxsjv5x5lf5wurql3nvgq36k342ud02za3etghjuw7aer7ehsspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsnmspqk

Publishing to

nostr.wine

relay.damus.io

nos.lol

Last Notes

2023-06-07 18:02:24 UTC

- reply

📅 Original date posted:2017-06-07
📝 Original message:On Wed, Jun 7, 2017 at 12:02 AM Gregory Maxwell via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> On Tue, Jun 6, 2017 at 10:39 PM, Tao Effect via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
> > I believe the severity of replay attacks is going unvoiced and is not
> > understood within the bitcoin community because of their lack of
> experience
> > with them.
>
> Please don't insult our community-- the issues with replay were
> pointed out by us to Ethereum in advance and were cited specifically
> in prior hardfork discussions long before Ethereum started editing
> their ledger for the economic benefit of its centralized
> administrators.
Please don't spread misinformation. Whatever you think of the DAO hard
fork, it's a simple fact that the Ethereum ledger was not edited.
-Nick Johnson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170607/2c04c534/attachment.html>

2023-06-07 17:59:59 UTC

- reply

📅 Original date posted:2017-04-12
📝 Original message:<pre>
BIP: bip-nickjohnson-ethereum-purpose
Layer: Applications
Title: Ethereum purpose allocation for Deterministic Wallets
Author: Nick Johnson <nick at ethereum.org>
Status: Proposed
Type: Standards Track
Created: 2017-04-12
</pre>
==Abstract==
This BIP defines a logical hierarchy for deterministic wallets on the Ethereum
blockchain based on an algorithm described in BIP-0032 (BIP32 from now on) and
purpose scheme described in BIP-0043 (BIP43 from now on).
This BIP is a particular application of BIP43.
==Motivation==
Because Ethereum is based on account balances rather than UTXO, the hierarchy
defined by BIP44 is poorly suited. As a result, several competing
derivation path strategies have sprung up for deterministic wallets, resulting
in inter-client incompatibility. This BIP seeks to provide a path to standardise
this in a fashion better suited to Ethereum's unique requirements.
==Path levels==
We define the following 2 levels in BIP32 path:
<pre>
m / purpose' / subpurpose' / *
</pre>
Apostrophe in the path indicates that BIP32 hardened derivation is used.
Each level has a special meaning, described in the chapters below.
===Purpose===
Purpose is a constant set to the hardened value of the BIP number assigned to
this BIP (equivalently, the BIP number, bitwise ORed with 0x80000000) following
the BIP43 recommendation.
It indicates that the subtree of this node is used according to this
specification.
Hardened derivation is used at this level.
===Subpurpose===
Subpurpose is set to the EIP number specifying the remainder of the BIP32
derivation path. This permits new Ethereum-focused applications of
deterministic wallets without needing to interface with the BIP process.
Hardened derivation is used at this level.
==Reference== * [[bip-0032.mediawiki|BIP32 - Hierarchical Deterministic
Wallets]] * [[bip-0043.mediawiki|BIP43 - Purpose Field for Deterministic
Wallets]]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170412/f13f375a/attachment.html>