execute_intents function. The Verifier supports multiple signature standards to enable signing from NEAR, Ethereum, TRON, Solana, Stellar, TON, and passkey-based wallets.
- For intents structure before signing, see Intent Types and Execution.
- For key management, see Account Abstraction.
Every public key registered to an account can sign intents on its behalf. See Account Abstraction for key management details.
Signature types
Different wallets use different signing standards. To allow users to sign with their existing wallet, the Verifier supports multiple verification methods — each corresponding to a specific wallet ecosystem (e.g., ERC-191 for MetaMask, Raw Ed25519 for Phantom). Each signed intent conforms to the MultiPayload enum.NEP-413
The NEP-413 standard is an off-chain message signing standard recognized by NEAR wallets.ERC-191
Compliant with the ERC-191 standard for off-chain message signing (Ethereum wallets like MetaMask).There is no
public_key field because it can be recovered from the secp256k1 signature and data.TIP-191
Compliant with TIP-191, TRON’s off-chain message signing standard. TIP-191 is fully compatible with ERC-191.Like ERC-191, there is no
public_key field because it can be recovered from the secp256k1 signature and data. The same recovery byte normalization applies.