Version, source and verification scope
Find the documented release and source, distinguish mocked validation from real-chain evidence, and understand known verification limits.
Content reviewed: · Documented version: v1.1.12 · Source code
Version and evidence
The Miner shows its application version beside the product name. The documentation review date and documented source version are listed on each page. These are explicit content-review records, not the time of your visit or a claim that a live chain probe just passed.
Use the linked versioned source and repository README for implementation details and release history. The deployed frontend version does not imply a smart-contract upgrade.
What verification does and does not establish
The repository has unit, component and Playwright tests, linting, type checks, dependency audit and bundle-size gates. Mocked wallets and RPC fixtures test controlled behavior without spending funds; they are not proof of current public-node health or a real-wallet transaction.
A result from an earlier release is historical evidence, not a fresh production check. Check the relevant pull request and CI run for the exact revision and tests. No test suite establishes that a product has no vulnerabilities or that an operation will always succeed.
Known limits
- Ethereum and Polygon mainnets are supported; other chains and contract wallets are not supported by this interface.
- The transaction interface requires desktop Chrome; documentation remains readable on other browsers and mobile devices.
- Unresolved transactions and damaged locks without a hash are not automatically discarded.
- One maintainer verification question, tracked as P2-C in the repository README, remains unproven: whether historical VMU destruction and count semantics match both current deployments. The CREATE2 verification gate has not been relaxed. Public RPC rate limits and availability remain external dependencies.