# Split Vault

The Split Vault distributes a token's tax revenue across multiple recipients based on pre-configured percentage shares. Instead of sending all market earnings to a single wallet, the tax is automatically split among up to 10 different addresses.

***

## How It Works

```
Tax Revenue (ETH) → Split Vault → Automatic distribution to recipients by share %
```

1. Every trade and transfer generates tax, and the market share of that tax flows into the Split Vault.
2. When ETH arrives, the Vault automatically attempts to distribute it to all configured recipients.
3. Each recipient receives their configured percentage of every distribution.

***

## Configuration

Split Vault recipients are configured during token creation and **cannot be changed afterward**.

* **Recipients**: 1 to 10 wallet addresses.
* **Shares**: Each recipient has a percentage share (in basis points). The total must equal exactly 100% (10,000 bps).

### Example

| Recipient        | Share |
| ---------------- | ----- |
| Creator wallet   | 60%   |
| Marketing wallet | 25%   |
| Community fund   | 15%   |

In this example, for every 1 ETH of tax revenue, the creator receives 0.6 ETH, the marketing wallet receives 0.25 ETH, and the community fund receives 0.15 ETH.

***

## Distribution Mechanism

### Automatic Distribution

When ETH enters the Vault, it automatically tries to distribute funds to all recipients in the same transaction. This works seamlessly for standard wallet addresses.

### Manual Claiming

If an automatic distribution fails for a specific recipient (for example, if the recipient is a contract with a complex `receive()` function), the funds are safely held in the Vault. Recipients can then manually claim their share at any time:

* **Dispatch** — triggers distribution to all recipients with unclaimed balances.
* **Claim** — a specific recipient withdraws their own accumulated balance.

No funds are lost if automatic distribution fails — they remain in the Vault until claimed.

***

## Key Characteristics

* **Multi-recipient** — supports up to 10 different wallet addresses, each with a configurable share.
* **Immutable configuration** — recipients and their shares are fixed at token creation and cannot be changed.
* **Best-effort auto-distribution** — funds are distributed automatically when received, with manual fallback if needed.
* **Native token only** — Split Vault currently supports native payment tokens (ETH) only.
* **Transparent tracking** — all distributions and claims are recorded on-chain via events.

***

## When to Use Split Vault

Split Vault is ideal for:

* Projects with multiple stakeholders who share the token's tax revenue.
* Tokens where the creator wants to allocate earnings to different wallets (e.g., operations, marketing, community treasury).
* Teams that want transparent, automated, and trustless revenue sharing without manual transfers.


---

# 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.base.meme/vaults/splitvault.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.