Parameters and who sets them
The numbers the system runs on, where each one lives, who can change it, and how a rule changes. Figures under Today are the values set at deployment or by the server's current rules. A value on the chain may since have been changed by whoever holds the role; read the contract for the current one.
On this page
"The Ops Safe" below means the co-op's multi-signature wallet, once the hand-over in On-chain authority has run on that network. Until then, the same power sits with the deployer key.
Savings
ESADepositVault.setAcceptedTokenOPERATOR_ROLE (the savings relayer)ESADepositVault.setClrusdClearUSDUpgradeable.setEncumbranceSourceESADepositVault.pausePAUSER_ROLESavings pay no interest; there is no rate to set.
Equity credits
Equity credits are kept by Clear's server, not by any contract. Their rules are set in the server's software, so they change only through a software change (see How a rule changes).
The multiplier applies to rent and bills, not to the savings match. Equity credits can never be withdrawn or redeemed for cash; no rule above can change that.
Assurance and the Clear Deed
Each protection unlocks at a number of equity credits, whatever the member's plan. The member app sets these thresholds and draws the path toward the Clear Deed from them.
The app's progress bar toward the Clear Deed also ends at 15,000 credits. A claim is filed in the app and read by a person, who moves it on by hand.
Credit
TermIssuer.setTermLimitAccessManager operator (the credit operator)TermIssuer, fixed in the contractTermIssuer, fixed in the contractTermIssuer, fixed in the contractRevolvingIssuer.addTier, setTierRateAccessManager operatorRevolvingIssuer.setTierCapacity, or LimitCalculator from pledged collateralLimitCalculator writes it from collateral for anyone who callsCollateralRegistry.setCollateralTermsOPERATOR_ROLEThe automatic split-plan limit. Clear's server sets term limits by a rule:
- $500.00 to start, once the member's identity check has passed.
- $250.00 more for every three instalments paid without a late mark.
- Growth above $500.00 is capped at half of the member's estimated monthly deposits.
- $5,000.00 is the most the rule will set. Anything higher is an operator's decision.
- It only ever raises a limit. Nothing is set for a member who is suspended, in default or behind.
The rule runs on its own on Base Sepolia, the test network. On any other network it is off until it is switched on in the server's settings. The figures are proposed and not yet signed off.
The reserve
AssuranceOracle.setTargetRTD, or a risk model registered with setTargetRTDSourceAssurancePool.moveBufferToPrimaryAccessManager operatorThe target is how much primary reserve the co-op aims to hold against what the reserve stands behind. Repayments fill the primary reserve up to the target before anything else. Raising the target above its current level also moves any excess into the primary reserve. How the reserve works: The reserve.
Shops
MerchantRegistry termsMerchantRegistry OPERATOR_ROLE (the Ops Safe)MerchantRegistry termsMerchantRegistry termsMerchantRegistry.setDefaultPayoutWindowMerchantRegistry.setActiveThe contracts enforce the payout window and whether a shop is active. Clear's server checks the approval cap and applies the discount on every charge. The Command Center prepares cap changes and switching a shop on or off as Safe transactions (The Command Center).
New-member offers
OffersIssuer.setTermsOffersIssuer.setTermsOffersIssuer.setCapOffersIssuer.setTreasuryMembership
Prices for Standard and Accelerated are set in the billing provider (Stripe) and are not listed here. What each plan changes is in Membership and the co-op.
How a rule changes
There are four kinds of rule, and each changes a different way.
- 1.A value on the chain: everything in the tables above marked as living in a contract. It changes by a transaction from whoever holds the role. Where that is the Ops Safe, the change needs signatures from more than one of the Safe's owners. The Command Center can prepare the transaction and collect signatures; it is executed in Safe{Wallet}.
- 2.A rule fixed in a contract: the instalment choices, when a default can be declared. It changes only by upgrading the contract, which is itself a transaction by the contract's admin or owner (Who can upgrade a contract).
- 3.A rule in the server or the app: equity credits, the automatic term limit, the protections. It changes through a reviewed change to the software that passes the automated checks, and reaches the live apps when it is released to production.
- 4.A Command Center setting: for example, the amount above which a refund or a purchase needs a second person. A change is a proposal that someone else must approve (The Command Center).
Rules that belong to the members, such as the bylaws and anything decided by member vote, have no process in the software yet (Membership and the co-op).