KredoFi docs
Testnet vs mainnet
What runs where, and the transactions that prove the mainnet path.
| Testnet demo | Mainnet | |
|---|---|---|
| Contract | kredofi.kency.testnet | kredofi.near |
| Scoring | Dev mode: the pinned scorer runs on our server; the server submits its output | OutLayer, Intel TDX; the contract accepts a score only in its own callback |
| Pinned scorer | testnet build ac8e2a9c… | production build 7048cc92… |
| Bank data | Plaid sandbox | Plaid sandbox (no production access yet) |
| Money | test USDC and test NEAR | native USDC configured; pool empty, no loans yet |
| Accounts | no-wallet demo accounts, a relayer pays every fee, or any testnet wallet | your own wallet |
| Loan term / grace / minimum hold | 2 min / 1 min / 1 min | 30 days / 7 days / 15 days |
| AI summary | yes, generated on our server | no |
| Extras in the scorer | prepared borrowers (Riya, Sam, Max, build your own); the shared sandbox login is tied to your account; a fetch receipt | none |
#Proof of the mainnet path
- Contract deployed in OutLayer mode: transaction.
- A real score computed inside OutLayer and stored by the contract's callback (band A, 1,000), with the unused fee refunded to the borrower: transaction (1 November, earlier build).
- Re-pinned to the reproducible build
7048cc92…(transaction) and scored again inside OutLayer with it (band A, 1,000, 7.6 seconds): transaction (2 November). - Contract upgraded with a state migration: transaction.
How to check these yourself: Verify it yourself.