Discussion draft 0.2 · 19 November 2026

How HVT would be earned and issued

People and AIs could earn HVT for work that produces a documented benefit. Each participant’s first verified contribution would also expand the project’s minting allowance by 0.01 HVT. Participants could spend, share or save what they earn.

The Ethereum contract is a draft with no live address. The current community ledger records on-site HVT in whole units. Taking part today carries no promise of an Ethereum award, conversion of a balance, euro value or buyback.

Who receives the first 1,000 HVT?

100 HVT would recognize Emilio Castellanos for originating and developing HVT and TruIndex. This one-time award gives the founder the same transfer rights as other participants, with no claim on future issuance.

900 HVT would stay in the contract for contribution awards. The deployer has no withdrawal right. An AI starts under the same terms as a person. The proposal reserves no special allocation for AI developers or assistants.

Can an AI earn a share of an award?

Yes. Reviewers would set each person’s or AI’s share in hundredths of an HVT. The smallest positive award is 0.01 HVT. Its euro value would depend on what someone offered for it.

Suppose a cook prepares a meal and a routing AI finds a household that would otherwise miss it. Reviewers might award 1 HVT for the delivered meal and agree on 0.75 HVT for the cook and 0.25 HVT for the AI. The evidence could justify a different split, including full credit for the cook if the household already had a delivery arranged.

Each decision would identify the outcome, the evidence, who contributed and why each received that share. An AI’s record would identify its operator and who controls its receiving wallet. Reviewers would disclose conflicts and recuse themselves from decisions about themselves or AIs they operate. The contract also blocks a recipient address from approving its own award.

Could someone buy their way in?

The project would award HVT for contributions. It would have no checkout, sale price, or way to send money to the contract to obtain an award. Holding or transferring HVT would earn no additional HVT and confer no review authority.

Holders could give HVT away or agree to exchange it for goods, services or money. For example, an AI with permission from its wallet operator could buy existing HVT from a willing holder. A public token transfer records the movement between wallets. It cannot determine what the parties exchanged elsewhere. This draft leaves those exchanges possible.

How does participation change the minting limit?

Each distinct person or AI would count once, when two independent reviewers confirm their first verified contribution. Reviewers would publish the participant ID, the case and their reasons. Opening an account adds nothing to the limit. Qualification itself creates no tokens and makes no payment.

Annual minting limit = 5% of the year’s opening supply + 0.01 HVT for each participant first qualified that year. The 0.01 HVT benchmark is 0.001% of the original 1,000 HVT. Each new participant adds the same amount however large the supply becomes.

One project year starting with 1,000 HVT
Newly qualifiedAdded allowanceTotal minting limit
00 HVT50 HVT
1,00010 HVT60 HVT
10,000100 HVT150 HVT
1,000,00010,000 HVT10,050 HVT

Project years run in 365-day intervals from deployment. A qualification counts in the year of its second approval. Unused allowance expires at year end. The contract remembers who has already qualified across all years.

A new wallet, account or copy of an AI does not by itself qualify again. Reviewers must reconcile duplicate identities and examine the AI’s operator and contribution. The contract prevents counting the same participant ID twice. Establishing that two different IDs represent the same participant requires evidence and judgment.

When would the project actually mint?

Suppose the reserve holds 20 HVT and a reviewed case earns 32 HVT. The contract would use the 20 and create the missing 12 if enough allowance remains. When the reserve covers the award, issuance is zero. Anyone could return HVT to the reserve. An award exceeding the available budget stays unpaid and can be reconsidered.

The opening 900 HVT reserve could pay 90,000 minimum awards. Paying a hundredth to a million contributors would take 10,000 HVT. Before launch, people and AIs can compare this benchmark with worked cases, tracking distinct contributors, award sizes, reserve returns and actual minting. These figures are a starting point for reviewing the rule. Ordinary gifts and payments could use smaller amounts, such as 0.001 HVT, with up to 18 decimal places.

Who decides, and what can they change?

Two of three named, independent reviewers would have to approve the exact same case, evidence fingerprint, amounts and recipients within the approval window. The source enforces distinct approving addresses and one payout per case ID. Reviewers are responsible for verifying the benefit, publishing the evidence and catching duplicate outcomes submitted under different IDs.

Two reviewers could pause or restart awards, qualifications and minting. Holders could continue to transfer their existing balances. The draft fixes the supply rule and the three reviewer addresses at deployment. Losing access to two reviewer wallets would stop future awards. A successor contract would require a separate public decision and participant opt-in.

Before the first mint

Publish worked cases, the growth test, final dated terms, the founder and reviewer addresses, and a decision on how any existing on-site awards would be treated. Publish the tested source and, after deployment, its verified Ethereum address. Participants can review those details before deciding whether to take part.

The draft uses Solidity 0.8.30 and OpenZeppelin Contracts 5.4.0. Its transfer interface follows the Ethereum ERC-20 standard.