Protocols & Third-Party Services

Roundtrip renders information, helps you compare terms, and prepares transaction details for you to review. That is the whole of its role.

It does not lend, does not approve applications, does not set rates or thresholds, does not hold assets, and cannot execute, reverse or block a protocol transaction.

Sign-in and embedded wallets are provided by Dynamic, an independent technology provider. Signing in may create wallets for you; it is not a blockchain transaction and does not authorise one.

That provider handles authentication data and wallet key material under its own terms and policies. Naming it here identifies who processes your sign-in — it does not describe a partnership.

Account and application records are stored in a Supabase-hosted database, and the interface is served through hosting and content-delivery infrastructure.

These services store records about your use of the interface. They are not part of any lending protocol and they never hold your collateral.

Bitcoin, Ethereum, Solana and any other network involved are public, permissionless systems operated by independent participants. They decide whether and when a transaction confirms, what it costs, and whether it is final.

No one in this stack, including Roundtrip, can reverse a confirmed transaction or recover funds sent to the wrong place.

USDC and USDT are issued by independent companies that control minting, redemption, reserves and, in some cases, the ability to freeze addresses. Their solvency and policies affect the value and usability of anything you borrow or repay.

Lending protocols rely on independent price oracles to value collateral and debt. The oracle price, not the price you see elsewhere, determines your health and whether a liquidation occurs.

The lending logic — maximum loan-to-value, interest accrual, liquidation thresholds and penalties, supported markets — lives in independent, permissionless protocol software governed by its own participants.

Where a deposit has to move between chains, additional cross-chain routing or deposit-channel software is involved, with its own timing, expiry and failure behaviour.

Protocol identity and the rules that apply must be shown to you at review, before any live signature: which protocol, which network, which asset, the amounts, the rate type, the loan-to-value and liquidation thresholds, and the known costs.

If that information cannot be displayed for a given action, the action should not be presented as ready to sign.

Where that information is not yet available from the protocol, the action stays disabled and the reason is shown instead.

Naming a protocol or provider identifies who is actually involved in a technical step. It does not imply a partnership, sponsorship, endorsement, joint offering or any responsibility by one party for another.