Forges

Two of the four tax buckets — Dividend and Liquidity — don't pay out on their own. They collect quietly in the background and wait.

A Forge is the thing that spends them. It's a small contract you attach to a bucket that decides what "spending" means: pay it to holders, add it to the pool, burn it.

Without a Forge attached, a bucket just keeps accumulating. Nothing is lost, but nothing happens either. If you allocated tax to Dividend or Liquidity, attaching a Forge is the follow-through that makes that allocation mean something.

Forges are for Utility Tokens only. Quick Launch tokens have no tax buckets, so there's nothing to attach.

The templates

• Dividend (min balance + payout mode) — pays the bucket out to holders in proportion to how much they hold. The current, recommended version.
• Dividend v1 (legacy) — an earlier version of the same idea, kept for tokens already using it.
• Auto-liquidity — adds the bucket to your token's locked pool position, deepening liquidity so future trades move the price less.
• Auto-burn — destroys the bucket's balance, permanently reducing supply.

Attaching one

From your token's entry in My Launches, or from its page, pick a template for either bucket and confirm. Two transactions: one deploys your own copy of the template, one points the bucket at it.

From then on, that bucket's share of tax goes straight to the Forge instead of piling up.

Only the token's creator can attach a Forge, and only to their own token's buckets.

If you supply a custom address

You can point a bucket at any contract address instead of a template. Be careful with this:

• It permanently and irreversibly routes all future tax from that bucket to that address, from the moment you attach it.
• Arcantis does not check, audit, or vouch for a custom address in any way.
• It cannot be undone.

The one reassurance: it's scoped to your token alone. A bad custom address can affect your token's bucket and nothing else — no other token, and no other creator's holders.

Only use an address you fully control or fully trust.

Running one

Once attached, a Forge is permissionless to execute — anyone can trigger it. You, a holder, a bot, a stranger. Whoever triggers it pays the gas, and the Forge spends whatever has built up since the last run.

This is deliberate: it means payouts don't depend on the creator staying around and remembering. If a Dividend Forge has money in it, any holder who wants their share can simply trigger it themselves.

For a Dividend Forge, running it also opens up per-holder claims — if you're owed something, a Claim button appears on that token's Forges panel when your wallet is connected.