Smart Contract Addresses
Deployed Templar Protocol contracts, and how to verify them. For deploying a new market, see Deploying a market.
Deployments
- Registry:
v1.tmplr.near - LST Oracle Adapter:
lst.oracle.tmplr.near
Markets
Market contracts are deployed dynamically through the registry. Each market represents a single asset pair (COLLATERAL → BORROW).
A selection of available markets is shown below:
| Account ID | Collateral Asset | Borrow Asset |
|---|---|---|
ibtc-iethusdc.v1.tmplr.near | Native BTC (via NEAR Intents) | USDC on Ethereum (via NEAR Intents) |
iethwbtc-iethusdc.v1.tmplr.near | wBTC on Ethereum (via NEAR Intents) | USDC on Ethereum (via NEAR Intents) |
ibtc-usdc-1.v1.tmplr.near | Native BTC (via NEAR Intents) | USDC on NEAR |
stnear-usdc-1.v1.tmplr.near | stNEAR on NEAR | USDC on NEAR |
ixlm-ixlmusdc.v1.tmplr.near | Native XLM (via NEAR Intents) | USDC on XLM (via NEAR Intents) |
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