Liquidium WTF Contract Addresses and Direct Settlement
Effective date: September 14, 2026 · Version: 1.0
This page is the canonical public record of Liquidium WTF deployments and direct-settlement information. “Official” or “verified” on this page means that Liquidium has confirmed the address or identifier; it does not mean that private source code has been published or verified on a block explorer.
Never trust an address received only through social media, direct message, search advertising, or an unsolicited support contact. Confirm the network, address, and transaction details on this page and the applicable block explorer before signing.
Robinhood Chain
Status: official Robinhood Chain loan proxy, operating as an upgradeable Beta Deployment. Ownership has not been renounced.
Users and integrations must call the loan proxy below. The implementation address identifies the code used by that proxy; do not send assets or settlement transactions directly to the implementation.
The following onchain state was checked at block 62,803,329, September 14, 2026 at 12:20:11 UTC. Administrative settings and the implementation can change during beta; check current onchain state before transacting. Deployment does not by itself mean every market is available in the hosted interface.
Deployment and current configuration
| Item | Configuration |
|---|---|
| Network | Robinhood Chain, chain ID 4663 |
| Loan proxy — use this address | 0x853918Ed9f97944ed50Dc50f3C9Fc50469ba7B02 |
| Implementation — do not transact directly | 0x24C19ebC293B3DAF977404d26a9e0b03A60d5055 |
| Deployment | September 14, 2026 at 10:37:33 UTC; block 62,742,623 |
| Deployment transaction | 0x78245f3c14dbe150d9640ed1bf2833cac0f51dc8a2141832c143820463c9e89c |
| Current phase | Beta Deployment; code upgradeable through the owner role |
| Owner, upgrade controller, and administrator | Safe Smart Account 0x9E8E73Cf04e5c1552B9EA6698DDab986Ace147a4 |
| Safe configuration | Version 1.4.1; 4 of 6 owners; no enabled modules or configured guard |
| Upgrade timelock | None |
| Pending owner and pending administrator | Both 0x0000000000000000000000000000000000000000 |
| Ownership renouncement | Not renounced; no renouncement transaction for this proxy as of the checked block |
| New-loan origination | Unpaused (originationPaused() is false); individual markets remain subject to allowlists and interface availability |
| Oracle signer | 0x79b5b63A313F6a6C8d83ae979F46d3422d4019a1 |
| Valuation validity limit | 900 seconds (15 minutes); collection/asset epochs are available through valuationEpoch(address,address) |
| Fee recipient | 0x79E6B30D76192a3246f542C131F1Aa232613bcf0 |
| Activation fee | 0.75% of principal, or 75 basis points |
| Protocol share of interest | 30% of interest, or 3,000 basis points |
| Contract maximum LTV | 100% |
| WETH | 0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73 |
| USDG | 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168 |
Both WETH and USDG were allowlisted at the checked block. Check assetAllowlisted(address) and collectionAllowlisted(address) for current status.
Implementation history and verification
The deployment transaction set implementation 0x24C19ebC293B3DAF977404d26a9e0b03A60d5055. No later Upgraded event was recorded through block 62,803,329.
- ERC-1967 implementation slot:
0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc. - Slot value at the checked block:
0x00000000000000000000000024c19ebc293b3daf977404d26a9e0b03a60d5055. - Implementation runtime bytecode hash (Keccak-256):
0x43a80c29b5510dfedb8bbc2273bf56e3943ceb438f62b3f3c70c90b48cd0f31d. - Download the verification and direct-settlement ABI for this implementation. This limited ABI includes the read and settlement functions described here; it does not include new-loan origination or administrative write functions.
Liquidium's source code for this deployment is private. Liquidium retains the current source commit, compiler settings, build artifacts, deployed bytecode hash, and deployment records internally. Public source-code verification on a block explorer is not promised.
During the Beta Phase, the Safe identified above holds the owner role that authorizes UUPS code upgrades. The Safe has no onchain timelock. No module, guard, or alternative execution route is configured to bypass its four-of-six approval threshold. An upgrade may replace the implementation used by the proxy while retaining the proxy address and stored state. Users must confirm the implementation and upgrade history shown on this page before every transaction.
The same Safe controls a separate administrator role. It can pause new loan originations, change the activation fee and protocol share of interest, change the fee recipient, change the authorized oracle signer and valuation settings, and add or remove supported collections and principal assets. Those controls do not change an active loan's economic terms or disable repayment, default claims, collateral claims, repayment claims, or other settlement functions available under the contract. A pause or allowlist change may prevent a signed but unfilled offer from being filled.
Liquidium will not change fees in place on an existing EVM deployment. If different fees are introduced, Liquidium will first pause new originations through the superseded deployment and will enable the new fees only through a new deployment. Existing loans will remain on, and may continue to settle through, the deployment where they originated. Users must create, sign, or fill new offers for the replacement deployment under the then-current Terms.
A deployment remains a Beta Deployment until Liquidium publicly announces that its owner role has been renounced and publishes the onchain renouncement transaction. Liquidium may continue using the same proxy after renouncement or may pause new originations and use a separate deployment. Each deployment retains its own beta or post-beta status. A zero owner() and pendingOwner() state and the renouncement transaction prove the state of the owner role, but do not independently prove source-to-bytecode correspondence or the absence of every possible code path in the private source.
Direct EVM settlement
The hosted interface is the recommended method. If the interface is unavailable, an eligible party may interact directly with the loan proxy above using the linked ABI and compatible wallet software, or an explorer that supports entering a custom ABI. The functions and instructions below apply only to the implementation currently identified on this page and must be rechecked after any upgrade. Direct interaction is technically complex and may cause irreversible loss if the wrong network, address, function, token, amount, or parameters are used.
| Purpose | Function on the loan proxy | Who may call | Important conditions |
|---|---|---|---|
| Read a loan | getLoan(uint256 loanId) | Anyone | Confirm the borrower, lender, collateral, repayment asset, amount, state, and maturity |
| Check whether matured | loanInDefault(uint256 loanId) | Anyone | A matured loan may still show Active until the lender claims collateral |
| Repay | repay(uint256 loanId) | Anyone | Must be confirmed no later than maturity; caller must approve the full stored repayment asset and amount; collateral returns to the recorded borrower |
| Claim a failed repayment transfer | claimRepayment(uint256 loanId) | Anyone | Funds are sent only to the recorded lender |
| Claim collateral after default | claimDefault(uint256 loanId) | Recorded lender only | Available after maturity while the loan remains active; transfers collateral to the lender and extinguishes the debt |
| Claim a failed collateral transfer | claimCollateral(uint256 loanId) | Anyone | Collateral is sent only to the recorded borrower or lender entitled to it under the stored state |
| Cancel one signed offer | cancelSignedOffer(bytes32 offerHash) | Offer's lender | Cancellation is effective only when the transaction confirms before a competing fill |
| Invalidate all older offers | incrementNonce() | Lender | Invalidates signed offers using the lender's prior nonce after confirmation |
| Check offer/allowlist state | signedOfferStatus(address,bytes32), lenderNonce(address), collectionAllowlisted(address), assetAllowlisted(address) | Anyone | Read from the active proxy on the correct network |
Early full repayment is permitted through repay, but it requires the full repayment amount agreed when the loan was created, including the full originally agreed fixed interest; there is no time-based rebate.
Before a direct transaction:
- Switch to Robinhood Chain, chain ID
4663. - Verify the active loan proxy address against this page.
- Read the loan and confirm every address, token, amount, state, and deadline.
- For repayment, approve the exact repayment asset for at least the full stored repayment amount.
- Simulate or review the transaction in trusted wallet software, then wait for confirmation.
- Confirm the final state and transfers on the block explorer.
Liquidium support will never ask for a seed phrase or private key.
Bitcoin verification and recovery
Bitcoin loans do not use the EVM loan proxy or EVM functions above. Users should verify Bitcoin transactions, scripts, addresses, and status in a reputable Bitcoin block explorer and use the loan flow shown in Liquidium's Bitcoin interface.
For compatible Instant Loan multisignature vaults, Liquidium publishes a browser-based recovery tool:
The recovery tool is an emergency method for compatible multisignature vaults; it is not a general settlement method for every Bitcoin loan. Verify the hosted domain and source before use. Liquidium support will never ask for a seed phrase or private key.
Liquidium will add any additional public Bitcoin or Internet Computer identifier here if users need it to authenticate the service, verify a transaction, or recover or settle an existing loan.
Retired deployments
| Network | Chain ID | Contract or identifier | Active period | Retirement reason | ABI/instructions | Existing-loan status |
|---|---|---|---|---|---|---|
| None at launch |
Retiring a deployment from the hosted interface does not erase its blockchain history or alter an existing loan. Liquidium will keep retired deployment records and necessary settlement instructions available for as long as users may reasonably need them.
Maintainer and corrections
Page owner: Liquidium Inc.
Technical maintainer: Liquidium team
Report an error: help@liquidium.wtf