From 1b9a7832c4111817e627f12446c09d0691fab658 Mon Sep 17 00:00:00 2001 From: Jacob Evans Date: Tue, 17 Sep 2019 18:06:53 +0100 Subject: [PATCH] Update v3-specification.md --- v3/v3-specification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v3/v3-specification.md b/v3/v3-specification.md index a76d1d5..d2f41fc 100644 --- a/v3/v3-specification.md +++ b/v3/v3-specification.md @@ -2386,7 +2386,7 @@ For more information about how this is used, see [hashing an order](#hashing-an- ## EIP-1271 Usage -Both the [`Validator](#validator) and [`EIP1271Wallet`](#eip1271wallet) signature types are [EIP-1271](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1271.md) compliant. Note that this standard does not specify how data should be encoded when it is passed to the verifying contract's `isValidSignature` function. The `Exchange` contract will pass data to the verifying contract that is ABI encoded with one of the following function signatures, depending on if a `Order` or `ZeroExTransaction` is being validated: +Both the [`Validator`](#validator) and [`EIP1271Wallet`](#eip1271wallet) signature types are [EIP-1271](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1271.md) compliant. Note that this standard does not specify how data should be encoded when it is passed to the verifying contract's `isValidSignature` function. The `Exchange` contract will pass data to the verifying contract that is ABI encoded with one of the following function signatures, depending on if a `Order` or `ZeroExTransaction` is being validated: ```solidity contract IEIP1271Data {