# Ecosystem Overview

The bonuz ecosystem is a layered system — protocol infrastructure at the base, consumer and brand applications on top, and a shared identity and engagement graph connecting everything.

Two entities operate the ecosystem:

* **Bonuz Inc. (St. Lucia)** operates the on-chain protocol suite: bonuz ID Protocol (identity, permissions, attestations) and bonuz Engagement Protocol / DNFT (programmable engagement assets, redemption, state management). These are the main rails that everything fundamental runs on.
* **Bonuz Technology (Dubai, UAE)** builds the applications and distribution layer: the bonuz Lifestyle Wallet, Brand Dashboard, SDK, and white-label apps for enterprise partners. All built on top of Bonuz Inc. protocols.

***

### The bonuz Human Layer — Architecture

The diagram above shows the full bonuz stack from bottom to top:

<figure><img src="https://1020566636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9HVEtjJ1liHMMIp9PMfN%2Fuploads%2Fkh77ct7kskblDxnXJQgU%2Fbonuz%20human%20layer%20diagram%2026-01.png?alt=media&#x26;token=0412b08d-489e-4932-829f-996131f0c916" alt=""><figcaption></figcaption></figure>

**Settlement Layers** — Base chains (Ethereum, EVM L1s) securing final state and asset settlement. The foundation for all higher-level applications.

**Execution Layers** — High-throughput, low-fee EVM-compatible execution environments (L1s, L2s, appchains/subnets). All upper layers inherit speed and scalability from these environments. bonuz is currently deployed on Base.

**Middleware Services** — Infrastructure and account abstraction layer. Key management (MPC/Passkeys), bundlers and paymasters, session keys, security, orchestration, monitoring, and indexing. Provider-agnostic, optimized for best consumer UX.

**bonuz — The Human Layer (Protocol & UX Rails)** — The core of the ecosystem. A chain-agnostic SDK surface providing:

* bonuz ID Protocol (identity, permissions, attestations)
* bonuz Engagement Protocol / DNFT (passes, vouchers, memberships, state management)
* Self-custodial wallet UX rails
* Gas sponsorship on core actions (optional gas abstraction)
* Loyalty, access, ticketing, quests, and programmable on-chain engagement

> "bonuz makes blockchains usable for real people and brands: 1-click login, self-custody, and programmable on-chain engagement."

The flow: 1-click social login → self-custodial wallet → dynamic NFTs for access, loyalty, ticketing, quests → gasless user experience → portable on-chain identity (bonuz ID).

**Application & Brand Layer** — Where the Human Layer meets users and brands:

* **bonuz Apps** (B2C) — Consumer apps built to showcase bonuz capabilities and onboard users directly. The flagship is bonuz: Lifestyle Wallet (bonuz.xyz).
* **bonuz Partner Dashboard** (SaaS / B2B2C) — Enables partners to run quests, issue rewards, and manage campaigns. On-chain and off-chain. Available at app.bonuz.market.
* **SDK** (SaaS / B2B) — Plug-in toolkit adding bonuz functionality to DApps and apps in hours: login, DNFTs, loyalty, social graph.
* **White-Label(s)** (Enterprise / B2B) — Fully branded bonuz app clones with custom feature sets. Brands may require fewer functionalities from the full technology stack.

bonuz enables endless applications and use cases — limited only by creativity, logic, and feasibility. The system is cross-device, cross-platform, and cross-language ready.

***

### How It All Connects

The ecosystem serves four main participant types:

**Users (Consumers)** download the bonuz: Lifestyle Wallet, onboard in seconds via email or social login, and receive a self-custodial smart account. They hold tokens, manage passes/vouchers/memberships as DNFTs, optionally activate their bonuz ID, and engage with brands through QR/NFC scanning at real-world venues or online campaigns.

**Brands & Partners** use the Brand Dashboard to create DNFT-based campaigns — loyalty programs, event passes, vouchers, Proof-of-Visit/Participation — using templates and rules. They distribute via QR, NFC, or links and monitor engagement with real-time analytics.

**Enterprise Partners** receive minimal custom white-label apps built by Bonuz Technology DMCC — brand-native, focused UX, running on bonuz protocols. These contribute users and data into the shared bonuz graph.

**Developers** integrate via the bonuz SDK, adding identity and engagement capabilities to their own apps. Every SDK integration contributes new users and graph growth into the Human Layer.

***

### Network Effects

Every participant strengthens the ecosystem. Users build identity and attestation history. Brand campaigns create engagement touchpoints. SDK integrations expand the graph. White-label apps bring new verticals. The **bonuz graph** — the shared network of identities, connections, attestations, and engagements — grows with each interaction, creating compounding value for everyone in the ecosystem.

***

### Quick Links

* [📱 bonuz: Lifestyle Wallet (Mobile App)](https://claude.ai/bonuz-ecosystem/mobile-app-social-wallet)
* [🤖 bonuz ID Protocol](https://claude.ai/bonuz-ecosystem/onchain-social-id-protocol)
* [😳 bonuz Engagement Protocol (DNFT)](https://claude.ai/bonuz-ecosystem/dynamic-nft-protocol)
* [🪄 Core Engagement Flow](https://claude.ai/bonuz-ecosystem/core-engagement-flow)
* [🛡️ Ecosystem / Wallet Security](https://claude.ai/bonuz-ecosystem/ecosystem-wallet-security)
* [🍕 Events & Communities](https://claude.ai/core-utilities-and-services/events-and-communities)
* [⭐ Merging the Real World with the Digital World](https://claude.ai/core-utilities-and-services/merging-the-real-world-with-the-digital-world)
* [🔌 bonuz SDK](https://claude.ai/bonuz-ecosystem/bonuz-sdk)
* [🚗 Product Roadmap](https://claude.ai/bonuz-ecosystem/product-roadmap)

<figure><img src="https://1020566636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9HVEtjJ1liHMMIp9PMfN%2Fuploads%2FvwX74g0AXnkPaLINvYnV%2FWhatsApp%20Image%202024-03-09%20at%2003.58.45_2c67586e.jpg?alt=media&#x26;token=5d3a3e3c-9b80-43c8-bead-8593ce0f98b9" alt=""><figcaption><p>bonuz Ecosystem Wallet &#x26; Functionality Logic Architechture - Version 3</p></figcaption></figure>

##

## Quick Links

{% content-ref url="../future-plans/creators-and-communities" %}
[creators-and-communities](https://whitepaper.bonuz.market/future-plans/creators-and-communities)
{% endcontent-ref %}

{% content-ref url="broken-reference" %}
[Broken link](https://whitepaper.bonuz.market/bonuz-ecosystem/broken-reference)
{% endcontent-ref %}

{% content-ref url="bonuz-engagement-protocol-dnft" %}
[bonuz-engagement-protocol-dnft](https://whitepaper.bonuz.market/bonuz-ecosystem/bonuz-engagement-protocol-dnft)
{% endcontent-ref %}

{% content-ref url="bonuz-lifestyle-wallet" %}
[bonuz-lifestyle-wallet](https://whitepaper.bonuz.market/bonuz-ecosystem/bonuz-lifestyle-wallet)
{% endcontent-ref %}

{% content-ref url="bonuz-id-protocol" %}
[bonuz-id-protocol](https://whitepaper.bonuz.market/bonuz-ecosystem/bonuz-id-protocol)
{% endcontent-ref %}

{% content-ref url="broken-reference" %}
[Broken link](https://whitepaper.bonuz.market/bonuz-ecosystem/broken-reference)
{% endcontent-ref %}

{% content-ref url="../engagement-use-cases/education-nft-certificates" %}
[education-nft-certificates](https://whitepaper.bonuz.market/engagement-use-cases/education-nft-certificates)
{% endcontent-ref %}

{% content-ref url="../future-plans/bonuz-promotions-and-discovery" %}
[bonuz-promotions-and-discovery](https://whitepaper.bonuz.market/future-plans/bonuz-promotions-and-discovery)
{% endcontent-ref %}

<br>


---

# Agent Instructions: 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:

```
GET https://whitepaper.bonuz.market/bonuz-ecosystem/ecosystem-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
