# Simulator Embed Guide

{% 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 %}

BASIS can publish a simulator to help users understand staking outcomes, booster effects, and reward flow under different assumptions.

## 1) Why a simulator matters

A simulator improves:

* user understanding
* support efficiency
* decision clarity
* trust through transparent modeling

It should reflect the live product structure accurately, including:

* same-token 1:1 swaps only
* real-time reward accumulation in the Staking Wallet
* full-position unstake behavior
* fixed pool lock-up constraints
* booster effects by duration

{% hint style="success" %}
A reliable simulator strengthens trust when it mirrors deterministic platform rules and state transitions exactly.
{% endhint %}

## 2) Recommended simulator inputs

Recommended inputs include:

* deposit asset: BTC / ETH / SOL / PAXG
* deposit amount
* selected staking token: stBTC / stETH / stSOL / stPAXG
* staking duration assumption
* booster selection:
  * 14D: +10%
  * 30D: +20%
  * 90D: +50%
  * 180D: +100% (2×)
* reward accumulation period
* unstake timing assumption after lock-up completion
* referral network contribution assumptions, if applicable

## 3) Recommended simulator outputs

Recommended outputs include:

* estimated stToken rewards
* projected Staking Wallet balance over time
* booster-adjusted reward comparison
* lock-up completion timeline
* full-position unstake outcome
* auto-credited claimable amount to the Staking Wallet as stToken
* fee impact summary:
  * Deposit: 0%
  * Swap: 0.01%
  * Withdrawal: 0.05%

## 4) Product rules to reflect in the simulator

| Rule                      | Requirement                                                   |
| ------------------------- | ------------------------------------------------------------- |
| Deposit assets            | BTC, ETH, SOL, PAXG only                                      |
| BTC deposit flow          | Copy your BASIS-assigned deposit address                      |
| ETH/SOL/PAXG deposit flow | Connect a Web3 wallet such as MetaMask                        |
| Swap behavior             | Same-token 1:1 only                                           |
| Supported pairs           | BTC→stBTC, ETH→stETH, SOL→stSOL, PAXG→stPAXG                  |
| USDT usage                | Internal accounting/display unit only                         |
| Minimum BTC deposit       | 0.0001 BTC                                                    |
| Rewards                   | Accumulate in real time as the same stToken                   |
| Wallet separation         | Funding Wallet for native assets, Staking Wallet for stTokens |
| Unstake behavior          | Entire staked position only                                   |
| Fixed pools               | Unstake only after lock-up period ends                        |
| Withdrawal timing         | BTC: 10 to 60 minutes, ETH/SOL/PAXG: 1-6min                   |

{% hint style="warning" %}
The simulator should not model unsupported actions such as USDT deposits, cross-token swaps, or partial unstake from fixed pools.
{% endhint %}

## 5) GitBook embed example

If the simulator is hosted at a public URL, GitBook can embed it:

```html
<iframe
  src="https://basis.pro/simulator"
  style="width: 100%; height: 900px; border: 0; border-radius: 8px;"
  title="BASIS Simulator"
></iframe>
```

## 6) Implementation guidance

Use the simulator to present deterministic product logic rather than speculative outcomes.

Recommended principles:

* keep calculations aligned with live platform rules
* update simulator logic in the same release as policy changes
* display assumptions clearly
* separate estimated reward projection from operational timing
* reflect state machine constraints and execution precision assumptions consistently

## 7) Trust note

BASIS emphasizes deterministic execution, mathematical constraint systems, and state machine risk controls.

Platform confidence should come from:

* transparent rule modeling
* precise balance transitions
* structural alpha capture logic
* research alignment with Base58 Labs
* infrastructure characteristics such as sub-50μs latency, 100K+ OPS, and proprietary routing systems in BHLE environments

***

Next: read Trinity FAQ.


---

# 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/simulator.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.