The problem Kyro solves

💸 The $2 Trillion of Trapped Capital 💸

Businesses are sitting on billions in unpaid invoices they can't touch. A business completes a job, issues an invoice, and then waits — 30, 60, 90 days — to get paid. Meanwhile:
• Payroll is due.
• Suppliers need to be paid.
• Growth stalls.

Banks won’t lend against receivables without:
• Collateral
• Deep credit history
• A pre-existing relationship

The result? A $2 trillion global trade finance gap

On the other side, investors have capital sitting idle with no clean way to deploy it into short-duration, real-economy yield. Existing DeFi vaults offer yield backed by speculation. There's no on-chain primitive for yield backed by actual commercial repayment.

⚡ Kyro closes both gaps simultaneously.
• SMEs get liquidity in minutes.
• Investors earn yield from real-world cashflows.
• The entire lifecycle is transparent and auditable on-chain.

SMEs can use Kyro to unlock cash from outstanding invoices without waiting for buyers to pay. Instead of waiting months to get paid:
1. Upload an invoice.
2. Verifies the document with an oracle.
3. Receive 80% of the face value in DDSC stablecoin

No wallet funding.
No gas fees.
No blockchain knowledge required.

The transaction is fully gasless.

Investors and funds can use the yield vault to deploy stablecoin capital into a pool of invoice-backed receivables. Deposits are tokenized as vault shares. As invoices settle, principal and interest return to the vault automatically and the share price rises.

Compliance officers and regulators can use the auditor portal to inspect the full lifecycle of every invoice on-chain — minted, funded, settled, or defaulted — without needing a wallet or any blockchain knowledge. KYC is enforced at the token transfer level via ERC-3643, so the protocol itself is the compliance layer, not a UI wrapper around it.

Developers building on ADI Chain can extract Kyro's ERC-4337 paymaster stack as a standalone toolkit — deploy native and ERC-20 paymasters, wire up the sponsor API, and give their own users gasless transactions in an afternoon.

Challenges I ran into

ADI Chain's testnet doesn't have a hosted bundler or paymaster service. The standard ERC-4337 tooling (Pimlico, Alchemy) doesn't support it. That meant we had to build our own relay: a backend API endpoint that accepts a signed UserOp, calls handleOps() on our EntryPoint directly, and returns the transaction hash.

Also, the paymaster kept rejecting UserOps with no useful error. The backend was signing with eth_sign (which prepends a message prefix) but the contract was recovering against a raw hash, so the recovered address was always wrong. Once we aligned both sides to use the same hashing approach and added a test that logged the recovered address directly, it was a one-line fix. Getting there took way longer.

Use of AI tools and agents

Kyro uses Claude in one keh place: parsing invoice documents uploaded by SMEs.

When a business uploads a PDF or image of an invoice, Claude reads the document and extracts the key fields — invoice amount, due date, buyer name, and currency — returning them as structured JSON. Those values populate the submission form instantly, so the SME never has to type anything manually.

The rest of the system is deterministic: oracle attestation is ECDSA signing, the blockchain logic is Solidity contracts, and the gas sponsorship is ERC-4337. AI is used exactly where rule-based approaches would struggle, and nowhere else.