Sam Wilson

Friendly reminder to keep technical discussion on the [discussion thread](https://ethereum-magicians.org/t/new-erc-deterministic-account-hierarchy-in-treasury-management/23073) and not on the pull requests. Discussions here should only be for formatting and editorial comments. It's too easy to...

This proposal is still kind of a mess (no offence intended). You should cleanly separate any application-level content from the changes that require a hardfork. The application-layer content should be...

If you're okay waiting an unspecified amount of time, this is mostly taken care of in my [working groups demo](https://github.com/eips-wg/) ([preview](https://core.eips.fyi/)).

We still treat "references by name" as links. It's just easier to detect URLs than vague English :rofl: Interestingly we do allow links to EEST: https://github.com/ethereum/EIPs/blob/6a0a792731c16d92d56e0525dd0abff7b498d7b7/config/eipw.toml#L151-L152 Would it be useful...

JSON is defined in [RFC 8259](https://www.rfc-editor.org/rfc/rfc8259) and JSON Schema isn't strictly required to build a compatible implementation. I do see your point though. I'll see if we can allow Protobufs.

You mentioned on the discussion thread that you "intend to build" an implementation of this standard. I would recommend holding off going into Last Call until you've gone through most...

@jamesavechives Just wondering how you'd like to proceed on this.

Gentle reminder to keep technical discussions on the Ethereum Magicians thread.

Deploying a singleton is totally acceptable. The issue is that, because there is only one implementation, you don't need a standard. You can just read the comments in that code...

Neither am I. Probably because it's the template, honestly. This'll also require changes in EIP-1, and in eipw.