# Trinity Overview

{% hint style="info" %}
Operator and jurisdiction: BASIS is operated by BASIS DIGITAL INFRASTRUCTURE LTD, a Seychelles IBC (LEI: [254900IX2F2KCWNSSS64](https://lei.bloomberg.com/leis/view/254900IX2F2KCWNSSS64)).
{% endhint %}

Trinity is BASIS’s contribution-aligned referral network.

It ties rewards to measurable platform activity rather than static network structure:

* Sign-ups do not create rewards.
* Network depth alone does not create rewards.
* Rewards are generated when downstream participants produce eligible activity and a distribution event is recorded by the system.

## 1) The central design choice: activity-based distribution

Trinity calculates and allocates upstream rewards based on realized downstream activity recorded within the platform.

This creates two important properties:

* Alignment: reward flow follows actual platform usage and participation
* Auditability: each distribution is associated with a discrete accounting event and timestamp

{% hint style="success" %}
Trinity is designed as a contribution-based reward system, not a passive sign-up structure. Reward eligibility depends on real activity inside BASIS.
{% endhint %}

## 2) Nodes describe reach, not hierarchy

Trinity uses Node to describe reward reach scope, not a fixed hierarchy of people.

* Node A: activity from users you directly referred
* Node B: activity from the next connected scope
* Node C: activity from the expanded connected scope

Your assigned policy parameters determine which nodes are active for reward calculation.

## 3) Policy parameters define reach and limits

Trinity parameters control:

* how far rewards can flow through the referral network
* applicable percentage rates where defined
* the maximum reward scope or cap available under the active policy

This is not a status badge. It is a ruleset governing distribution logic.

## 4) Why Trinity exists inside BASIS

A structural alpha platform requires aligned incentives, durable participation, and strict control logic.

Trinity is designed to:

* reward contributors in proportion to the activity their referral network generates
* avoid pure sign-up driven mechanics
* preserve auditability through deterministic accounting events
* remain compatible with BASIS risk controls and system constraints

## 5) Platform context

Trinity operates within the broader BASIS infrastructure:

| Platform Property | Description                                                               |
| ----------------- | ------------------------------------------------------------------------- |
| Operator          | BASIS DIGITAL INFRASTRUCTURE LTD                                          |
| Jurisdiction      | Seychelles IBC                                                            |
| LEI               | 254900IX2F2KCWNSSS64                                                      |
| Research          | Base58 Labs research support                                              |
| Execution Model   | Deterministic execution with math-constrained state transitions           |
| Alpha Source      | Structural alpha capture and execution precision                          |
| Infrastructure    | BHLE with sub-50μs latency, 100K+ OPS, proprietary routing infrastructure |

{% hint style="info" %}
BASIS emphasizes deterministic execution, mathematical constraints, and state machine risk controls to support transparent reward accounting and platform-wide consistency.
{% endhint %}

***

Next: read Key Definitions.


---

# 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://docs.basis.pro/trinity-referral-and-vip/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.