Skip to content

fix(config): refuse to start with an unusable chain price cap - #760

Merged
MoonBoi9001 merged 4 commits into
mb9/send-per-entity-price-ceiling-to-iisafrom
mb9/refuse-unusable-per-chain-price-caps
Oct 27, 2026
Merged

MoonBoi9001 merged 4 commits into
mb9/send-per-entity-price-ceiling-to-iisafrom
mb9/refuse-unusable-per-chain-price-caps

Conversation

@MoonBoi9001

Copy link
Copy Markdown
Member

Dipper now refuses to start when any entry in max_grt_per_30_days is not a positive number, and the error names the chain and its value. A cap of 0 shuts out every priced indexer on that chain, and IISA rejects a negative one, which dipper treats as an outage and retries every 60 seconds without end.

Dipper's per-chain cap on what it pays each 30 days was never checked when the service started.
A cap of 0 shuts out every priced indexer, and IISA refuses a negative one, which dipper retries
every 60 seconds forever. Startup now refuses any cap that is not positive, naming its chain.
@MoonBoi9001
MoonBoi9001 added this pull request to stack #765 October 27, 2026 08:40
@MoonBoi9001
MoonBoi9001 marked this pull request as ready for review October 27, 2026 09:44
Every offer's on-chain payment limit comes from this cap, so 0, a negative or NaN offered
indexers nothing and infinity lifted the limit. Test configs now use the default of 20,000.
It rejects caps of 0, negative, NaN and infinity, and only a cap of 0 excludes every priced
indexer, so the old name described 1 case out of 4.
@MoonBoi9001
MoonBoi9001 merged commit dd404b2 into main Oct 27, 2026
12 checks passed
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.

1 participant