Andreas Freund

> Yes, but having full tooling and using libraries is too complex. The implementations and tests should be as simple (no tooling, no libraries, no package files, etc...) as possible....

> I put up a PR with some fixes for the new build system: [Therecanbeonlyone1969#1](https://github.com/Therecanbeonlyone1969/EIPs/pull/1) @SamWilsn thank you! What is the status of the discussion on including the reference implementation...

@MicahZoltu @SamWilsn @Pandapip1 may I have an update, please?

> > With this naming convention, another Sidetree method implementer choosing to use Ethereum and IPFS on a different contract address would have to come up with a different name...

@OR13 3rd party refers to anyone (non-contract) ... we could add a check to ensure that msg.sender is not a contract -- there is an open-zeppelin contract for that ......

oh and the anchor file URI is strong so we can make that longer @OR13

I understand the approach to use log storage to avoid paying for gas. With 1.X that approach will no longer work since the logs will be flushed after a certain...

I was under the impression that we have both the IPFS hash and the Merkle Trie Roothash at our disposal ... this would provide two anchor points.

@OR13 ... ok. need to read the latest spec. totally understand the design criteria for v1 of the contract. I think we need to account for in the new design:...

I generally agree with you. Summary of state of the art is here -- https://medium.com/matter-labs/optimistic-vs-zk-rollup-deep-dive-ea141e71e075 Since we do not have to worry about digital assets things get simpler. BTW, I...