Why
A self-description changed, and self-descriptions are where revenue models announce themselves early. Use Ethereum cheaply sells transactions and earns per transaction. Run your chain here sells space and earns rent. The second is a better business — recurring, less elastic, harder to leave — and it is a different relationship with whoever builds on top. Tenants and users are not the same thing, and the shift is visible in the sentence before it is visible in the accounts.
The convergence is what makes it worth a card rather than a note. headless-exchange-engines describes an interop project selling matching, clearing and settlement so others can run venues on it. This is an L2 selling settlement space so others can run chains on it. Different starting points, one destination: sell the place, not the tool. When two competitive positions arrive at the same model independently, it is usually because the tool has commoditised and the place has not.
Which reframes a decision this project actually has to make. Which chain do we launch on looks like a technical question — throughput, fees, tooling, ecosystem. Under a rent model it is a commercial negotiation, and the terms are the ones any tenant should ask about: who controls the sequencer, how are fees split, and what does leaving cost. Those three determine margin more than gas prices do, and none of them appears in a benchmark.
The exit cost is the term to price first, because it is the one nobody markets. Migration is quoted in engineering weeks, which understates it — liquidity does not migrate with the code, integrations have to be re-agreed, and users have to be told to move. A host that is cheap to join and expensive to leave has priced the second half into the first, and the honest way to compare two offers is to compare them at the moment you want to go.
How it works
The lease term sheet
| Term | The question | Why it is margin, not architecture |
|---|---|---|
| Sequencer control | Who orders transactions, and can they censor or reorder? | Ordering rights are MEV rights; whoever holds them holds a claim on your flow |
| Fee split | What share goes to the host, and who can change it? | A split that the host can revise unilaterally is not a price, it is an option |
| Exit cost | Engineering weeks, plus liquidity that will not follow, plus integrations to re-agree | The only term that grows the longer you stay |
| Host failure | What happens to open positions if the host stops operating? | For a settlement product this is not a business risk, it is a correctness question |
Two pitches, one destination
| Was selling | Now selling | Earns from | |
|---|---|---|---|
| L2 / Offchain Labs | Cheap blockspace on Ethereum | Somewhere to run your own chain | Rent on settlement space |
| Interop / LayerZero ATLAS | Messaging between chains | An engine to run your own venue | The venues built on it |
Both moved from selling a tool to selling a place, which usually means the tool stopped being scarce. For a tenant the practical consequence is identical either way: the thing being negotiated is no longer performance, it is control.
The row to price first
Exit. Everything else is quoted openly because it helps the host compete; exit cost is the one term that only matters after you have committed. Estimate it honestly and it changes the ranking more often than fees do: a host that is 30% cheaper per transaction and locks liquidity behind a bridge nobody else supports is not cheaper. cross-border-rail-interop reached the same conclusion about payment corridors — governance, not throughput, decides which rail wins — and a lease is governance written as a contract.
Where it lands in Jayverse
- Devnet: fill the lease term sheet before picking an OP-Stack host. Before committing devnet's later OP-Stack L2 to any host, fill four rows — who controls the sequencer, how fees split and who can revise it, exit cost in engineering weeks plus liquidity that won't follow, and what happens to open positions if the host stops operating — and price the exit row first.
- Verex/Bridge: add a host-failure row to the design doc. For a settlement product, "what happens to open Verex positions or bridge state if the host stops operating" is a correctness question, not a business risk — write the answer down before devnet depends on any rented sequencer.
- Devnet: compare hosts at the moment of leaving, not joining. When evaluating any settlement-space host (an OP-Stack provider, an interop engine), compare total cost including migration and re-agreed integrations, since a host that's cheap to join and costly to leave has already priced the difference into the join fee.
Key expressions
| Expression | 뜻 · 쓰이는 자리 |
|---|---|
| pitch (n.) | (영업용) 홍보 문구, 제안 · 회사가 자신을 어떻게 소개하는지 말할 때. "An L2's pitch moved from cheap blockspace" |
| term sheet | 조건 요약서, 계약 조건표 · 협상 전에 핵심 조건들을 정리한 문서. "the deliverable is a term sheet" |
| price (v.) | 값을 매기다, 가격을 산정하다 · 눈에 안 보이는 비용을 수치화할 때. "Price the fourth row first" |
| commoditise | 범용재화되다, 흔해져서 차별성을 잃다 · 한때 희소했던 기술이 누구나 쓰는 것이 될 때. "usually because the tool has commoditised" |
| elastic | (수요·가격에) 탄력적인 · 경제학 용어로, 조건이 바뀌면 쉽게 변하는 성질. "recurring, less elastic, harder to leave" |
| claim on | ~에 대한 권리, 청구권 · 누군가의 자산이나 흐름에 대해 갖는 권한을 말할 때. "holds a claim on your flow" |
| tenant | 세입자, 입주자 · 플랫폼에 자기 서비스를 올려 쓰는 쪽을 비유할 때. "Tenants and users are not the same thing" |
| unilaterally | 일방적으로 · 상대 동의 없이 한쪽이 조건을 바꿀 수 있을 때. "a split that the host can revise unilaterally" |
| price ... into | ~을 (가격에) 미리 반영하다 · 나중에 들어갈 비용을 처음 가격에 녹여 넣었을 때. "has priced the second half into the first" |
| MEV | 최대 추출 가능 가치(Maximal Extractable Value) · 트랜잭션 순서를 정하는 자가 얻을 수 있는 초과 이익, 시퀀서 통제권의 핵심 쟁점. "Ordering rights are MEV rights" |
| LayerZero | 크로스체인 메시징 프로토콜(인터옵 프로젝트) · 메시징을 팔던 데서 남들이 자체 벤처를 구축하는 엔진을 파는 쪽으로 옮겨간 예로 언급됨. "LayerZero's ATLAS announcement of 2026-08-26" |
| ATLAS | LayerZero가 발표한 신규 제품 · 메시징을 넘어 남들이 자체 벤처(venue)를 구축할 수 있게 해주는 엔진으로 소개됨. "An engine to run your own venue" |
| Offchain Labs | Arbitrum을 개발한 회사 · 저렴한 블록스페이스 판매에서 '너의 체인을 여기서 운영하라'로 전략을 바꾼 L2 업체로 언급됨. "Offchain Labs' shift toward custom and app-specific chains" |