RFPs

From Local Area Network
Logos RFP Program
What it is: Grants for builders to deliver set pieces of work on the Logos stack
Run by: Logos
Founded:
Status: Active
Licence: Funded work is open source under MIT and Apache 2.0 unless agreed otherwise
Join or copy: Read an open RFP, then submit a proposal as a GitHub issue

The Logos RFP Program gives grants to independent developers and teams. Each Request for Proposals (RFP) describes a tool, piece of infrastructure, application or integration that the Logos ecosystem needs. Builders answer with a proposal. Funded projects can range from prototypes to near-production applications.

Focus areas

Proposals should fit one of three categories:

  • Developer tooling and infrastructure
  • Applications and integrations
  • Ecosystem and community enablement

Each RFP has a size tier, from XS to XL. For example, RFP-005 is tier L, with an estimated six months of work for a team already working on LEZ.

How to apply

  1. Browse the open RFPs in the RFP repository or on the Builders Hub.
  2. Read the full RFP file in the RFPs folder.
  3. Open a proposal issue using the template. Pick the RFP from the list.
  4. Use your proposal issue for questions. Logos posts updates there or through your contact details.

The proposal template asks for:

  • project name, team name and a contact
  • team members, their links, roles and status (full-time, part-time or contractor)
  • a summary and a technical approach
  • milestones, payouts and a timeline
  • the total budget requested, in US dollars
  • relevant experience and a plan for after delivery
  • agreement to the RFP terms and to open-source licensing

How a proposal is reviewed

  • Timing. Logos reviews proposals weekly and usually replies within 14 days.
  • Criteria. Proposals are judged against the RFP itself. Logos may also weigh technical feasibility, ecosystem impact, budget, team experience, compliance and reputational risk.
  • Dialogue. Logos may ask questions or suggest changes to milestones, budget or scope.
  • Selection. A notice that a proposal is going forward is not binding. A grant exists only once a written Grant Agreement is signed. Logos may ask for identity, compliance or financial details first.
  • Milestones. Work runs in milestones set in the Grant Agreement. Each milestone of an accepted proposal is tracked as its own GitHub issue so engineers can review it on its own.
  • No reasons owed. Logos does not have to explain a decision.

An example of milestone review is the RFP-003 atomic swaps grant, awarded to Gateway.fm. Its review thread splits the work into seven milestones and records each decision. The reviewer writes that acceptance means "the code does what the milestone asks on LEZ testnet". Security is judged by a third-party audit in the last milestone.

Open RFPs

Status as given in the repository on 9 October 2026.

RFP Title Tier Status Deadline
RFP-005 Multisig and Coordination L Open 16 October 2026
RFP-012 Curated Lending Vaults L Closed, reopening soon None set
RFP-014 Liquidation and Auction Engine L Closed, reopening soon None set

RFP-005: Multisig and Coordination

RFP-005 asks for an audited M-of-N multisig program on LEZ, private by default. It comes with an encrypted coordination room for each multisig, built on the Logos chat module. The deliverables include a Logos module API, a command-line tool and a Basecamp mini-app. Proposals must name at least one tier-1 audit firm and include the audit in the budget. Benchmarks must use real proving. The forum announcement was posted on 30 September 2026 and submissions close on 16 October 2026.

Closed RFPs

RFP-001 Admin Authority Library, RFP-002 Freeze Authority Library, RFP-003 Atomic Swaps with LEZ, RFP-004 Privacy-Preserving DEX, RFP-008 Lending and Borrowing Protocol, RFP-013 Reflexive Stablecoin Protocol, RFP-015 Token Launchpad: Bonding Curve, RFP-016 Token Launchpad: LBP, RFP-017 Privacy-Preserving Token Vesting, RFP-019 On-Chain TWAP Oracle and RFP-020 RedStone Off-Chain Oracle Adaptor for LEZ.

RFP or λPrize?

An RFP grant is agreed before work starts and is paid against milestones. A λPrize is claimed after the work is built and in use.

See also

Sources

Page status: Usable. Stub · Outline · Usable · Guide · Star. Anyone can improve this page and change its status.