|
| 1 | +# QLX Onboarding Limits |
| 2 | + |
| 3 | +Progressive limits applied to new businesses and investors while they build history on the QuickLendX protocol. |
| 4 | + |
| 5 | +## Audience |
| 6 | + |
| 7 | +This document is written for **operators** and **support** staff who need to explain or verify the progressive limits that apply to newly onboarded participants. |
| 8 | + |
| 9 | +## Purpose |
| 10 | + |
| 11 | +New businesses and investors start with conservative limits. These limits increase automatically (or via governance) as the participant builds a positive history of successful invoices, repayments, and dispute-free activity. |
| 12 | + |
| 13 | +The goal is to: |
| 14 | +- Reduce protocol risk from brand-new participants |
| 15 | +- Allow legitimate users to grow their capacity over time |
| 16 | +- Keep the rules transparent and auditable |
| 17 | + |
| 18 | +## Limit Categories |
| 19 | + |
| 20 | +| Category | Description | Initial Value (example) | |
| 21 | +|-----------------------|--------------------------------------------------|-------------------------| |
| 22 | +| Max Open Invoices | Maximum number of concurrent open invoices | 3 | |
| 23 | +| Max Invoice Amount | Maximum size of a single invoice | 5,000 USDC | |
| 24 | +| Max Total Exposure | Maximum total outstanding principal | 15,000 USDC | |
| 25 | +| Max Concurrent Bids | Maximum number of open bids an investor can place| 5 | |
| 26 | +| Max Position Size | Maximum size of a single investment position | 2,000 USDC | |
| 27 | + |
| 28 | +> Exact numeric values are stored in the contract’s configuration and may be updated via governance. Always check the on-chain parameters for the current numbers. |
| 29 | +
|
| 30 | +## Progression Rules |
| 31 | + |
| 32 | +Limits increase based on the following signals (examples): |
| 33 | + |
| 34 | +1. **Successful Invoice Completions** |
| 35 | + After N invoices are fully repaid without dispute, the Max Invoice Amount and Max Total Exposure increase. |
| 36 | + |
| 37 | +2. **Time on Platform** |
| 38 | + After a minimum number of days with positive activity, concurrent invoice and bid limits are raised. |
| 39 | + |
| 40 | +3. **Dispute History** |
| 41 | + Any dispute that is resolved against the participant can freeze or reduce limits until a cool-down period ends. |
| 42 | + |
| 43 | +4. **Governance Override** |
| 44 | + Protocol administrators can manually raise or lower limits for a specific participant when justified. |
| 45 | + |
| 46 | +## Worked Example |
| 47 | + |
| 48 | +A new business is onboarded: |
| 49 | + |
| 50 | +- Day 0: Max Open Invoices = 3, Max Invoice Amount = 5,000 USDC |
| 51 | +- After 5 successful invoice cycles with no disputes: |
| 52 | + - Max Open Invoices → 5 |
| 53 | + - Max Invoice Amount → 10,000 USDC |
| 54 | + - Max Total Exposure → 30,000 USDC |
| 55 | + |
| 56 | +An investor starts with: |
| 57 | + |
| 58 | +- Max Concurrent Bids = 5 |
| 59 | +- Max Position Size = 2,000 USDC |
| 60 | + |
| 61 | +After consistent successful bids and repayments, both limits are raised by the progression rules. |
| 62 | + |
| 63 | +## Related Documents |
| 64 | + |
| 65 | +- `CAPS.md` – hard protocol-wide caps |
| 66 | +- `INVESTOR_RISK_MODEL.md` – risk scoring that can influence limits |
| 67 | +- `GOVERNANCE.md` – how parameters and individual overrides are changed |
| 68 | + |
| 69 | +## Implementation Notes |
| 70 | + |
| 71 | +The limits are enforced inside the Soroban contracts. Off-chain services should never assume a participant can exceed the on-chain limits. |
| 72 | + |
| 73 | +When in doubt, query the contract for the current effective limits of a given business or investor address. |
0 commit comments