TIGERLAYER
Shido Network
Access PIN
Roadmap
one free hour, once per device
What this is

Tiger Layer

Tiger Layer is on-chain intelligence for the Shido network. Mostly that means reading the chain. Twice, it means building on it. Everything here comes from a full Shido node we run ourselves, with the transaction index switched on. That is what makes deep wallet history and real contract analysis possible, and it is also why there is a PIN on the door. Seven tools and an association set provider sit on top of it, and two of the tools, Vanish and Claw, are protocols of our own, still on testnet.

Alongside Vanish we run an association set provider. It does three things, all from public ledger data. It screens deposits into Vanish for a clean, traceable origin and keeps that set — a set that is empty for now, because Vanish is still on testnet, the provider watches mainnet, and nothing yet checks it at withdrawal. It screens what arrives on Shido — every bridge payout and every IBC receipt — with the same rules, and that part runs in earnest, every half hour, against everything the chain has received. And it records what tokens and the people behind them have actually done on the chain — liquidity pulled from a traded pool, supply minted after launch, a pause thrown — each as an observation with the transaction that proves it, never as a verdict. Our own index and node for Shido, Etherscan's for Ethereum and BSC, published lists such as OFAC. No KYC, no private lists, nothing you have to take our word for — the rules are written down, and the result can be rebuilt from the chain and checked against ours. It sits behind the PIN with everything else, as its own tab beside Vanish: the association set, the inflows, the behaviour. None of it is tied to Vanish: anything built on Shido that needs to know whether funds have a traceable origin, or whether a wallet has emptied a pool before, can be given the same data.

Roadmap

Where this goes next.

No dates on purpose. A phase moves when the work is actually done, and anything that touches real money waits for outside review first.

Shippedrunning now
  • Our own node, our own index. A full Shido node with the transaction index switched on, and our own index built on top of it.
  • A validator, not just an observer. We run a Shido validator as well as the indexing node, so the chain this site watches is one we help secure. It appears in the Validators tab on the same terms as everybody else's.
  • Prowl. Blocks and transactions as they land, staking and unstaking as it happens, rewards claimed, and every buy and sell going through the DEX — each row traced back to the transaction that made it.
  • Validators. Who is securing the chain, how much is bonded to each, who is jailed, and how stake has been moving between them — plotted on a world map by where the nodes appear to sit.
  • Trace and Visualizer. A wallet's full history — transfers, swaps, staking, contracts touched — filtered to any date range, with financial-year presets for when you need one year cut cleanly, and the filtered result exports as CSV. The same history also draws as a graph of counterparties and the paths funds actually took.
  • Scent. Tokens, pools and holders.
  • An association set provider for Shido. Every thirty minutes, against our own mainnet node, it traces a deposit's lineage: where the funds came from, whether anything in that lineage touches a sanctions, mixer or exploit label, whether the origin is traceable, which exchange it came out of. It writes two Poseidon Merkle roots, an append-only history of them, and a per-deposit decision log giving the reason for every call, on its own page. Vanish is still on testnet, so the set it keeps today holds no deposits; the same rules already run on every arrival, below.
  • What arrives on Shido, screened. Every native SHIDO payout from the bridge and every inbound IBC packet the chain has accepted — from Osmosis, Noble and Axelar — read from our own index, our own record of every packet since the channels opened, and our own node, and rescreened every half hour as new ones land. Each recipient goes through the same screen as a Vanish deposit: its funding lineage on Shido, the same address on Ethereum and BSC, the published lists; for IBC the origin sender is checked against the lists too. External screening is rate-limited, so the inflows page also says what is still waiting rather than counting it as clear.
  • Behaviour, with the evidence attached. Three things Shido's own history can show a token or the people behind it doing: most of a traded pool's paired value taken out in one transaction, supply minted by the deployer after the token had a market, a pause thrown. Each is recorded as an observation with the transaction that proves it — the pool's balance before and after, who acted, how long after launch — never as a verdict. Only an insider taking a pool's value is listed; a liquidity provider leaving, an unvalued pair, or a wallet we know by name is recorded and not listed, and a project's explanation is printed beside its row. The wallets listed feed the inflow screen, so an arrival funded by one of them shows why, on the behaviour page.
  • Public ledgers only, on every chain it reads. Shido lineage and events come from our own index and our own node. Ethereum and BSC screening comes from Etherscan's, because we cannot index those chains ourselves — sanctions-list membership, transactions with sanctioned addresses, mixer and hack-list interaction. The lists themselves are public and auto-refreshed: OFAC digital-currency addresses, the Tornado set, our bot registry. No KYC records, no addresses you arrived from, no private lists — every decision rests on facts anyone can check, which is what lets all of it be rebuilt from public data and the published rules instead of taken on trust.
  • The association set provider inside the tools. Its findings sit where people already look, not only on their own pages. A Trace lookup shows whether an address is listed, has been screened as an arrival, or is clear — and the transaction behind it. The Visualizer rings a listed wallet so it stands out in a graph without anyone reading a table. And the provider has its own tab beside Vanish, with the association set, the inflows and the behaviour.
  • Access without an account. One free hour per device on the common PIN. No form, no email list, no wallet connection to look around.
Nowbeing worked on
  • Fewer, larger reads. Transaction detail now arrives in batches — four hundred transactions in five requests instead of four hundred — with retries on transient failures and failover to a second node when one is unhealthy.
  • Faster, and better on a phone. The site was built at a desk; more of its readers arrive on a phone. Pages are being trimmed to load quicker and laid out to read on a small screen — no sideways scrolling, controls that fit under a thumb, text that can be read on the move — and the common paths through the tools and the two apps made shorter. Checked on real phones, not only on wide monitors.
  • Checks that run themselves. The figures on screen are verified against the node on the box — staking totals, APR, counts, block times.
Nextqueued
  • Claw, hardened then deployed. Tighten the testnet venues, put the contracts in front of outside eyes, then mainnet. Sealed orders, one clearing price per batch.
  • Making the association set binding. The screening engine is complete and running, but nothing consumes what it produces: the root is a file rather than an on-chain value, and Vanish's circuit has no membership proof, so a withdrawal today ignores the set entirely. Posting the root on chain and proving membership at withdrawal is what turns a recorded opinion into a rule. And because the provider watches mainnet while Vanish is still on testnet, the set it keeps today is empty — there are no deposits on the chain it reads. The screening itself is no longer untested, though: the same rules run every half hour against everything that arrives on Shido.
  • More chains, more sources behind the labels. Ethereum and BSC are screened today. The Cosmos chains that send packets into Shido — Osmosis, Noble, Axelar — are not: a packet's sender is checked against the lists, but its own history on its chain is not examined, and the page says so rather than implying wider coverage than there is. The same applies to what feeds the labels — the exploit list is thin, and a professional attribution source belongs in place before any of this runs against real money. A lineage rule is only ever as good as the ledgers and lists behind it.
  • More behaviour, and being told. A token only its insiders ever manage to sell, one funder behind several emptied pools — the same shape as the three rules that run today, each an observation with its transaction. More flags can be added on request: if there is a pattern you want watched, say so. And a message when a new observation or a flagged arrival lands, instead of a page waiting to be read.
  • Knowing more of the chain by name. Lineage only means something when the ends of it are recognised: which addresses are exchanges, which are bridges, which are bots, which are contracts rather than people. That registry is small today and grows by hand — every address identified turns a deposit from unknown into classified — and keeping it current as the chain moves matters as much as extending it. This is the part that never finishes.
  • Vanish, hardened then deployed. Deposit a fixed amount, withdraw to a fresh address, prove membership without revealing which deposit was yours. Testnet hardening and outside review first.
  • A route for a disagreement. Every page offers review to anyone who thinks a call about their funds or their project is wrong — a message with the transaction hash — and an explanation given is printed beside the row it explains. What is still missing is the record of what changed and why, so a reversed call is as visible as the call was.
  • Trace and the Visualizer, pushed further. The history is already there; the ways to read it are not finished. More of a wallet's story in one place: better clustering of counterparties, richer contract decoding so a row says what actually happened rather than which method was called, more ways to slice a wallet's activity, and a graph that stays readable when a wallet has thousands of edges — the paths worth following, the counterparties that actually matter — with exports that keep up with all of it. These two get the most use, so they get the most work.
  • Watchlists and alerts. Follow an address, a validator or a token and be told when it moves, instead of sitting on Prowl waiting for it.
  • Access beyond the free hour. Longer access for people who use the site properly, and for project owners who need to keep an eye on their own project. How that is paid for — including whether a token makes sense for it — is still being worked out, and it will land wherever it suits Shido users and Tiger Layer both.
Laterwanted, not scheduled
  • Risk in Scent, with the evidence attached. Contract capability scoring that shows the reason for the flag, not a number you are asked to trust.
  • More of what the node already sees. Governance, IBC flow and the rest of the chain the site does not surface yet.
  • Whatever earns its place. The list above is what we can see from here. After it the job is the same one — keep building the things that make Tiger Layer worth opening every day, and let what people ask for decide the order.

If one of these matters more to you than the rest, say so — the order is not fixed.