Hi everyone,
We are the team behind Debifi, and we are currently in the closed beta phase of our new Bitcoin lending API. We are looking for technical feedback from this community on our architecture and threat model.
The Problem we are solving:
The current Bitcoin lending market is plagued by custodial opacity and rehypothecation risks. Institutional players and developers need programmatic liquidity, but current "black box" solutions require them to hand over their keys.
Our Approach (The Architecture):
We have built a lending infrastructure based entirely on a 3/4 Multi-Sig setup.
- We do not take custody.
- Zero rehypothecation.
- Focus on on-chain verifiability.
Our API allows developers, quantitative funds, and treasury managers to integrate native collateral management directly into their own dashboards or trading setups.
A practical example of our data transparency: Clark Moody is currently using our API to pull live data on non-custodial loans to display them on his dashboard. Other institutional Partner companies are using the architecture to scale their own institutional liquidity.
Why we are posting here:
We want to know what you think about our trust-minimized setup.
1.) What edge cases in a 3/4 multi-sig escrow setup for lending do you think are most often overlooked?
2.) What specific endpoints or webhook triggers would you absolutely require if you were building an automated arbitrage or treasury tool on top of this?
You can find our documentation/demo here:
https://gitlab.com/debifi-publicWe are actively answering questions regarding our threat model and architecture in this thread. If any developers are interested in poking around the live API, we still have a few spots open in our closed beta (shoot us an email at
api@debifi.com).
Looking forward to tearing down the architecture with you.
