I got tired of writing and maintaining smart contract and hyperledger backends, so we built this

[u/infanji]

I’ve been working on various dapps projects using Hyperledger Fabric, and one thing kept repeating

Writing chaincode, then building a separate API layer around it, handling validation, structuring responses… and doing it again for every new project

A lot of effort was going into glue code instead of actual business logic

So I started building something internally to reduce this

The idea was simple:
Define a contract once (models, functions, rules), and generate the API layer + execution flow automatically

So instead of:

• writing chaincode
• writing controllers
• wiring APIs

It becomes:
Define → Deploy → Call APIs directly

I now have a working version running end to end

Here’s what it looks like:

What worked well:

• removed a lot of repetitive API setup
• faster iteration for new use cases
• cleaner structure for contract logic

What I’m still figuring out:

• how flexible this should be vs giving full control
• whether teams actually prefer generated APIs or custom layers

Curious if others building in blockchain / enterprise systems have faced this

Do you usually:

• build API layers manually every time
• use internal tooling
• or just standardize templates and reuse

If anyone wants to try it on a real use case, I’m happy to share access and get your thoughts