On this page

GPU FOUNDRY / FIELD GUIDE

Build it.
Understand it.

Your guide to components, on-chain circuits and Zcash mining. Understand the build, follow the funds, verify the contracts.

Build your GPU

BNB CHAIN / 56

ZCASH / POWV2 / GPU FOUNDRY

Turn activity into work.

ZEC EMBER is an independent community project designed to use Flap trading-tax revenue to fund Zcash mining procurement.

Make the trail visible.

BNB transfers can be checked on-chain. Supplier receipts and pool data complete the operational record. Mining returns are variable; there is no holder-dividend mechanism.

01THE FUNDING PATH

Follow the funds.

The vault is the on-chain starting point. An operator carries out the purchase with a real hashrate provider.

01Trading taxFlap on BNB Chain

02BNB vaultRevenue recorded

03ProcurementOperator + provider

04Zcash miningProject ZEC address

Allocate the revenue. The factory requires 100% of the configured tax allocation to go to the procurement vault, with no factory commission. The buy and sell tax percentages will be selected at launch; they are not published yet.
Withdraw a defined budget. The operating owner or Flap Guardian withdraws BNB to the configured procurement treasury, referencing a unique invoice hash.
Fund a provider order. The operator converts and transfers the budget through an available supported route, then places a limited hashrate rental order. NiceHash’s Equihash market currently uses BTC. The contract does not perform this conversion or purchase.
Verify the work and settlement. Match the supplier order with accepted shares, delivered hashrate, and pool payouts to the project’s native Zcash wallet. Publish the related receipts and transaction records.

Allocation is not the trading-tax rate.

“100% to the vault” describes where collected tax is allocated. It does not mean a 100% buy or sell tax. Zcash mining proceeds are settled separately into the configured BSC reward asset. The GPU reward pool accounts for available rewards by GPU weight.

02CONTRACT DESIGN

A vault with clear authority.

The implementation targets Flap Vault v3 and Factory v2.3 on BSC. It is an operator-managed procurement treasury.

VAULT INTERFACEv3VaultBaseV3

FACTORY SPECv2.3VaultFactoryBaseV2

REVENUE ASSETBNBNative asset only

Operating owner

The launcher becomes the vault owner. The owner may withdraw funds, recover ERC20 tokens, change the procurement treasury, and transfer operating ownership.

Flap Guardian

The Guardian has the same administrative permissions as a permanent backup authority. The project owner cannot revoke that access. The Guardian owns the beacon and controls implementation upgrades.

Everyone else

Anyone can read the public state and synchronize newly received BNB. Token holders do not gain withdrawal rights or an automatic claim on the vault balance.

Where a withdrawal can go

Each withdrawal goes only to the configured procurement treasury. Both owner and Guardian can change that treasury, so it is not an immutable destination lock. Changes and withdrawals emit public events.

Implementation & accounting details

vaultQuoteToken() = address(0) — native BNB is the only supported revenue quote. WBNB and other ERC20 quote assets are rejected for launch.

withdrawForMining(amount, invoiceHash) — requires an authorized caller, a positive available amount, and a unique nonzero invoice commitment. It updates accounting before transfer and uses reentrancy protection.

totalReceived — recognizes BNB balance increases, including donations. It is not a pure measurement of trading tax alone. Repeated synchronization does not count the same revenue twice.

newVault(...) — only the canonical Flap VaultPortal may create vault instances through the factory. The factory creates the vault; Flap handles the token launch.

An invoice hash is a commitment to a document. It does not prove supplier payment, hardware ownership, delivery, or the use of withdrawn funds. Those require supporting records.

Read the official Flap specification

03MINING OPERATIONS

Buy the right kind of power.

Zcash mining uses Equihash 200,9, measured in solutions per second. Start with a bounded rental to verify the connection and accounting before scaling.

01 / HASHRATE MARKET

NiceHash

Buy Equihash hashrate using the active BTC marketplace. Set the pool, price, speed limit and total order budget. Check account requirements and fees before funding.

Explore marketplace

02 / RIG RENTAL

MiningRigRentals

Select the Equihash/zcash market, create a pool profile, and rent individual rigs for a defined duration. Verify the payment currency and network shown by your account.

Browse available rigs

2Miners / Zcash SOLOPOOL CONNECTION PROFILE

Official guide

ALGORITHM: Equihash / Zcash (200,9)
HOST: solo-zec.2miners.com
MRR / ASIC PORT: 1010
NICEHASH PORT: 1111
USERNAME: YOUR_PROJECT_ZEC_ADDRESS
PASSWORD: x

Use a native Zcash transparent address controlled by the project. A BSC 0x address cannot receive native ZEC payouts. The reference address shown in the website is not an address to use for project orders.

SOLO or a shared pool?

SOLO rewards depend on finding a block and can be absent for long periods. For initial operational testing, the regular 2Miners pool is an alternative: zec.2miners.com with the same 1010 / 1111 port distinction.

Regular pool settings

What about physical miners?

The BITMAIN Z15 Pro is an Equihash ASIC rated at 840 KSol/s and 2,780 W. Hardware ownership adds power, hosting and maintenance costs. Current stock and Z15 hosting availability need a supplier quote.

Manufacturer specifications

04READ THE SIGNAL

Real data. Clear attribution.

The homepage refreshes public 2Miners data every 30 seconds. Until a project mining address is configured, it displays the supplied external reference account.

EXTERNAL REFERENCE · NOT PROJECT ASSETSt1b5F53pKHcU4au6wZzhfrP7Hfoa7jZxuhhIndependently verify the account

Hashrate and workersPool-estimated current and average hashrate, and the workers connected to that address. A worker is not necessarily one physical machine.

History and rewardsChart points and balances come from the pool. Missing values remain unavailable. Pool-wide blocks cannot be claimed as project-mined blocks.

Telemetry, with a timestampA delayed upstream response is marked as delayed or stale. This is a data visualization, not a camera livestream. A physical camera feed requires a separate video source.

Data endpoints for independent verification

Base URL https://solo-zec.2miners.com

GET /api/stats
GET /api/accounts/{address}
GET /api/accounts/{address}/hashrates/5m
GET /api/accounts/{address}/shares/5m

Hashrate history returns actual: [{x, y}]. x is Unix seconds; y is Sol/s. The 5m suffix is the sampling bucket. Account ZEC amounts use 100,000,000 base units per ZEC.

2Miners API documentation

05EMBER FOUNDRY

Build logic. Share funded rewards.

Mint six ERC-1155 component types: board, NAND core, LATCH memory, power, cooler and chassis. Collect the complete recipe, burn all required parts and receive an ERC-721 GPU in your wallet. GPU holders share available pool rewards according to their NFT weight.

From mining proceeds to GPU rewards.

Zcash mining happens on external Equihash machines. Proceeds are settled into the pool’s configured BSC asset. The contract records NFT ownership, calculates each holder’s share and handles reward claims. Distributions are limited to assets available in the pool.

Permanently recorded. Repeatedly executable.

Each GPU stores its circuit program and artwork directly on BNB Chain. The GPU contract has no upgrade, program-editing, execution-pause or expiry mechanism. Anyone can read its program and call evaluate; NFT transfers and the end of a reward period do not disable execution. The website is only an interface.

Continued access requires BNB Chain and an available RPC node. Execution happens when called: input bits and previous memory are supplied by the caller, and the contract returns the result and next memory. It does not automatically write state on every block. Circuit availability and mining reward availability are separate.

program(tokenId) · evaluate(tokenId, inputBits, stateBits)

An executable collectible

The current release offers 1, 4 or 16 Boolean SIMD lanes, each a five-NAND half-adder plus one latch. The seven-byte instruction format and two-pass evaluator are original implementations inspired by NAND/LATCH composition. These are Boolean parallel circuits executed by the chain. Zcash proof of work is performed by external Equihash miners.

A finite, funded reward stream

Each consumed NAND/LATCH unit adds one reward unit; the other four types are required without adding weight. Shares accrue over the funded duration while an NFT is owned. New assemblers have no claim on earlier accrual. On transfer, already earned rewards remain with the seller. Holding ZEMBER alone does not participate in this independent NFT reward pool.

Each component costs 0.000005 BNB. E1 requires 10 units for 0.00005 BNB; E4 costs 0.00014 BNB and E16 costs 0.0005 BNB. Assembly has no extra protocol fee; network gas is separate.

Mint is open on BNB Chain.

The lifetime issuance limit is 1,000,000 component units across all six types. Assembly burns do not replenish this limit. Rewards are denominated in BNB and become claimable when a funded reward period is active. Connect your wallet, mint the missing components, then confirm assembly to receive your GPU NFT.

Build your GPU

TapeOut’s published concept document

Open the GPU FoundryTry the logic. Inspect the reward rules.

05NEXT IGNITION

The path to launch.

The website and contract implementation are prepared. Production addresses, launch settings and the first procurement order come next.

TOKEN$ZEMBERNot launched

VAULT FACTORYDeployedBSC mainnet · v2.3

PROJECT MININGPendingReference feed connected

01
Set the project identities.
Choose the operating owner and procurement treasury, preferably multisigs, and create the project’s native Zcash payout address.
02
Deploy and verify on BSC.
Validate the contracts on testnet, then deploy the factory on mainnet and publish its verified address. Complete the Flap launch using native BNB and the selected buy/sell tax settings.
03
Publish the addresses.
Add the factory, vault and token addresses to the website. Configure the project mining account so the dashboard stops displaying the reference miner.
04
Place the first measured order.
Set a procurement budget and duration, fund the provider account, and verify delivered work. Publish the withdrawal, order receipt and eventual ZEC settlement together.

Website configuration reference

These are deployment settings, not published contract addresses. Supply real project values after verification.

ZCASH_MINING_ADDRESS=<project native Zcash address>
ZCASH_POOL_MODE=<solo or pplns>
NEXT_PUBLIC_FACTORY_ADDRESS=<verified BSC factory>
NEXT_PUBLIC_VAULT_ADDRESS=<project BSC vault>
NEXT_PUBLIC_TOKEN_ADDRESS=<launched BSC token>
NEXT_PUBLIC_BSC_RPC_URL=<BSC RPC endpoint>
NEXT_PUBLIC_MINING_STREAM_URL=<optional HTTPS camera URL>

Keep provider credentials and wallet secrets out of public environment variables. The optional camera setting opens the configured video source; pool telemetry remains independent.

Open the treasury consoleInspect the vault. Follow the funding.

07CONTRACT REGISTRY