From Lease to Onchain: How r3nt Encodes Rental Agreements

Introduction

A rental agreement is a legal contract that defines the relationship between landlord and tenant: monthly rent, payment due dates, security deposit, maintenance obligations, renewal options, and termination conditions. In the traditional world, this agreement exists as a PDF or a paper document, signed by both parties and stored in filing cabinets or cloud drives. Its enforcement relies on trust, manual reminders, and, when disputes arise, the slow and expensive machinery of courts and lawyers.

The r3nt protocol by SQMU transforms this static document into a living, executable smart contract that automatically enforces the agreed terms. The encoding process takes the essential clauses of a lease – those that can be expressed as deterministic rules – and translates them into code that runs on the blockchain. Once encoded, the lease becomes self‑operating: rent payments are verified and distributed automatically, late fees are calculated and applied without human intervention, security deposits are held in transparent escrow, and renewal or termination logic executes according to predefined conditions.

This article provides a step‑by‑step guide to encoding a rental agreement within the r3nt protocol. It explains which lease terms are amenable to onchain representation, how the encoding process works in practice, and what landlords, tenants, and agents need to prepare. For a broader understanding of the r3nt protocol, refer to the r3nt documentation. For a detailed walkthrough of how r3nt works, see the how r3nt works section.

What Can Be Encoded – And What Cannot

Not every clause in a lease can be translated directly into smart contract code. Subjective or discretionary provisions – such as “tenant will maintain the property in good condition” or “landlord will make reasonable efforts to repair” – require human judgment and are not suitable for automation. However, the majority of economically significant and objectively verifiable terms can be encoded.

Encodable Lease Terms

Lease Element	Onchain Representation
Monthly rent amount	Integer value in stablecoin units (e.g., 2500 USDC)
Payment due date	Block timestamp or calendar date (e.g., 1st of each month)
Grace period	Number of days after due date before late fee applies
Late fee	Fixed amount or percentage of rent, calculated automatically
Security deposit amount	Stablecoin amount held in escrow contract
Deposit release conditions	Conditions encoded as time‑based or oracle‑triggered (e.g., “after lease end, release unless landlord files claim within 14 days”)
Lease duration	Start and end block timestamps
Renewal options	Boolean flag with notice period (e.g., “tenant may renew for 12 months if notice given 30 days before end”)
Termination penalties	Fixed amount or percentage of remaining rent due upon early termination
Authorised payment wallet	Whitelisted wallet address(es) for tenant

Non‑Encodable (Off‑Chain) Terms

Maintenance responsibilities and quality standards.
Dispute resolution procedures (though the contract can trigger a mediation oracle).
Pet policies or noise restrictions.
Any term that requires subjective assessment.

In practice, the encoded lease is paired with a traditional legal agreement that incorporates the smart contract by reference. The legal document defines the full set of rights and obligations, while the smart contract automates the financial and payment‑related clauses. This hybrid approach ensures legal enforceability while maximising operational efficiency.

Step‑by‑Step: Encoding a Rental Agreement in r3nt

The encoding process is typically performed by an r3nt agent – a licensed property manager, broker, or tokenisation service provider – using the agent dashboard. However, landlords with technical expertise can also encode leases directly through the Base web app or Farcaster mini‑app.

Step 1: Prepare the Lease Documentation

Before any encoding begins, the landlord and tenant must agree on a standard lease agreement in their jurisdiction. This document should include all the terms that will later be encoded. The agent reviews the lease to ensure it is complete and compliant with local rental laws.

Key documents needed:

Signed lease agreement (PDF).
Property identification (address, area in square metres).
Landlord’s wallet address (where rent will be sent if not opting into r3nt).
Tenant’s wallet address (to be whitelisted for payments).
Deposit amount and bank account (if not using onchain escrow).

Step 2: Input Lease Data into the Dashboard

The agent logs into the r3nt agent dashboard and selects “New Lease Encoding”. A form appears with fields corresponding to the encodable terms:

Property details: Select the tokenised property (already registered in the SQMU standard) or create a new property record.
Tenant information: Enter tenant’s name, email, and wallet address. The dashboard will trigger a KYC/AML check if required.
Financial terms:
- Monthly rent (stablecoin and amount).
- Payment due date (e.g., “1st of each month”).
- Grace period (e.g., 5 days).
- Late fee (e.g., “$50 or 5% of rent”).
- Security deposit (amount and release conditions).
Duration and renewal:
- Start date and end date.
- Renewal options (automatic or manual, notice period).
- Early termination fee (if any).
Distribution rules:
- If landlord opts into r3nt: select the underwriting epoch or request a new epoch.
- If landlord does not opt in: provide the landlord’s wallet address for direct rent distribution.

The dashboard validates the inputs (e.g., ensuring dates are in the future, amounts are positive) and provides a summary.

Step 3: Hash and Anchor the Legal Document

To create a verifiable link between the off‑chain legal agreement and the onchain smart contract, the dashboard computes a cryptographic hash (SHA‑256) of the lease PDF. This hash is stored in the smart contract’s Lease Registry. Anyone can later verify that the PDF matches the hash, proving that the onchain contract corresponds to a specific legal document that was not altered after signing.

The agent uploads the PDF to a secure storage (e.g., IPFS or a private server) and records the URL in the dashboard. The hash is stored onchain; the PDF itself remains off‑chain to save gas costs.

Step 4: Generate the Smart Contract Code

Based on the input data, the dashboard generates the configuration for the r3nt rental contract. r3nt uses a factory pattern: a generic RentalContract.sol is deployed for each lease, with parameters passed to the constructor. The generated parameters include:

Landlord wallet address (or epoch vault address).
Tenant whitelist (one or more addresses).
Rent amount, due date, grace period, late fee.
Deposit amount and escrow conditions.
Start and end timestamps.

The dashboard also generates the necessary ABI (Application Binary Interface) and deployment bytecode.

Step 5: Deploy the Smart Contract

The agent (or landlord) connects their wallet to the dashboard and signs a transaction to deploy the RentalContract to the chosen EVM chain (Arbitrum or Base). The deployment transaction costs a small amount of gas (typically less than $1 on layer‑2 networks). Once confirmed, the contract receives a unique address.

The dashboard records this address and automatically populates the Lease Registry with the lease hash, contract address, and metadata.

Step 6: Whitelist the Tenant’s Wallet

The tenant’s wallet address must be added to the contract’s whitelist before they can make payments. The agent (or landlord) calls the addToWhitelist function on the rental contract, signing a transaction that includes the tenant’s address. This step can be done immediately after deployment or after the tenant completes KYC.

Step 7: Notify the Tenant and Provide Access

The tenant receives an email or notification from the dashboard with:

A link to view the lease on a block explorer (e.g., Arbiscan).
A link to the r3nt interface (Base web app or Farcaster mini‑app) where they can make payments.
Instructions for connecting their wallet and authorising the first payment.

The tenant can now see their lease terms, payment schedule, and deposit status in the interface. They do not need to understand the underlying smart contract.

Step 8: Activate the Contract

The contract becomes active at the start timestamp. The tenant’s first rent payment is due on the first due date after activation. The smart contract automatically begins monitoring payments and executing distribution logic.

What Happens After Encoding: The Live Lease

Once the contract is active, the following processes run automatically:

Monthly Rent Payment

On or before the due date, the tenant sends the exact rent amount (e.g., 2,500 USDC) to the rental contract’s address. The contract’s receive or payRent function:

Validates the amount.
Checks that the sender is whitelisted.
Compares the block timestamp to the due date.
If on time: transfers the rent to the landlord (or epoch vault) and emits a PaymentReceived event.
If late: calculates late fee, adds it to the next month’s obligation, and records the late payment.

Security Deposit Management

The tenant transfers the deposit amount to the escrow contract at the start of the lease. The escrow holds the funds until the release conditions are met. At lease end:

If no claim is filed within the notice period, the contract automatically returns the deposit to the tenant.
If the landlord files a claim (e.g., for damages), the escrow holds the funds until a resolution is reached (via oracle or off‑chain agreement).

Renewal and Termination

Renewal: If the lease includes an automatic renewal clause, the contract extends the end timestamp by the renewal period, provided no termination notice was received before the deadline.
Early termination: If the tenant terminates early, the contract calculates the termination penalty (e.g., two months’ rent) and deducts it from the deposit or sends a bill to the tenant.

Investor Distributions (if opted into r3nt)

If the landlord has opted into r3nt, the rental contract sends each payment to the epoch vault rather than to the landlord. The vault then distributes the rent pro‑rata to SQMU‑R token holders. The landlord receives an upfront lump sum at the beginning of the lease, as described in the epoch‑based underwriting article.

Practical Example: Encoding a One‑Year Apartment Lease

Consider a residential apartment in Dubai with the following lease terms:

Monthly rent: 8,000 AED (represented as 2,180 USDC, assuming exchange rate).
Lease duration: 12 months, starting 1 June 2026.
Payment due date: 1st of each month.
Grace period: 5 days.
Late fee: 5% of monthly rent.
Security deposit: 8,000 AED (2,180 USDC), refundable at end of lease if no damage.
Landlord opts into r3nt for upfront payment.

Encoding steps:

Agent uploads the lease PDF, computes hash 0x7a3....
Agent inputs rent amount (2180 USDC), due date (1st), grace period (5 days), late fee (5%).
Agent enters landlord’s wallet address and tenant’s wallet address.
Agent selects an existing epoch or creates a new epoch for this lease.
Dashboard generates the rental contract configuration.
Agent deploys the contract to Arbitrum (gas cost ~$0.50).
Tenant’s wallet is whitelisted.
Tenant receives access link.

Result: On 1 June 2026, the contract becomes active. The tenant pays 2,180 USDC via the Base web app. The contract validates, sends the payment to the epoch vault, and the vault distributes it to investors. The landlord already received an upfront payment of approximately 23,000 USDC (discounted 12‑month rent) at the start of the lease. The tenant’s payment history is recorded onchain, and the deposit is held in escrow.

Benefits of Encoding Rental Agreements

For landlords, tenants, and agents, encoding leases brings tangible advantages:

Stakeholder	Benefit
Landlord	No manual rent collection, automatic late fees, reduced tenant default risk (if opted into r3nt), transparent payment history.
Tenant	Clear payment schedule, instant receipts, deposit transparency, no need to remind landlord of payment.
Agent	Recurring fee opportunities, reduced administrative overhead, ability to manage multiple leases from a dashboard.
Investor	Direct visibility into underlying lease terms, predictable yield from encoded contracts.

Limitations and Considerations

While encoding greatly improves efficiency, it is not a panacea. Landlords and tenants should be aware of:

Gas costs: Each transaction (deployment, payment, distribution) incurs network fees, though these are very low on Arbitrum and Base.
Technical requirements: Tenants need a wallet and some familiarity with stablecoins. Non‑technical users may require assistance.
Legal enforceability: The smart contract supplements, not replaces, the legal lease. Disputes over non‑financial terms still require traditional resolution.
Oracle dependency (optional): Some conditions (e.g., “deposit release upon inspection”) require an oracle, introducing a trust assumption.

Getting Started with Lease Encoding

Landlords and agents interested in encoding rental agreements can begin by:

Familiarising with r3nt: Read the r3nt overview and how r3nt works.
Tokenising the property: Ensure the property is tokenised under the SQMU standard (1 token = 1 m²).
Joining the waitlist: Sign up at r3nt.sqmu.net to receive early access.
Partnering with an agent: For landlords without technical expertise, working with an r3nt agent simplifies the process.

The r3nt protocol is designed to make lease encoding as simple as filling out a web form. The underlying complexity is hidden, but the benefits are fully realised.

Conclusion

Encoding a rental agreement into a smart contract transforms a static, paper‑based obligation into a dynamic, self‑executing financial instrument. The r3nt protocol provides a structured, step‑by‑step process for landlords and agents to convert traditional lease terms into onchain code, automating rent collection, late fees, deposit escrow, and investor distributions.

This encoding is not merely a technical exercise; it is a fundamental improvement in the efficiency and transparency of rental markets. Landlords save time, tenants gain clarity, and investors access predictable yield. As more leases move onchain, the rental process becomes faster, cheaper, and less prone to dispute.

To learn more about encoding rental agreements with r3nt, visit the r3nt documentation and explore the how r3nt works section. For assistance with your first encoded lease, contact an r3nt agent or join the waitlist.

SQMU – Tokenised Real Estate

Leave a ReplyCancel reply