OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Smart Contracts

Intents

Intents is a public Rust smart-contract repository for NEAR. Its Verifier evaluates signed peer-to-peer exchange requests and can execute matched intents atomically. The repository also includes Proof of Authority token-bridge contracts and a controller interface.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Intents — OpenViST project profile in Smart Contracts.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the repository when you need NEAR contract code for verifying and atomically settling matched peer-to-peer intents, or when examining its separate PoA bridge components. It is developer infrastructure, not a turnkey trading interface.

Who it is for

  • Smart-contract developers building peer-to-peer asset exchanges on NEAR.
  • Teams developing services that verify and submit signed intents.
  • Developers exploring contract-based token bridging to NEAR.

Documented uses

  • Evaluate whether signed exchange requests can be fulfilled.
  • Settle reciprocal asset intents together in an atomic transaction.
  • Build NEAR contract artifacts from the repository.
  • Explore the included PoA bridge and shared signing-payload interfaces.
Before you choose

Requirements & limits

The repository is public and specifies an MIT license. It documents obtaining contract and ABI artifacts from releases or building from source.

  • The Verifier can be used independently, according to the README, while the repository includes additional components that work alongside it.
  • A documented swap requires deposits, signed reciprocal intents, joint submission through execute_intents, and subsequent withdrawals.
  • BIP-322, TIP-191 and ERC-191 are represented through internal payload traits; the README says these implementations are not a stable public API.
  • The PoA token and factory contracts are separate bridge components; examples of external assets do not guarantee arbitrary-asset support.
  • The repository documents build, integration-test and lint commands, but this profile does not claim they were executed.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build the contracts from source

Produce contract artifacts using the repository’s documented build targets.

Before you start

  • A working copy of the near/intents repository.
  • The build environment required by the repository; the README does not enumerate its dependencies.

Steps

  1. Run the command below to build one contract, optionally setting REPRODUCIBLE=1.

    Documented command
    make CONTRACT[/VARIANT]

  2. Alternatively, run make to build all contracts.

  3. Find the build artifacts in the res directory.

Expected outcome

Contract build artifacts are placed in `res`.

Guide limitations

  • This is a build recipe, not a deployment or runtime guide.
  • The README does not specify the full build environment prerequisites.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
near/intents · Official homepage title · retained in its source language
How we review sourcesSuggest a correction