01 / SOURCEOne mint. One finalized observation.
Needle reads the mint account through a Solana mainnet RPC and checks its program, type, initialization and slot. It records mint and freeze authorities, raw supply, decimals and parsed Token-2022 extensions. No signing and no funds move.
Remote metadata, token accounts, liquidity, holders, program upgrades and off-chain claims are outside this reading. Issuer-declared names are not identity verification. Revoked base roles alone do not establish that a token is safe.
02 / COMPARISONChanges have context.
Splice compares the normalized fields with your previous stored reading. Supply changes and permission changes are separate. A comparison covers two observations; it cannot reconstruct changes between them or identify the transaction that caused a difference.
Unknown extensions remain in the raw evidence and are explicitly marked uninterpreted. Transfer hooks and other programs are not audited by SPOOL.
03 / EVIDENCEA receipt you can take with you.
Seal saves the raw account response, finalized slot, observation time and a SHA-256 checksum. JSON exports include those fields and the comparison. The checksum detects file modification; it is not an independent signature, proof of consensus or audit.
Evidence depends on the configured RPC. You can cross-check the mint on Solana Explorer and independently query an archival RPC for historical evidence.
04 / AUTOMATIONThe archive works after you leave.
Enable “Observe daily” on a saved mint. A server-side Vercel cron runs once a day in the 01:45–02:44 UTC window. It reads up to 40 distinct observed mints across the service. When capacity is full, additional observation requests are declined; manual reads remain available.
A scheduled run may be delayed or fail if the RPC or storage is unavailable. Failed runs preserve the previous reading. A manual re-read lets you recover immediately. Scheduled configuration and an observed automatic execution are shown separately on your shelf.
05 / THE SPOOL TOKENThe tool comes first.
The archive is usable without a token. A future SPOOL token could support the shared cost of observations and storage, if a transparent funding mechanism is introduced. Token payments, fee routing, governance and rewards are not active features. There are no holder return claims.
Until the project owner supplies a dedicated launch identity or an explicit contract address, the site displays “CA: soon”. A configured address is labeled separately from a launch verified on-chain.
PRIMARY REFERENCESSolana: getMultipleAccounts ↗Solana: Token extensions ↗Vercel: cron timing ↗