Transparency

Fees, in the open

Every way this project charges anything, in one table, the contract that enforces each fee, its compiled ceiling, where the money goes, and whether anyone can redirect it. Numbers below are read from BNB Chain or compiled into immutable code, except where a panel says it is showing a fixture preview; where a read fails, the page says so instead of guessing. All amounts in BNB.

Utility contracts not yet deployed

The deed, market, auction, raise and loan addresses land here at deploy. Rows marked deploy-gated show their compiled defaults; the $APARTMENT trade-tax row is live today. The RevenueVault is not deployed either, so every figure in the flywheel panel below (totals, run history and transaction hashes alike) is a demo fixture rather than a chain read. Addresses appear the moment they exist, nothing on this page is invented.

StreamTodayHard capDestinationStatusContract

$APARTMENT trade tax

Every $APARTMENT trade is taxed by the token contract; the tax converts to BTCB and routes to holder wallets through the BTCB distributor, live on BNB Chain since Aug 1, 2026. Numbers on those surfaces are BTCB received by holders.

set in the token contract, this page only prints numbers it reads live, so no percentage is shownFixed by the deployed token contract.BTCB distributor → holder wallets. Never touches the project treasury.Live

Deed mint fee

Paid once when a symbolic deed NFT is minted. Deeds are self-attested tokens, the fee buys the mint transaction, nothing else.

0.002 BNB, compiled default until deploy0.05 BNB, compiled into the immutable contract; the admin can never exceed it.Treasury. Honesty note: the destination is admin-settable, setTreasury exists on ApartmentDeed, so this one stream can be redirected by the admin key.Deploy-gated
ApartmentDeed: published at deploy

Market sale fee

Deducted from the sale price on every fixed-price deed sale. Seller proceeds sit in the market contract until the seller collects them, no admin role can touch them.

2.5% (250 bps), compiled default until deploy5%, compiled MAX_FEE_BPS; the admin can never exceed it.Treasury. Destination IMMUTABLE, no setter exists in the bytecode, so no admin (or stolen key) can ever redirect it.Deploy-gated
DeedMarket: published at deploy

Auction sale fee

Charged at settlement on the winning bid, read from feeBps at settle time. Outbid refunds and seller proceeds are pull-credits in the auction contract until collected.

2.5% (250 bps), compiled default until deploy5%, compiled MAX_FEE_BPS; the admin can never exceed it.Treasury. Destination IMMUTABLE, no setter exists in the bytecode, so no admin (or stolen key) can ever redirect it.Deploy-gated
DeedAuction: published at deploy

Raises

The platform takes NOTHING. No fee parameter exists anywhere in ApartmentRaises: openers withdraw the full amount, contributors' refunds are full.

0, no fee existsNone possible, there is no fee code to raise.Nothing flows to the platform. Every wei stays between opener and contributors.Deploy-gated
ApartmentRaises: published at deploy

Loans

The platform takes NOTHING. No fee parameter exists anywhere in LoanDesk: repayment is principal plus the borrower-set thank-you sum, all of it to the lender.

0, no fee existsNone possible, there is no fee code to raise.Nothing flows to the platform. Every wei stays between borrower and lender.Deploy-gated
LoanDesk: published at deploy

Where the fees go

Platform fees arrive in the RevenueVault contract as BNB. On each run the vault splits that BNB and swaps it on PancakeSwap into two things: $APARTMENT, which is sent to the burn address, and BTCB, which is sent to a single address fixed in the contract at deploy. Nothing else leaves this contract, there is no third destination and no function that can send any of it anywhere a role chooses.

Vault not deployed yet

The vault is not deployed yet; the figures below are demo fixtures, not chain reads, including the transaction hashes in the run table, which are made up and point at no transaction. Addresses, totals and run history appear here the moment the contract exists.

BNB converted (lifetime)12.5 BNB

Fee revenue this contract has actually swapped, summed across every run. BNB from a leg that reverted is not counted, it never left the vault.

$APARTMENT sent to the burn address (lifetime)48,200,000 $APARTMENT

Bought by this contract and measured as the balance change at 0x…dEaD, never as a router quote, $APARTMENT taxes trades, so only the delivered amount is reported. Tokens anyone donated to the vault are counted separately and are not in this figure.

BTCB forwarded (lifetime)0.0184 BTCB

Bought by this contract and measured as the balance change at the sink address fixed in the contract at deploy. Donated BTCB is counted separately.

BNB waiting in the vault0.9 BNB
Current split50% burn leg · rest BTCB leg
Runs3
Last run111d ago

Every address involved

  • RevenueVault: published at deployWhere fees land and where every run starts. This is also the treasury address the deed, market and auction contracts pay into.
  • Burn address: 0x00000000…dEaD ↗Compiled into the contract as a constant. Tokens sent here cannot be moved again by anyone, including us.
  • BTCB sink: published at deployThe destination is chosen once, at deploy, and is immutable afterwards. It can never be the admin or operator address, or a plain wallet. It is published here the moment it exists.
  • $APARTMENT: 0xd79860bb…7777 ↗The token the buyback leg acquires. Its own trade tax applies to that purchase, set by the token contract, not by this vault.
  • BTCB: 0x7130d2A1…ad9c ↗Binance-Peg Bitcoin on BNB Chain, the asset the second leg forwards.
  • PancakeSwap V2 router: 0x10ED43C7…024E ↗The only venue this contract can trade on. Immutable, set in the constructor, no setter exists.

Recent runs

TransactionBNB in$APARTMENT burnedBTCB forwardedBlock
0x00000000…002bdemo5 BNB19,200,0000.007454,991,000
0x00000000…002ademo3.5 BNB13,600,0000.005154,936,000
0x00000000…0029demo4 BNB15,400,0000.005954,880,000

What is automatic, what is not, and what nobody can do

Fee revenue arrives here automatically, the deed, market and auction contracts send it with no human in the loop. Converting it does not happen automatically: an operator signs each run, sets the slippage limits, and pays the gas. Every run is one transaction you can read on BscScan.

No role can move BNB, $APARTMENT or BTCB out of this contract to any address of its choosing. There is no rescue function, no sweep, no withdrawal. The cost of that is real: anything that gets stuck here is stuck forever.

What the admin can do is retune the split, and it takes effect immediately, there is no timelock on it. Within the compiled 10%–90% bounds that moves BNB between the burn leg and the BTCB sink, and nothing else: both legs always keep a share, and no new destination can be introduced. The sink itself is fixed at deploy and can never be the admin address, the operator address, or a plain wallet, the contract rejects all three at construction.

Buying $APARTMENT on PancakeSwap also pays the token’s own trade tax, which the token routes to the BTCB distributor. That amount is set by the token contract, not by this vault, we do not control it and do not promise a figure.

Limits compiled into the contract

  • Dust floor, a run needs at least 0.01 BNB in the vault; below that the balance simply waits.
  • Per-run ceiling, at most 100 BNB is converted in one call; a larger balance is processed over several runs and nothing is stranded.
  • Cooldown, 10 minutes between runs, so a stolen operator key cannot repeat a bad run quickly or quietly.
  • Deadline window, a run’s deadline can be at most 30 minutes ahead, so a signed run cannot sit in the mempool and land at a price nobody agreed to.
  • Split bounds, the burn leg can never be set below 10% or above 90%, and the BTCB leg always receives the exact remainder. Both legs always get a share.
  • Slippage is mandatory, a run with a zero minimum-out reverts. Both minimums are set by the operator and recorded in the transaction.
Platform fees arrive in the RevenueVault contract as BNB, automatically, from the deed, market and auction contracts. On each run the vault swaps that BNB on PancakeSwap into two things and only two things: $APARTMENT, which is sent to the burn address 0x…dEaD where nobody can move it again, and BTCB, which is sent to a single address fixed in the contract when it was deployed. The split between the two can be retuned by the admin within limits compiled into the contract, and both sides always receive a share, but no admin, no operator, and no stolen key can send any of it anywhere else: the burn address is written into the code, the BTCB destination is immutable, and there is no rescue, sweep or withdrawal function of any kind. The cost of that guarantee is that anything stuck in this contract is stuck forever. Runs are not automatic: an operator signs each one and sets its slippage limits, and every run is a single transaction on BscScan with the BNB spent, the $APARTMENT burned and the BTCB forwarded all recorded in its logs. Buying $APARTMENT also pays the token’s own trade tax, which the token routes to the BTCB distributor, that amount is set by the token contract, not by this vault, and we do not promise a figure. This contract is immutable and unaudited, read it.

The treasury

Balance right now-

Published at deploy, the treasury address lands with the contracts.

Address
Published at deploy

One treasury for every stream that has one: deed mint fees, market sale fees, auction settlement fees. A plain, always-payable address, an EOA at launch. User money never sits here: proceeds, refunds and payouts stay in their contracts until their owners collect them.

Can the destination be changed?
  • ApartmentDeed (mint fees), ADMIN-SETTABLE, setTreasury exists, so the admin key can redirect this stream.
  • DeedMarket (sale fees), IMMUTABLE, set once in the constructor; no setter exists in the bytecode.
  • DeedAuction (settlement fees), IMMUTABLE, set once in the constructor; no setter exists in the bytecode.

That is the words-vs-code truth, per contract. Raises and loans have no fee destination at all, there is nothing to redirect.

Deeds sold or auctioned on this site are symbolic, self-attested tokens and confer no legal rights, buying or winning a deed buys the NFT, not an apartment, not a title, not any claim on a real-world asset. A deed's verification tier resets to zero the moment it transfers, including through a sale or auction here: you are buying the token, never the tier. Auctioned deeds sit escrowed in the auction contract until settlement; if nobody bids, the deed simply goes back to the seller. Outbid amounts, seller proceeds and loan payouts sit in their contracts until their owners collect them, and no admin role can take or redirect any of it. On every sale or settled auction a fee (currently 2.5%, hard-capped at 5% in immutable code) goes to the project treasury, which also receives deed mint fees; raises and loans carry no platform fee at all. During the 72-hour hold after a raise closes, the site's guardian key can freeze the raise, which permanently converts it to refunds. The guardian can never take or redirect funds. Loan principal transfers instantly and is unprotected. Deeds, shares and loan collateral are symbolic and confer no legal rights. Contracts are immutable and unaudited, read them.