The plain-english docs.

01Overview

Bankestate is a memecoin with a transparent treasury policy. Every transaction fee on $BSTATE is routed on-chain into USDC, then into shares of legal entities that own real property. Rental income flows back into the treasury and a portion is streamed to holders on a predictable cadence.

What's deliberate here: the contract does not claim to deed land on-chain. It holds legal instruments — SPV shares, fractional property tokens, and income rights — that represent ownership of the underlying property.

02Fee routing

Each buy and sell of $BSTATE incurs a small fee, collected by the protocol in whatever asset was on the inbound side of the swap — ETH, SOL, USDC, or the token itself. The fee is forwarded to the treasury contract every block.

There is no team wallet skim, no marketing wallet, no separate buyback wallet. Every basis point goes to the treasury contract.

03USDC bridge

Volatile inputs are auto-converted to USDC via on-chain DEX routes. Stability is required because:

• Real estate platforms price everything in dollars.
• SPV share acquisition is a discrete, dollar-denominated transaction.
• Accounting and legal compliance demand a stable base unit.

The bridge runs continuously and accumulates USDC into the acquisition queue, which is drawn down when the treasury executes its next SPV purchase.

04SPV acquisition

Once the USDC queue exceeds the configured threshold, the treasury executes a purchase against a whitelisted real-estate platform. The treasury receives one of:

• SPV shares — equity in a legal entity that owns one or more properties.
• Fractional property tokens — on-chain representations of those shares (RealT-style, Lofty-style, Ark7-style).
• Income rights — claims on the rental cashflow without full equity.

Each acquired position is recorded in the on-chain SPV registry with a unique identifier, property address hash, share count, and acquisition price. The registry is the source of truth for the treasury's real-estate book.

05Treasury policy

The treasury maintains a target allocation across three buckets. Rebalancing is governed and runs on a published schedule.

Drift bands are ±5% on each bucket. If a bucket drifts outside its band, the rebalancer is authorized to act without a new vote.

06Distributions

Rental income collected by SPVs is paid into the treasury contract on the platform's native cadence (usually monthly). The treasury then streams a fixed share to $BSTATE holders, claimable on-chain.

Holders claim from a Merkle-rooted distribution contract. Unclaimed amounts roll over to the next cycle for up to 12 months.

07Governance

$BSTATE holders vote on bounded parameters: fee rate (within a hard ceiling), target allocation, platform whitelist, and distribution split. Votes are token-weighted with a configurable quorum.

Some values are not governable — the existence of a USDC bridge, the SPV registry contract, and the public-receipt requirement are immutable. This is intentional: governance can tune the treasury, not abolish it.

08Risk & limits

Real things this design is exposed to:

• Platform risk — an SPV operator fails or misappropriates funds.
• Property risk — vacancy, damage, market depreciation.
• Stablecoin risk — USDC issuer event.
• Liquidity risk — SPV shares are slow to exit.
• Regulatory risk — jurisdictional reclassification of tokenized real estate.

Mitigations are policy-level: whitelist diversification, capped per-SPV exposure (5% of book), the T-bill liquidity buffer, and the documented stablecoin fallback. None of these eliminate risk — they shape it.

09Contracts

All addresses, ABIs, and the SPV registry schema are published in the repo and pinned in the contract metadata. Each release ships with a signed treasury report and a settlement summary.

Until launch, addresses appear as tba. This page is the canonical source after deploy.