“We Are Ready” Says Ethereum 2.0 Coordinator at ConsenSys – Trustnodes

“We Are Ready” Says Ethereum 2.0 Coordinator at ConsenSys


Ethereum abstract

“We (the community) are ready (in my honest opinion as product owner of one of the clients). Let’s do this thing.”

So says Ben Edgington, an ethereum 2.0 developer, after expressing confusion at the two weeks delay by Danny Ryan, the Ethereum 2.0 coordinator, who said we needed to wait for the audit of a BLS cryptography library.

“Danny said that deployment had been pushed back slightly to allow the audit of the Blst crypto library to be completed first. I don’t know why this was a blocker as neither the deposit contract nor the official deposit tooling use that library,” Edgington said.

Later on when asked for clarification, Ryan gave no response, but Edgington publicly said:

“I have some responsibility for coordinating all the Eth2 activities at ConsenSys – this involves not a few people, not a few moving parts, and a fair amount of planning. Being in limbo is a programme manager’s nightmare.

Besides – we (the community) are ready (imho, as product owner of one of the clients). Let’s do this thing.”

After somewhat dismissive suggestions were raised about “a desire to get something ‘finished’ or otherwise reach a milestone,” Edgington said:

“But we’re there – it isn’t even a prediction at this point: maybe an expression of frustration that nobody pulled the trigger yet.”

The problem therefore may be more who pulls the trigger and how? There’s risks here about fake contracts and the rest. Once it’s deposited you can’t get the eth back. But there is one way of being sure what is the real eth address.

If you recall a couple of weeks back Ryan published the version one spec release candidate. The final v1 spec is now to be published, and that contains the smart contract address.

Unless they’re going to create some vanity address, which is very unlikely, then the spec can’t know what the address is before the contract is published as the address is created once the contract is published. Therefore:

“Dunno, apparently quantstamp says it’s ready for launch. Theoretically if the client teams get too angry at us for not saying ‘SHIP IT’ they could just do it themselves.”

So said Vitalik Buterin, the ethereum co-founder, about a week ago. Meaning we all kind of know what’s going on and what’s going on is that this is actually imminent.

“In principle one or more client teams could deploy the contract, make a release and start the chain. It’s permissionless, right? Which is kind of the point. But far better to move forward together in step,” Edgington says.

If the client teams are ready, as the client teams are saying they are, then it’s not clear why this wouldn’t be moving together in step because it appears all is good to go.

We apparently just need some Nakamoto now to begin the process of launching the genesis block of ethereum 2.0 which occurs automatically after 500,000 eth is deposited with a week buffer time.

Update: Danny Ryan publicly commented to say: “There is no such thing as ‘official’ tooling. Blst is by far the most performant library and is integrated into almost all clients as the default choice.

Only last week did lighthouse strip out the ability to make deposits on their client. Not sure about the rest.

It is and will be an incredibly prominent bls library for all things bls. One of those bls things is creating and verifying deposits.”

Edgington says: “We marked our deposit tooling as deprecated in Teku 3 weeks ago and plan to disable it before the deposit contract is deployed.”

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>