Locks collateral
A smart contract locks the pledged asset under the rules configured for the position.
Named engine · Financial infrastructure layer
Collateralisation by smart contract.
Anchor lets an asset be committed as collateral under rules that a smart contract enforces. It locks the collateral, reads price data from Beacon to value the position, and relies on Reserve, the platform treasury engine, as the backstop. Anchor describes collateralisation as a function only: it implies no lending product and makes no custody claim.
What it does
Anchor is the collateralisation engine. It holds a pledged asset in contract logic under the rules set for the position, draws its valuation inputs from Beacon, and looks to Reserve for the backstop. The record is silent on lending, so Anchor implies no lending product, and its custody wording stays functional.
How it works
Three steps, each with one job.
A smart contract locks the pledged asset under the rules configured for the position.
Anchor reads Beacon's data feeds to value the collateral it holds.
Reserve, the treasury engine, stands behind the collateral position as its backstop.
Where it fits
Anchor belongs to the financial infrastructure layer and is built from two supplying engines. It needs a reliable value for what it holds, and a defined source of support behind each position.
Collateralisation by smart contract.
Used by (0)
Beacon supplies the value. It brings external price and reserve data on-chain through an oracle network, and Anchor reads those feeds rather than sourcing data itself. Reserve supplies the backstop: the platform treasury, managed for DAMREV's own value and kept apart from customer funds, stands behind the collateral position.
No engine lists Anchor as a dependency, so a collateral position is an end point rather than an input to other engines. Registry does count Anchor among the engines that draw on the register of holders, which is how a locked position stays tied to the record of who owns the asset.
Standards and integrations
Controls
Anchor enforces the lock: once collateral is committed, the contract holds it to the rules set for that position, valued from Beacon's feeds.
Common questions
Short answers to the questions people ask most about this topic.
Anchor provides collateralisation as a function: it locks an asset and holds it to rules. The record is silent on lending, so it implies no lending product.
Anchor values locked collateral from Beacon's on-chain data feeds, which Beacon sources through an oracle network.
Reserve, the treasury engine for the platform's own value, provides the backstop for each collateral position.
The collateral is held in contract logic under the position's rules. Whether that is non-custodial in the regulatory sense is reserved, so Anchor makes no custody claim either way.
Contract logic applies the rules for a position the same way every time. Soroban runs natively on the Stellar ledger, where the asset itself is recorded.
Where next
The pages below pick up where this one ends. Start with the one closest to where your asset or programme stands today.
Last updated:
Insights

Since 17 September 2026 a tokenized securities venue may run automated liquidity pools in tokenized listed stock without registering as an exchange, on conditions.

The GENIUS Act binds payment stablecoin issuers from 18 January 2027, not the firms that hold or settle in stablecoins. Service providers follow in 2028.

The CLARITY Act stalled on a 49 to 50 vote, so tokenized securities stay with the Securities and Exchange Commission, as before.

Guernsey's guidance of 24 July 2026 lets a fund or issuer record and transfer its investments as tokens, under the regimes already applying to it.
Tell us what you want to tokenize.
We will show you how DAMREV can run it.