01
Bitcoin
Settlement anchor and long-term collateral thesis.
Build Bitcoin liquidity in public.
uLend is being built as a multichain lending and borrowing market, with Bitcoin as the settlement anchor. This record shows what is live, in progress, planned, and conditional.
LiveIn progressPlannedConditional
Announce outcomes, not aspirations.
Every public milestone needs a named owner, an observable completion condition, and a clear statement of what remains outside uLend’s control.
Bitcoin is the anchor. The rest has a job.
The product story stays simple even when the build is not: users access liquidity without selling their Bitcoin, while settlement, execution, commercial delivery, and public proof stay distinct.
02
SCL
Deterministic execution path for the Bitcoin-native lending track.
03
Orobit
Engineering ecosystem supporting the build and integration path.
04
SQRL
Commercial Layer 2 path for product delivery and institutional workflow.
A roadmap with gates, not vague dates.
01In progress
Foundation and proof
Make the lending path safe, intelligible, and observable.
Product controls, clear route selection, contract and treasury disclosure, audit and legal readiness, and public measurement of what users can actually do come before growth claims.
- Risk, eligibility, and market-availability disclosures
- Product and treasury evidence that separates deployed code from market readiness
- A shared public narrative across uLend and uEnd
02Planned
Initial exchange access
Open the Tier 2 listing window with operational discipline.
Target window: August 2026. The goal is orderly initial exchange access backed by clear token information, custody, liquidity planning, community communications, and user support.
- Exchange acceptance and venue due diligence
- Technical, custody, liquidity, legal, and communications readiness
- Official venue announcement before any token is described as listed or available
03In progress
Bitcoin lending path
Bring the SCL, Orobit, and SQRL build path into the product.
The architecture is being sequenced around a Bitcoin-native lending and borrowing experience: Bitcoin as the anchor, SCL as the execution route, Orobit as the engineering ecosystem, and SQRL as the commercial Layer 2.
- Integration design and product specification
- Risk, custody, and settlement controls before public user flows
- Clear separation between connected markets and newly released product paths
04Conditional
Further venue expansion
Build toward MEXC and LBank only when the prerequisites are met.
MEXC and LBank are future venue targets in the listing plan. They are not announced uLend listings. Any expansion depends on each venue’s acceptance, liquidity and legal readiness, and a public announcement from the venue and uLend.
- No venue, date, price, or trading pair is confirmed by this roadmap
- Market-access communications follow official exchange notices
- Community updates state the evidence, timing, and limitations clearly
Collaboration is part of delivery, not a substitute for it.
SQRL
Commercial Layer 2 build path
uLend is aligning its Bitcoin-native product narrative and commercial delivery path with SQRL. User-facing availability depends on released scope and completed operational controls.
Orobit
Engineering ecosystem
Orobit supports the engineering context around the SCL and Bitcoin track. The public roadmap will track what is integrated and usable, not architectural intent alone.
Nimbus
Capital and liquidity pathway
A proposed strategic facility is intended to support capital, collateral, and liquidity planning around the listing sequence. It is under discussion and is not a completed funding, transfer, or exchange deal.
Planned does not mean promised.
ULEND is a utility and participation token, not a claim on company or protocol revenue. This roadmap does not offer tokens, predict price, guarantee liquidity, promise a listing, or confirm a partnership beyond the evidence stated above.
Before acting on product or token information, read the token economics and risk disclosure. Official release notes replace a roadmap item only when it has shipped or been formally announced.