Skip to content

Conversation

@gregdhill
Copy link
Member

Signed-off-by: Gregory Hill gregorydhill@outlook.com

We saw a number of timeouts on testnet when vaults were waiting for the faucet to respond. This change allows the faucet to respond immediately if the funding request is valid and then spawns a separate task to submit and watch the transaction(s). My plan was to batch and return the extrinsic hash to subscribe in the vault client but that is not possible (paritytech/subxt#559). My proposed next step is to simply retry registration if the client does not have sufficient funds or we could wait for the account to have sufficient funds before continuing.

Signed-off-by: Gregory Hill <gregorydhill@outlook.com>
@sander2
Copy link
Member

sander2 commented Jul 26, 2022

This change in isolation will break the funding process, so I don't think it's a good idea to merge without having the vault side ready

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants