Describe the bug
Currently, the faucet endpoint does use the multi-cast feature of the API. So faucet requests won't get multi-casted to overridden targets in the multi-cast configuration.
To Reproduce
Steps to reproduce the behavior:
Send a faucet request to a testnet API with multicast configured with multiple targets
Observe the faucet request only gets routed to the default backend proxy stacks-node.
Expected behavior
Testnet faucet requests should get routed to all targets configured in the mult-cast config file.
We looks like we haven't ran into problems with this in a couple years (maybe due to improved mempool propagation in the stacks-node?). Going to close for now, please feel free to re-open.
Describe the bug Currently, the faucet endpoint does use the multi-cast feature of the API. So faucet requests won't get multi-casted to overridden targets in the multi-cast configuration.
To Reproduce Steps to reproduce the behavior:
Expected behavior Testnet faucet requests should get routed to all targets configured in the mult-cast config file.
API version: 1.0.7