Blend Capital

• Name: Blend Capital
• URL: https://blend.capital/
• Category: lending-protocol operating company / frontend-and-docs steward / Soroban credit-market interface operator
• Tags: stellar-ecosystem
• Summary: Blend Capital belongs in companies/ because the protocol is intentionally framed as an ungoverned lending primitive, but the practical operator shell is still named and centralized in places that matter. Script3 Ltd. controls the mainnet interface, the legal terms wrapped around that interface, the docs shell, the GitHub organization, and the public community / announcement surface users are told to follow. The useful question is not only how do isolated pools and backstops work? but who controls the easiest access path, can change or discontinue that path, and keeps shaping the public operating perimeter around Blend even while saying the contracts themselves are not company-upgradeable?
• What it does:
  • Operates the web-hosted Blend app at mainnet.blend.capital, the main user-facing path for borrowing, lending, backstopping pools, and claiming BLND
  • Publishes and controls the legal terms for that interface through Script3 Ltd., a Delaware corporation
  • Maintains the Blend docs shell and points users toward the Blend Capital GitHub organization as the best technical source of truth
  • Packages community and announcement flow through the public Discord and the @script3official social account referenced in the FAQ
  • Presents Blend as a headless hyperstructure with no DAO while still providing the branded interface, docs, code-hosting, and community shell most users will actually rely on
• Key claims:
  • The app terms say the App is a copyrighted work belonging to Script3 Ltd., a Delaware corporation, and that those terms govern access to the web-hosted interface at https://mainnet.blend.capital
  • The same terms say Script3 developed the App and contributed to the Protocol, but cannot take custody or control of assets deposited on the protocol and cannot upgrade or freeze the protocol smart contracts
  • The terms also say Script3 reserves the right to modify, suspend, or discontinue the App, in whole or in part, with or without notice, and that Script3 has no obligation to provide support or maintenance
  • Blend’s FAQ says there is no DAO and directs users to the Blend Discord and @script3official for further information, which is a good reminder that headless governance rhetoric still sits next to a very real company-run communications surface
  • The technical docs explicitly tell readers to use the Blend Capital GitHub for a better understanding of the protocol, reinforcing that repo stewardship and docs authority remain part of the practical operator boundary
• Whitepaper: The company note is not the right home for the lending design itself; use blend-capital and ../whitepapers/blend-capital-primary-sources-2026-05-08.md for the protocol mechanics.
• Sources:
  • https://blend.capital/
  • https://www.blend.capital/faq
  • https://docs.blend.capital/
  • https://docs.blend.capital/tech-docs/general
  • https://docs.blend.capital/github
  • https://mainnet.blend.capital/termsofservice

Internal linkages

• Product / protocol note: blend-capital.
• Useful company-side contrast where a branded interface still shapes access around an onchain system: sablier-labs and safe.
• Lending-market operator contrast where offchain judgment still matters even when the protocol story tries to stay modular: gauntlet and steakhouse-financial.

Protocol / company boundary

• Keep blend-capital on the protocol surface: isolated pools, standard-versus-owned pool design, backstop first-loss capital, utilization controls, interest-rate dynamics, and the deployer/backstop governance model inside each market.
• Use this company note for the named operator shell above that protocol: the Script3-run app, terms, docs, GitHub stewardship, and community / announcement surfaces that shape how most users actually reach and understand Blend.
• That split matters because who can change pool parameters inside a pool? and who controls the main access path, documentation, and legal shell around Blend? are different questions.

Control surface

• Practical leverage sits in interface availability, front-end transaction rendering, docs framing, repo stewardship, public announcements, and the legal terms users accept when they rely on the official Blend app.

• The limit is important too: Script3 says it cannot custody user assets and cannot upgrade or freeze the protocol contracts. That means the company is not the entire Blend story.

• But the company boundary still matters because most users will meet Blend through Script3-controlled software, docs, repos, and support/community channels long before they reason directly from Soroban contracts.

• Last reviewed: 2026-08-12 UTC