Standalone demo mode: not connected to the blockchain. Prices, target work, fee rates and balances are illustrative and do not represent production parameters; Platform Ecosystem Fund is not included in the simulation.
An NVDA stock-token-backed
Decentralized Treasury Economic System
Built on the BTC Stock Protocol, BTCNVDA is issued under public, uniform on-chain rules, distributing rewards based on effective work.
NVDA is used for payments and reserves; BTCNVDA is a separately issued protocol token.
Verifying on-chain state.
Genesis Ledger.
Time Condition Is Met.
On-chain Transaction Executes Successfully.
- 01Deploy and InitializeToken Is Created and the Official Pool Is Initialized at Deployment.
- 02Genesis Accrued Rewards Accumulate Round by RoundPublic trading is closed and no user work accrues during the first 24 hours.
- 03Settle Minting and Inject Protocol LiquidityRewards for Ended Rounds Must Be Settled, Minted, and Injected as POL via an On-chain Transaction.
- 04Participation After OpeningAll Opening Conditions Must Be Met; Reaching the Time Threshold Does Not Automatically Trigger an On-chain Transaction.
Payment and Treasury Reserve Asset
Used for Trading and Mining Rewards
Treasury reserve is NVDA. When trades can be executed, BTCNVDA can be sold for NVDA; the actual amount received depends on price, fees, and liquidity.
Approximately 350,000 genesis tokens over the first 144 rounds are allocated to protocol-owned liquidity. Accrued output, actual minting, and pool injection are three distinct stages. Total supply is capped at 21 million.
Each cell represents one 600-second protocol issuance round. It is not a Robinhood on-chain block; accrual, minting, and liquidity injection are recorded separately.
Issuance and Funding Details
Work is the total protocol fee from qualifying buys, not the full trade volume, and not the treasury's net inflow after revenue sharing. Genesis tokens belong to protocol POL; per-round POL injection cannot be directly inferred from cumulative totals.
Issuance status pending
—
Effective Work — NVDA
—
Cumulative POL deposits are not current pool balances.
Exact token amounts
Genesis records000 → 143
Reading Official Genesis Rounds.
Work distribution
Area represents each address’s share of effective NVDA Work.
Select a Round to Read On-chain Contributions.
Public issuance begins at Round 144. Rectangle area represents an address's Work relative to the round's total Work; addresses are not equivalent to unique users. Small contributions can be viewed in the list below. Rewards are calculated using max(round total Work, target Work) as the denominator and are reconciled against on-chain results — they do not equal area share multiplied by the full reward.
Trade to Mine.
Official Trading Path.
- Official Pool ID
- 0x4cc2e5d23e1c94645466ba014ea2b0c1834d8c6f0527d0a67b3878738ac08c6d
- Hook Contract Address
- 0x541c980ed3e0b5ced0bde5352c32bdab9d26a0cc
- Buy Work
- Actual Protocol Fee Collected on Buys
- Sell Work
- Does not generate
This mechanism does not tax ordinary ERC20 transfers. Trades in other pools not bound to this Hook are not counted toward this Hook's Work.
Official Pool · Trade to Mine
BTCNVDA / NVDA is the official Uniswap v4 pool on Robinhood Chain. BTCStockHook connects token trading, issuance rewards and treasury funding.
What you trade
Buy BTCNVDA with NVDA, or sell BTCNVDA for NVDA. Execution depends on the pool price, liquidity and fees.
Where liquidity comes from
BTCNVDA issued under the genesis rules is deposited into this same pool as protocol-owned liquidity. It supports trading and is not allocated to the team.
How trading earns mining rewards
Protocol fees actually collected on qualifying buys count as your Work toward additional BTCNVDA rewards for that round. Purchased tokens and mining rewards are separate; sells do not generate Work.
Protocol fees use the current contract rate: 30% goes to the platform ecosystem fund and 70% to the project, funding maintenance reserves and buy walls under the protocol rules. Network gas is paid separately.
Look at Contribution First, Then Reward.
÷ max(Round Total Work, Round Target)
The full planned reward is only received when the target is met and no other participants contribute in that round. Contributing more does not raise that round's issuance cap; with other participants present, rewards are allocated proportionally by contribution.
- Initial Target
- 0.010777023386140748 NVDA
- Target Change
- Halves Every 4,320 Rounds per Issuance Cycle
- Current Total Fee Rate
- —
- Reward Claim Timing
- After the Participating Round Ends
Every Contribution, Fully Traceable.
Connect Your Wallet to View Your Participation Record.
Only requests the public address and network information; no signing or charges. Unconnected wallets are not shown as zero rewards.
—
Ended-round rewards are allocated by contribution; pending rewards are separate from wallet balances.
My Participation Records
| Block Rounds | Individual Work · NVDA | Round Total Work · NVDA | Reward · BTCNVDA | Status |
|---|---|---|---|---|
| Connect Your Wallet to Read Actual Participation Records. | ||||
Matured rewards are not automatically transferred to your wallet. The claim entry will be enabled once the official handoff is complete.
Treasury Status, Item by Item.
The Platform Ecosystem Fund is included in the total fee and supports the platform ecosystem.
The Platform Ecosystem Fund receives 30% of the 1–10% dynamic total fee rate; the project's share is 70%, with no additional fee stacked on top. Work is calculated from the actual total protocol fee on buys; the revenue split does not reduce Work.
The maintenance reserve accrues up to 2% of the project's share; successful maintenance issues NVDA claims at a fixed amount, subject to balance and cap constraints — claims become actual wallet funds only after redemption. Mining rewards come from a separate token issuance, not a direct distribution of protocol fees to participants.
Seven Tiers, One Unified Mechanism.
The seven price tiers and their funding are read directly from the contract. Virtual depth is not shown before a buy wall is established; the unconverted ledger balance updates with maintenance settlements and does not equal the currently withdrawable balance.
BTCNVDA acquired via buy-wall fills is later burned through harvest and maintenance operations. A user's sell does not automatically burn these tokens within the same transaction.
Understand BTCNVDA.
21 million cap
600 seconds per round; every 4,320 rounds forms one issuance cycle, with planned rewards and target Work halving per cycle. Early rounds plan approximately 2,430.56 tokens per round.
24-hour genesis POL
The first 144 rounds allocate approximately 350,000 tokens to protocol-owned liquidity, not distributed to the team. Time accrual, settlement minting, and POL deposit are verified separately; the first valid public trade may complete settlement and POL deposit.
3% initial protocol fee
Total fee dynamic range 1%–10%. Of this, 30% goes to the Platform Ecosystem Fund and 70% to the project. Maintenance takes up to 2% of the project portion; selling does not generate Work.
Reserve and reward are not the same asset.
NVDA is an existing NVIDIA stock token; BTCNVDA is an independently issued protocol coin. Sell proceeds depend on fees, price, and liquidity, with no commitment to redeem at a fixed treasury share.
The buy wall absorbs BTCNVDA with NVDA, and maintenance proceeds are burned after harvest. The asset issuer's own transfer and custody rules still apply.
Verification starts from the contract.
Verify identity and mechanism via the address and public read-only source below. Ordinary ERC20 transfers and other pools not bound to this Hook do not automatically generate official Work or fee splits.
Source code and deployment materials ↗Instance identity and data source
- Platform
- BSP Treasury · BSP Treasury Platform
- Protocol
- BTC Stock Protocol
- Target production chain
- Robinhood · 4663
- Reserve asset NVDA
- 0xd0601CE157Db5bdC3162BbaC2a2C8aF5320D9EEC
- BTCNVDA / Factory / Hook / Pool
- Production addresses loaded from shared instance definition
- Deployment transaction receipt / Genesis start time
- Production genesis time loaded from verified on-chain records
- Current page data
- Deployed instance · awaiting read-only sampling
Both sites share the same production instance definition. Wallet connection is only used to read public account information; this version has no signing or transaction-sending capability.