> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/white-label/w3caas-web3-casino-as-a-service/built-on-chain.md).

# Built On-Chain

W3CaaS runs natively on PlayBlock, Playnance's purpose-built, gasless blockchain — not a Web2 platform with a token added on top.

***

{% columns %}
{% column %}
{% hint style="info" icon="hive" %}

#### Playblock

The blockchain infrastructure layer powering transaction execution across the Playnance ecosystem.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="landmark-dome" %}

#### Architecture

Modular, scalable architecture designed for high-throughput iGaming operations.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="shield-exclamation" %}

#### Security

Smart contract-based execution with transparent, immutable, and auditable transaction flows.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

{% columns %}
{% column %}
{% hint style="success" icon="money-bills" %}
**On-Chain Payment**

Wallet-native payments processed on-chain through smart contracts.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="success" icon="heart-circle-check" %}
**On-Chain Transparency**

Every transaction is recorded on-chain and remains visible and verifiable.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="success" icon="list-check" %}
**On-Chain Settlement**

Settlement is automatic, immediate, and contract-enforced.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

{% hint style="warning" icon="check" %}
**On-chain by design** — every bet, payout, and revenue split runs through audited smart contracts.
{% endhint %}

{% hint style="warning" icon="check" %}
**Non-custodial** — players keep control of funds and operators avoid custody risk.
{% endhint %}

{% hint style="warning" icon="check" %}
**Provably fair** — RNG, odds, and outcomes stay verifiable on-chain in real time.
{% endhint %}

{% hint style="warning" icon="check" %}
**Gasless and instant** — PlayBlock processes 1M+ daily transactions with 0.3-second settlement.
{% endhint %}

{% hint style="warning" icon="check" %}
**Audited and aligned** — CertiK audited and designed for MiCA-aligned operations.
{% endhint %}

{% hint style="warning" icon="check" %}
**Global scale** — multi-currency, multi-language, and active across 180+ countries.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.playnance.com/white-label/w3caas-web3-casino-as-a-service/built-on-chain.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.