Where We Are Now

We claim that Earthlings is verifiable. Such a claim makes sense only when it is possible to say exactly what is being verified and by what means. Instead of the general formula "our code is open", we therefore publish the precise boundary: what is open, what is closed, and for what reason.

The founding period is now under way: until the day the Declaration is adopted, the people is still being founded, and some of the numbers below read differently from how they will read afterwards. The rules and dates of that period are set out in the document The Founding Period - we do not repeat them here, so that the dates keep a single source.

None of the closed components determines who is an earthling and how a vote is counted. That is determined by the open smart contract.

• The rules of the passport. Read the contract's source code in the repository: the passport is non-transferable, one per wallet, and the holder can burn it themselves.
• How many passports have been issued. Call the contract's totalSupply. That number does not come from us - it comes from the blockchain. But it has to be read correctly, and we explain how. The contract currently holds four test entries, made while debugging the system before launch, and none of them is a real participant. From 7 September 2026 until the day the text is adopted, this number means people who have confirmed their identity and are taking part in the founding: they become earthlings only after the Declaration is adopted. After adoption, the number of passports issued is the number of earthlings.
• Whether a particular address holds a passport. Call balanceOf. The answer: 1 or 0.
• DAO votes. Open the space on Snapshot and see the proposals, the votes, and the signatures. Every vote is signed by the voter's wallet - we can neither add a vote nor forge someone else's.
• The right to vote. Snapshot asks our server whether an address holds a passport. This step has to be trusted at the moment of voting - but not afterwards: the addresses of everyone who voted are public, and anyone can check each of them for themselves in the contract on Polygon. A discrepancy would be visible.

We describe the last point plainly because it is one of the two places where we have to be trusted. We prefer to name them ourselves rather than leave them to be discovered by someone checking.

The second place is the contract owner's keys. In the deployed version of the contract, the functions for issuing and burning a passport are available to the owner, and the owner key is currently with the founder. Article 21 of the Charter permits burning against the holder's will on two grounds only and only with a procedure: notice, a period for objections, an opinion of the Council, a secret ballot with a higher majority, appeal. These guarantees are not in the code - they are procedural. That means they now rest on our word rather than on the technology, and we acknowledge it. What is being done about it: separating the rights of issuance and burning into distinct roles, adding a delay on executing a burn, and transferring ownership to a multisignature of six elected signatories. The timing is in the Roadmap.

An honest list of what is declared as a principle but not yet done:

• The contract source code is published in the repository, but it is not yet verified in a blockchain explorer. This means that the correspondence between the published source and the deployed bytecode for now has to be checked independently. Verification is in progress.
• No independent security audit has been carried out. It is planned before operations are expanded.
• The Treasury smart contracts are not deployed. Only the passport contract is deployed; the internal economy of participation is for now kept in the platform's own ledger.
• The public voting channel is deployed and technically working, but no substantive votes have yet been held in it.
• A vulnerability search programme (bug bounty) is declared as a principle but has not yet been opened.
• The contract owner's rights have not been split or transferred. Issuing and burning a passport are available to a single key, there is no delay on execution, and the key is with the founder. The restrictions of Article 21 of the Charter operate procedurally.
• There is still no multisignature on the treasury wallet. The signature threshold is one; this can be checked at the wallet address. The move to a composition of six signatories is a criterion for the transition between phases.

The registry of passports lives on the blockchain, not on our servers, and the contract code is open. From this follows something practical: if the infrastructure is stopped or its operation is captured, the community can build a new platform against the same registry. People and their passports carry over; the server layer is replaceable.

Reproduction has two supports, and the second is no less important than the first. The registry gives continuity of people, and the published specification gives the ability to assemble the instrument anew: the rules, thresholds, quorums, periods, and procedures are set out in full in the Charter, in the Treasury document, and in these documents. What is reproduced is therefore not our code but the system as described. Copying the closed server side is not needed and will not be needed.

Keeping the server side closed therefore does not negate the people's right to continue without the founders. The signs of a lawful continuation - a preserved unamendable core, the will of verified people, and continuity of procedures - are described in the document Roadmap of the Transitional Period.