Ehu Shubham Shaw, Tyler Rosa, Ajay Gupta, Tejas Kulkarni, Frank
We are building a decentralized gap financing platform that enables real-world businesses — including real estate developers, SMEs, startups, and contract holders — to raise capital from retail and institutional investors globally.
Borrowers can raise funds through two options:
- Debt Financing (stable interest payments)
- Tokenized Equity Offerings (ownership upside)
Powered by Polkadot's cross-chain capabilities, our platform ensures capital aggregation from multiple blockchains, payout in stablecoins, and transparent, milestone-based fund disbursements.
- Borrowers request funding via debt or tokenized equity.
- Investors fund projects using assets from multiple chains.
- Platform aggregates funds into stablecoins (USDC, aUSD).
- Smart contracts manage milestone disbursements, interest repayments, and equity distributions.
- Intended to use Polkadot Asset Hub
- Key Functions:
- fundProject(): Investors fund the borrower's project.
- payoutBorrower(): Funds released to borrowers upon milestone completion.
- repayLoan(): Borrower repays principal + interest.
- claimInterest(): Investors claim interest payouts.
- Built using React.js
- Wallet integration: Polkadot.js Wallet and Metamask (for EVM assets)
- Displays available projects, investment flows, borrower status, and repayment dashboards.
| Page | Screenshot |
|---|---|
| Investor Dashboard |  |
| Borrower Application Portal |  |
| Milestone Tracking Interface |  |
/contracts - Smart contracts in Ink! /frontend - React app /scripts - Deployment scripts for Asset Hub /readme-assets - Demo video and screenshots
Contract deployed to Polkadot Asset Hub Block Explorer link: (https://moonbase.moonscan.io/address/0xcBB143822176058A864ed9583f56360D51317579)
We successfully deployed the smart contract; however, we encountered persistent issues with the faucet. The faucet repeatedly returned an "out of funds" error, preventing us from obtaining DEV tokens needed for testing. Despite having funds sent directly to a key we could use, the balance continued to show 0 DEV.
We attempted several workarounds, including using different devices, IP addresses, and network connections, but none fixed the issue. Additionally, the faucet’s 24-hour cooldown period significantly delayed our progress, and we did not have the time available to wait between attempts.
Due to these challenges, we decided to run the application locally with a setup that closely mirrors the intended deployment. This allowed us to move forward with testing and running the application as planned, despite the issues with the faucet.
