Vault

Deposit · redeem · NAV
Vault status — Phase 2 in progress

The estate is not yet deployed.

The Fake Estate vault contract has not shipped to mainnet. Deposits, share issuance, NAV and the redemption queue come online once NEXT_PUBLIC_VAULT_ADDRESS is configured against the deployed vault. The FWA core it will trade against is already live — see the position book for real on-chain state.

NAV / share
— ETH
pending deployment
Free ETH
—
pending deployment
Queued redemptions
—
pending deployment
See how it worksTechnical breakdown

Position book

Live · FWA core 0xB276…
Open positions
…
live listings in the pool
Average backing
…
ETH per position
Price to draw one
…
ETH · what a buyer pays
Crown pot
…
ETH · earned by the top position
live from FWA core 0xB276…Ac1c · updated —
Protocol parameters — read live from the core
The crown
Tithe on every acquisition
topListingShareBps · live 1%, not the repo's 5%
—
Margin to seize the crown
topThresholdBps · a challenger must beat the top by this
—
Settlement
Standing bid
settlementDiscountBps · what a purchaser gets to sell back
—
Cut on acquisition
ownerAcquisitionFeeBps
—
Cut on settlement
ownerSettlementFeeBps
—
Sell-branch 15% goes to
retainedToProtocol
…
Timing
Purchaser-only window
settlementWindow · to keep or sell the NFT
—
Anyone can finalize after
finalizeWindow
—
VRF selection timeout
selectionTimeoutBlocks
…
Collection eligibility — collectionWhitelisted()
—
The vault's eligible universe is the 42 whitelisted collections. Try 0x60E4d786628Fea6478F785A6d7e704777c86a7c6 (MutantApeYachtClub).

The vault's positions

Live once deployed
Per-position book

Populated when the vault goes live.

Every vault position — collection, floor, backing, the keep/sell ratio, fees earned and status — is on-chain, but it is reconstructed from the vault's events (not a single core getter). It renders here from an indexer as soon as the vault contract is deployed and its keeper starts listing. The aggregate pool state above is already live from the FWA core.