# HardwarePlay Tokenomics and Legal Framework

Version: 0.1 (Draft for legal review)
Date: 2026-04-12
Status: Internal working draft, not final legal text

## Important Notice
This document is a business and legal framework draft for HardwarePlay. It is not legal advice and does not replace review by a qualified lawyer in the jurisdictions where HardwarePlay operates.

This document does not constitute:
- an offer of securities,
- an investment solicitation,
- financial advice,
- tax advice,
- legal advice.

No person should rely on this document for financial or legal decisions without independent professional advice.

## 1. Purpose and Scope
This paper defines how the HardwarePlay ecosystem is structured from a tokenomics and legal perspective, including:
- the relationship between HardwarePlay NFTs, the platform stable-value token, and the investor token,
- marketplace mechanics,
- fee routing and percentage-based distributions,
- periodic buyback logic,
- operational and legal boundaries.

This paper applies to all blockchain-enabled features of HardwarePlay built on Sui infrastructure, unless a separate written policy overrides a specific section.

## 2. Ecosystem Architecture
HardwarePlay uses Sui as the underlying blockchain infrastructure. HardwarePlay remains the application, commercial, and product layer.

In practical terms:
- Sui = infrastructure layer (registration, ownership, transfer rails),
- HardwarePlay = branded platform layer (products, rights, marketplace logic, integrations).

Users acquire HardwarePlay assets that are issued on Sui. They do not acquire ownership of the Sui network itself.

## 3. Asset Layers
### 3.1 HardwarePlay NFT (HP-NFT)
Role:
- represents ownership, access rights, utility rights, or project-specific claims tied to a tag, campaign, or digital object.

Core functions:
- ownership record,
- transferability,
- rights gating in platform workflows,
- linkage to physical NFC tag identity where applicable.

### 3.2 HardwarePlay Stable-Value Token (Working name: HPS)
Role:
- medium for platform settlement and predictable-value internal operations.

Legal caution:
- the term "stablecoin" may trigger specific regulatory treatment in some jurisdictions.
- final naming and implementation must be reviewed before public launch.

Operational intent:
- settlement of selected marketplace fees,
- service payments,
- treasury/accounting layer for recurring platform transactions.

### 3.3 HardwarePlay Investor Token (Working name: HPI)
Role:
- ecosystem-linked token intended to receive value support via predefined percentage routing from platform activity.

Important boundary:
- rights linked to HPI must be explicitly documented.
- no implicit promise of profit, dividend, or guaranteed return is made unless separately defined in legally approved terms.

## 4. Token Naming Policy
Current working names:
- HP-NFT (HardwarePlay NFT)
- HPS (HardwarePlay Stable-Value Token)
- HPI (HardwarePlay Investor Token)

Final public names may be changed after:
- trademark checks,
- legal review,
- exchange or wallet display compatibility checks,
- product communication review.

## 5. Marketplace Design
The HardwarePlay marketplace supports two primary market streams:
- NFT transfer and resale,
- public sale of advertisement space linked to platform inventory.

### 5.1 NFT Trading Flow
1. A seller lists an eligible HP-NFT.
2. A buyer executes purchase under marketplace rules.
3. Transfer and confirmation occur on supported rails.
4. Fee routing executes based on configured percentages.

### 5.2 Public Ad Space Sales
Ad inventory may be sold through public listing flow.
Revenue from ad sales can be routed through the same distribution logic framework as NFT transactions, if configured.

## 6. Distribution Logic and Percentage Routing
Every eligible transaction can be split by percentage buckets.

Example routing buckets (illustrative):
- platform operations,
- project reserve,
- ecosystem growth,
- investor-support bucket,
- buyback bucket.

Final percentages must be published in an official schedule before launch.

### 6.1 Parameter Table (To be finalized)
- Platform operations: [X%]
- Reserve/Treasury: [X%]
- Growth/Marketing: [X%]
- Investor-support route (HPI-related): [X%]
- Buyback route: [X%]
- Other routes: [X%]

Constraint:
- total must equal 100% for each configured transaction class.

## 7. Periodic Buyback Mechanism
HardwarePlay may execute an automatic periodic buyback mechanism for selected tokens, based on predefined treasury rules.

Minimum policy requirements:
- fixed cadence (for example weekly, monthly, or epoch-based),
- transparent budget source,
- documented execution conditions,
- publicly stated handling of acquired tokens (for example treasury hold, burn, controlled release).

No guaranteed market effect is promised. Buyback is an operational mechanism, not a guarantee of price performance.

## 8. How Investor Value Support Is Fed
Investor-side support (HPI-related) can be fed through percentage allocations from qualifying platform transactions.

This mechanism is based on:
- transaction volume participation,
- predefined routing percentages,
- transparent accounting and reporting.

This is not a guarantee of future value, liquidity, or return.

## 9. Account, Wallet, and Order Policy
### 9.1 Account requirement
Orders are processed only through a valid HardwarePlay account.

### 9.2 Wallet-first policy
For direct mint-to-user flows, wallet linkage is required at order or activation stage.

### 9.3 No-wallet scenarios
No-wallet orders may be permitted under explicit policy conditions.
Consequences can include:
- no immediate onchain ownership,
- additional transfer/migration fees if ownership is moved later,
- reduced access to blockchain-linked features.

## 10. Refund, Return, and Replacement Policy (Platform Level)
### 10.1 Non-refundable categories
Minted tags and custom products are non-refundable.

### 10.2 Returns
Returns for eligible non-custom physical items may be accepted under policy, with customer-paid shipping unless mandatory law states otherwise.

### 10.3 Defective tag replacement
HardwarePlay may replace defective tags at HardwarePlay cost for up to 2 months after purchase date, subject to validation.
After that period, replacement may require a new paid purchase.

### 10.4 Swap operations
Approved replacement requests can be operationally swapped in platform records by HardwarePlay, so workflow continuity is preserved.

## 11. Regulatory and Legal Positioning
Legal treatment depends on jurisdiction and token functionality at launch time.

Before public rollout, HardwarePlay should complete formal review for:
- token classification,
- consumer law compliance,
- financial promotion restrictions,
- AML/KYC triggers,
- sanctions screening obligations,
- data protection requirements.

### 11.1 No unauthorized financial claims
Public communication must avoid unapproved statements such as:
- guaranteed returns,
- guaranteed token price growth,
- risk-free investment language.

## 12. Risk Disclosures
Users and participants should be informed of at least:
- technology risk,
- smart contract and integration risk,
- liquidity risk,
- market volatility risk,
- regulatory change risk,
- operational and treasury risk.

## 13. Governance and Change Control
HardwarePlay may update tokenomics parameters only through documented change control.

Minimum change control standard:
- written proposal,
- internal review,
- legal review where required,
- publication before effect where user rights are impacted.

## 14. Data, Compliance, and Recordkeeping
HardwarePlay should retain records for:
- transaction routing,
- buyback execution logs,
- treasury movements,
- allocation snapshots,
- policy version history.

Where required by law, KYC/AML procedures may apply before enabling certain functions.

## 15. Jurisdiction and Priority of Documents
This paper is an explanatory framework and does not override:
- Terms and Conditions,
- Privacy Policy,
- Purchase Terms,
- any mandatory local law.

In case of conflict, the legally approved contractual documents prevail.

## 16. Launch Checklist (Legal-Ready)
Before publication and PDF distribution, confirm:
- final token names,
- final percentage schedule,
- final buyback rules,
- final rights linked to HPI,
- final consumer and refund wording,
- final jurisdiction clauses,
- legal counsel sign-off.

## Appendix A: Recommended Public Summary Text
"HardwarePlay assets are issued on Sui infrastructure. Users obtain HardwarePlay NFTs and tokenized platform assets under HardwarePlay rules. Marketplace transactions can route percentage-based allocations to operations, reserve, growth, investor-support mechanisms, and periodic buyback according to published policy parameters."

## Appendix B: Required Legal Disclaimer for Public PDF
"This document is provided for informational purposes only and does not constitute legal, tax, investment, or financial advice, nor an offer to sell or a solicitation to buy any security or financial instrument. Any token-related model described herein is subject to legal review, regulatory compliance, and final published terms."