Core concepts
A lien is collateral bound to a debt. Encumbra makes that binding enforce itself.
Everything in Encumbra is a lien: a record that an asset backs a debt. The owner sets the terms when opening it, and the creditor accepts them by charging against the line. The difference from a traditional lien is where enforcement happens. Here it is on-chain and automatic, up to the value of the collateral.
The lifecycle
An owner escrows a title and a creditor finances or leases against it. While payments are current the lien is in good standing and the asset operates.
- Miss the due date and the asset disables itself.
- A past-due lien can be liquidated immediately, with no waiting period. A keeper who liquidates a title-backed lien buys the title at its declared value, and the title transfers on-chain.
- A late installment payment (
payInstallment) cures the lien and brings the asset back, if nobody has liquidated it first. A plainrepaypays debt down but does not move the due date.
| State | Asset runs? | Can be liquidated? |
|---|---|---|
| Good standing | Yes | No |
| Frozen | No | Only if past due or under water |
| Past due | No | Yes, if there is debt |
| Under water | Yes, until liquidated | Yes |
| Liquidated or closed | No | No, it is finished |
Self-enforcement
The novel part is that the collateral obeys the lien. A financed device polls one view, isAssetEnabled(id), and runs only while the lien is active, not frozen and not past due. The view ignores collateral health, so an under-water lien keeps running until a keeper liquidates it.
- Device pollsisAssetEnabled(id)
- Returns trueactive, not frozen, not past due
- The asset runs
- Device pollsisAssetEnabled(id)
- Returns falseblock.timestamp > dueDate
- The machine powers itself offno repo crew
This is Szabo's idea of property that stops working on default, implemented as a single on-chain predicate rather than a lawsuit.
Standing and installments
How a lien stays in good standing depends on what it finances.
Leases
- A schedule is an installment amount and a period.
- Paying an installment rolls the due date forward and keeps the asset enabled.
- The schedule is set once. It cannot be rewritten to dodge a past-due default.
Agent credit
- The lien tracks a rolling balance against a credit limit.
- Every charge is bounded by the limit the owner authorized.
- Repaying frees up headroom to draw again.
Default and the liquidation waterfall
On default, liquidation is permissionless. Anyone can trigger it and be paid a keeper reward.
- Lien becomes liquidatablepast due, or under water
- Anyone calls liquidateliquidate or liquidateAsset
- Waterfall pays outkeeper, creditor, protocol, owner
The proceeds then flow through a fixed waterfall, each step paid from what is left:
- 1Keeper rewardPaid off the top, which is designed to keep even a deeply under-water lien worth liquidatingsenior
- 2CreditorPaid from what remains after the keeper reward, up to the outstanding receivable
- 3Protocol feeThe penalty plus any accrued usage fee
- 4Owner surplusThe borrower's remaining equity. Bad debt appears when collateral cannot cover the keeper reward plus the receivable
MAX_FEE_BPS. The cost is that the creditor can lose up to the keeper reward even when collateral is worth more than the debt. The contract flags this ordering as intentional but pending a product-owner decision, so it is a policy choice that may be revisited.For the fee rates and a worked example with real numbers, see Fees & waterfall.
Collateral models
One contract supports two shapes of collateral, so the book can span physical assets and pure credit at once.
Whole asset
- One non-fungible token title, escrowed when the lien opens.
- On default, a keeper buys it at the appraised value and the title transfers on-chain. The owner declares that value and the contract does not verify it.
- Fits an indivisible machine, vehicle or deed.
Fungible
- Collateral and debt are token balances, liquidated in-kind.
- Backs agent credit lines and any divisible collateral.
Pricing and oracles
How a lien's health is measured depends on what backs it and what it owes.
| Situation | How value is read |
|---|---|
| Collateral and debt are the same token | Value is read directly |
| Collateral and debt are different tokens | A price oracle is required. A cross-token lien cannot be opened at a naive parity |
| A non-fungible token lease | Priced at its appraised value, declared by the owner and not verified by the contract |
The oracleOracle. The price source used when collateral and debt are different tokens. On the testnet it is a placeholder, not a production price feed. is a single address that the admin can replace at any time, with no delay and no event. A replaced oracle reprices every open cross-token lien. That is why the admin's oracle control matters, and why per-lien oracle binding is planned for v1. It is not built.
The roles
Five parties interact with a lien. Each has a clear job and a clear limit.
| Role | What they do | Limit |
|---|---|---|
| Owner | Posts collateral and authorizes the terms. Consents to credit by setting the limit. | Can close a lien only once its debt is zero. |
| Agent / drawer | Draws on the line (agent credit) or operates the leased asset. | Draws are capped by the credit limit. |
| Creditor | Finances or leases against the collateral and records charges. | Charges cannot exceed the limit. On default, paid after the keeper reward and ahead of the protocol. |
| Keeper | Anyone who triggers liquidation of a defaulted lien. | Is paid the senior reward, capped by MAX_FEE_BPS. |
| Admin | One address today. Sets the three fee rates, the treasury address and the price oracle. | Each fee is capped at 10%. No function lets the admin move escrowed collateral directly. The admin can swap the price oracle with setOracle, which controls the under-water check, and that call emits no event. There is no timelock today. See Security and Risks. |