Borrow against collateral · Sepolia

Your collateral. Your credit. Your terms.

Follow the complete VaultFi borrower journey from wallet eligibility to collateral release. Live execution stays locked until the controlled test lane is reopened.

1
Wallet Waiting
2
Eligibility Waiting
3
Collateral Waiting
4
Loan quote Ready
5
Borrow Locked
6
Repay & unlock Future stage
Wallet Not connected
Borrower —
KYC —
Next Loan —
01

Borrower eligibility

Wallet identity, KYC and account state.

Network —
KYC status —
Existing loans —
Live borrower —
02

Collateral locker

Current wallet and protocol custody state.

Locker No locker yet
Deposited 0 vCOLL
Borrower vCOLL —
Vault custody —
Loan-locked collateral 0 vCOLL
No collateral locker exists for this connected wallet yet.
03

Market & oracle readiness

Both feeds must have at least 900 seconds of execution runway before a live loan can be armed.

vUSD / USD —
Round —
Price —
Runway —
vCOLL / USD —
Round —
Price —
Runway —
Connect the borrower wallet to read current Sepolia state.
04

Your loan offer

Exact terms from the controlled Loan #2 plan.

You borrow 1,000 vUSD
Collateral 2 vCOLL
LTV 25%
APR 10%
Term 30 days
Protocol fee 25 vUSD
You receive 975 vUSD
Canonical wallet
KYC verified
Collateral available
Loan #2 available
Oracle runway
Controlled test boundary

Live borrowing remains locked.

Validate all borrower conditions now. The final wallet transaction will only be armed after a separate fresh on-chain requalification and explicit authorization.

Connect the staged borrower wallet to begin.
05

What happens after borrowing

Expected post-loan state shown as a preview only.

1
Loan #2 opens LoanManager next ID should advance from 2 to 3.
2
2 vCOLL locked Collateral remains in protocol custody.
3
975 vUSD received Net of the staged 25 vUSD protocol fee.
4
Repay & release Enabled only after exact post-loan audit.

Expected after successful Loan #2

Next loan ID 3
Borrower loans 1
vUSD wallet 975
Collateral locked 2 vCOLL

These values are expectations, not claims about current on-chain state. They become authoritative only after the actual transaction is mined and audited.

08

Live Loan #2 state

Exact LoanManager reads. Before Loan #2 exists this panel remains in pre-loan state automatically.

Contract authority

Loan #2 not read yet

Refresh borrower state to inspect LoanManager.

Exists —
Status —
Locker —
APR —
Principal —
Interest —
Total debt —
Collateral locked —
Borrower —
Borrow token —
Collateral token —
Repayment recipient —
Created —
Maturity —
Repayment amount authority totalDebt(2)
Repayment transaction repayLoan(2)
Collateral release Automatic inside repayment
Repayment boundary

Repayment broadcast remains disabled.

The dashboard can read the exact amount and recipient, but cannot sign or submit repayLoan.

06

Repayment

Prepared for the next contract-binding stage.

Coming next

Repay Loan #2

Exact repayment amount, accrued interest and repayment calldata will come directly from the live LoanManager contract after the loan exists.

07

Collateral release

The final borrower lifecycle step.

Protected

Unlock collateral

Release controls remain unavailable until repayment completion has been authenticated on-chain.

Controlled execution model

Transaction review

Preview the exact write sequence and repayment requirements. Nothing on this page can sign or broadcast a transaction.

All writes disarmed
A

Create Loan #2

Future borrower write

Target
LoanManager
Method
createLoan(...)
Authorization
Separate fresh authorization
Current state
Parked / not executed
B

Repayment approval

Conditional ERC-20 write

Token
vUSD
Spender
LoanManager
Current allowance
—
Required allowance
—
Approval required
—
C

Repay Loan #2

Future borrower write

Total debt
—
Wallet vUSD
—
Funding gap
—
Method
repayLoan(2)
Collateral release
Internal after successful repayment
Future controlled sequence Waiting for Loan #2

Repayment sequencing becomes authoritative only from live LoanManager debt, vUSD balance and vUSD allowance reads.

Review-only calldata model
Allowance
allowance(borrower, LoanManager)
Approval target
—
Approval amount
—
Approval calldata
—
Repay calldata
—
Pre-live execution handoff

Build complete · execution remains disarmed

The borrower experience is ready for a controlled test, but no previous nonce, oracle age, gas estimate or authorization is treated as current execution authority.

EXECUTION DISARMED
Build lane —
Parked R6 authorization —
Authorization consumed —
Real createLoan executed —
Current nonce authority —
Oracle freshness authority —
Browser signing Disabled
Browser broadcast Disabled
Next real test boundary Fresh requalification → fresh authorization → one write
1 Requalify Chain, nonce, KYC, locker, treasury, oracle, gas and exact simulation.
→
2 Authorize Fresh explicit authorization for one exact borrower transaction.
→
3 Execute once A transaction hash permanently consumes that write authorization.
→
4 Authenticate Receipt plus exact transaction and post-state audit.

Fresh createLoan requalification checklist

Sepolia chain ID Canonical borrower Pending nonce Native gas balance KYC status Pause / freeze state Locker #2 state Next loan ID Borrower loan count Treasury balance Treasury allowance Liquidity limits vUSD oracle round vCOLL oracle round Oracle answers Oracle age / runway Gas estimate Fee parameters Max transaction cost Exact createLoan simulation Exact calldata SHA-256
Historical values are context, not execution authority.

The earlier expected borrower nonce of 2 and prior Round 11 oracle evidence remain part of the audit history, but they must not be reused as current execution inputs without fresh Sepolia reads.

If a transaction hash appears Authorization consumed · never rerun that write stage
If send returns no hash Do not resend · inspect nonce and protocol state
If post-state audit fails after a hash Adjudicate the known transaction · do not repeat it
If oracle/state drifts before send Stop · requalify · require fresh authorization
Exact staged execution identity
Borrower
—
LoanManager
—
Create Loan #2 calldata SHA-256
—
Repay Loan #2 calldata SHA-256
—
Operator handoff
View machine-readable handoff
Pre-live test rehearsal

Run the transaction lifecycle without touching Sepolia

Deterministic synthetic evidence exercises the same customer-facing success and failure states before any real borrower transaction is reopened.

Simulation only
Scenario Not run
Expected state —
Observed state —
Acceptance —
State trace No rehearsal has been run.

All evidence in this section is synthetic and local.

No wallet required No RPC No keystore No signing No broadcast No authorization consumed
Test execution audit

Transaction lifecycle & receipt authentication

This surface never sends a transaction. Paste a transaction hash produced by the controlled execution lane and VaultFi will independently authenticate it against the staged model.

Read-only auditor
1 Preparing
2 Wallet confirmation
3 Submitted
4 Mined
5 Authenticated
6 Post-state verified

Hashless outcome policy: never resend automatically. Inspect nonce and contract state first.

No transaction has been audited.
Audit state PREPARING
Hash —
From —
To —
Nonce —
Value —
Receipt status —
Block —
Mined time —
Input —
Event —
Post-state —
Fail-closed rules Wrong sender / target / value / calldata → BLOCKED Expected nonce mismatch → NONCE_DRIFT Hash but no receipt → SUBMITTED No hash after an external send attempt → HASHLESS_OUTCOME_UNKNOWN, never resend Receipt status 1 is not enough by itself: exact transaction authentication is required
Sepolia borrower action

Create collateral locker

Prepares the exact createLocker(address,uint256) transaction for vCOLL. Browser broadcast remains disarmed until separately authorized.

EXECUTION DISARMED
Collateral token —
Vault —
Wallet vCOLL balance —
Vault allowance —
Readiness Not checked
Exact calldata —

Collateral approval to the Vault is a separate blockchain write and will never be performed automatically.

Technical transaction specification
LoanManager
CreateLoan SHA-256
Browser broadcast
Disabled