SerevinSerevinDocumentation
The guide/Using the workspace
Available in the workspace

Markets & on-chain data

Where lending figures come from, what the displayed numbers mean, and how freshness is checked.

In this chapter

A market is a contract configuration

The workspace uses Robinhood Chain, chain ID 4663, with ETH as the native gas asset. An asset is identified by its chain and contract address, not only by its ticker or logo. Two unrelated tokens can share the same ticker.

For each configured Morpho market, Serevin reconstructs the market identity from its loan asset, collateral asset, oracle, interest-rate model and liquidation loan-to-value parameter. A mismatch is treated as an error. USDG precision and relevant token identities are checked before values are formatted.

The reviewed lending pairs use spUSDG, mGLO, syrupUSDG, USDe or WETH collateral with USDG debt. These are Morpho markets, not deployments of the Serevin isolated-lending contract. Manage market opens Serevin’s native lending desk, whose transaction controls await reviewed release configuration.

Accounting headroom is not a borrowing guarantee

Supplied assets and borrowed assets are read from stored market accounting. Utilization compares borrowing with supplied assets. Book headroom is their difference. These are useful indicators of a market’s state, but the interface does not simulate your borrow or establish that the entire difference can be withdrawn immediately.

Actual execution can depend on balances, interest accrual, collateral, the oracle, token restrictions and changing chain state. Do not treat a supplied-assets total as cash sitting idle, or the displayed headroom as an approved loan offer.

Position reads show supply shares, debt shares and recorded collateral. Shares are accounting units. The current workspace does not calculate a fully accrued present redemption value from every share balance.

In the current implementation
Book headroom = stored supplied assets − stored borrowed assets

A block and a time for every response

A direct RPC response is pinned to one block. Before reading contracts, the application verifies the chain ID, block number, block hash and timestamp. It rejects a block more than 120 seconds old or more than 30 seconds in the future. Individual RPC calls have a 12-second timeout. These checks apply to Serevin’s direct on-chain reads; a Route API result has its own provider metadata and expiry.

The hosted data service uses a dedicated Alchemy connection with Robinhood’s public endpoint as backup. A transport failure can switch the current read session to the backup once, after verifying chain 4663. Contract calls keep the same block number, and the final block-hash check still applies. A contract revert or integrity failure does not trigger a retry. Provider credentials stay on the server.

After the contract reads finish, the block hash is checked again. If the block changed during the request, the response fails instead of combining values from inconsistent chain history.

The workspace footer labels the market snapshot with an explicit UTC date and time. A quote has its own expiry and is not refreshed merely because the market timestamp changes. Refreshing requests new information; it does not commit an execution price.

Unavailable is different from zero

A token or contract read can fail independently of other reads. The interface reports unavailable values rather than inventing a zero balance. An empty route search likewise returns no quote, not a fallback exchange rate.

Displayed token amounts are formatted from integer-based strings. Truncation never rounds a small balance upward. If a nonzero amount is smaller than the displayed precision, the interface indicates that it is below that precision.

Related documentation

Morpho documentationRobinhood Chain token contracts
This guide describes the current source implementation. Production terms and verified deployment addresses will be published before real transactions are enabled.