Korean income real estate · on-chain settlement
The hard part is the settlement.
Moving money from a wallet into a Korean real-estate fund is nine steps, five counterparty roles and twelve to nineteen days. We drew the whole route, deployed four contracts, and built steps 03 and 07.
Nothing on this page is an offer of a security.
4 contracts deployed · 9 steps encoded · 8 checks per request · 12–19 day target
target 12–19 days
three appointments
● built · ◌ awaiting counterparty · ○ modelled
What the codebase contains2
Deployed, exercised and openable.
One product is live in this build — a tokenised interest in a Seoul Capital Area logistics asset, issued and redeemed by contracts anyone can open in a block explorer. The settlement path underneath it is the engineering.
Four contracts, live on Base Sepolia testnet.
0x814D…4295eView ↗0xd525…12bd9View ↗0xb88d…46c32View ↗0x0f77…cF7eView ↗Tokenising the asset is the easy part.
The settlement is the engineering.
Nine steps. Two are ours. Three are missing companies.
Steps 03 and 07 run on our contracts today. Steps 04–06 are not missing code — they are missing appointed counterparties: each has a specified role, an SLA target and a hand-off contract in the workflow data, so an appointment is a configuration change rather than a build. Full step table →
scroll →
On chain — built · Not appointed — awaiting counterparty · Modelled / recorded / testnet
Design targets, not measured performance. T+N is calendar days.3
Five counterparty roles — specified, not appointed.
Agent rail
OmniFlow builds the base rail for the agent economy.
An x402 payment rail an autonomous client can drive itself — discover, pay, verify, subscribe — over HTTP 402 and EIP-3009, through a self-hosted facilitator, exposed as four MCP tools. The rail is stateless by design: nothing about a request survives settlement.
Eight checks, every request
- scheme and network match
- recipient matches payTo
- value covers the price
- authorisation already active
- authorisation not expired
- signature recovers to the payer
- nonce not already used↗ chain read
- payer balance covers the value↗ chain read
Steps 02 and 03 are agent-executable; the rail halts where a human counterparty is required. Read the rail spec →
Four tiers, ascending risk. One is live on testnet.
Listed REIT Income
Listed Korean REITs held for distribution income; the lowest rung.
DocumentedKorea Logistics Income
Seoul Capital Area logistics held through a Korean real-estate fund.
Live · testnetSenior Development Credit
Senior secured lending against Korean development projects.
PipelineOpportunistic Credit
Higher-yield situational credit; the highest rung.
PipelineWe publish a yield only when it can be evidenced.
What we withdrew, and why
A tier publishes a yield only when the net figure survives debt, fees and withholding from sourced inputs of a single quarter.
One of four tiers clears it today. The other three are pipeline and publish no yield.
Illustrative underwriting inputs for candidate products that were not launched · RSquare Q2 2026, treaty rates as then applicable.5
What backs the 3.43%.
The engine is rent. A Seoul Capital Area logistics asset yields a 5.32% going-in cap; senior debt, fund fees and Korean withholding take it to an illustrative 3.43% net objective. Every input is dated, sourced, and shown below rather than summarised.
Korea Logistics Income
Live · testnetIllustrative objective, derived at 60% LTV from sourced inputs · for an asset OmniFlow does not own.
basis flips asset → equity · (5.32 × 100 − 4.93 × 60) ÷ 40 = 5.91
Sources: RSquare Q2 2026 — Seoul Capital Area logistics cap and senior debt, one source and one quarter · Bank of Korea base rate 2.75% from 2026-07-16 · Korea–Singapore treaty, dividend article.
Inputs dated 2026 Q2 · derivation and revision history →
Open it and check.
One appointment converts three modelled steps into two — it unblocks step 04, because the same counterparty class covers the conversion and the deposit leg. Steps 05 and 06 still await a remitting bank and a Korean receiving relationship. Every figure here is derived from a dated source you can check, and every step you cannot yet take is named with the company that has to fill it. The survey is done. What it needs now is counterparties.
Enquiries only. Nothing on this page is an offer of a security.
Status
Built and verifiable
- Four contracts deployed and exercised on Base Sepolia testnet, addresses above
- Nine workflow steps encoded as data, with owners, targets and document slots
- An x402 payment rail with a self-hosted facilitator and eight verification checks
- Four MCP tools, three free and one paid
- A published derivation for the one live tier, every input dated and sourced
Standing conditions
- Everything shown as live runs on the Base Sepolia testnet with a mock settlement token. There is no mainnet deployment.
- OmniFlow is pre-incorporation and holds no licence. The operating and fund entities described here are structures we intend to form.
- No assets, investors, revenue, partnerships, audit or token. No counterparty is appointed; each is named by role.
- Nothing about rail activity is persisted, so there is no request count, revenue figure or user number to report.
Notes
- An illustrative objective, never a guarantee, for an asset OmniFlow does not own. Not a forecast.
- Counts of what the codebase contains — facts about the source, not about usage or demand.
- Targets are design parameters for counterparties that do not yet exist, not measured performance.
- Withholding is published as a band — 3.63% at 10%, 3.43% at 15% central, 3.14% at 22% — because which rate applies depends on a structure that is not yet formed.
- Underwriting inputs for candidate products that were never launched, retained so the standard can be checked against the decision.
Nothing on this page is an offer of a security, a solicitation, or investment advice. Figures are illustrative and derived from stated sources; assumptions are marked as assumptions at the point they are used.