Want to discuss or change something about the EOS Constitution? Everyone is welcome to join video conference calls — start by catching up with summaries of past calls to get involved in Week 5.

— Week 5 Call Schedule —

NOTE: some call times have changed this week to better accommodate participants from every timezone. Also find call schedules on our website.

Call #1: English

Tuesday, September 18 at 5:30pm EDT / 21:30 UTC.

60–70 minutes — Register Here.

Call #2: Korean & English

Wednesday, September 19 at 9:00pm Seoul Time / 12:00 UTC.

60–70 minutes — Register Here.

Call #3: Chinese & English

Thursday, September 20 at 9:00pm Beijing & Shanghai Time / 13:00 UTC.

60–70 minutes — Register Here.

AGENDA: Participants will be in groups of 5–7 people, to compare Daniel Larimer’s v2 EOS constitution proposal with the current EOS constitution.

Prepare by reading:

Daniel Larimer’s v2 proposal, “Intent of Code is Law” — https://medium.com/@bytemaster/the-intent-of-code-is-law-c0e0cd318032

Current EOS Constitution— https://github.com/EOS-Mainnet/governance/blob/master/eosio.system/eosio.system-clause-constitution-rc.md

Which articles in the constitution and Dan’s proposal are directly related? What makes one article better, and what should be improved? Notes and prepared thoughts are welcome along with impromptu remarks and opinions. Everyone should have a voice in EOS.

Week 4 Constitution Series Recap

Three calls happened this week to host discussions about current EOS Constitution Articles X— XX.

Call #1 welcomed 33 Chinese & English participants, with a turnout of ~75% Mandarin Chinese primary speakers.

Martin Breur of EOS Nation again provided an excellent call summary from all groups:

Thank you again Martin for your excellent work — please read his full call #1 summary for information from all five discussion groups.

Call #2 was held in English, on Tuesday at 7:45pm EDT. The small group continued discussions where call #1 left off, focusing on Articles XV and XVI.

Article XV — Termination of Agreement

A Member is automatically released from all revocable obligations under this Constitution 3 years after the last transaction signed by that Member is incorporated into the blockchain. After 3 years of inactivity an account may be put up for auction and the proceeds distributed to all Members according to the system contract provisions then in effect for such redistribution.

The English only group generally agreed this article needs to be removed, as it creates too much negativity both inside and out the EOS community.

Intent for this article could be unexplained — it was included at the last minute and may have something to do with Dan’s URI proposal to share resources with all of Earth’s inhabitants. One of Dan’s primary arguments for URI is that nobody should be able to lay claim to something forever, and this Article falls in line with that belief.

If this Article were to remain and impact someone holding their EOS, it could cause more work for arbitration and dispute resolution groups.

Article XVI — Developer Liability

Members agree to hold software developers harmless for unintentional mistakes made in the expression of contractual intent, whether or not said mistakes were due to actual or perceived negligence.

Varied opinions in the group about who should be at fault in a blockchain transaction, and how much can be expected of the end user upholding their part by reading the Ricardian contracts.

Experienced developers should hold more weight of responsibility for bugs than end users, who are limited in their capacity to vet contracts. The group settled on a responsibility ratio of 80/20 towards developers.

The word “unintentional” is too subjective and could lead to many unnecessary dispute resolution cases as well. Any bug could be automatically labeled “unintentional” — what’s harder to prove is a malicious actor claiming their efforts to be unintentional. The group generally agreed subjective language of any type should be removed.

Watch the call #2 live stream recording here.

Call #3 was in Korean & English, taking place Wednesday morning at 1200 UTC. Video recording here.

Two breakout groups decided to discuss the same Articles as the English only call — XV and XVI. When the two Korean groups came together and shared their thoughts, a similar consensus of ideas was discovered between the groups and those of the English call, which many in call #3 found satisfying.

Furthermore, members of the Korean speaking group organized another call for the following day, to begin drafting an alternative version of the EOS constitution. A snapshot of their work in progress:

Other Community Calls

The Dispute Resolution & Arbitration group held a call on Monday September 10, shortly after call #1 of the Constitution Referendum Series. Amy Wan hosted EMAC to talk about their Chinese alternative to ECAF. Watch the video here: https://youtu.be/_fRthpmD4Wc

EOS Ignite hosted its third weekly governance discussion call, offering an in-depth look into discussions about the EOS Constitution (video link). This week the group began its focus on Daniel Larimer’s v2 Constitution proposal.

Next Thursday, September 20 at 3:00pm EDT, EOS Ignite will continue discussions about Daniel Larimer’s v2 Constitution proposal.

We look forward to further community discussions next week — let’s dive a little deeper and determine what’s important to the community in an EOS constitution.

— — — — — — — — — — — —

EOS Alliance — Empowering EOS For All.

We seek to inform the community and provide a platform for collaborative decision making. Everyone should have a voice in EOS.