# FLAP BTC — Work and settlement domains

## Personal workchain
The browser builds a personal chain with real double SHA-256 computations. It is not Bitcoin's 80-byte consensus header. Header strings bind the namespace, version, BNB chain ID, personal chain ID, height, parent, miner, difficulty, challenge and nonce. The inner digest is hashed as 32 bytes. A 60-second CPU budget, bounded workers and hidden-tab stop protect device responsiveness. Export verification checks every hash and parent. The miner label alone is not a wallet signature or identity attestation.

## Inventory-funded season implementation
FlapBtcSeasonV1 is included in the source package, separately from the deployed FLAP vault factory. It requires a reward token, future start block, 8–128 block epoch length, 8–128 epochs per halving era, 1–256 claims per epoch and 12–24 zero-bit difficulty. The sponsor funds and activates before the start. Actual tokens received determine the budget, including incoming transfer tax. The first era pays 8 units per proof, followed by 4, 2, 1. Unit = floor(actual inventory / (15 × epochs per era × claim capacity)). This bounds all possible claims within initial funding; rounding dust and unused inventory can be recovered by the sponsor after the final epoch.

The current epoch's preceding block hash seeds its challenge. Every claim is double SHA-256 over ABI-encoded season contract, chain ID, challenge, claimant and nonce. One claim per address per epoch; first valid claims compete for capacity. The contract refuses stale epochs, copied proofs for another claimant, duplicate claims and invalid work. Rewards are gross token units; token transfer tax may reduce net receipt. Address limits do not establish unique humans. Mining faster has no guaranteed payout, and transaction ordering affects scarce claims.

## Activation boundary
The FLAP factory manages project tax-vault assets and records theme parameters. It is not the season reward contract. No reward season is activated or funded by the website. A season needs its own reviewed deployment, token CA, funding transaction and published start before claims are available. No season address is fabricated and personal browser blocks cannot be submitted as season proofs.

## Sources
https://developer.bitcoin.org/reference/block_chain.html
https://docs.flap.sh/en/flap/developers/vault-developers/vault-and-vaultfactory-specification