OWN, clearly explained
This page brings together the identity, genesis supply, initial allocation and important terms of OWN. It explains what each record can tell you — and what it cannot.
Minted Token
Recorded token facts and verified contract identity are different. Contract verification evidence is still to be supplied.
For information about the OWN Access Pool and related acquisition arrangements, continue to bitlease.capital. The Foundation’s token and supply record remains here.
OWN is a fungible ERC-20 token issued on Ethereum, with a recorded genesis mint and a fixed supply. It is one token identity, not a collection of separately minted assets. Its technical record is distinct from the acquisition arrangement offered on BitLease.
A token reference should identify the contract, explain supply creation and provide evidence. A name or symbol alone cannot identify the right contract. The contract-record preview below marks the particulars still to be supplied.
OWN at a glance
| Field | Recorded fact |
|---|---|
| Token name and symbol | OWN |
| Blockchain network | Ethereum |
| Token standard | ERC-20 |
| Fixed total supply | 1,000,000,000 OWN |
| Supply creation | A single genesis mint |
| Issuer of record | OWN Token Foundation |
The recorded total supply is a statement about the number of OWN created. It is not a statement of current circulation, present holder balances or market value.
Start with the official identity record
The official identity connects the network and deployed contract to its deployment transaction, block and code evidence. The reading guide below explains how to compare these records.
The Foundation's Contract Identity Record is the authoritative reference for OWN's particulars. It is not yet published on this site. Once supplied and approved, its network and contract details must match the corresponding public explorer record. Another token with the same symbol is not an OWN identity.
A token standard is not a promise of additional utility
ERC-20 provides a common technical interface for a fungible token on Ethereum. It does not by itself establish governance rights, rewards, exchange availability, lending, guaranteed liquidity or a particular customer's contractual rights. Those matters require their own evidence and terms.
How to read verification evidence
The official identity record is not yet published here. These checks explain how to read it when available; they do not authenticate an address.
| Record to obtain | What to compare |
|---|---|
| Network and chain ID | Match both against the Foundation record and the explorer. |
| Full contract address | Compare every character and the corresponding explorer entry. |
| Deployment transaction and block | Match the transaction hash, block number and deployment record. |
| Source code and code hash | Compare source verification, compiler settings and deployed code evidence. |
| Genesis records and recipient map | Reconcile the mint and transfers with the four allocation classes, including multiple team wallets where applicable. |
The chain ID, full address, deployment transaction, block number, code hash and recipient wallet map remain to be supplied. This table is a lookup guide, not a completed contract record.
Match the network and full address
Compare the Foundation’s official record with the exact contract on the corresponding block explorer. A name, symbol or copied logo is not enough.
Check the deployed code
Read the source-verification status and compiler details. A source-code match is not a security audit or formal verification.
Read supply with its units
Compare totalSupply() and decimals() with the official record before interpreting the displayed amount.
Trace creation and allocation
Check the mint and original transfers against the allocation register. Deployment and mint can have different transaction records; four allocation classes do not necessarily mean four receiving wallets.
Read the terms alongside the chain
Code and transfers do not establish every contractual right, beneficial interest or off-chain restriction. Those questions require the applicable operator, vesting and institutional records.
The supplied supporting documents describe a design with no continuing privileged mint, administrative burn, upgrade, pause, blocklist, recovery or forced-transfer power. When code evidence is supplied, check the deployed code for each of those powers alongside ordinary ERC-20 transfers and approvals. This is a source-based design description and code-reading checklist, not an independent code audit or live-chain verification.
One genesis mint. One billion OWN.
Later transfers or commercial use do not change the historical genesis quantity.
The fixed supply was minted directly into the specified recipient wallets at Genesis. Minting and initial allocation happened together; neither 49G Holding Ltd nor the Foundation held the entire supply as an intermediate step. Later transfers are separate events.
No additional OWN supply is described as available for future minting under the token's recorded design. Fixed quantity does not mean fixed price, fixed demand or an assurance about an individual's acquisition outcome.
Genesis allocation — four different purposes
The one-billion-OWN supply was minted directly into the specified recipient wallets at Genesis across four allocation classes. These classes do not imply four wallets or four transactions. The table records recipients and purposes at mint, not current wallets or balances.
49G Holding Ltd originated the mint-and-distribution instruction specifying destination routes. The instruction conferred no ownership interest in the one-billion-OWN supply. The Foundation's Council independently adopted it through its own decision-making process, and the Foundation carried out the approved mint directly into the specified recipient wallets.
| Genesis allocation | Percentage | Quantity at mint | Recipient |
|---|---|---|---|
| Evergreen — OWN Access Pool inventory | 50% | 500,000,000 OWN | BitLease Capital Ltd |
| Utility Reserve — platform OWN utilities | 40% | 400,000,000 OWN | BitLease Technology Ltd |
| Issuer — ecosystem development and ongoing support | 6% | 60,000,000 OWN | OWN Token Foundation |
| Original founding and development team | 4% | 40,000,000 OWN | Designated wallets of the original BitLease founding and development team |
- What the allocation shows
- The original recipients, quantities and purposes at mint, as listed above.
- What it does not show
- What remains in any recipient's wallet today, how much has been acquired through the Plan, whether any holder has sold tokens or the currently circulating quantity. Those are different questions requiring a different and current evidence set.
Institutional vesting — a timetable for specified tranches
Institutional allocation scheduleNot a customer payment plan
Institutional vesting governs specified allocations, not a participant’s payment calendar.
The Foundation's 60,000,000 OWN Issuer allocation and the original team's 40,000,000 OWN allocation each have a 12-month cliff from genesis. Both follow five equal releases at months 12, 15, 18, 21 and 24: 12,000,000 Foundation OWN and 8,000,000 team OWN become available at each checkpoint.
The combined 100,000,000 OWN was already minted at genesis. Each release changes availability, not the total supply.
Vesting for these tranches is implemented through separate tools and instruments outside OWN’s ERC-20 token contract. The core token contract does not contain these tranche-release functions. The Foundation’s tranche uses its Council-approved vesting vehicle; the Foundation administers the team’s arrangement under the applicable allocation instrument.
Administration of the team’s vesting does not mean custody of its beneficiary wallets. A release calendar alone does not prove that an ordinary ERC-20 wallet is technically unable to transfer tokens. The separate tools’ enforcement, custody and release records remain to be independently verified here.
The Evergreen and Utility Reserve tranches were free of Genesis vesting. Their use and any other restrictions are governed by the recipients' own instruments; absence of Genesis vesting is not proof of current circulation.
Read the schedule relative to genesis
Genesis to month 12
The supply is minted and allocated at genesis. The Foundation and original-team tranches remain unreleased under their respective vesting instruments until month 12.
Month 12
First release: 12 million Foundation OWN and 8 million team OWN.
Month 15
Second release: 12 million Foundation OWN and 8 million team OWN.
Month 18
Third release: 12 million Foundation OWN and 8 million team OWN.
Month 21
Fourth release: 12 million Foundation OWN and 8 million team OWN.
Month 24
Fifth release: 12 million Foundation OWN and 8 million team OWN. The schedule reaches 60 million and 40 million OWN respectively, completing both allocations.
These are scheduled quantities and months relative to genesis, not confirmed calendar dates or evidence of completed on-chain transfers. Actual availability and transfers at a given date require the corresponding records.
This schedule is not the customer's payment calendar, the timing of an OWN Access Plan instalment or the date on which a customer obtains a specified ownership right.
Total, allocated and circulating supply are not interchangeable
Genesis quantity, historical allocation and current circulation answer different questions.
A token can be minted without being available for sale. It can be allocated to a recipient while still subject to vesting or an operator agreement. These states describe the same fixed supply from different perspectives.
Total supply means the number of OWN created: one billion, fixed under the recorded design.
Allocated supply identifies how that same one billion was distributed across the four genesis tranches. An allocation is a historic assignment, not a live balance.
Circulating supply means OWN held outside the operator’s own holdings, including its inventory and reserves, and transferable under its governing instrument. Unsold inventory does not count merely because it is unrestricted. Released vesting tokens count after beneficiaries transfer them onwards; Plan units still subject to transfer restrictions are excluded. Each figure needs a date, a stated method and records; no live total is verified here.
A block explorer's current total-supply field or an individual wallet balance is not, by itself, an authoritative calculation of this fuller circulation measure. Every published figure should identify what it measures and when it was verified.
A dated circulation calculation should reconcile unsold Pool inventory, active LTO commitments, purchases of existing OWN, Utility Reserve allocations and programme commitments, and released or unreleased Foundation and team balances. Track later transfers and apply each relevant operator or vesting condition, counting each token once. No single inventory total or release schedule can substitute for that reconciliation.
What is fixed and what can change?
Read changing quantities with their definitions and verification dates.
- Fixed by the token's recorded design
- One genesis mint and the total number of OWN created. The official identity refers to one deployed contract, not a sequence of replacement tokens.
- Historical, not continuously changing
- The original allocation percentages and quantities at genesis.
- Able to change over time
- Ownership of units, vesting releases under the applicable instruments, Plan-related movement and the supply that qualifies as circulating. Market valuation can also change, but this page does not present a price or forecast.
Permanent identity and its limits
The supplied design gives OWN one permanent ERC-20 contract identity. Under the Catastrophic Token Continuity and No-Remedy Decision Framework, the Foundation has no power in that core contract to fix, freeze, reverse, reissue or migrate OWN.
A code defect, network failure or fork, or lost or stolen keys cannot be remedied by the Foundation. The Framework provides no replacement OWN or compensation from the Issuer tranche. Any response would record and communicate verified facts.
Separate vesting tools have their own controls and records. An operator’s or custodian’s obligations remain governed by its own terms and applicable law. The Foundation Wind-Down and Public-Record Continuity Plan provides for the official record to survive the institution; a successor gains no privileged power over core OWN.
These are documented design and policy positions, not independent verification of deployed code or ancillary-tool enforcement.
Who maintains which part of the record?
OWN Token Foundation is the issuer of record. It maintains the token's official identity and supply information, cares about OWN's future and supports the growth of its ecosystem.
BitLease Technology Ltd operates the platform through which the OWN Access Plan is provided. BitLease Capital Ltd is the sole Lessor of the OWN Access Pool, whose inventory was supplied from the Evergreen genesis tranche.
49G Holding Ltd originated the genesis mint-and-distribution instruction. The original BitLease founding and development team received the 4% allocation into designated wallets. The Foundation's Council acted independently, and the Foundation remains separate from the 49G group.
The Foundation does not sell OWN to the public through this reference page, set a token price or operate the customer's acquisition agreement.
Key terms
- OWN
- The ERC-20 token whose official identity and supply are maintained by OWN Token Foundation.
- Ethereum
- The blockchain network named in OWN's recorded token design. This statement does not independently verify a deployed contract.
- ERC-20
- A technical standard for fungible tokens on Ethereum. It does not itself grant additional utility or contractual rights.
- Genesis mint
- The initial creation of OWN's fixed supply in a single mint event.
- Contract address
- The identifier of a deployed smart contract on a specific network; it must be checked against the official record before use.
- Allocation
- The documented division of the Genesis supply, minted directly into the designated recipient wallets at mint. An allocation is a historical assignment, not a live balance.
- Total supply
- The number of OWN created: one billion, fixed under the recorded design. It is distinct from a current circulating quantity.
- Vesting
- Timed release for a specified tranche through separate vesting tools and its governing instrument, outside the OWN ERC-20 contract. It is not a customer payment calendar; a timetable alone does not prove technical enforcement.
- Circulating supply
- Under the Foundation’s definition, OWN outside the operator’s own holdings, including inventory and reserves, and transferable under its governing instrument. Released vesting tokens enter this measure after onward transfer. Unlocking alone is insufficient; each figure needs a dated method and records.
- LTO
- Lease-to-Own, a model organising an acquisition through agreed payments over time. Cost, eligibility and rights depend on the actual agreement.
- OWN Access Pool
- The token inventory supplying the OWN Access Plan, with BitLease Capital Ltd as Lessor. It is distinct from the Foundation issuer treasury and is not an investment fund offered by the Foundation.
- OWN Access Plan
- The name of an external BitLease arrangement. Further information about the Access Pool and related arrangements is available at bitlease.capital.
- Evergreen inventory
- The continuing access-inventory model built around the original 500 million OWN. Replenishment purchases existing available tokens; it is not new minting, automatic return or a guaranteed repurchase.
- Utility Reserve
- BitLease Technology Ltd’s 400-million-OWN allocation for platform utilities and discount support. Its use commitments belong to the operator’s policy, not additional restrictions in OWN’s ERC-20 code.
- Issuer allocation
- The Foundation’s 60-million-OWN mission resource. Vesting makes existing tokens available; separate governance and budget authority determine their use.
- Right of Use
- A term used in acquisition agreements. Its meaning and any limits must be read in the responsible provider’s own documents; continue to bitlease.capital for the related information.
- Full Settlement
- A contractual completion term. Read the relevant provider’s own documents for its meaning and requirements; further reading is available at bitlease.capital.
- Finance-free
- A cost description whose scope depends on the provider’s own documents. This glossary does not state the current costs or conditions of the OWN Access Plan; continue to bitlease.capital.
- Liquidation
- The forced closing of a position or sale of assets under an arrangement’s rules. Its triggers and consequences depend on that arrangement.
Questions about the minted token
Is OWN's total supply the same as the number currently circulating?
No. One billion is the fixed Genesis supply. For example, unsold Pool inventory does not circulate merely because no Genesis vesting applies to it. Released vesting tokens count after onward transfer; externally held units must also be transferable under their governing terms. A circulating figure needs a date, a stated method and records. This page provides no verified live total.
Does a fixed supply prevent OWN's price from changing?
No. Fixed supply describes the token's recorded quantity, not its market value or what an acquisition will cost under a particular agreement.
Can I rely on any token called OWN in a wallet or search result?
No. A name or ticker can be ambiguous. The official Contract Identity Record is not yet published here; no address shown elsewhere is verified by this website.
Does the institutional vesting schedule tell me when my Plan will finish?
No. Institutional vesting governs specified genesis allocations; the customer's agreement governs payment dates, rights and completion conditions.
Is this page a place to purchase the token?
No. This page explains token facts and roles. The OWN Access Plan is offered through BitLease, not by the Foundation on this reference page.
Continue from the facts to the wider idea
Read the acquisition example, learn about the Foundation or prepare an ecosystem proposal.
Sources and evidence status
These descriptions draw on the supplied editorial sources below. Their edition numbers belong to separate document series; none is independent verification. The current Foundation Corpus and corrected Supporting Master Series 1.1.0 inform these descriptions. The supporting PDFs control the identified corrections that are absent from their editable companions. This editorial update does not amend governing instruments, verify deployed code or establish current wallet balances.
- OWN Token Foundation Corpus, edition 1.0; README amended 2 November 2026, 2 November 2026.
- OWN Token Foundation Supporting Master Series, edition 1.1.0 (corrected PDFs), 24 October 2026.
- Website Content Master — English, edition 2.2, 15 October 2026.
- OWN-LTO Complete Reading Edition, edition 3.2 (corrected), 14 October 2026.
- Website Content Master — updated allocation and vesting, edition 0.1.0, 24 October 2026.
No source file is offered for download here.
- Foundation stewardship and decisionsSupplied editorial record
The Foundation’s finite issuer resource, independent approvals, written commitments and dated institutional records.
What it does not establish: A release of vested tokens is not an approved expenditure. A described framework is not evidence of an actual award, a current budget or a completed project.
- Token design and genesisSupplied editorial record
Ethereum, ERC-20, a single genesis mint and the recorded one-billion-OWN quantity.
What it does not establish: Contract address, deployment transaction and corresponding verification evidence are still to be supplied. This record does not authenticate an address.
- Original allocationSupplied editorial record
The four allocation classes, minted directly into the designated recipient wallets at Genesis, with their recorded percentages and quantities.
What it does not establish: Historical allocation is not a current wallet balance, a circulation calculation or a market value.
- Institutional vestingSupplied editorial record
Separate vesting tools outside the OWN ERC-20 contract, with a 12-month cliff and five releases at months 12, 15, 18, 21 and 24: 12 million Foundation OWN and 8 million team OWN at each checkpoint.
What it does not establish: Relative months are not confirmed calendar dates or evidence of actual transfers. The ancillary tools, governing instruments and execution records require their own verification.
- BitLease Capital information (Opens an external website)External reading destination
BitLease Capital Ltd holds the OWN Access Pool. Read about its role and the related arrangements on its own website.
What it does not establish: This link is a reading destination, not verification of current offer terms, eligibility or an application service.
- Roles and acquisition explanationSupplied editorial record
The supplied distinctions between Foundation, operator, lessor, token, inventory and agreement.
What it does not establish: The editorial explanation does not replace a governing instrument or establish current customer eligibility. Corporate records and current operator terms have not been independently verified here.
Description, proposal and availability
A described model or potential use is not proof that it is available to a particular person today.
- Foundation resources and ecosystem supportDocumented governance framework
- The corrected supporting series describes budgeted, independently approved support for defined work. This website does not announce an open grant round, a funding award or a promise to operate another party’s service.
- Access Pool and acquisition informationExternal reading destination
- The owner-selected destination is bitlease.capital. Read the responsible organisations’ own information there. This website does not authenticate a current offer or individual eligibility.
- OWN on another platformProposal
- A collaboration direction to explore. No third-party integration or new asset-ownership right is announced by this website.
- Official contract identityAwaiting verification evidence
- Contract particulars and deployment evidence remain to be supplied. The illustrative record cannot authenticate an address.
What changed
This history describes the website’s explanation and presentation. It does not record a change to legal instruments, token terms or an operator agreement.
· 2026.11.03.10
The final Foundation message
Replaced the earlier recording with the final Foundation video, with a matching poster, English captions and transcript. The Foundation’s official social profiles and token information remain available.
· 2026.11.03.9
Official Foundation social profiles
Added the Foundation’s official LinkedIn and X profiles to the footer, contact page and publisher identity metadata. These profiles identify OWN Token Foundation. Token facts and the separate responsibilities of other organisations remain unchanged.
· 2026.11.03.8
A concise introduction and an external reading destination
Kept the Foundation’s token and supply record here, shortened the application explanation and linked to bitlease.capital for further reading. Detailed provider terms are no longer reproduced in the page, glossary, diagrams or printable guide. Token facts and the approved imagery remain unchanged; this does not amend a governing instrument or verify an external offer.
· 2026.11.03.7
Reading and recovery refinements
Improved keyboard dismissal of the chapter index and page-error recovery, and reduced unnecessary early font loading. Token facts, supply figures, source qualifications and contact availability remain unchanged. This update does not verify deployment or authorise publication.
· 2026.11.03.6
Genesis, vesting and the Foundation’s authority
Clarified direct minting into recipient wallets and separate vesting tools, expanded the explanation of token permanence and circulating supply, and added a guide to governance and independence. Allocation amounts and the five release checkpoints remain unchanged. This is an editorial update, not verification of implementation or amendment of governing instruments.
· 2026.11.03.5
The two paths move to Collaborate
Moved the existing two-path photograph to the Collaborate opening and kept Home’s two directions in a shorter, text-led composition. Token facts, Foundation roles and programme terms remain unchanged.
· 2026.11.03.4
The corrected supporting series becomes the reference
Reconciled the explanation with the corrected Supporting Master Series 1.1.0. Clarified release conditions and inventory replenishment, expanded verification and record guidance, and added a page on the Foundation’s own stewardship decisions. Allocation amounts and release checkpoints remain unchanged; no live contract verification, operator offer or funding award is established.
· 2026.11.03.3
A clearer photographic and reference presentation
Brought the supplied recording forward, reorganised page openings around their reading tasks, and gave token records and operator relationships greater visual weight. The Foundation’s role, token facts, service terms and publication states remain unchanged.
· 2026.11.03.2
Editorial presentation polish
Simplified labels and repeated introductions, replaced generic headings with specific reader tasks, and refined interface motion. The supplied photography, video, token facts and service boundaries are retained.
· 2026.11.03
The supplied Foundation video
Replaced the illustrative animation with the supplied Foundation message, an opening frame from that video and English captions timed to its speech. The full transcript and complete video frame remain available alongside native playback controls.
· 2026.10.24.3
The Foundation and OWN lead the story
Reworked the homepage around the Foundation’s purpose, OWN’s fixed beginning, its first application on BitLease and an open invitation to builders, platforms and educators. Shortened acquisition detail with routes to the full explanation. Existing photography and token facts are unchanged.
· 2026.10.24.2
Allocation recipients and five release checkpoints
Aligned the allocation record with the latest supplied master: the original BitLease founding and development team receives its 4% allocation into designated wallets; Holding originated the genesis instruction. The release schedule now explicitly shows months 12, 15, 18, 21 and 24, with 12 million Foundation OWN and 8 million team OWN at each checkpoint. This corrects the website’s description; it is not evidence of completed transfers or a change to the fixed supply.
· 2026.10.24
Verification guidance and more useful proposals
Added a guide to reading verification evidence, clarified supply states and the distinction between a service discount and token value, and refined education, research and proposal prompts. Contract identity remains unverified here; no token, allocation, vesting or operator terms have changed.
· 2026.10.18
Support, obligations and clearer proposals
Clarified the Foundation’s support for OWN and its ecosystem alongside each operator’s separate responsibilities. Added the price-movement and missed-payment distinction, five proposal prompts and clearer routes for other tokens. These explanations do not amend token or operator terms.
· 2026.10.16.2
Reading and reference edition
Added a shared glossary, evidence-status register, rights comparison and printable reading brief. These presentation and explanation changes do not amend token or operator terms.
· 2026.10.16
Clarity and access edition
Clarified reader routes, agreement stages and illustrative states; improved reading contrast, navigation and local enquiry preparation. No contract verification or online submission was introduced.
OWN, in a few essentials
Editorial edition 2026.11.03.10 ·
This guide covers the Foundation’s token record and the separate roles around OWN. For information about the Access Pool and related arrangements, continue to BitLease Capital’s own website.
- OWN · The token
- The token issued by OWN Token Foundation, with a defined identity, a recorded fixed supply and an intended utility purpose.
- OWN Access Pool · The inventory
- The original access inventory held by BitLease Capital Ltd as Lessor. It is separate from the Foundation’s issuer allocation.
- OWN Access Plan · The pathway
- An external BitLease arrangement. Continue to bitlease.capital for information about the Access Pool and related arrangements.
The Foundation issues OWN, cares about its future and supports the growth of its ecosystem. That support does not make it the Plan’s operator, lender or contractual seller. It is independent of the 49G group.
Information about acquiring OWN
BitLease Capital Ltd holds the OWN Access Pool. Read about its role and the related arrangements on its own website.
Identity status. The official Contract Identity Record is not yet published here. A token name or symbol alone does not verify a contract; no address shown elsewhere is verified by this website.
OWN Token Foundation reading guide. Based on the supplied OWN Token Foundation Corpus 1.0; README amended 2 November 2026 (2 November 2026) and OWN Token Foundation Supporting Master Series 1.1.0 (corrected PDFs) (24 October 2026) and Website Content Master — English 2.2 (15 October 2026) and OWN-LTO Complete Reading Edition 3.2 (corrected) (14 October 2026) and Website Content Master — updated allocation and vesting 0.1.0 (24 October 2026). The editorial date is not a verification date. See Sources and evidence status on this page for the limits of these records.