Skip to content
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

Merged
merged 18 commits into from
Oct 19, 2022
Merged

Enable cross-chain authorizers #1488

merged 18 commits into from
Oct 19, 2022

Conversation

dcroote
Copy link
Contributor

@dcroote dcroote commented Oct 4, 2022

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.

@dcroote dcroote marked this pull request as draft October 4, 2022 04:07
@dcroote dcroote self-assigned this Oct 6, 2022
@dcroote dcroote marked this pull request as ready for review October 6, 2022 08:21
@dcroote dcroote requested a review from a team October 6, 2022 08:21
Copy link
Contributor

@Siegrift Siegrift left a 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.

@dcroote dcroote requested a review from Siegrift October 14, 2022 08:00
Copy link
Contributor

@Siegrift Siegrift left a 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'],
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@dcroote
Copy link
Contributor Author

dcroote commented Oct 19, 2022

Tested on localhost (same way as e2e tests), looks fine.

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).

@dcroote dcroote merged commit 4b28436 into master Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cross-chain authorizers
2 participants