ERC-8348 Financial lease contract interface (Financial Lease)

Draft · Vaults & DeFi · created 2026-07-23

A jurisdiction-neutral interface for querying a lease contract's payment schedule, balance, arrears, default status, purchase option, and party assignment. It represents lessee status as an ERC-721 token, so portfolio transfer and securitization can use existing NFT infrastructure.

Why it is needed

Leasing is a globally significant credit instrument, but no ERC has defined how lease contracts should be queried on-chain. ERC-4907 covers only temporary usage rights for NFTs, not installments, interest, arrears, purchase options, or assignment. ERC-2615 adds lending and mortgage roles and security interests, but has no credit semantics such as schedules, index-linked units, arrears models, or purchase options. ERC-3475 standardizes only redemption-focused fungible debt instruments, not bilateral contracts with named parties, formal default, and asset collateral. Outside the EVM, ACTUS is a taxonomy for describing financial instruments as cash flow patterns, but it can only be read by adopting the entire taxonomy. Without a common interface, each issuer exposes its own custom contract, forcing integrators such as secondary markets, securitization vaults, auditors, and credit rating agencies to write separate custom adapters per issuer and country.

What to implement

In depth

Legal layer and parties

jurisdiction returns the applicable jurisdiction for the lease as a country code, and governingLaw returns the governing law as a string. agreementHash is a hash pointing to the off-chain contract, and assetReference is a string identifying the leased asset. lessor and lessee return the lessor's and lessee's addresses respectively, and the lessor must match the holder of the ERC-721 token whose tokenId equals the leaseId. agreementHash links on-chain state to the off-chain contract, but whether the token carries legal effect as ownership or a claim depends on each jurisdiction's legal framework.

Unit of account and conversion rules

The schedule is denominated in units of account and converted into a settlement asset (ERC-20). denomination returns the unit symbol and the oracle address; for fixed-amount leases, the oracle must be address(0) and both conversion functions must be identity functions. The conversion rate in conversionRateAsOf represents the number of settlement asset base units per 1e18 units of account. Rounding must not be biased in the caller's favor: convertToAssets, used to calculate the amount owed, must round up, while convertToUnits, used to reflect payments, must round down.

Two-stage model of arrears and default

InArrears is the objective fact that a payment deadline has passed unpaid, while InDefault is a legal act that must be explicitly declared by an authorized declarer, emitting DefaultDeclared. Default is curable: once arrears are cleared, the lease returns to a non-arrears status and DefaultCured is emitted. Completed, PurchaseExercised, and Terminated are terminal statuses, and terminal statuses cannot transition among each other except for the Completed to PurchaseExercised transition.

Arrears/penalty calculation as a function of elapsed time only

The amount returned by arrears() must be a function only of the payment schedule, the recorded payment history, and the time elapsed since each installment's deadline, and must not depend on the number or frequency of state-changing calls. Query functions must reflect state accrued as of the current block.timestamp, not as of the last time state was stored. Given the same schedule, payment history, and elapsed time, the arrears amount must be identical regardless of how many calls occurred in between. Penalty accrual must be measured from each installment's own specific deadline, and must not grant an implicit grace period starting from when the arrears were first observed on-chain.

Early termination

Termination reasons are distinguished by namespaced identifiers (TERMINATION_MUTUAL_AGREEMENT, TERMINATION_DEFAULT). Mutual termination requires active consent from both the lessee and the holder of lessor status (via a propose/accept procedure, etc.) and can be initiated from any non-terminal status. Termination due to default requires the lease to be in InDefault status, and is only possible after a configurable delay greater than zero has passed since the declaration. On termination, LeaseTerminated and TerminationRecorded must both be emitted, and economic figures such as balance, arrears, and penalties must not change after termination. The settlement method for remaining debt after early termination is out of scope for this standard.

Input freshness tracking

inputFreshness(leaseId, input) returns, for each input, the time it was observed off-chain (observedAt), the time it was recorded on-chain (reportedAt), and the declared tolerance (maxStaleness). The default input identifiers are INPUT_INDEX_OBSERVATION, INPUT_COLLECTIONS, INPUT_ARREARS_RECORD, INPUT_INSURANCE_STATUS, INPUT_ASSET_CONDITION, and INPUT_RESIDUAL_APPRAISAL. An input that has never been reported must return zero values rather than reverting. Only INPUT_INDEX_OBSERVATION feeds into values derived from conversionRateAsOf, and it is the only input that can revert a state-changing call. The rest are off-chain evidence uploaded by an authorized servicer that emit ServicingUpdated but do not affect balance or state calculations.

Payment-path liveness and the cure period

For index-linked leases, if the index observation is too old, calls requiring conversion such as pay() or exercisePurchaseOption() can fail. In this situation, even though the lessee cannot make payments, default-related actions (declaring default, termination for default, return of the collateral asset, etc.) must not proceed unless the index has remained non-stale for a cure period of G seconds (0 < G < maxStaleness). This determination must be based on the oracle's own on-chain verifiable record, not a timestamp supplied by the caller. Arrears and penalties continue to accrue during the cure period.

Optional extensions and Draft status

IFinancialLeaseAnchored links a lease to an asset registered in the ERC-8325 registry, and the chainId, registry address, and anchor identifier tuple must be either all zero or all populated. IFinancialLeaseAssetBound requires the collateral asset to be held in escrow while the lease is Active, InArrears, or InDefault; when the purchase option is exercised and canSettleAsset is true, settlement must occur simultaneously with payment; and return of the asset due to default is not automatically triggered merely by the InDefault state, but requires an explicit call from an authorized party. This EIP is still in Draft status, so its content may change or discussion may stall.

Things to watch out for

Original ERC · ← ERCs