May 2026
22 days ago by ReadMe API
- Bank-funded deposits into the lending pool. Capital providers can fund a pool deposit by bank transfer through the integrated payment provider, with the deposit credited to the depositing account rather than stranded at the on-ramp. Wire-transfer participants receive confirmation emails through the issuance workflow, and a "deposits in transit" view shows funds that are on their way.
- A pool-based lending venue running on Fabrica-maintained contracts. The pool contracts used for lending against property tokens were vendored and extended, adding a recipient parameter for deposits, a constructor-set liquidation grace period, and a token symbol getter required by the pool tooling. This established a pool-based lending venue running on contracts the project maintains directly.
- Pools page for lenders. The application added a page for viewing and interacting with lending pools, including deposit and withdrawal flows with disclosures, a projected instant-redeemable preview so a lockup is not a surprise, and positions valued at their fair share price.
- Multi-pool support. Lending moved from a single branded pool to per-pool labels and routing, so distinct pools (for example a California-only pool and a general lending pool) can run side by side, each with its own deposit and bank-funding settings.
- Lending consolidated on the pool-based venue. The interactive peer-to-peer lending flow was retired as that venue wound down new originations, while existing loan history remains visible and pool-based lending continues. Because a property token is a standard, the protocol is not tied to any single venue and can support new ones as they emerge. See Lending for the current options.
