Taking your seats
EVERY TRADE IS A TICKET.
Every swap creates activity inside the pool. That activity generates fees. Those fees become the revenue that powers the show's mechanism.
Nobody buys a seat at SHOWTIME. You trade, and the trade is the ticket — printed at the moment of the swap, torn at the door of the Big Top, and counted in the night's receipts.
THE HOOK RUNS THE SHOW.
THE HOOK
Uniswap V4 Hooks allow programmable logic to interact with pool activity. A Hook is a contract the pool calls at defined moments in its lifecycle — so protocol logic can run as part of the pool's own execution rather than alongside it.
The Ringmaster does not perform. He decides what happens next, and when — and the ring obeys.
For SHOWTIME, the Hook is the mechanism controlling the performance: the piece of the system that sits between a swap and everything that follows it.
PROGRAMMABLE BY DESIGN.
Uniswap V4 Hooks provide a programmable execution layer around pool activity. Where V3 gave every pool the same fixed behaviour, V4 lets a pool nominate a contract that the PoolManager calls at defined points in its lifecycle.
SHOWTIME uses this programmable layer to implement its fee and token mechanics. What that logic does, precisely, is a property of the deployed Hook — which is why the panel below reads the contract's own ABI rather than describing behaviour from a brochure.
No Hook ABI has been installed, so no callbacks, functions, events or permissions can be shown. Paste the deployed artifact into src/lib/contracts/hookAbi.ts and this panel will list exactly what the contract implements — and nothing else.
Address permission bits — 0x63A172…e24044
Uniswap V4 encodes a hook's permissions in the least significant bits of its deployed address. The flags above are decoded from NEXT_PUBLIC_HOOK_ADDRESS using the protocol's own bit layout — they describe which callbacks the PoolManager is permitted to invoke, not what SHOWTIME's logic does inside them.
WELCOME TO THE BIG TOP.
The pool is where the show happens. Every trade enters the Big Top. The Hook controls the programmable performance.
Liquidity is the canvas. Trades are the audience arriving. Fees are the receipts at the end of the night. All of it happens under one roof, in one contract, on Ethereum Mainnet.
The diagram is a metaphor, not a topology: it shows what the pool contains, not the call graph. The call graph is the ABI, in Act 03.
Uniswap V4 Hooks allow protocols to add programmable logic around pool activity — before and after swaps, before and after liquidity changes — inside the pool's own execution.
SHOWTIME uses the Hook as its Ringmaster: the single place where the protocol decides what a trade means beyond the trade itself.
THE HOUSE COUNTS EVERY TICKET.
Trading against the pool produces fees. Those fees are the night's takings — the revenue that the protocol's configured mechanism then acts upon.
Where that revenue goes is decided by the deployed contract, not by this page. The routing described below is read from configuration; if it has not been documented, the site says so rather than guessing.
0.1
EVERY SHOW HAS A FINAL ACT.
Every show has a final act. The protocol's configured mechanism directs revenue toward buyback and burn according to the deployed contract implementation.
Tokens that reach a burn address leave circulation permanently. What is counted below is exactly that: balances held at the standard burn sinks, and transfers into them — observable facts, not a description of intent.
0.1
THE SHOW CONTINUES.
SHOW OVER?
NEVER.
THE SHOW NEVER STOPS.
NO EVENTS INDEXED
Connect a wallet to see your $SHOWTIME balance, what you have received, and your last activity. SHOWTIME reads your wallet — it never asks for a signature to display anything.
DON'T TAKE THE HOUSE'S WORD FOR IT.
ABI status
The token reads use the EIP-20 standard interface, which is safe to assume of any ERC-20. Nothing beyond it is assumed. Hook behaviour is only ever described from an installed artifact.
One or more addresses are unset. Populate NEXT_PUBLIC_TOKEN_ADDRESS, NEXT_PUBLIC_HOOK_ADDRESS and NEXT_PUBLIC_POOL_MANAGER_ADDRESS in .env.local. All three must be Ethereum Mainnet addresses.