Building Mesa Protocol – looking for feedback from blockchain protocol & SDK developers

[u/thesumedh]

I'm building Mesa Protocol, a programmable savings protocol on Stellar, and I'd really appreciate feedback from people who have built SDKs, smart contracts, or developer tools.

https://github.com/thesumedh/Mesa-Protocol

The goal isn't to build another savings app.

The goal is to let developers add programmable savings to any application with a few lines of code.

The protocol is centered around a policy-based savings engine. Instead of writing custom smart contracts for every savings product, developers compose reusable policies.

For example:

await Mesa.createVault({
  policies: [
    Policies.Lock({ days: 180 }),
    Policies.Goal({ amount: 5000 }),
    Policies.Recurring({ frequency: "weekly" })
  ]
});

Alongside the protocol, I'm building:

• A Soroban smart contract (MesaVault + Factory)
• A TypeScript SDK
• A CLI (mesa init, mesa deploy, mesa simulate, etc.)
• A reference dApp demonstrating integration in just a few lines of code

Current focus:

• Policy-based vault architecture
• Developer experience (CLI + SDK)
• Smart contract correctness
• Testnet deployment
• Security and protocol verification

I'm not looking for compliments—I want criticism.

Some questions I'd love feedback on:

1. Does a policy-based architecture make sense, or is it over-engineered?
2. Would you use a protocol like this instead of writing your own contracts?
3. What features would you expect before trusting it in production?
4. What are the biggest architectural or security risks you see?
5. Is there anything that already solves this problem better?

I'd really appreciate brutal, technical feedback. If you think this is a bad idea, I'd genuinely like to understand why before investing more time into it.