Community Call Recap 8
The 8th Community Call was marked with announcements of major progress and hinted towards the end of the initial testing phase of proto-Vortex.
The first half of the call focused on going over the changes made in the proto-Vortex, including the fact that proto-Vortex is now gated, meaning that in order to participate in proto-Vortex, you now need to be both BioAuthenticated, and have a running node.
Another key feature that was introduced was the new “invision” tab, which not only has a clear overview of the state of the “governance”, such as data on how decentralized the governance actually is, participation, concentration of power, and delegation ratio, but also looks at how “healthy” the state of governance is at any given time.
The risk factors are also clearly listed, and there is a new feature that was added, allowing governors to signal that they feel the Vortex has become illegitimate. Currently, by design, if 66.6% +1 of all governors signal that they feel the Vortex has become illegitimate, a reset protocol will be initiated, resetting the Vortex to its initial state. (Now imagine if that feature existed for governments worldwide… if 66.6% + 1 of the population of a nation believes their government is not acting in the interest of its people, and the “button” is pushed, resetting the budget, spending, who is in charge of the government, its policies, and whatnot… that is what one would call the real “nuclear option”.)
It was announced that after one or two weeks of testing with the gated proto-Vortex, proto-Vortex will go live, restructuring the fee structure for human nodes, and for activity in governance. Details are to be released.
Aside from proto-Vortex, the group also went over Articles 11, 12, and 13 of the Humanode Charter, completing its task of reviewing all 12 Articles in full.
For your information…
Article 11 — Courts and the Humanode Codex
11.1 Humanode Codex. The Humanode Codex shall define adjudicable conduct standards, prohibited actions, reporting procedures, evidentiary requirements, remedies, and sanctions applicable to Human Nodes and Governors, as adopted and amended through Vortex procedures.
11.2 Right to Report. Any participant permitted by the Codex may submit a report of alleged misconduct, abuse, or violation of the Codex through the designated governance interfaces.
11.3 Court Composition. A Court shall consist of twelve (12) jurors assembled from Governors. Jurors shall be selected by a protocol-defined process intended to be impartial, and shall exclude (a) the reported party, (b) the reporting party where applicable, and (c) any Governor with a conflict of interest as defined by the Codex.
11.4 Procedure. Court procedure, timelines, and standards of proof shall be as defined by the Codex and implemented by protocol and/or governance interfaces.
11.5 Determination and Remedies. A Court may determine outcomes including dismissal, admonition, censure, restitution directives, temporary suspension of governance participation, removal of chamber privileges, and other remedies or sanctions defined by the Codex, to the extent enforceable by protocol. Unless otherwise specified by the Codex, imposing any sanction beyond dismissal shall require not less than a two-thirds (2/3) affirmative vote of the jurors.
11.6 Publication. Court outcomes shall be recorded in an auditable manner consistent with Article 12, subject to privacy and safety constraints adopted by valid governance action.
It is to be noted that the Court feature has not been implemented into proto-Vortex at this time. It will be added at a later date, in the on-chain version as a module, after the details have been hashed out (such as how exactly the jury will be selected, and after the “crime and suggested punishment” is clarified).
Articles 12 and 13 are pretty straightforward, tying the legal knots.
Article 12 — Records, Transparency, and Enforcement
12.1 Auditability. Proposals, votes, delegations, CM values, veto actions, Court outcomes, and Formation commitments shall be recorded in an auditable manner as determined by protocol and application design.
12.2 Protocol Enforcement. Protocol-enforced rules are those implemented in Vortex code. Application-level rules may supplement user experience and coordination but shall not override or contradict protocol enforcement.
Article 13 — Amendment and Interpretation
13.1 Amendment. These Charters may be amended only through valid Vortex governance actions as implemented in protocol, including proposal, quorum, voting, and veto procedures.
13.2 Construction. Headings are for convenience only and shall not control interpretation. Defined terms shall be interpreted consistently unless context requires otherwise.
13.3 Severability. If any provision of these Charters is unenforceable in an off-chain context, such unenforceability shall not affect the operation of the protocol code, which remains controlling.
After the wording is hashed out, corrections are made, and preparations are complete, the full Humanode Charter will be presented to the Community for a vote. If approved, the Charter will be built into the Vortex at launch.
And finally, at the end of the call, the “Hub” was introduced. If you haven’t checked it out yet, visit https://thehub.town/ or thehub on X https://x.com/thehubtown !
For those interested in joining the discussions or the live testing that will happen this coming Saturday, join us at the next Community Call.