Fix gateway initialization by properly funding escrow during setup #724
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.
The gateway service was failing to initialize properly because the escrow contract wasn't being funded correctly. This was causing the gateway's health check to fail with connection reset errors, even though the container was running.
This also has the benefit of using local-network configuration directly in our funding instead of defining constants.
Note
Previous funding script remains in place, maybe useful out of the local-testnet setup