Concept Mining5 source only Source e0617449

Contract graphLink to this section

TL;DRLink to this section

Core authenticates work but does not mint tokens or allocate rewards.
Mining holds funded SQK and accounts for rewards on wallet-held NFT positions.
Token and NFT are immutable direct deployments; Core and Mining retain separate timelock-owned upgrade administration.

What it isLink to this section

The contract graph is the set of connected contracts that record work, manage Miner NFTs, and distribute SQK rewards.
Core records work, Mining calculates rewards, Token tracks SQK, and the NFT tracks ownership.
A separate renderer generates NFT images.
There is no Controller contract, staking escrow, transfer hook or public multiplier setter.

Component	Binding and responsibility
`Core` proxy	Canonical work ledger; fixed stream, round clock, difficulty and work cap
`Core` implementation	Version 2 logic; separate `Core` ERC-7201 namespace
`Core` `ProxyAdmin`	Transparent upgrade admin owned by the approved Operator `Timelock`
`Mining` proxy	Funding policy, reward index, positions, pending activations and custody
`Mining` implementation	Version 5 logic in `squeek.mining.storage.v5`
`Mining` `ProxyAdmin`	Actual transparent admin owned by `Mining`'s configured governance timelock
`Token`	Fixed `Mining` mint caller and recipient; lifetime cap; ordinary ERC-20 balances
`NFT`	Fixed `Core`, `Mining`, Guardian snapshot, governance, economic recipient, renderer and page
`Renderer` and validator	Stateless DotGrid rendering and strict page validation
Page root and chunks	Immutable code-resident visual data

How it worksLink to this section

The NFT registers each newly minted Miner with Mining.
Anyone can submit new rounds to Core with a valid Reporter signature.
Anyone can run a Mining checkpoint to calculate rewards from settled rounds.
Token mints the requested SQK to Mining within its lifetime supply cap.
Mining allocates rewards to eligible NFTs according to their active mining power.
The current NFT owner claims already-funded rewards to their wallet.

Contract connectionsLink to this section

The system map shows how these contracts connect to measurements, settlement and public data. The table below lists the checks used to verify their connections.

NFT registration finishes before a receiving smart contract can act on the new NFT. Transfers need no Mining callback because unclaimed rewards stay with the NFT and become claimable by its new owner.

Reciprocal identity checksLink to this section

Check	Required relationship
`Mining` `configuration()`	`Core`, `Token`, collection and governance match the approved graph
`Token` `mining()`	Equals the `Mining` proxy, not its implementation
`NFT` `mining()` and `sqkCore()`	Equal the `Mining` and `Core` proxies
`Mining` `deploymentIdentity()`	Actual implementation and immutable transparent dispatch admin match expectations
`ProxyAdmin` `owner()`	Equals the approved timelock for that proxy
Implementation metadata	Code address, version and layout digest match the approved source/runtime identity
`NFT` visual identities	`Renderer`, validator, page root, page hash, asset-set hash and seed are authenticated

Rules and boundariesLink to this section

Bootstrap requires a fresh paused Core with zero work and unused Mining, Token and NFT contracts with zero supply. It uses up Mining's one-time bootstrap permission.
Core pause stops settlement and Mining checkpoints. It does not revoke NFT ownership, stop Token transfers or disable claims from funded custody.
NFT Guardian pause affects mint issuance, not ordinary NFT transfers, metadata or proceeds sweep.
Token cannot change its Mining binding, cap or authority and has no owner, proxy, burn or transfer pause.
Mining can be upgraded. A malicious upgrade could spend held SQK incorrectly or mint all remaining supply without work; Token only enforces the fixed mint caller, recipient and lifetime cap.
Core and Mining have separate upgrade controls. An event or metadata getter alone does not prove new code is safe.
Donations increase Mining's actual balance without increasing funded claim credit or mintable capacity.

ExampleLink to this section

When Core settlement completes several Squeek blocks in one Ethereum transaction, a later Mining checkpoint funds their eligible rewards. NFT owners claim only the whole base units already credited to their live positions.

Moving an NFT to another wallet moves access to its unpaid credit without moving the already-claimed Token balance. Burning a merge donor does not restore lifetime NFT issuance capacity.

SourceLink to this section

Mining5 source specification e0617449. First-party source is private; see source and release scope.

Records verified work and tracks settled rounds and Squeek blocks on Ethereum. Calculates rewards from settled work, holds funded SQK, and pays eligible NFT owners. The Miner ERC-721 contract. Tracks NFT ownership and coordinates minting and merges with Mining. Applies Core or Mining upgrades authorized by its governing Timelock. Generates Miner NFT artwork from fixed onchain visual data. Queues governance operations and enforces a delay before they can be executed. The SQK ERC-20 contract. Enforces the lifetime supply cap; only Mining can mint SQK. Checks that visual data conforms to the required DotGrid format. When new mining power starts earning. Minting and merging schedule it for a later round, and a checkpoint must process the change. A reward update that processes settled work and scheduled mining-power changes. It can make rewards available but doesn't pay them to an owner's wallet. The Miner NFT permanently burned in a merge. Its unclaimed rewards move to the survivor, but its image is not combined or kept. SQK issued under the mining reward rules. You can direct a share of your Miner's rewards to fund SqueekFi projects. The physical mining device that records accepted wheel-magnet passages as work. It is separate from the virtual Miner NFTs. Squeekchain's record of accepted wheel-magnet passages. It doesn't prove animal identity and isn't how Ethereum reaches consensus. Combining two eligible same-level Miners you own into one higher-level Miner. One NFT is permanently burned; the survivor keeps both Miners' unclaimed rewards. The completed Squeek blocks a Miner must wait through before merging. It measures completed work, not elapsed time or Ethereum blocks; transfers don't reset it. The power used to calculate a Miner's share of rewards when eligible and active. A larger share of total power can mean a larger share of rewards. A ten-minute period used to group measured work. The device saves a completed round's work total when measurement remained uninterrupted. The transferable token used for mining rewards. It has a lifetime supply cap and is separate from the Miner NFT and the device's work count. A completed amount of settled work. Enough recorded work completes one Squeek block; it is not an Ethereum block. Squeek Miner NFTs earn SQK linked to recorded wheel activity. Owners can direct a share of those rewards to fund SqueekFi projects. Squeekchain's ecosystem for hamster-powered onchain finance. Miner owners can choose to fund projects with a share of their SQK rewards. The Miner NFT you keep in a merge. It gains a level, keeps its ID and image, and receives both Miners' unclaimed rewards. A Miner's recorded reward balance that hasn't been paid to a wallet. It stays with the NFT when ownership changes. One wheel-magnet passage that met the device's counting rules and was saved. It records work, not an amount of SQK.