How the house works.

$HOUSE is launched on Pons V2 with its creatorFeeRecipient set to the address that collects trading fees. Supply is fixed: no mint function, no team allocation. Holding the token is the entire position.

As the token trades, creator fees accumulate in the Pons V2 fee escrow. The pool's harvest() pulls them out. Native ETH fees are swapped to a dollar stablecoin through an allowlisted router with slippage bounds; stablecoin fees pass straight through. deploy(propertyId, amount) then routes that capital cross-chain into a real property on Lofty.

Lofty (lofty.ai, a Y Combinator company) tokenizes 100+ real US single-family rental homes. Each property is held in its own US LLC with a real address and deed, and is sold as fractional tokens. Rent is paid daily, in USDC, at a variable yield that averages around 9% — targeted at 8–10% across the homes the pool funds.

Lofty settles on Algorand, so the treasury deploys and returns value cross-chain. Each epoch the keeper calls settle(root, amount, snapshotBlock): it fixes a block, publishes a Merkle root of the $HOUSE balances at that block, and allocates USDG to that epoch out of what the pool is not already owing. A holder then calls claim(epochId, amount, proof) and is paid their leaf, once per epoch. Whoever held at the snapshot is paid for that epoch; a later buyer starts at the next one. No lockup, nothing to stake. We would rather have used a running accumulator, but that needs a hook on the token's transfers to settle a seller before their balance moves — $HOUSE is launched on Pons V2, we do not own that contract, and reading a live balance at claim time would let anyone buy immediately before claiming and take the whole accrued history. Lofty's rent arrives in USDC; the treasury converts it to USDG before distributing, so holders always claim in USDG on Robinhood Chain.

Coming soon: none of this runs yet. The pool is deployed and verified, but $HOUSE does not exist, so fees are held by the treasury wallet named in the contracts table below until the recipient is moved to the pool. The automatic settle() and the pull-based claim() all arrive with HousePool — until it is deployed there is no accumulator, no epoch and nothing is claimable. The recipient move to the pool is a single on-chain transaction and it will be posted when it happens.

The only inflow is Pons creator fees. There is no mint, no emissions and no protocol fee skimmed from holder rent. The swap from ETH fees to a stablecoin is bounded by slippage limits set on an allowlisted router.

Lofty positions are fractional tokens that can be sold on Lofty's own marketplace; the yield is variable and can change with occupancy and expenses. v1 policy is to hold and compound; any redeem(propertyId) is operator-gated and posted.

• No owner path to your rent. Claims are pull-based: only you can claim your share. There is no emergency withdrawal and no admin drain — the contract ships without one. Every owner function (rescue, sweepToken) is bounded by balance − totalOwed, so it can only ever touch money that has not been distributed yet. Once an epoch is settled, that USDG leaves the pool only when its owner claims it. The cost of that guarantee, stated plainly: rent that is never claimed stays in the pool forever, because nobody can move it.
• Interim custody (v1 launch). HousePool does not exist at launch, so $HOUSE creator fees accrue to a treasury wallet the team controls rather than to a contract. That is custody, and it is a trust assumption: the wallet holds the fees, and nothing on chain forces it to hand them to the pool. When the pool is deployed the recipient is moved with transferCreatorFeeRecipient and the transaction is posted.
• Not audited. The contracts have not completed a formal audit. Treat everything as experimental.
• Real-estate / RWA risk. Rent and principal depend on real homes and on Lofty performing. Real estate can underperform; vacancies and expenses reduce yield.
• Variable yield. The ~9% figure is Lofty's stated average; individual homes range higher and lower and can change. Nothing here promises a rate.
• Cross-chain risk. Lofty settles on Algorand while $HOUSE lives on Robinhood Chain. Bridging value between chains is a real dependency.
• Keeper / operator risk (v1). The treasury deploys and settles through a keeper/operator. That is a trust assumption until it is further decentralised.
• Fee dependency. Distributions are funded by trading fees. If trading stops, harvests shrink. Nothing here promises a rate.

HousePool is deployed and verified on Robinhood Chain; its row below is a live address. $HOUSE has not launched, so its row reads not deployed until the address is published. The USDG token and the Pons V2 escrow and factory are live. The Treasury row is the interim creator-fee recipient: it is where $HOUSE fees land until the recipient is moved to the pool.