Wrapping Up the KZG Ceremony

The KZG Ceremony had the most participants of any multi-party computation. It was a transparent, open process that produced a secure cryptographic basis for EIP-4844.

Discover how Carl Beekhuizen performed the Ceremony Devcon talk: “Summoning the spirit of the Dankshard”

Dencun upgrade This post will provide a complete record of the people and outcomes that made 2023’s Ceremony a reality.

Outcomes & Methods

The Ceremony lasted for 208 Days: Jan 13 13:13 UTC 2023 until Aug 08 23:08 UTC 2023

Contributions totaled 141 416 The largest installation of its kind was made at the time this publication.

To prevent spam, contributors were required to authenticate via an Ethereum address or sign in through Github.

• Sign up with Ethereum was used by 132 021 (93.36%)
• Github was used by 9,395 users (6.64%).

In order to prevent spam, Ethereum addresses had to send a minimum number of transactions. “nonce”(before the start of the Ceremony on block 16,394,155, 2023/01/13 at 00:00 UTC. The requirements were modified according to the current needs.

• Nonce 3: Jan 13 – March 13
• No new logins allowed between March 13th and April 1st, but lobby cleared out. Anyone already logged in was able complete their contribution.
• April 01-16 – Public contributions are closed for Special Contributions
• April 16-25:
• April 25-May 8, 64
• May 8-25:
• May 25 – June 27: 16
• June 27 – Aug 23: 8

Blacklisting excessive logins/pings is a way to stop bots and scripts interrupting genuine contributors. The blacklist was reset to remove any honest accounts that were accidentally added. four times Throughout the entire contribution period.

Please Note: We do not recommend that you use KZG contributions to create a list of unique identifiers. e.g. For airdrops, e.g. The sign-in requirements and the nonce requirement encouraged honest contributions but were only minor obstacles for actors who wanted to contribute more than once. The analysis of the onchain and transcript activity shows that most contributions were made by linked addresses controlled solely by one entity. Because these contributions added entropy to the final transcript, they did not detract.

Verifying transcripts

8ed1c73857e77ae98ea23e36cdcf828ccbf32b423fddc7480de658f9d116c848The sha-256 output of the final transcription is used to calculate the hash.

The transcript is 242 MBGitHub has a version of the code available in English. ethereum/kzg-ceremony repo You can also via IPFS CID QmZ5zgyg1i7ixhDjbUM2fmVpES1s9NQfYBM2twgrTSahdy.

You can verify the transcript in several ways. It can be explored on the internet and verified. ceremony.ethereum.orgYou can also use a dedicated verification script written in rust.

Geoff’s Blog Post explains the check-out system in detail: Verifying the KZG Ceremony Transcript.

There was a commemorative POAP NFT Contributors who log in using their Ethereum addresses can claim this reward. The POAP is designed to match the original hosted interface. It also includes the hash code of the transcript within the border (8ed…848). Over 76k NFTs were claimed by participants. Anyone who verified transcript output could also tweet as social proof Verification tweets: recent success here.

As mentioned above The list of newly minted POAPs is not a good anti-sybil indicator, eg. For airdrop eligibility.

Special Contributions

The Special Contribution Period was April 1-16, 2023. The Special Contribution Period allowed participants to make contributions in ways they may not have been able to do during the Open Contribution Period.

Special Contributions are an additional level of assurance beyond the standard contribution.

• Computing over entropy within an isolated environment is a good way to reduce the risk of a malicious entity extracting entropy. It’s highly unlikely that malicious entities could have extracted entropy from an air-gapped system, which wipes and destroys hardware.
• It is unlikely that all the detailed documentation (see links below) associated with real reputations have been coopted by an evil coordinating entity. Future observers are welcome to examine the records.
• Risks associated with different hardware and Software Limits
• When measuring an explosion, the output of Ceremony is not compromised by a failure in the regular entropy production (eg. Measurement of an explosion is a good example. The hosted interface is a good example.
• Contributions involving a large group of people are more difficult to fake than contributions with just one person

Original Ethereum blog post The 14 special contributions are documented in detail, with information on their methodology, where they can be found in the transcript as well as links to media that document them.

• Cryptosat: Entropy from Space
• The KZG Marble Machine is a 3D printed marble machine
• Mr. Moloch’s Ephemeral album II: A day-long musical journey
• Dog Dinner Dance Dynamics: a good boy get dinner
• CZG-Keremony : a pure JS KZG client
• Improvised Theater: unpredictable improv
• A Calculating Auto: Self-driving cars collect data
• Sydney, a noisy city with stories to tell
• Exothermic Entropy, chemicals that go boom
• Lightning never strikes the same place twice
• The Great Belgian Beer Entropy Caper. Recording a night out with friends.
• KZGamer – summoning Dankshard by using a Dice Tower
• Cats continue to be a part of the internet
• An iOS KZG Ceremony Client

Learn more about the construction of these structures by using this resource. workEthereum, as well as in general and its particular context.

Audits

Two audits, one for each component, were performed, given the importance of security to this project.

Client Implementations

Participants could choose from a range of local implementations, each with its own features.

CLI Interfaces

Browser Interfaces

1. audit: QmevfvaP3nR5iMncWKa55B2f5mUgTAw9oDjFovD3XNrJTV
2. doge: QmRs83zAU1hEnPHeeSKBUa58kLiWiwkjG3rJCmB8ViTcSU

BLS Libraries

This shout-out is for the dozens and dozens of people in the Ethereum community who have been involved with design, coordination audits, devops, writing code, etc. Your efforts would have made this project impossible!

I would like to thank the tens or thousands of people for taking the time and effort to report bugs and scale Ethereum.