Block Estates Handbook

Inside the property machine

This document turns the collection into a readable operating system: 4,444 estates, four property classes, activation bills, floor oracle, rent ledger, reserve math, Genesis priority and explicit failure controls. The goal is to make holders understand the machine before the machine asks for trust.

Supply4,444fixed estate district
Classes4Tier 1 to Genesis
OracleL5 medianunique seller filter
Outflow cap1.8%rolling 24h reserve limit
01

The 60 second loop

  1. Own a Block Estate from the 4,444 item district.
  2. The estate enters the registry as Tier 1, Tier 2, Tier 3 or Genesis.
  3. The FloorOracle publishes a filtered floor reference.
  4. The holder activates the estate and opens a lease window.
  5. The activation bill is priced by floor reference and tier weight.
  6. The RentLedger adds points by time, weight, hold behavior and occupancy.
  7. The ReservePool meters any future reward spend with depth and daily caps.
  8. Genesis estates receive the highest priority lane across access windows.
02

Property classes

Tier is not cosmetic. Tier defines the estate's mathematical weight, lease window and ceiling. That gives the collection a visible structure: a Base Parcel should not read the same as a Genesis Corner Estate.

TierTitleWeightLot SpaceWindowCeilingRole
Tier 1Base Parcel1.00x4 lots24h1.20%entry allocation
Tier 2Upper Unit1.55x3 lots18h1.80%stronger rent weight
Tier 3Prime Block2.65x2 lots12h2.70%priority lane
GenesisCorner Estate5.00x1 lot8h4.00%top registry status
03

Activation bill

Activation is the moment a house stops being a static picture and enters the district ledger. The bill should be visible, bounded and derived from market state instead of invented by hand.

Proposed activation pricingbill = max(1, 1.42 x floor_ref^0.84) x tier_weight

The exponent makes the curve feel serious while keeping it usable: if the floor doubles, the bill rises less than 2x. Genesis still carries more weight because its multiplier is higher.

04

Math sheet

floor_refmedian(L1, L2, L3, L4, L5)

Five cheapest live listings from unique sellers. The median resists one-wallet floor pressure.

activation_billmax(1, 1.42 x floor_ref^0.84) x tier_weight

The bill rises with floor value while the exponent keeps it from exploding too fast.

reserve_depthreserve_balance / open_bills

Shows whether the reserve can comfortably support current active estates.

pool_ratereserve_balance x 0.08 / open_bills

Meters a window of the reserve against all unsettled activation bills.

payout_ratemin(tier_ceiling, pool_rate + tier_base)

Higher tiers can have higher ceilings, but the reserve still controls the final rate.

rent_pointsactive_hours x tier_weight x hold_multiplier x occupancy_bonus

The core non-financial score for access, priority and future phases.

moving_rateprevious_rate x 0.90 + new_reading x 0.10

Smooths oracle movement and avoids sharp half-hour jumps.

daily_outflowsum(claims_24h) <= reserve_balance x 0.018

The reserve has a daily circuit breaker.

05

Floor oracle rules

A floor oracle is only useful if it refuses obvious manipulation. The proposed Block Estates oracle reads the five lowest live listings from unique sellers, uses the median as the reference, then smooths the result over time.

Unique sellersOne wallet cannot fill the whole sample.
Median sampleThe middle reading resists one extreme low or high listing.
Bounded movementReadings move gradually and can be paused during bad data.
06

Reserve pool

The reserve is the part that makes the system honest. Rewards, credits or future utility spend should come from a finite pool with meters, not from a paragraph that says everything will work forever.

SourceFunction
Activation billsPrimary utility sink when a house enters an active lease window.
District lot salesOptional future room and lot layer for collectors who build neighborhoods.
Creator allocationRoyalties or treasury top-ups can be pointed at the reserve if enabled.
Partner feesFuture marketplace, launchpad or tooling revenue can refill the district.
07

Contract map

The final build can be phased, but the architecture should be described as a system. This is the clean contract map for the full utility stack.

EstateNFTThe 4,444 estate collection and token metadata.
DistrictControllerActivation, lease windows, lot capacity and settlement state.
FloorOracleFiltered listings, unique seller rule, smoothing and bounded movement.
RentLedgerRent Point accounting, multipliers and claim windows.
ReservePoolFunds, daily outflow caps, reserve depth and spend controls.
GenesisRegistryGenesis priority, boosts, early access and top-lane permissions.
DeedRendererReadable property deed page for each estate.
08

What can go wrong

  • If later phases are not shipped, Rent Points remain a participation score rather than a liquid reward.
  • If floor listings are thin or manipulated, the oracle needs filters, bounds and a manual pause path.
  • If too many estates activate at once, reserve depth falls and payout rate compresses.
  • If marketplace royalties are bypassed, reserve top-ups must come from other sources.
  • No language here should be treated as guaranteed yield, equity, dividend, revenue share or financial advice.
09

Glossary

EstateOne NFT house inside the 4,444 supply.
Tier WeightThe multiplier used in activation and Rent Point math.
Floor RefA filtered floor value used for bills and system readings.
Open BillAn active activation bill that has not fully settled.
Reserve DepthHow much reserve exists relative to open bills.
Rent PointsA non-financial score for access, priority and participation.
Lease WindowThe time window during which an activated estate accumulates score.
GenesisThe highest property class with maximum registry priority.