Open one leaf of the crypto encyclopedia.
Ten shelves, one hundred entries, one leaf per open. You stack a leaf on the order slip, call open() for gas only, and the contract holds no BOT.
Stack a leafTen shelves, one hundred entries, one leaf per open. You stack a leaf on the order slip, call open() for gas only, and the contract holds no BOT.
Stack a leafMost crypto explanations arrive as a wall of text or a thread you scroll past. BlockWiki is built as a printed reference: ten shelves, ten questions each, one question per leaf. You pull the leaf you actually need instead of reading the whole book.
The chain records that a wallet opened a given leaf, and when. The answer is not stored in the contract. After the open, that same wallet signs one short line and the site returns the entry.
That keeps the record honest and cheap. open(uint256 entryId) is the only write, it takes an entryId from 1 to 100, and it costs gas only. The contract never holds BOT, so there is no balance to manage and no exit to wait for.
The leaf you stack is the entry. The wallet sends that id. Gas is the only charge, and nothing is left in the contract.
Find the question on its shelf and stack that one leaf on the order slip. The click is on the leaf itself.
open(entryId) costs gas only. The same wallet then signs one short line. A second open of that leaf reverts.
The site returns the entry to the wallet that opened it. openedAt is a public read if you want to check the time.
open() stores the time. It does not store the answer, and it does not take BOT.
That wallet can open each leaf only once.
Another wallet opens the same leaf for itself.
No product fee and no deposit.
The contract keeps when the open landed.
The answer stays off the contract.
The contract never holds BOT. Nothing to withdraw.
Someone who has just signed a first transaction and wants to know what a nonce is before the next one. Someone who keeps hearing “snapshot” and wants the airdrop shelf to explain claims and the theft patterns around them. This shelf does not run an airdrop, and no page here asks for a seed phrase.
A person teaching a study group who wants each question on its own card. A builder checking the vocabulary of pools or contracts before a review. The record is per wallet per leaf, so a reader can mark a shelf and leave the rest.
It records that the calling wallet opened a given entryId and stores the time. It emits Opened. It does not store the answer text, and it does not move any BOT.
Gas only. There is no BOT fee, no deposit, and no subscription. The contract never holds BOT, so there is nothing to withdraw at any point.
Not from the same wallet. A second open of the same leaf reverts. Another wallet can open that same leaf for itself, and both opens are recorded separately.
One hundred, ten shelves of ten: Keys, Gas, Blocks, Signatures, Tokens, Contracts, Pools, Using a dApp, Reading the chain, and Airdrops. entryId runs from 1 to 100.
Two public reads: COUNT for the total, and openedAt(who, entryId) for the time a specific wallet opened a specific leaf. Everything is on BOT Chain, chain id 677, native token BOT.
The signature proves the same wallet is asking for the entry, so the site returns the leaf to the reader who opened it. It is a plain message signature, not a transaction, and it never asks for a seed phrase.
The ten shelves and one hundred entries are written, and the site is up. open() is gas only. The contract is not on mainnet until gas arrives, so the site does not show an address yet.
The contract goes live and the official site carries the address. Until then, stacking a leaf still works, and reading waits.
Corrections to individual leaves are printed as revisions, with the changed entry noted rather than silently swapped.
A plain index of which shelves readers open most, taken only from the public openedAt reads.
Pick the question you have been carrying and open that one leaf. Your wallet marks it, the chain keeps the time, and the answer comes back to that wallet. No BOT is deposited, so there is nothing to withdraw.
Back to the index