Notes on time, ownership, and onchain culture
A leaderboard where rank is the bid and nothing else, and which publishes the clicks each paid rank received. Two captures three minutes apart show the top two positions differing twelvefold in lifetime clicks but only 1.5x in live click rate. What the price buys, and what no price can.
Token 1 has a name, a clock time and two traits, but its image field is empty. A note on the difference between owning a coordinate and owning its picture, without pretending the omission was intentional.
The genesis block says 18:15:05 UTC on 3 January 2009. The public release email came five days later, and block one later still. Three surviving records make the idea of Bitcoin's exact birth second less tidy, and more interesting.
Every post-Merge Ethereum block is stamped :11, :23, :35, :47 or :59. That leaves 7,200 of the day's 86,400 seconds reachable, and which 7,200 was settled by a miner's clock in November 2020.
Base genesis is stamped 00:35:47 UTC, the 2,147th second of the day. The block holds no transactions and 32 bytes of text: an old video game mistranslation with its last word deliberately flipped.
Every Base block timestamp equals genesis plus two seconds per block, and genesis is an odd number. Checked against 200 random blocks: no exceptions. Half the seconds of the day have never carried a block on the chain this collection lives on.
tokenURI returns metadata the contract builds onchain and hands back as a data URL. Decoded from the real first mint: two traits, a clock reading, an empty image field, and a link that is not the one you set.
referrerEarnings and referrerCount hold your tally, and anyone can read them with no wallet. A walkthrough, plus the honest gap between the referrer written into a mint's event log and the credit the contract actually keeps.
One call to getSecondData returns the owner directly. The standard ERC-721 path gets there in two hops: secondToTokenId, then ownerOf. Both read the same state, so they should always agree, checked here against the real first mint.
The second you own never moves, but the link it holds can change for as long as you hold the token. A note on treating a fixed point in time as a page you curate over years, not a purchase you shelve.
The embeddable widget is a sealed iframe that reads one second off Base and draws it. A look at its two modes, the single view call it makes, the referral address it carries, and why it never touches a wallet.
Two collector appetites pull in opposite directions: one wants the earliest token id, the other wants a second that already means something on the clock. Why they rarely land on the same token, and why the contract grades neither.
Every mint carries two numbers: the second you choose (0 to 86,399) and the ERC-721 token id the contract assigns in mint order. The first mint proves they differ. Second 333 holds token 1.
Some clock times are easy to hold in the head: 11:11:11, 12:34:56, high noon. A note on why a patterned second is memorable, and why the contract still sees just another numbered token with no extra trait, rarity class, or promised value.
The monthly jackpot has no host. Once the timer runs out, the first connected wallet can run the draw. A note on holding a button nobody is assigned to press, and why the person who clicks is usually not the one who wins.
Checking one second is instant; rebuilding the whole leaderboard is slow, on purpose. getSecondData versus the SecondMinted event scan, and why one read is cheap while the full map is expensive.
The About page says 86,400. Check it without trusting the page: two read-only calls return the fixed cap and the live minted count. The walkthrough now uses Base's public RPC because this address has no generated read form on Basescan.
Sixty seconds in a row is a minute, and also sixty separate tokens that happen to sit next to each other. A note on runs versus scatters, where a set is real, and where it is only a story you keep about your own seconds.
Ten percent, stored as basis points and readable off the contract. What a creator royalty covers, why a plain transfer skips it while a sale honors it, and where the honest limits are.
The mint button takes one second at a time, but the contract can do more. A read of mintBatch in the ABI: arrays of seconds and URLs, one referrer, one atomic transaction, and the caveats that stay whether you claim one second or ten.
No server, no stored table of owners. The counter, leaderboard, timeline, and Your Seconds are all read live from Base on every visit. How a stateless front end reads a stateful chain, and what happens when the RPC is slow.
A public balance, a 30-day timer, and a draw any connected wallet can trigger. A read of the getJackpotInfo view, the permissionless drawJackpot call, and the JackpotPaid event, with honest notes on what the front-end code does not reveal.
No cookie, no tracking pixel. A referral here is a wallet address passed into the mint call and written to the ledger. A look at the ?ref= link, the referrer field, the 10% share, and what the contract keeps track of.
The live clock follows your local time, while the token stores only a numbered position in the day. A note on time zones, shared coordinates, and the context a second cannot keep for you.
A second is two things bolted together: a token that does not move, and a URL you can rewrite any time. They have different lifespans. A primer on link rot, the editable pointer, and why the site only opens plain http(s) links.
If a second is really yours, you should be able to see it without trusting our website. A no-signature walkthrough of reading ownership and the stored URL through Base's public RPC, including a July 26 correction about the contract's unverified explorer status.
The set inherits its 86,400 slots from the day, but clock order is not mint order. Why second 1 can be claimed after second 50,000, and where the word "rare" quietly misleads.
A second on this site is not a picture of a clock. It is an integer, a stored link, and a line in a ledger you do not control. Here is what each of those parts really means.