ERC-1271:合约账户签名验证ERC-1271: Standard Signature Validation Method for Contracts
交集:当 AI 内容凭证或数据授权由合约账户而不是个人私钥签署时,验证者需要问「这个合约是否认可该签名」;ERC-1271 给出合约侧统一验证入口。
适用范围:官方摘要说 EOA 能用私钥签消息而合约不能,因此提出通过 signing contract 上的 isValidSignature(hash, signature) 验证签名。它规定验证接口,不规定合约内部怎样决策,也不保证签名背后的业务声明真实。
未解决:合约钱包、多签与权限模块各自实现验证逻辑,跨应用仍要核对实现与升级风险;该规范已从 EIPs 仓库移到 ERCs 仓库,状态 Final,但本站不推断所有合约账户都支持。The intersection: when an AI content credential or data permission is signed by a contract account rather than a personal private key, verifiers need to ask whether the contract recognises the signature; ERC-1271 provides a common contract-side validation entry point.
Scope: the abstract says EOAs can sign messages with private keys but contracts cannot, and proposes validation through isValidSignature(hash, signature) on the signing contract. It standardises the interface, not the internal decision logic, and does not make the underlying business claim true.
Open: contract wallets, multisigs and permission modules implement their own validation, so applications still need to check implementation and upgrade risk; the specification moved from the EIPs repository to ERCs and is Final, but this site does not infer support by every contract account.
关键参数Key specs
- 协议状态 / status
- Final(官方 ERC 状态;具体部署范围官方未说明)
- 规范来源 / source
- https://raw.githubusercontent.com/ethereum/ercs/master/ERCS/erc-1271.md
- 核验日 / checked
- 2026-11-07
官方原文怎么说What the source says
Externally Owned Accounts (EOA) can sign messages with their associated private keys, but currently contracts cannot.
We propose a standard way for any contracts to verify whether a signature on a behalf of a given contract is valid.
status: Final
资料与许可Source and licence
- 资料时间Source checked
- 2026-11-07
- 许可 / 类型Licence / kind
- official-specification
- 许可说明Licence evidence
- https://raw.githubusercontent.com/ethereum/ercs/master/ERCS/erc-1271.md
- 类目Category
- 协议档案Protocol records