-
Notifications
You must be signed in to change notification settings - Fork 72
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
Enable cross-chain authorizers #1488
Conversation
0ba0edf
to
aa4c3dc
Compare
959d30c
to
f2ca933
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of using the examples to test this, but I think the example should be a bit more polished and runnable by other users and real chains.
packages/airnode-examples/contracts/coingecko-e2e/EverythingAuthorizer.sol
Outdated
Show resolved
Hide resolved
packages/airnode-examples/test/example-files-are-up-to-date.test.ts
Outdated
Show resolved
Hide resolved
packages/airnode-node/src/evm/handlers/initialize-provider.test.ts
Outdated
Show resolved
Hide resolved
Having the addresses in secrets.env is unnecessarily roundabout for ending up with the addresses in config.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM. Tested on localhost (same way as e2e tests), looks fine.
{ | ||
maxConcurrency: 100, | ||
authorizers: { | ||
requesterEndpointAuthorizers: ['0xE2E0000000000000000000000000000000000000'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: You can put them into secrets for easier implementation. But I know they are not secrets in practice so hardcoding makes sense as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks- I considered this, but because canonically we do not store addresses like this as secrets I opted instead for the placeholder addresses that get replaced.
Thanks. I make some fixes to the cross-chain aspects of the integration and confirmed it's now working on Sepolia (same chain) with a polygon mumbai cross-chain authorizer (in addition to localhost E2E via CI). |
Closes #1284.
The core logic is in initialize-provider.ts and the coingecko-cross-chain-authorizer README has an explanation of how this user-runnable integration works.