ERC-5267 — EIP-712 Domain Retrieval

Back to Account & Authentication

ERC-5267: EIP-712 Domain Retrieval

A meta-standard: contracts that use EIP-712 should expose their domain via a single view method so that wallets and indexers can construct typed signing requests without hard-coding the domain.

Required Method

function eip712Domain() external view returns (
    bytes1 fields,
    string memory name,
    string memory version,
    uint256 chainId,
    address verifyingContract,
    bytes32 salt,
    uint256[] memory extensions
);

Neo Equivalent

A Neo contract's domain is fully derivable from its manifest and script hash — wallets and clients fetch it via ContractManagement.GetContract(...) and the network ID via Runtime.GetNetwork(). The C# port just exposes a convenience method that returns the same metadata, but it's optional.

Live on Neo TestNet

Both implementations are deployed on Neo N3 TestNet (network magic 894710606).

Implementation	Contract Hash	Deploy Tx
Solidity (neo-solc)	0x1dd8a39225d515a4621c5214f336c78f4b19bb6c	0x5994e152…d7add3a8
Neo C# (nccs)	0xdcfa06612bfa8614e4d197bc8206b68320cd9877	0x028edfdf…3d17508

Cross-implementation getName and getVersion calls return identical MyDApp / 1. Source pairs under docs/standards-mirror/deployments/erc-5267/.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

contract DomainExposer {
    string  public constant NAME    = "MyDApp";
    string  public constant VERSION = "2";

    event EIP712DomainChanged();

    function eip712Domain() external view returns (
        bytes1   fields,
        string memory name,
        string memory version,
        uint256  chainId,
        address  verifyingContract,
        bytes32  salt,
        uint256[] memory extensions
    ) {
        fields            = bytes1(0x0f);   // name | version | chainId | verifyingContract
        name              = NAME;
        version           = VERSION;
        chainId           = block.chainid;
        verifyingContract = address(this);
        salt              = bytes32(0);
        extensions        = new uint256[](0);
    }
}

using System.ComponentModel;
using System.Numerics;
using Neo;
using Neo.SmartContract.Framework;
using Neo.SmartContract.Framework.Attributes;
using Neo.SmartContract.Framework.Native;
using Neo.SmartContract.Framework.Services;

namespace R3E.Examples;

[DisplayName("DomainExposer")]
[ContractPermission("*", "*")]
public class DomainExposer : SmartContract
{
    /// <summary>
    /// Convenience method for clients that prefer an explicit domain query over
    /// reading the manifest + network ID. The manifest already contains
    /// name and contract hash; this just bundles them.
    /// </summary>
    public static (string, BigInteger, UInt160) Domain()
    {
        var contract = ContractManagement.GetContract(Runtime.ExecutingScriptHash);
        return (contract.Manifest.Name, Runtime.GetNetwork(), Runtime.ExecutingScriptHash);
    }
}

Why Neo Has Less Ceremony

Wallet clients on Neo construct domain-bound signing payloads from the contract manifest and the network ID — both authoritative and immutable per-contract. There's no per-deploy "name + version" string to keep in sync because the manifest already carries Name, the script hash already identifies the deploy, and the network ID distinguishes mainnet/testnet.