Context
Meru appears in Stellar ecosystem listings tagged as lending on mainnet, but hasn't been assessed against the independence bar. It's the only known outstanding candidate that could slot into the existing taxonomy with no methodology work — if it clears.
Two protocols have already been investigated and rejected on this bar: YieldBlox turned out to be a community-managed pool on Blend V2 rather than an independent protocol, and Templar's lending state lives on NEAR with only its price oracle native to Stellar. Meru gets the same treatment. The evaluation is the work here; the adapter only follows if it passes.
Scope
In scope: confirm from Meru's own contracts and documentation whether it is an independently-scoreable, native-Soroban lending protocol on mainnet. If it clears, implement the adapter against the existing Adapter interface and five-factor taxonomy.
Out of scope: writing any scoring logic before the independence check passes. If it fails, the deliverable is the documented finding, not code.
Acceptance criteria
Difficulty
Hard — design decision required before code
Notes / open questions
The independence check is the majority of the work. The scoring code is comparatively mechanical once the interface is understood — the Blend and K2 adapters are both available as reference implementations covering two genuinely different on-chain shapes.
Context
Meru appears in Stellar ecosystem listings tagged as lending on mainnet, but hasn't been assessed against the independence bar. It's the only known outstanding candidate that could slot into the existing taxonomy with no methodology work — if it clears.
Two protocols have already been investigated and rejected on this bar: YieldBlox turned out to be a community-managed pool on Blend V2 rather than an independent protocol, and Templar's lending state lives on NEAR with only its price oracle native to Stellar. Meru gets the same treatment. The evaluation is the work here; the adapter only follows if it passes.
Scope
In scope: confirm from Meru's own contracts and documentation whether it is an independently-scoreable, native-Soroban lending protocol on mainnet. If it clears, implement the adapter against the existing
Adapterinterface and five-factor taxonomy.Out of scope: writing any scoring logic before the independence check passes. If it fails, the deliverable is the documented finding, not code.
Acceptance criteria
*Safetyfactors populated from real on-chain data, each anchored to Meru's own protocol parameters rather than Blend's or K2's numbersROADMAP.mdunder investigated-and-skipped, with the specific reason, same as YieldBlox and TemplarMETHODOLOGY.mdupdated with any protocol-specific anchoring decisionsDifficulty
Hard — design decision required before code
Notes / open questions
The independence check is the majority of the work. The scoring code is comparatively mechanical once the interface is understood — the Blend and K2 adapters are both available as reference implementations covering two genuinely different on-chain shapes.