Vawlt Slawth
Enter

Verify

Don't trust us.
Check it.

The Slawth checks every swap against the official market price from Pyth, the price network most of Solana runs on, and refuses a swap that comes out too far under it. The code only accepts official Pyth prices, and there's no admin override for that. So the one thing that matters is which Pyth price each token uses. Here it is, read straight off the chain, with the time of the reading beside it.

  1. 01

    Only Pyth prices

    Each token has a Root: a small public account naming the one official Pyth price feed the Slawth uses for it. The code refuses anything that isn't a real Pyth feed.

  2. 02

    Posted 24 hours ahead

    A new feed is posted in public and sits as pending. We wait 24 hours before switching it on, so you can check it first. Every feed change and every program upgrade is public on chain.

  3. 03

    Don't like it? Walk.

    Revoke your delegation any time. Your tokens never leave your wallet, so there's nothing to withdraw and nothing to wait for.

Live from the chain

The Roots

Read at 27 Sept 2026, 23:16 UTC · v2 swaps: paused · v2 sign-ups: not open yet

The fence

Why a fake feed can't sneak in

The program itself refuses a price account unless all three are true. These rules bind everyone, the program's owner included:

  • 1It's owned by Pyth's receiver program.
  • 2It carries the feed ID written in the Root.
  • 3It sits at the exact address Pyth works out for that ID.

So the only choice a Root makes is which official Pyth feed to use. That's exactly what the checks above compare against Pyth's own public list, and the 24 hours wait gives you time to look.

What the timer doesn't stop

  • The 24 hours is a public waiting period we're choosing to keep, not a hard rule we can't skip. The program's owner key can switch a pending feed on early, or replace a live one, without waiting. It can still only pick an official Pyth feed (the fence above applies to everyone), and it has to do it in a public transaction.
  • You can see whether we kept our word: a Root's active stays NULL until it goes live. If it turns live before the time shown above, that's on chain for anyone to see.
  • The program can still be upgraded, so its rules could change in a later version. An upgrade is public too; the security page has the details.
  • Either way, your exit doesn't change: revoke the delegation and the Slawth can't touch anything.

Where the 24 hours comes from

The Registry

The waits aren't just a number on a web page. They're stored in the program's Registry account, and the program holds anyone but the owner key to them when switching a feed on.

New feed
24 hours
delay_new_secs = 86,400
Replacing a feed
72 hours
delay_replace_secs = 259,200

Registry account 6YJuVp…a2iwYn

No need to take this page's word either

Check it on Solscan yourself

  1. 1

    Open a Root

    Click any “Root account” link above. It opens that account on Solscan.

  2. 2

    Open the Data tab

    It sits next to Transactions on the account page.

  3. 3

    Hit “Decode with IDL”, then Decode

    You'll see active: NULL (not live yet) and pending with the feed_account it's waiting to switch on. Once a Root goes live, active holds the feed.

When did the clock start? The decoded pending_at is the moment the feed was proposed, in Unix seconds (paste it into any epoch converter). The Root's Transactions tab shows the same moment. Add 24 hours and that's the earliest anyone other than the owner key can switch it on.

Is the feed really Pyth's? Click the feed_account. Its Owner line reads Pyth Receiver Oracle Program (rec5EKMGg6MxZYaMdyBfgwp4d5rB9T1VQH5pJv5LtFJ). Solscan also names the SOL feed “Pythnet Custody Price (SOL) Account”, and the USDC and USDT feeds the same way.