-
Notifications
You must be signed in to change notification settings - Fork 391
chore: output BatcherPaymentService addresses as JSON
#1698
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
Conversation
BatcherPaymentService addresses as JSONBatcherPaymentService addresses as JSON
| --sig "run(string batcherConfigPath, string outputPath)") | ||
|
|
||
| # Extract the batcher payment service values from the output | ||
| # new_aligned_layer_service_manager_implementation=$(echo "$forge_output" | awk '/1: address/ {print $3}') |
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.
Shouldn't we do the same change as in [contracts/scripts/deploy_batcher_payment_service.sh](https://github.com/yetanotherco/aligned_layer/pull/1698/files#diff-4a582041a459061d1464141cee38003ede0385187a21ad63ffdb01dc84cdf8c5)
Both solutions work, but just for keep consistency
batcher_payment_service_proxy=$(jq -r '.addresses.batcherPaymentService' $BATCHER_PAYMENT_SERVICE_OUTPUT_PATH)
batcher_payment_service_implementation=$(jq -r '.addresses.batcherPaymentServiceImplementation' $BATCHER_PAYMENT_SERVICE_OUTPUT_PATH)
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.
Yes. I didn't do it just to minimize the amount of changes. I'll add it in a bit
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.
Done. I also removed some stale comments (0c0bbc8), lmk if that's OK
|
@MegaRedHand Are you aware the batcher payment addresses are currently being outputted in |
|
I saw the bash script uses An alternative could be to do that from the Solidity script. I can change to that approach if that seems better. |
If the issue arises from the usage of Alternatevly, if we need to have these addresses in another file, we would have to make a big migration since many components read the BatcherPayment addresses from the existing output file. |
Sure! Just to clarify, the changes in this PR don't touch the part that updates the |
JuArce
left a comment
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
avilagaston9
left a comment
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!
Co-authored-by: Uriel Mihura <[email protected]>
Co-authored-by: Uriel Mihura <[email protected]>
Co-authored-by: Uriel Mihura <[email protected]>
Co-authored-by: Uriel Mihura <[email protected]>
Output BatcherPaymentService addresses as JSON
Description
This PR changes the
BatcherPaymentServicedeployment script to follow the convention of outputting the addresses of deployed contracts in a JSON file.Type of change
Refactor
Checklist
testnet, everything else tostaging