-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle REDACTED sender address #33
Conversation
here’s the repo for ccip-v2.ens.xyz: universal-offchain-unwrapper i’m almost certain that sender addresses aren’t being replaced with i think what is much more likely is that you’re using Cloudflare Logpush or similar, and the log software is redacting the sender address thinking that it’s sensitive data. see related Cloudflare Community post would be happy to be proven wrong, just can’t see how that’s possible at this time |
follow-up on this: started looking into it and this might be a cloudflare bug, still gathering info edit: nvm, this is still what i outlined above i think |
can you try adding a console.log for the sender value, and then tail your worker? e.g. |
ah ok, so definitely a cloudflare logging thing then. in that case i think the actual issue is definitely somewhere within your worker. |
https://zuplo.com/blog/2022/03/04/the-script-will-never-generate-a-response It seem to be about the Cloudflare worker script is using a global variable to store a promise |
I have pushed a temporary fix by removing the use of global variables at ensdomains/evmgateway#36 It work after removing global variables |
ENS Official CCIP Gateway Proxy (https://ccip-v2.ens.xyz) redact sender address with
REDACTED
. However, ccip-read-server implementation doesn't supportREDACTED
and response with "Invalid request format". Causing resolving process to fail.For example: https://op-gateway-worker.optidomains.workers.dev/REDACTED/0xea9cd3bf000000000000000000000000f079f2a30f3c797f8e6920ad783b74846a9acbf4000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000002000001ff000000000000000000000000000000000000000000000000000000000102200304ff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000020438bfe3fc990665148f8ac1638323ab84054a5c22a1ab61fe63cebc3040129cb0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000020438bfe3fc990665148f8ac1638323ab84054a5c22a1ab61fe63cebc3040129cb000000000000000000000000000000000000000000000000000000000000000b6465736372697074696f6e000000000000000000000000000000000000000000.json
Response: Invalid request format
We fix this by checking if sender is
REDACTED
then set it toaddress(0)