> For the complete documentation index, see [llms.txt](https://hellstreet.gitbook.io/hellstreet-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hellstreet.gitbook.io/hellstreet-docs/introduction/general-aspects.md).

# 🪐 General aspects

<figure><img src="/files/zemboRq16quWQHpRnZ9Z" alt=""><figcaption></figcaption></figure>

**This section lays out the high-level design principles, technical building blocks, economic assumptions, governance approach, and community / safety considerations that guide HellStreet. It’s written for product leads, devs, creators, and community managers who need a clear, realistic foundation for how a modern urban metaverse is designed, operated, and evolved. Expect concrete standards, familiar Web3 terms, operational guidance, and practical trade-offs — no fluff.**

***

#### 1) High-level vision & value proposition ✨ <a href="#id-1-high-level-vision-and-value-proposition" id="id-1-high-level-vision-and-value-proposition"></a>

**HellStreet is an urban-first metaverse: a persistent, modular city where social gameplay, creator economies, and real ownership converge. Our objective is to deliver:**

**Playable social worlds** (hubs, roleplay zones, PvP/PvE arenas) optimized for emergent interaction and low entry friction. **Creator-centric tooling** that lets non-programmers and studios alike publish experiences, monetize assets, and iterate quickly. **Real economic rails** that connect in-platform commerce to on-chain settlement and composable NFT/FT standards. **Interoperability & scalability** — users should take identity, key items, and reputation across worlds while the platform scales to thousands of concurrent players.

{% hint style="info" %}
**Why this matters:** players expect high fidelity, social depth, and seamless commerce; creators expect discoverability, fair revenue splits, and technical predictability; partners expect secure settlement and auditability. HellStreet sits at the intersection of these expectations.
{% endhint %}

***

#### 2) Architecture & technical stack (practical summary) 🧩 <a href="#id-2-architecture-and-technical-stack-practical-summary" id="id-2-architecture-and-technical-stack-practical-summary"></a>

**Core principles:**

**Hybrid on-chain / off-chain architecture** — keep high-frequency state (player position, ephemeral session data) off-chain for performance; record critical ownership/state on-chain (NFTs, land deeds, final receipts).

**Modular orchestration** — HellStreet Create handles instance sharding, streaming, and cross-service messaging so worlds can scale independently.

**Standards-first approach** — use established token and signing standards to maximize interoperability with wallets, marketplaces, and third-party tooling.

**Recommended components (real, industry-standard):**

**Settlement Layer:** Ethereum mainnet (for anchor & high-value settlement) + Layer-2/sidechain(s) for day-to-day commerce (Optimistic rollups / zk-rollups / EVM sidechains).

**Token Standards:** ERC-20 — fungible tokens (platform currency, governance token). ERC-721 — unique NFTs (LAND deeds, exclusive wearables). ERC-1155 — semi-fungible bundles (loot crates, stackable consumables). EIP-2981 — royalty standard for creator royalties. EIP-712 — typed data signing for off-chain approvals and gasless UX.

**Storage & persistence:** IPFS / Arweave for durable metadata and media; metadata pinning and content hashing to ensure provenance.

**Identity & wallets:** WalletConnect / MetaMask / hardware wallet support + an optional custodial flow for fiat on-ramp (KYC gated).

**APIs & SDKs:** REST + GraphQL APIs for public metadata + WebSocket / webhooks for live events; Unreal / Unity runtime SDKs and a JavaScript SDK for web integrations.

**Bridges & cross-chain:** Standard bridging patterns (wrapped assets, verifiable proofs) for moving assets between the L2/sidechain and mainnet settlement layers.

***

<figure><img src="/files/gFuCCQKNqe6nhX0aqYsK" alt=""><figcaption></figcaption></figure>

#### 3) Economy, tokenomics & monetization 🔁 <a href="#id-3-economy-tokenomics-and-monetization" id="id-3-economy-tokenomics-and-monetization"></a>

**Currency & asset model:**

* **Platform currency (optional ERC-20):** used for in-game microtransactions, marketplace fees, staking, and governance voting.
* **NFTs as utility & collectibles:** wearables, LAND, access passes, and event tickets use ERC-721/1155 with immutable provenance and optional royalty logic.
* **Consumables & sinks:** design in-game sinks (repair, consumable cosmetics, craft fees) to create demand and reduce inflationary pressure.

**Typical revenue & payout flows:**

* **Primary sales:** creator mints + initial sales on HellStreet Exchange (platform takes a configurable commission).
* **Secondary royalties:** enforced via EIP-2981 for creator earnings on resales.
* **Event & land revenue:** ticket sales, entrance fees, vendor rent, and revenue share between landowner and visiting creator.
* **Staking / rewards:** token staking to secure services, earn protocol rewards, or gain priority access to drops.

**Practical economic controls:**

* **Caps & mint limits:** limit supply per drop to create scarcity and predictability.
* **Fee & burn mechanisms:** marketplace fees and optional burn from consumables to moderate token supply.
* **Dynamic pricing tools:** auctions, Dutch auctions, or reserve pricing for premium assets.

***

<figure><img src="/files/W3xFWxPf4FGbmKpzCADL" alt=""><figcaption></figcaption></figure>

***

#### 4) Interoperability, portability & composability 🔗 <a href="#id-4-interoperability-portability-and-composability" id="id-4-interoperability-portability-and-composability"></a>

**Identity & avatars:**

* **Universal Avatar model:** a canonical avatar schema with exportable appearance metadata. Avatars follow a composable equipment model (slot system) to ensure cross-world compatibility.
* **Account abstraction:** consider ERC-6551 (token bound accounts) or account abstraction patterns to allow wallets to own rich profiles and to enable game accounts bound to NFTs.

**Asset reuse & composability:**

* **Shared metadata schema:** all assets expose the same JSON metadata shape (name, description, rarity, asset URIs, trait schema) so marketplace and discovery engines can index uniformly.
* **Runtime compatibility layers:** a small runtime mapping layer converts asset behavior across different worlds (e.g., a “jacket” in one world maps to a body slot in another with fallback textures).

**Cross-platform flows:**

* **Bridging:** use wrapped representations and merkle proof verification to move assets between chains/layers. Avoid non-reversible bridging logic; maintain clear user receipts and on-chain anchors.
* **External marketplaces & marketplaces:** make metadata verifiable so third-party platforms can list HellStreet assets while royalties and provenance remain intact.

***

<figure><img src="/files/shmNWsu5JrjbJbxFYiaa" alt=""><figcaption></figcaption></figure>

***

#### 5) Security, fraud prevention & compliance 🛡️ <a href="#id-5-security-fraud-prevention-and-compliance" id="id-5-security-fraud-prevention-and-compliance"></a>

**Security practices:**

* **Smart contract audits:** third-party audits for all minting, marketplace, and bridge contracts. Public audit reports and bug bounty programs.
* **Transaction watch & risk scoring:** monitor large transfers, pattern anomalies, and wash-trading signals; create rate limits for new vendors.
* **Escrow & dispute resolution:** marketplace escrow for high-value sales and a documented dispute workflow.

**Compliance & legal:**

* **KYC/AML where necessary:** for fiat on-ramps, large withdrawals, or regulated regions. Implement sanctions screening and suspicious activity reporting.
* **GDPR & data privacy:** support data export/deletion requests; separate on-chain public data from off-chain personal data and minimize PII storage.
* **Age gating:** enforce 13+/18+ rules per feature (monetization/fiat flows) in user flows.

***

#### 6) Governance & community participation 🗳️ <a href="#id-6-governance-and-community-participation" id="id-6-governance-and-community-participation"></a>

**Governance model:**

* **Hybrid governance:** mix off-chain signaling (Snapshot proposals) with on-chain voting for treasury allocation and protocol upgrades. Use a governance token (ERC-20) with delegated voting and quorum thresholds.
* **Localized governance:** allow LAND or district stewards to set local rules (event noise, monetization rates, neighborhood moderation), subject to platform guardrails.

**Community funding & grants:**

* **Spotlight grants & accelerator:** curated grants for high-quality worlds, with technical support and marketing placement.
* **Revenue sharing programs:** transparent revenue splits for grant recipients and incubated creators.

***

<figure><img src="/files/y8LWgHTwmVS2utPz7Bpf" alt=""><figcaption></figcaption></figure>

***

#### 7) Creator economy & tooling 🛠️ <a href="#id-7-creator-economy-and-tooling" id="id-7-creator-economy-and-tooling"></a>

**Creator tooling (must-have):**

* **Visual Create editor:** drag-and-drop modules, logic nodes for events/triggers, and a publish pipeline that packages assets to the Exchange.
* **Template marketplace:** starter worlds, UI kits, and purchasable gameplay modules (e.g., leaderboard module, ticketing events module).
* **Testing & QA flows:** staging sandboxes, load testing for event hosts, and automated validation (asset size, polygon counts, animation loops).

**Metadata & best practices:**

* **Metadata schema:** include clear fields for royalty percentage, license terms, usage rights, and creator contact.
* **Preview assets:** always publish 3–6 second preview clips and multi-angle screenshots for marketplace listings.
* **Versioning:** maintain semantic versioning for world templates and document migration paths for updates.

***

#### 8) UX, accessibility & inclusion ♿️ <a href="#id-8-ux-accessibility-and-inclusion" id="id-8-ux-accessibility-and-inclusion"></a>

**UX priorities:**

* **Low friction onboarding:** walletless guest flows, optional custodial accounts, and meta-transaction patterns (gas abstraction) to reduce first-time friction.
* **Clear affordances:** visible costs, refund/chargeback policy, and transparent ownership receipts.
* **Progressive disclosure:** advanced creator features behind opt-in tooling; beginners see guided templates.

**Accessibility:**

* **Visual & audio accessibility:** subtitles, high-contrast UI mode, remappable controls, and audio description options.
* **Localization:** UI & marketplace copy in major languages; creator metadata supports multi-language descriptions.

***

<figure><img src="/files/G3GQlGkPw1kqKPYpjLgj" alt=""><figcaption></figcaption></figure>

***

#### 9) Safety & moderation 🚨 <a href="#id-9-safety-and-moderation" id="id-9-safety-and-moderation"></a>

**Moderation model:**

* **Multi-tier approach:** combination of automated filters (asset scanning, profanity/NSFW detection), community reporting, and human review.
* **Local controls:** LAND owners can configure local moderation rules within global policy boundaries.
* **Transparent appeals:** a documented appeals process for content takedowns and enforcement actions.

**Community safety features:**

* **Scam prevention education:** in-client prompts about private keys and phishing, plus an active “report scam” flow.
* **Verified vendors & badges:** reputation signals for trustworthy creators and sellers.

***

#### 10) Metrics & success signals 📈 <a href="#id-10-metrics-and-success-signals" id="id-10-metrics-and-success-signals"></a>

**Key metrics to monitor and iterate on:**

* **DAU / MAU & session length** (first 7/30/90 days)
* **Creator retention & revenue per creator** (monthly)
* **Marketplace volume & royalty flows** (primary/secondary)
* **Average concurrent users per world & peak shard counts**
* **Incident rates** (fraud, moderation, performance issues) and mean time to resolve (MTTR)

{% hint style="info" %}
Use telemetry from HSC to build heatmaps (player flow), economic dashboards (supply & sinks), and creator analytics (engagement/monetization).
{% endhint %}

***

<figure><img src="/files/QDlXfxfxIhuvmPMh8Rds" alt=""><figcaption></figcaption></figure>

***

#### 11) Practical recommendations & trade-offs ✅ <a href="#id-11-practical-recommendations-and-trade-offs" id="id-11-practical-recommendations-and-trade-offs"></a>

**Latency vs. consistency:** use eventual consistency for most social features; reserve strong consistency for financial settlement.

**On-chain granularity:** store durable ownership and provenance on-chain; keep ephemeral session state off-chain for performance.

**Royalties enforcement:** prefer marketplace-level enforcement + clear metadata (EIP-2981), but communicate that secondary marketplace enforcement is not absolute across third parties.

**Interoperability scope:** start with avatar traits and a small set of high-value items for cross-world portability; expand gradually.

***

#### 12) Example user stories (concrete scenarios) 🎯 <a href="#id-12-example-user-stories-concrete-scenarios" id="id-12-example-user-stories-concrete-scenarios"></a>

> **Creator:** Maria publishes a night-club world in the Create editor, mints 200 VIP passes (ERC-1155), lists them on HellStreet Exchange, and runs weekly ticketed shows. She earns primary sale revenue + royalties on secondary sales.

> **Player:** Jamal completes a city scavenger quest and receives a limited “Drone Key” NFT reward; he uses the key to access a rooftop vendor that sells exclusive cosmetic skins.

> **Operator:** A festival requires 20,000 concurrent seats — HSC auto-scales shards, routes clients to instances, and batches mint confirmations for festival NFTs to a Layer-2 rollup for fast settlement.

***

#### Closing notes — why this matters <a href="#closing-notes-why-this-matters" id="closing-notes-why-this-matters"></a>

**Designing HellStreet with clear technical standards, hybrid architecture, and community-first economics makes the platform resilient, extensible, and welcoming. By combining off-chain performance with on-chain guarantees, exposing robust creator tooling, and enforcing fair marketplace patterns, we create a sustainable urban metaverse where play, creation, and ownership are tightly coupled — and where users can meaningfully participate in the platform’s growth.**

***

<figure><img src="/files/f1MtAJgjZCu3hJ0Uxzni" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hellstreet.gitbook.io/hellstreet-docs/introduction/general-aspects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.