Skip to content

feat(network-monitor): fund accounts from the funding service - #2603

Open
SantiagoPittella wants to merge 2 commits into
fs/2-request-fundsfrom
fs/3-network-and-monitor
Open

feat(network-monitor): fund accounts from the funding service#2603
SantiagoPittella wants to merge 2 commits into
fs/2-request-fundsfrom
fs/3-network-and-monitor

Conversation

@SantiagoPittella

Copy link
Copy Markdown
Collaborator

Summary

Adds support in hte network monitor for the funding service. The chain's faucet is no longer a source of fees, because a network does not always run a public faucet. --faucet-url still configures the faucet checks.

--funding-request-timeout defaults to two minutes, because the service answers only once its note is committed.

Added operator documentation and internal page for design.

Changelog

[[entry]]
scope       = "network-monitor"
impact      = "breaking"
description = "Fees are funded from the funding service via `--funding-service-url`; the faucet is no longer a source of fees."

[[entry]]
scope       = "docs"
impact      = "added"
description = "Operator documentation for the funding service."

@SantiagoPittella
SantiagoPittella added this pull request to stack #2602 September 9, 2026 19:25
Comment on lines +196 to +197
/// The funding service client; `None` when none is configured (zero-fee chains only).
funding: Option<FundingClient>,

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not this PRs problem, but I wonder if we can't somehow make it so that these things are always required, even on zero-fee chains.

One option is of course to just not have zero fee chains.. but I was hoping the flows could remain agnostic to the fee amount, as in fee=N holds even for N=0.

Comment thread bin/network-monitor/src/faucet.rs Outdated
@SantiagoPittella
SantiagoPittella removed this pull request from stack #2602 September 11, 2026 21:01
@SantiagoPittella
SantiagoPittella added this pull request to stack #2616 September 11, 2026 21:02
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