Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Permissionless token pools #652
Permissionless token pools #652
Changes from 20 commits
b111359
60b19b0
5ad0364
0c2b602
1657c8c
8e0fe16
9fea02d
123638a
a84800a
fbda5e7
208c889
62d8b62
3325c86
7b0a7f7
8d73c06
1c15e67
4ba8886
6cd835a
f50dca5
c89ff60
4367860
85e7a66
573e213
a95c6a8
e8e3892
a054ee4
9c73d96
f35ca89
0a1544f
796c4d4
e8bce92
91311e9
927f404
9268032
08c1880
15425a7
d19790d
b6053c1
a51ceac
985e372
2156bd5
a8959ec
7dde9bd
eb8873d
8721682
eb57271
6bb2e73
52d559a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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.
suggestion: what do you think of the alternative option to pass the
destToken
instead of the pool? This way we can validate more strictly by queryinggetPool(destToken)
via the registry on the dest chain - and we can always be sure that the pool represents the token correctlyIn this case the mapping on the src chain would have to change to
token => chainSelector => token address (bytes)
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.
Adds an additional 5.8k gas for a single msg token and increases the size of the contract. Probably not worth it
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.
can we call it smt like
tokenDataForDest
to be more clearThere 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.
To double check my understanding - this was previously the source of truth for if a token is supported?
So the new method to determine this would be to read from of the token pools from
mapping(uint64 remoteChainSelector => RemoteChainConfig) internal s_remoteChainConfigs;
?If
(source chain pool).getRemotePool(chain selector destination)
.getRemotePool(chain selector source) == source chain pool addressThere 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.
+1, Commit DON was using this to find supported tokens
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.
It was using it to find tokens it needs to push prices for. This should be addressed by @justinkaseman next PR which introduces explicitly which tokens to push prices for
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.
@RensR Justin's PR gets all tokens supported by an offramp and filters out ones missing price getter config in job spec, so it is still requiring a trusted source for a list of supported tokens