BHCT Whitepaper · Contents10/19
- Version
- v1.8
- Issued
- November 5, 2026
- Issuer
- NVEX Foundation
- Download PDF · 676KB
Chapter 10
Foundation and disclosures
NVEX Foundation
The NVEX Foundation manages BHCT and the NVEX website and is pursuing a BHCT integration partnership with Zetaverse's separate operator. The foundation's registered name and location will be published in this chapter and on the disclosure board once confirmed.
| Role | Details |
|---|---|
| Token management | Treasury and contract permissions, BHCT payout tools and records |
| NVEX website | Balance lookup, account wallet linking, reward history and supply API |
| Proposed integration partnership | Agree exchange of reviewed results, BHCT terms of use and payout procedures with the operator |
| Disclosure | Whitepaper, disclosures and supply data |
Separate Zetaverse operator
The Zetaverse operator handles the platform and creator programs, brand matching, and the contract, delivery and performance review process. The operator's legal entity information and partnership scope will be published once verified and confirmed.
Campaign contracting parties, payment receipt and settlement, review approval, BHCT payout responsibility and funding, refunds, dispute handling and information exchange will be set in contracts and policies and announced before participation. NVEX's payout tools are distinct from the operator's campaign review role; pursuing a partnership does not assign every settlement and payout responsibility to either party.
Proposed collaboration and handoffs
| Work | Role in the proposed collaboration | Handoff and verification records |
|---|---|---|
| Brand requirements · contracting | The operator organizes terms with brands and creators and identifies contracting parties | Brief, contract, work scope and rights |
| Delivery · review | The operator collects materials and records confirmation by the contractually designated approver, such as the brand | Deliverables and reasons for revisions, approval or rejection |
| Reward terms · budget | The operator and NVEX agree conditions, funding, approval and payout responsibility | Campaign reward terms, budget and approval basis |
| Token payout · verification | NVEX's tools register confirmed recipients and an authorized wallet signs | Linked wallet, amount and reason, on-chain receipt |
| Disputes · incidents | Assign contacts and handoffs separately for review or contract issues and account or transfer issues | Submission reasons, verification, reconsideration and outcome |
| Disclosure · change management |
Proposed service receipt · return · shutdown responsibilities
| Work | Responsibility and funding to specify in contracts |
|---|---|
| Catalog supply | Actual operator or partner scope, slots, costs, deadlines and support contact |
| Optional additional rewards | NVEX and operator budget approval, review and payout roles, and separation from contractual compensation |
| Service receipt · refunds | Official receiving-wallet management and reconciliation, non-delivery, cancellation, completed work, gas, refund contact and reserves |
| Foundation returns · reallocation | Returnable amounts and timing, refund and dispute reserves, voluntary transfer and approval after actual receipt |
| Suspension · exit | Responsible parties, funding, deadlines and notices for confirmed unpaid rewards, accepted bookings and refunds |
Return and refund duties would be separated by order and contract. The proposed model does not use refund funding first to sustain reward reuse. It contains no promise that the foundation will buy back holders' tokens for cash if the business collaboration ends.
Disclosures
The following are posted with a date on the disclosure board. Published disclosures are never edited; corrections are posted as new correction disclosures.
- Issuance and supply changes (including burns and recoveries)
- Allocation plans and allocation wallets
- Reward payouts
- Changes to contract permissions and permission wallets
- Starting, changing or stopping a use
- Scope and progress of integration with the Zetaverse operator, and terms of use
- New versions of this whitepaper
- Security incidents and responses
Documents and versions
The whitepaper, risk notice, terms of use and privacy policy are versioned. Published versions are never edited; they are replaced by new versions, and changes to the whitepaper are kept in the changelog.
Operating-policy revisions and document · PDF references
Routine reward, catalog and quarterly-budget changes use separate policy revisions rather than rewriting the whitepaper each time. Structural, rights or allocation changes that alter the text require a new whitepaper version and disclosure.
| Policy record | Retention and display rule |
|---|---|
| Revision identifier | Unique identifiers such as ECO-0001, with proposed or confirmed status |
| Reference · effective date | Proposals have a reference date, not confirmed activation; confirmed effective registration accepts today or past dates only |
| Change basis | Korean and English explanations, before/after tables and linked disclosure |
| Application boundary | New orders and uncommitted budgets; no retroactive changes to approved rewards or accepted bookings |
| History · document link | Immutable past records and document-specific operating-table snapshots with revision and reference date |
Future-effective scheduling is not supported. Passing a proposed reference or future planning date does not automatically confirm or activate tables; separate approval, registration and disclosure are required.
Current web tables display the current revision and reference date. A PDF and its historical document print view use the snapshot linked to that document, with the operating revision and date stated in the PDF. Later live changes do not silently alter old PDFs or commitments.
Official channels and contact
Official channels and a contact address will be announced once confirmed.
This whitepaper is for information only and is not investment advice. Plans and figures may change; material changes are posted on the disclosure board. Read the full risk notice · Disclosure board