"Invalid address 0x" when submitting order without extension (hasExtension = false)

[jufelka]

Summary
Submitting a limit order without an extension (hasExtension flag set to false, no extension field in JSON) results in a 400 response:
{"error":"Bad Request","message":"Invalid address 0x","statusCode":400}
I cannot identify any field still pointing to an empty/zero address that the API treats as required. It looks like the backend still tries to parse an interaction / extension structure.

var makerTraitsNoExtBI = Traits.BuildMakerTraits( allowedSender: null, expirationUnix: 1755385393UL, nonceOrEpoch: 3UL, series: 0UL, partialFillsAllowed: true, multipleFillsAllowed: true, preInteraction: false, postInteraction: false, needCheckEpochManager: false, hasExtension: false, usePermit2: false, unwrapWeth: false);
Verification of Flags Before Sending
bool hasExtension = ((makerTraitsNoExtBI >> 249) & BigInteger.One) == BigInteger.One; bool postInteraction = ((makerTraitsNoExtBI >> 251) & BigInteger.One) == BigInteger.One; bool preInteraction = ((makerTraitsNoExtBI >> 252) & BigInteger.One) == BigInteger.One; Console.WriteLine($"hasExtension={hasExtension} postInteraction={postInteraction} preInteraction={preInteraction}");

JSON Payload Sent
{ "orderHash": "0xe52e480e5d58...", "signature": "0xb778d632b...", "data": { "makerAsset": "0xff970a61a04b1ca14834a43f5de4533ebddb5cc8", "takerAsset": "0x82af49447d8a07e3bd95bd0d56f35241523fbab1", "maker": "0x618...", "receiver": "0xc0dfdb9e7a392c3dbbe7c6fbe8fbc1789c9fe05e", "makingAmount": "1000000", "takingAmount": "500000000000000000", "salt": "17869197887894548966920054135963920299014857184121198371937508994779341940462", "makerTraits": "28948022309329048855892746252171976963321485972528220729556049814025540730880" } }

Response
{ "error": "Bad Request", "message": "Invalid address 0x", "statusCode": 400 }

[jufelka]

Update. The problem is in 'allowedSender'. If I set it to any address I get "Private orders are not supported through public API". But if it is emtpy, the error is ""Invalid address 0x"

[svanas]

@jufelka I'm receiving this error, too:

{"error":"Bad Request","message":"Invalid address 0x","statusCode":400}

I'm curious if you solved it or gave up. Thanks!

[belactriple9]

Hello!

As of right now, the 1inch Hosted Database for limit orders only accepts LimitOrderWithFee whose implementation in the SDK can be found here: https://github.com/1inch/limit-order-sdk/blob/master/src/limit-order/limit-order-with-fee.ts. This means the receiver must be the FeeTaker extension implementation address and the extension must be properly encoded and not just null. The reason you are receiving Invalid address 0x is because, as you observed, the empty extension is still attempting to be parsed since it is required.

The issue is not with 'allowedSender'. The allowedSender is a way to create P2P style orders by specifying the lower 10 bytes of a specific taker's address in the makerTraits. The error "Private orders are not supported through public API" means these lowest 10 bytes of the makerTraits are no null when they should be. As an aside - technically the LimitOrderWithFee extension does have a whitelist check but it's different than this private order system.

[svanas]

@belactriple9 I'm confused. Are you saying the "receiver" must always be set to a non-0x address and an "extension" must be present?

Previously, my "receiver" was set to 0x0000000000000000000000000000000000000000 and my "extension" was set to 0x and this worked just fine.

I noticed the official frontend uses the following receiver: 0xc0dfdb9e7a392c3dbbe7c6fbe8fbc1789c9fe05e.

[belactriple9]

It is not currently possible to use the 1inch API, limit order database, without the receiver being the FeeTaker extension implementation and the full, correct extension.
You may use the fee-info endpoint to get the FeeTaker address and any fees that must be included in the extension: https://business.1inch.com/portal/documentation/apis/orderbook/swagger?method=get&path=%2Fv4.1%2F1%2Ffee-info