Smart Contract Addresses

Deployed Templar Protocol contracts, and how to verify them. For deploying a new market, see Deploying a market.

Deployments

Core

Oracles

See Oracles for how these fit together.

Markets

Market contracts are deployed dynamically through the registry. Each market represents a single asset pair (COLLATERAL → BORROW) in its own contract account.

Market account names follow <collateral>-<borrow>[-<n>].v1.tmplr.near, where each asset name is built from up to three parts: i if the token is held through NEAR Intents, the host chain when the asset is not native to it (eth, xlm, sol), and the asset symbol. So iethwbtc is WBTC on Ethereum held through Intents, ixlmusdc is USDC on Stellar held through Intents, and ibtc is native BTC held through Intents. A numeric suffix distinguishes successive deployments of the same pair.

The authoritative list is on-chain:

near contract call-function as-read-only v1.tmplr.near list_deployments \
    json-args '{"offset": 0, "count": 100}' network-config mainnet now

The call is paginated: count caps the page size, so if a page comes back full, request the next one with offset advanced by the page size ({"offset": 100, "count": 100}) and repeat until a page contains fewer than count entries.

Markets listed on app.templarfi.org

The markets currently offered in the app. Their immutable parameters and oracle configuration are on Risk Parameters.

Deprecated markets

These markets were retired from the app at the end of August 2026. Where the same pair was redeployed, the successor is the -1 or -2 market above. They remain on chain and fully functional (markets cannot be paused or removed), so existing positions can still be repaid and withdrawn, but the app no longer offers them and Templar's bots and monitoring focus on the listed markets. Users with positions in a deprecated market should migrate to its successor, or to another listed market for the same collateral.

Other active markets

The live Markets API classifies these markets as active, but they were not linked from the app navigation in a 2026-09-15 snapshot:

Use the API's status field for the current operational classification. The registry's list_deployments output remains the complete deployment list and includes historical contracts as well as active markets.

Each market's oracle account, price identifiers, and risk parameters are available from its get_configuration view; see Market Configuration. The declarative specifications markets were deployed from are in deployments/v1/. The registry's get_deployment view identifies the version key and code hash used at deployment; see Registry.

A separate registry, templar-alpha.near, hosts pre-release and liquidation-test markets on mainnet. Markets under it are not production markets.

Contract Verification

All smart contracts use reproducible builds. To verify deployed code:

near contract verify deployed-at <contract-id> mainnet now

Example output:

INFO The code obtained from the contract account ID and the code calculated from the repository are the same.
|    Contract code hash: DaudmUa3nAym9dfQkn8mpNPZxkphSRGwEaTMgtymVhFE
|    Contract version:	1.0.0
|    Standards used by the contract:	[nep330:1.2.0]
|    View the contract's source code on:	https://github.com/Templar-Protocol/contracts/tree/1d736e62a86424dd947284cbd8e83bef803fa9fb
|    Build Environment:	sourcescan/cargo-near:0.13.4-rust-1.85.0@sha256:a9d8bee7b134856cc8baa142494a177f2ba9ecfededfcdd38f634e14cca8aae2
|    Build Command:	cargo near build non-reproducible-wasm --locked

The verification compares the on-chain code hash with a build from the commit recorded in the contract's NEP-330 metadata, so it establishes that the deployed bytecode matches the published source commit. Whether that commit is covered by an audit must be checked separately against the audit reports. Released contract artifacts and their SHA-256 digests are recorded under contract/artifacts/releases/.