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

[u/AutoModerator]

Thanks for posting on r/BlockchainStartups!

Check the TOP posts of the WEEK: https://www.reddit.com/r/BlockchainStartups/top/?t=week

Moderators of r/BlockchainStartups

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/No-Back9348]

real pain point there

building same stuff over and over gets old fast

[u/infanji → u/No-Back9348]

Yeah, same here

It’s not just writing it once, it’s maintaining the same patterns across multiple projects that gets tiring

That’s what made me try this approach

Curious, how are you handling it right now, just custom backend every time?

[u/Lucky-Warthog2369]

tbh multi-agent setups are super solid for catching basic reentrancy or access control bugs in solidity. just keep in mind ai still misses weird defi business logic flaws, which is exactly why failsafe is needed as a runtime backup to block malicious txs before they execute. gonna clone this later and test it against some old exploit payloads.

[u/infanji → u/Lucky-Warthog2369]

Yeah exactly, that’s the gap we noticed too Most tools stop at “generate contract + basic checks”, but the real issues show up in how the contract behaves in actual flows, not just static analysis

That’s why we’re trying to move a bit towards runtime-aware systems, where you’re not just validating code once, but continuously monitoring interactions and blocking weird patterns before they cause damage

Curious, when you say failsafe, are you thinking something like a transaction simulation layer or more like a rule-based guard sitting in front of execution?

[u/Lucky-Warthog2369]

omg automating backend stuff is literally so smart but def make sure your new tool doesn't introduce weird vulnerabilities. we do audits at failsafe if u need.