LUSCA | $INK (@lusca_ai)

One rollup, two chains. Code Atlas places every kept contract by the function and event names it shares with the others. Open RollupAdminLogic on Arbitrum (0xf9725312bd91ccfa3ad797e78a8a10b6d692fcd6): 73 functions, 14 events, Sourcify verified. Its closest relative is a second Arbitrum deployment, 0x2733fc1c97f6562466e9b29d64bcc6dc833cc88d: 100%, all 87 names identical. Next is the Ethereum copy, 0x0ae4dd666748bf0f6db5c149eab1d8ad27820a6a: 98%, 85 shared names, 71 functions. The two names that separate them exist on the Arbitrum side only: anyTrustFastConfirmer and setAnyTrustFastConfirmer. Same admin surface on two chains, two names apart, found by comparing what the agents had already stored. No source diff, no extra network call.

One keypair, one upgrade. 330 of the 657 upgradeable Solana programs LUSCA keeps have a single keypair as their upgrade authority. 327 have a program-derived address. 108 more are immutable. 765 programs in total. How it is read: the upgrade authority stored from each program's on-chain account (read through @helius) is checked against the ed25519 curve. A point on the curve is a keypair, so one private key can sign an upgrade. An address off the curve is program-derived: it has no private key and only the program that owns it can sign. No extra RPC call, no project labels. Example: OKX DEX Router, proVF4pMXVaYqmy4NjniPh4pqKNfMmsihgd4wdkCX3u. Upgrade authority CjoV5B96reuCfPh2rRK11G1QptG97jZdyZArTn3EN1Mj, a single keypair. A single keypair is a fact about custody, not a verdict. The control map states it for every kept program, next to its custody chain.

This is not a mockup, and it's not a render made for marketing. What you're watching is LUSCA's live interface, showing our chain agents reading real programs and contracts as it happens. Nobody picks the addresses. The agents find them on their own, read them on-chain, and decide what's worth keeping. Every call on screen is a real call. Solana reads run through @helius, and each field appears the moment its call returns: upgrade authority, proxy and implementation, instructions, verified source. Then the verdict: kept for SEPIA-1's training data, or rejected with the reason. Why it matters: AI training data is usually a black box. You're told what a model learned from and you take it on trust. Here you can watch the data being collected and checked, live, one read at a time. Our biggest update so far. More than 15,000 reads and counting.