
Chainlink VRF: A Proof Needs an Answering Service
A contract can retain its history while a service stops answering. What Chainlink’s two November VRF shutdown dates mean.
Read story →Every coin has a story. Explore the human dramas, multi-million dollar heists, and visionary breakthroughs behind Web3.
Previously published articles, ordered by their latest recorded revision.
Choose a topic, then follow the stories behind it.
Showing 18 of 163 stories.

A contract can retain its history while a service stops answering. What Chainlink’s two November VRF shutdown dates mean.
Read story →
One Send button can lead to a crypto wallet or a bank account. The asset, custodian and receiving path explain the difference.
Read story →
The phone recorded several iterations. Neither attempt left a proof. What ten Android devices reveal about reading a ZK benchmark.
Read story →
A borrowed game item can return at the deadline. An ephemeral token can disappear instead. Fort Canning gives those endings different rules.
Read story →
A name can stop resolving while nobody else can register it. ENSv2’s shorter grace period makes that distinction visible.
Read story →
Testnet records show the Protocol 30 boundary. Ledger readers still need the new format, and Mainnet remains a separate vote.
Read story →
Stopping reads or marking a peer as paused does not automatically stop every route that adds to its queue. Two disclosures show why the distinction matters.
Read story →
An expired delivery transaction need not cancel the approval inside it. Solana’s nonce plan makes that distinction central to offline signing.
Read story →
An old receipt says a digest was once recorded. A live account slot answers a different question: does this account still attest to it?
Read story →
Solidity can run behind an access gate. Compatible contract code does not mean the same ledger, signers or approval rules as public Ethereum.
Read story →
Proposal 346 now has recorded approval. Token launch and the move of the computing marketplace still require different evidence.
Read story →
Different token pairs can be doorways into the same pool. A v4 label alone does not tell the whole route.
Read story →
An empty queue response can mean you are looking at the wrong pool. Cronos v1.8 makes that distinction matter.
Read story →
The data travels to validator servers. A much smaller signed record goes on-chain. Fibre separates those two jobs.
Read story →
Two RPC services returned the same handoff certificate. The shared history is visible; the promised speed needs separate measurement.
Read story →
The same disk can receive a different weight. The same block reward can fund a different job. Solstice separates the two.
Read story →
The transfer was already on-chain. The new question is who computes it—and which rules every validator must reproduce.
Read story →
What if a wallet could reject the result of a signed transaction? Inside a proposal with a very precise undo boundary.
Read story →