Deployment

Live Deployment Evidence - CreditGateVault on Coston2

Current strict-revocation deployment (2026-08-13): Vault `0x9a2E0476a02137116C8656786d323d937FaCfBCa` with child CreditScoreSBT 0xa31cAAa3F67e53A1Dcb6bDd20816361402A04005. This is the deployment configured by the frontend. Earlier Coston2 vaults and their FDC close artifacts are historical only.

Deployment Details

Settlement Readiness

• The vault accounts for 0.09 USDT0 of lender liquidity. Current readback shows loan 1 funded for 0.009 USDT0, with 0.081 USDT0 available.
• The owner-controlled settlement agent is configured on-chain and can approve USDT0 before a proof submission.
• A repayment proof must originate from the XRPL address snapshotted when the loan is drawn, pay the protocol XRPL settlement account, include the exact 32-byte loan commitment, and verify through FDC.
• On successful proof verification, the settlement agent supplies USDT0 atomically before collateral is released. A missing balance or allowance reverts without consuming the proof.

Verified Contract State after deployment

owner()                 = 0x42BBE5B88D088346e705906A93e3b848639983fb
paused()                = false
nextLoanId()            = 2
totalManagedAssets()    = 90000000000000000
availableLiquidity()    = 81000000000000000
settlementAgent()       = 0x42BBE5B88D088346e705906A93e3b848639983fb
repaymentReceiverHash() = 0xcd0c08cc6a98cc47c9b2b9a2ba5878db45b27e5eba225f2b7f1a5ea46d6948f3
loan 1 state            = FUNDED (4)
loan 1 principal        = 9000000000000000
loan 1 collateral       = 500000 FXRP units
outstanding principal   = 9000000000000000 USDT0 raw
CreditScoreSBT          = deployed by the vault constructor

Contract References

Reproduce

forge test --summary
cast code 0x9a2E0476a02137116C8656786d323d937FaCfBCa \
  --rpc-url https://coston2-api.flare.network/ext/C/rpc

Current-Vault FDC XRPPayment Evidence on Coston2

Status: A real XRPL Testnet payment was attested through Flare FDC, verified by the live Coston2 FdcVerification contract, and closed loan 1 on the vault used by the frontend.

The earlier zero message-integrity code (MIC) request is retained only as a negative operational control. The request below was generated by Flare's verifier and contains a nonzero MIC.

End-to-end evidence

Reproduce verification

forge script script/FDC/VerifyXRPPayment.s.sol \
  --rpc-url https://coston2-api.flare.network/ext/C/rpc \
  --sig "run(string)" evidence/fdc/raw-proof-response.json

The submission script checks the on-chain loan state before broadcasting. Once a loan is CLOSED, it exits successfully without replaying the proof.

Root cause and prevention

Flare's verifier supplies the MIC-bearing abiEncodedRequest. A hand-encoded zero-MIC request can pay FdcHub fees yet not be indexed by providers. The retrieval driver rejects zero-MIC inputs and performs bounded post-finalization DA retries before reporting a provider indexing failure.