From b0aa6db40633846abf3546c7a3d4d9435c7f0ff9 Mon Sep 17 00:00:00 2001 From: Jacob Evans Date: Tue, 17 Sep 2019 17:47:11 +0100 Subject: [PATCH 1/2] fix typo --- 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 d4f4082..a76d1d5 100644 --- a/v3/v3-specification.md +++ b/v3/v3-specification.md @@ -2454,7 +2454,7 @@ Doing any sort of division in the EVM may result in rounding errors. [`fillOrder - `marketBuyOrders` and `marketSellOrders` have been deprecated - The addition of [`marketBuyOrdersFillOrKill`](#marketbuyordersfillorkill) and [`marketSellOrdersFillOrKill`](#marketsellordersfillorkill) - All of the `marketBuy*` and `marketSell*` functions now allow multiple different assets to be bought or sold (be careful with this!) -- The ordering of transfers during a single fill has changed. A fill now first transfers an asset from the taker to the maker, opening up the ability to integrate the [`ERC20BuyerAsseyProxy`](https://github.com/0xProject/ZEIPs/issues/47) (along with other similar contracts) +- The ordering of transfers during a single fill has changed. A fill now first transfers an asset from the taker to the maker, opening up the ability to integrate the [`ERC20BuyerAssetProxy`](https://github.com/0xProject/ZEIPs/issues/47) (along with other similar contracts) ### Changes to order matching From 1b9a7832c4111817e627f12446c09d0691fab658 Mon Sep 17 00:00:00 2001 From: Jacob Evans Date: Tue, 17 Sep 2019 18:06:53 +0100 Subject: [PATCH 2/2] 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 {