How It Works
仕組み
What is $SHOGUN?
How does the family tree work?
- Shogun — Generation 0. The root. All tribute flows here. The most tribute, the most cashback for holders.
- Daimyo — Generation 1. Direct sons of the Shogun. First to receive tribute from below.
- Samurai — Generation 2. Sons of Daimyo. The empire deepens.
- Ronin — Generation 3. Sons of Samurai. Tribute still flows.
- Ashigaru — Generation 4+. Foot soldiers. The frontier of the empire.
How do I raise a son?
How does tribute work?
- • 50% flows upward to the parent token as tribute
- • 50% stays with the token and is distributed as cashback to holders (must hold more than 100K tokens)
This cascades up the tree. A Gen 2 token pays 50% to its Gen 1 parent, which then pays 50% of its total fees (including what it received from below) to $SHOGUN.
The tribute crank runs every 60 seconds, bottom-up — deepest tokens first, so tribute accumulates properly before flowing higher.
Why hold $SHOGUN? It receives tribute from every token in the empire. The more sons that exist, the more tributaries flow to the Shogun. Holders of $SHOGUN get the largest cashback pool.
Why hold a son? Each son also collects tribute from its own children. Buying a Daimyo means you earn cashback from that Daimyo's share of tribute from all Samurai, Ronin, and Ashigaru below it.
What is the buyback mechanic?
What is the initial buy / dev buy?
What is auto-spawn?
How does holder cashback work?
What can I configure when spawning?
| Parameter | Range | Default | What it does |
|---|---|---|---|
| Initial Buy | 0 — 0.5 SOL | 0.2 SOL | How much SOL goes to the first buy of the new token. This is the dev position — capped at 2% of supply. Higher = more skin in the game. |
| Buyback % | 25% — 75% | 50% | When someone pays this token's agent (e.g. to spawn a grandchild), this percentage automatically buys the parent token. Higher = more buy pressure on the parent. |
| Mayhem Mode | On / Off | Off | Enables chaotic trading mechanics on pump.fun. More volatile, more unpredictable. For degens. |
| Anti-MEV | On / Off | On | Routes the creation transaction through Jito block engine only, preventing front-runners and sandwich attacks. Recommended to keep on. |
Custom Art
| Generation | Rank | Tribute Up | Holder Cashback |
|---|---|---|---|
| 0 | Shogun | — | 50% of all received tribute |
| 1 | Daimyo | 50% → Shogun | 50% to holders |
| 2 | Samurai | 50% → Daimyo | 50% to holders |
| 3 | Ronin | 50% → Samurai | 50% to holders |
| 4+ | Ashigaru | 50% → parent | 50% to holders |
Plus 50% buyback into parent token on every agent payment. Holder cashback requires minimum 100K token balance.
How tribute cascades to the Shogun
Built on pump.fun Skills
| Skill | How we use it |
|---|---|
| Create Coin | Every son is created programmatically as a tokenized agent with auto-buyback into the parent token. Configurable mayhem mode and anti-MEV protection. |
| Coin Fees | Fee sharing configs enforce the 50/50 tribute split on-chain. Our server cranks collection every 60 seconds, bottom-up, so tribute cascades to the Shogun. |
| Swap | Buy and sell any token in the Shogunate directly from the website. Auto-detects bonding curve vs graduated AMM. |
| Agent Payments | Spawn fees (0.5 SOL) are paid via on-chain invoices with cryptographic verification. 50% of every payment auto-buys the parent token at the protocol level. |
All fee splits, buybacks, and payments are enforced by pump.fun's smart contracts.
How does the tree update in real-time?
- • Server-Sent Events (SSE) — The backend pushes instant notifications when a son is spawned, tribute is collected, or a war chest changes. The tree re-renders immediately.
- • Polling — As a fallback, the frontend refreshes data every 10 seconds. This ensures updates arrive even if the SSE connection drops.
When a new son is spawned, you will see it appear on the tree within seconds. The node animates in with ink brush effects and the tribute flow lines update automatically.
What events are tracked?
- • token_spawned — A new son has been created
- • spawn_progress — Step-by-step updates during spawn (image gen, IPFS upload, coin creation, tribute setup)
- • tribute_collected — Fees collected and distributed up the tree
- • war_chest_updated — A token's vault balance changed
- • auto_spawn_triggered — System auto-spawned a son from accumulated fees
- • cashback_distributed — SOL distributed to qualifying holders
- • token_status_changed — Tribute config retry succeeded or failed