Build in publicBase web appLandlords · Tenants · Investors · Agents

r3nt by SQMU is building an onchain rental marketplace with a stronger paper trail.

The goal is straightforward: let landlords, tenants, investors, and agents coordinate around cleaner booking state, wallet-native payment flows, and a product narrative that treats rental data as something worth reconciling properly.

What this page is

This is the public-facing placeholder while the product is still being tested and refined. The public narrative is live before the full marketplace is opened to everyone.

We are using this surface to explain what we are building, attract the right early community, and let search engines find a clearer story than a blank holding page ever could.

Rental coordination is still fragmented

Listings, identity, payment schedules, deposits, and follow-up usually live in different tools with different levels of trust and accountability.

Property media and rental state belong in different places

r3nt by SQMU keeps the chain focused on canonical booking and payment state while rich listing presentation stays queryable and easy to update.

Capital needs clearer proof than private spreadsheets

SQMU-R is designed to make epoch participation visible in the investor wallet while the underwriting logic remains tied to protocol-defined epochs.

Who this is for

A balanced marketplace, not a single-role product.

We are not treating rental operations as a landlord-only tool or an investor-only wrapper. The product story only works if each role can see where they fit.

Landlords

Publish richer property media offchain while pricing, booking state, deposits, and scheduling remain anchored to the chain.

Tenants

Discover rental opportunities with clearer availability, wallet-native booking actions, and payment flows designed to feel trustworthy instead of improvised.

Investors

Follow rental activity through epoch-based underwriting and hold SQMU-R tokens as visible wallet proof of participation in a given epoch.

Agents

Coordinate local knowledge, property access, and service layers around an onchain booking system that is easier to reconcile after the fact.

How it works

A cleaner split between onchain state and richer property context.

The chain should carry the canonical facts. The app should carry the presentation layer. The indexer and metadata layer should make both usable without pretending to replace the ledger.

List

A landlord creates a property with geographic coordinates, pricing, deposits, and booking constraints while richer description and media live offchain.

Book

A tenant selects available dates, confirms the booking flow with a wallet, and funds the required deposit and first payment interval.

Settle

Bookings and payment events become the source material for epoch-based underwriting rather than being buried in an app-only database.

Underwrite

Investors follow epoch pricing, bookable square metres, and SQMU-R token holdings while the underlying liquidity stays grounded in an audited ERC-4626 vault.

Investor story

SQMU-R is the visible token layer for epoch participation.

At a high level, r3nt by SQMU is designed so investors can follow rental underwriting through protocol-defined epochs instead of opaque spreadsheets or verbal updates. SQMU-R is the wallet-held, non-transferable token that makes that participation visible.

Visible in the wallet

The token is meant to make epoch participation legible without flattening everything into a generic vault balance.

Tied to a specific epoch

Each holding represents a protocol-defined epoch position rather than an endlessly rolling, anonymous ownership marker.

Non-transferable by design

The product is being shaped around underwriting participation, not a secondary-market trading narrative.

Grounded in Base

Wallet-native interactions, clear transaction ladders, and public contract behavior remain core to how the platform is being built.

Build in public

The product is still being tested. The narrative is ready to be public.

This page deliberately says less than a hype deck and more than a maintenance banner. It is here so the story, the intended users, and the direction of travel are visible while the product itself continues through local testing and mainnet readiness work.

That means some pieces are already clear and others are still being refined. We want that to read as honest progress, not as a finished launch pretending to be complete.

Clear already

Landlord, tenant, investor, and agent roles all matter.
Canonical booking and payment state belongs onchain.
SQMU-R is part of the external investor narrative.

Still being refined

Public launch timing and open access gates.
Final mainnet-ready narrative around underwriting flows.
Which public community channels go live first.

FAQ

Questions we expect this page to answer first.

Is r3nt by SQMU live on Base Mainnet today?

Not as a public, fully open marketplace yet. This page is the public narrative surface while wallet flows, listing creation, booking logic, and underwriting mechanics continue to be tested and refined.

What does SQMU-R represent?

SQMU-R is the wallet-visible, non-transferable token for a given underwriting epoch. It is meant to make participation legible without turning those positions into a secondary-market trading surface.

Why keep listing media offchain if bookings are onchain?

Long descriptions, images, and videos change more often and need better presentation than the chain should handle directly. The protocol keeps canonical rental state onchain and uses indexed metadata for the richer listing layer.

Who should follow the project right now?

Landlords exploring new distribution, tenants who care about clearer booking state, investors interested in epoch-based rental underwriting, and agents who understand local trust layers are all part of the intended market.

Follow the build

Join the waitlist.

Join with wallet on Base, or leave an email or Telegram.