Source scope Source 9e38b931

Source and release scopeLink to this section

TL;DRLink to this section

System/API pages describe Mining4 integration; contract and reward pages describe Mining5 source.
These docs do not identify a verified Mining5 deployment or approve it for production.
Source revisions identify code versions, not contract addresses or audit results.

Release identityLink to this section

Documentation domain	Source revision	Applicability
System and public API	`9e38b9313c9b4926ad15c7cd691d7f5789bdbc55`	Measurement and service behavior; Mining4 API integration
Core2, `Token`, Mining5, and `NFT` mechanics	`e0617449299d5bb600d6379fec592cff055fa520`	Source-defined contract and reward behavior; not a deployed release

Do not use Mining5 tuples, events or transaction examples with a Mining4 API or deployment. These are different interfaces, not an upgrade already completed.

First-party source is private. These pages explain it, but internal documentation links are not publicly inspectable code or an independent security audit.

Public third-party links document inherited standards. They do not prove which code or configuration a first-party deployment uses.

Components and addressesLink to this section

This site supplies no verified Mining5 addresses: Core and Mining proxies or implementations, Token, NFT, factories, or governance roles.

A deployment record must identify the network, component addresses, active implementations, code hashes, initialized connections and the checks performed. An address or source revision alone is not enough.

Historical deployments have separate configurations and do not verify these contracts. This site is not an address directory for past or current networks.

Verified statusLink to this section

The contract reference describes Core version 2, Mining version 5, Token's fixed mint authority and cap, and NFT mechanics. It does not report live setup, activation, balances, governance connections or successful owner transactions.

The API snapshot supports Mining4, not Mining5. An older release does not prove that a new deployment is safe or compatible.

This page reports no live contract checks or independent audit. Before signing, obtain an explicitly approved deployment record and follow the contract-read procedure.

Known limitationsLink to this section

A permanent proxy address does not identify its current implementation or prove storage compatibility.
Explorer source matching, security review, deployment verification and production approval are separate checks.
Token's lifetime cap limits supply but does not require work before minting; that protection depends on Mining and its upgrade governance.
Source-defined constants are not a sale promise, earning forecast, or approved launch configuration.
Documentation publication does not authorize deployment, activation, or publication of contract source and build inputs.

SourceLink to this section

Source snapshots 9e38b931 and e0617449 define this page's scope; see release identity. First-party provenance is maintained privately, and these identifiers do not grant repository access.

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.