-
Notifications
You must be signed in to change notification settings - Fork 208
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
10445 transfer pfm #10448
Draft
iomekam
wants to merge
16
commits into
master
Choose a base branch
from
10445-transfer-pfm
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
10445 transfer pfm #10448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deploying agoric-sdk with Cloudflare Pages
|
0xpatrickdev
force-pushed
the
10006-transfer-pfm
branch
from
November 12, 2024 01:35
90839e5
to
4e4f8c9
Compare
- in order to determine whether its possible to route a transfer through a particular ibc chain, we must know if they have the PFM module installed
- adds `ICQ_ENABLED` and `PFM_ENABLED` constants to support `CosmosChainInfo` - this data is not available via a well-known registry like cosmos/chain-registry, but necessary for the Orchestration API
- use `ts-blank-space` since `tsx` is no longer in `node_modules/.bin` - prefer yarn command instead of standalone script
- add `pfmEnabled: boolean` data - update snapshot tests
0xpatrickdev
force-pushed
the
10006-transfer-pfm
branch
2 times, most recently
from
November 12, 2024 01:38
1792090
to
5617071
Compare
0xpatrickdev
force-pushed
the
10006-transfer-pfm
branch
2 times, most recently
from
November 13, 2024 22:26
784feb2
to
d08f946
Compare
- in order to determine whether its possible to route a transfer through a particular ibc chain, we must know if they have the PFM module installed
- adds `ICQ_ENABLED` and `PFM_ENABLED` constants to support `CosmosChainInfo` - this data is not available via a well-known registry like cosmos/chain-registry, but necessary for the Orchestration API
- use `ts-blank-space` since `tsx` is no longer in `node_modules/.bin` - prefer yarn command instead of standalone script
0xpatrickdev
force-pushed
the
10006-transfer-pfm
branch
from
November 13, 2024 22:32
d08f946
to
6121bed
Compare
iomekam
force-pushed
the
10445-transfer-pfm
branch
from
November 14, 2024 15:09
c4f220f
to
dd376bf
Compare
…-sdk into 10445-transfer-pfm
0xpatrickdev
force-pushed
the
10006-transfer-pfm
branch
6 times, most recently
from
November 26, 2024 01:03
71059f0
to
5b163e4
Compare
0xpatrickdev
force-pushed
the
10006-transfer-pfm
branch
5 times, most recently
from
November 26, 2024 07:07
d6db026
to
2fa2f75
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes: #10445
Description
Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
Upgrade Considerations