Found something sitting quietly in the OpenLedger tokenomics document that most people walk straight past.
the reserve allocation. 11.71% of Total supply. 117,100,000 OPEN tokens. sixth category in the token table. and next to the vesting schedule column four letters. TBD.
went through the entire tokenomics document carefully on my pc specifically looking for any additional detailon this category. one reference. one line. strategic reserve schedule TBD. nothing else.
the reserve category exists in most token Distributions as a catch all for scenarios the founding team cannot fully anticipate at launch. reegulatory requirements that emerge later. strategic partnerships that require token commitments. emergency protocol funding. secondary market Interventions.
The existence of a reserve is not unnusual. 117.1 million tokens with no defined vesting schedule is worth understanding precisely because of what TBD actually means in practice.
TBD is not the same as l0cked. locked means a smart contract enforces a release schedule that nobody can change unilaterally. TBD means a schedule has not been defined yet which means the tokens are subject to a schedule that will be determined by whoever controls that decision. at the current Stage of the protocol, during the progressive decentralization phase, that decision sits with the founding team. 117.1 million tokens. no enforced timeline.
No published criteria for when or how They deploy.
To put that number in context 117.1 million OPEN is larger than the entire liquidity and market operations allocation at 50 million. it is larger than the ecosystem fund TGE unlock at 20 million. it represents 11.71% of total supply sitting in a category where the release mechanism has not been publicly Committed to in any document i could find.
Went back through the tokenomics doc and the whitepaper both. same result.
the whitepaper describes the reserve as strategic which is accurate as far as it goes. strategic reserves serve real purposes. the question is not whether a reserve should exist. the question is whether 117.1 million tokens should remain on an undefined schedule indefinitely while the rest of the token table has fully documented vesting parameters. every other category community rewards, ecosystem fund, team, investors, liquidity has a defined schedule. this one does not.
That asymmetry is worth noting Quietly.
the tension here is not about intent. it is about structure. a reserve with no defined schedule is functionally different from a reserve with a locked Schedule regardless of what the team intends to do with it. intent is not enforcement.
Documentation is not a smart contract. and 117.1 million tokens on an undefined timeline is a structural fact about this protocol that sits in the tokenomics table waiting for someone to read it carefully enough to notice.
still cant figure out why the reserve schedule is the only allocation in the entire token table without a defined vesting timeline