-
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
refactor: add config params to stellar network for finality #499
base: main
Are you sure you want to change the base?
Conversation
@blockchainguyy |
@@ -630,6 +630,9 @@ | |||
"horizonRpc": "https://horizon-testnet.stellar.org", | |||
"networkType": "testnet", | |||
"chainType": "stellar", | |||
"decimals": 7, | |||
"finality": "1", |
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.
@blockchainguyy Can you share your research on the finality mechanism? Since it's a critical piece, we should validate
"explorer": { | ||
"name": "Stellar Expert", | ||
"url": "https://stellar.expert/explorer/testnet" | ||
}, | ||
"tokenSymbol": "XLM" |
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.
perhaps move these before contracts
key, so they're easier to spot (same elsewhere)
"decimals": 7, | ||
"finality": "1", | ||
"contracts": { | ||
"AxelarGateway": {} |
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 don't like adding an empty contract field. Makes it more confusing when testing if a contract config is present
https://axelarnetwork.atlassian.net/browse/AXE-7116