Built in the open.
Understood by everyone.

A forest starts at the core.

SHERWOOD / $SHER is an independent Zcash mining project designed for Robinhood Chain, with a planned token launch on Pons v2. Its name comes from Sherwood Forest: an invitation to build something together.

The CPU Lab is a visual study. SEED, GROVE and FOREST illustrate different core counts; they are not live hardware inventory, a mining performance feed or products offered for sale. Actual mining uses Equihash ASIC hardware or rented hashpower; processor core counts are not Zcash mining performance. See the Zcash mining guide.

One treasury. A clear path.

1. Pons fees settle. Creator fees accumulate upstream before a Pons sweep credits the appropriate escrow ledger.
2. The vault claims. After the vault is configured as fee recipient, settled fees are collected into the treasury before procurement.
3. The owner withdraws. Funds leave only for the designated procurement wallet. The contract records withdrawals in events.
4. The operator purchases Equihash hashpower. The mining provider connects to the configured pool. Native ZEC payouts settle to the project’s Zcash wallet, separate from the Robinhood Chain vault.

Treasury balances and fee settlement are inspectable onchain. An empty escrow does not establish that no fees have accrued. The vault performs no trading or upstream sweeps.

Protocol reference: Pons v2 documentation. Integration must use the escrow and factory belonging to this specific launch.

The ZEC destination.

The project mines native Zcash using Equihash. The operator selects an Equihash rental or ASIC provider and configures a mining pool with the project’s Zcash payout address. Provider payments may require a separate currency conversion after the owner withdraws from the ETH vault.

The mining observatory polls 2Miners every 30 seconds for the configured project account, workers, balances and hashrate history. Values reflect pool observations and may lag hardware activity. The 6-hour and 24-hour chart controls filter returned observations; empty periods remain empty. Delayed data is labeled with its last observation time. Public network and pool totals appear separately, including before the project account is connected. Another miner’s address is never substituted for SHERWOOD.

Pool payouts go to the project’s Zcash account. The EVM vault cannot receive native ZEC. Any return to Robinhood Chain requires an operator-managed conversion. SHERWOOD plans to distribute mining proceeds to CPU NFT holders once the distribution program is defined and activated; pool payouts shown on the dashboard are payments to the project, not distributions to holders.

Pool setup: 2Miners Zcash instructions. Provider selection and pool rewards do not establish a guaranteed return.

The procurement treasury.

SherwoodVault is a non-upgradeable procurement treasury. It has no token mint, reward pool, staking, factory or proxy. The launch token is created separately by Pons, and the CPU NFT collection uses a separate ERC-721 contract. The project still has one procurement treasury.

The vault receives ETH directly and holds ERC-20 tokens. Native accounting includes forced ETH. Token balances remain separate from ETH totals. Reentrancy protection applies to claims and withdrawals.

Network source: Robinhood Chain network documentation.

Someone is accountable.

The owner can claim fees, withdraw ETH and tokens, update the procurement destination, and redirect future Pons fees if the vault is retired. The owner therefore has custody of treasury funds. Public balances and transaction records make these actions inspectable; they do not prove that a provider has delivered mining hashpower.

Public accountability

The contract’s balances, source code and transaction history are public. The project operator manages procurement separately from this website.

Holder rights

The procurement vault grants no direct withdrawal permission to token or NFT holders. SHERWOOD plans mining proceeds distributions for CPU NFT holders through a separate operator-managed process. The existing vault and CPU NFT contract do not execute those payouts. Allocation rules and the activation date will be published before the program starts.

From concept to first purchase.

1. Choose the owner and procurement wallet. Verify Pons factory and escrow addresses for the intended launch.
2. Deploy and verify the single vault. Test its deposits, claims and withdrawals before routing revenue to it.
3. Create $SHER through Pons v2. Set the fee recipient to the vault using the platform-supported process. Claim any old recipient balances separately.
4. Publish the verified token address, trading link and vault address on this website.
5. Collect settled fees, withdraw for procurement and publish the provider order and delivery evidence.

Deployments use the Robinhood deployment guide. The source repository includes a deployment script and tests. The vault address is published above. Token creation and treasury actions require the operator's wallet signature.

A CPU you can collect.

The SHERWOOD CPU First Edition is a separate, non-upgradeable ERC-721 collection on Robinhood Chain. Minting is free plus the network gas fee. Supply is permanently capped at 1,000, with one lifetime mint per wallet. Transferring your NFT does not reset the mint limit.

Choose SEED, GROVE or FOREST before signing. These are aesthetic choices with the same rights; there are no promised rarity or performance tiers. The 3D model is an interactive preview. The NFT itself contains permanent SVG artwork and JSON attributes generated by the contract, with no external image host or mutable metadata.

SHERWOOD intends CPU NFT holders to participate in future distributions from the proceeds of purchased Zcash hashpower. This is an operator-managed program in preparation; payouts are not live. The NFT is digital and does not deliver physical hardware. Its permanent artwork and ownership record are onchain; mining runs on separately purchased Equihash capacity.

Choose and mint your CPU. Connect a compatible wallet, select your edition and confirm the transaction. The mint panel shows your receipt and the NFT minted by your wallet, including whether it has since been transferred.

Mining proceeds. CPU participation.

The intended flow is creator revenue → purchased Equihash hashpower → mined ZEC → distributions to CPU NFT holders. Mining and settlement are operated outside the NFT contract. The CPU artwork and ownership record are permanent onchain; they do not create a processor that runs Zcash mining inside Robinhood Chain.

The project intends to share actual mining proceeds with CPU NFT holders. The share allocated to holders, treatment of costs, allocation per NFT, eligibility snapshot, transfer rules, payment currency, payout schedule and delivery or claim method have not been finalized. These terms will be published before payouts are activated. The SEED, GROVE and FOREST design configurations do not establish a payout weight or fixed hashrate.