Fund entry from the verified-user channel and close the last founder question - #163
Merged
Conversation
…e last question The last founder-reserved question of the milestone — how a brand-new person pays for their first action — is answered from tokenomics that already existed. On completing HUB verification for the first time, the chain issues that person's first day's `hub_verified_user_incentives` portion immediately as an entry airdrop, so a brand-new account can transact. From the second day it continues as an ordinary daily mint permission under the same thirty-window accumulation cap. Nothing about the channel total changes; only the delivery of day one does. After the first million users the problem does not recur, because bridges, swaps, and direct purchases exist by then. The rate is derived rather than chosen. The owner supplied the population and the period — the first 1,000,000 verified users, daily, for two years — and those with the founder-directed cap divide exactly: 125,001,000,000,000,000 / 1,000,000 / 731 = 171,000,000 atomic, or 1.71 native units per user per day, with no remainder. 730 cycles leaves 420,000,000, so the period is 731, the same as a seat's issuance period. Three supplied figures reproducing the accepted cap to the atomic unit is what makes this the intended reading rather than a plausible one, so the channel's rate leaves the unresolved list. A fully pre-minted pool was described first and then refined away, and the refinement is also the only option the constitution permits: a conforming chain opens with zero supply and zero accounts, so a pre-minted pool would be a genesis allocation under another name. The next action becomes M3.10a, specifying economy-transition-v6, with nothing blocking it. The handoff now carries the six things version six must define, including the one place this direction reaches the M1 account-identifier boundary.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation only. Answers the last founder-reserved question of the milestone,
and it is answered from tokenomics that already existed.
The direction
On completing HUB verification for the first time, the chain issues that
person's first day's
hub_verified_user_incentivesportion immediately as anentry airdrop, so a brand-new account can transact at all. From the second day
it continues as an ordinary daily mint permission under the same thirty-window
accumulation cap. Nothing about the channel total changes — only the
delivery of day one. After the first million users the problem does not recur,
because bridges, swaps, and direct purchases exist by then.
The rate is derived, not chosen
The owner supplied the population and the period: the first 1,000,000
verified users, daily, for two years. Those with the founder-directed
cap determine the fourth figure exactly:
The division is exact and 730 cycles is not, leaving a remainder of
420,000,000 — so the period is 731, the same as a Founder Seat's issuance
period, and 1.71 sits in the same family as the economy's other legs (171.0,
34.2, 17.1, 3.42). Three supplied figures reproducing the accepted cap to the
atomic unit is what makes this the intended reading rather than a plausible one.
The channel's rate therefore leaves the unresolved list.
Pre-mint was rejected, and the constitution required that anyway
A pre-minted pool was described first and refined away. The refinement is also
the only option the constitution permits: a conforming chain opens with zero
supply and zero accounts, so a pre-minted pool would be a genesis allocation
under another name.
Left as mechanism, recorded so it is chosen rather than discovered
The order of credit and fee inside registration (credit first, so entry is
self-funding); who submits a registration; and that the airdrop is paid once per
identity, which HUB already guarantees.
Review item
An entry payment is an anti-abuse surface. A million entry payments are a
million reasons to attempt a false registration, so the constitution's liveness,
unlinkability, coercion, and false-acceptance requirements for the verifier are
load-bearing here in a way they were not when verification only gated a seat
purchase.
Verification
Focused metadata path. 5 repository skills and 176 internal Markdown links
validated;
tests/toolspasses 14 tests.