refactor: move FilBeam domain to chain configuration

[bajtos]

Summary

• Add filbeam.retrievalDomainName property to the Chain interface
• Configure FilBeam domains for mainnet (filbeam.io), calibration (calibration.filbeam.io), and devnet (localhost:8080)
• Update createPieceUrl to use chain configuration instead of hardcoded chainId check
• Update all callers to pass Chain instead of chainId

Test plan

• All 351 existing tests pass
• New tests for createPieceUrl covering all three chains
• Build passes
• Linter passes

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	synapse-dev	0551853	Jan 27 2026, 01:11 PM

[rvagg]

seems good to me, although I hope that devnet address isn't important for the standard path because so many things want to listen to 8080 there's a good chance you'll hit something existing on dev machines

[bajtos]

seems good to me, although I hope that devnet address isn't important for the standard path because so many things want to listen to 8080 there's a good chance you'll hit something existing on dev machines

Yeah, I share your concern.

Actually, FilBeam does not support local devnet. It would be nice to throw a helpful error when trying to retrieve a devnet piece via FilBeam, but it's not clear to me how to achieve that and I feel this is not worth our effort right now.

[rvagg]

there is the filbeam retriever in synapse-sdk, maybe it should be pulling the base address from the chain? in that case, a better port number might be advisable because I think we include it in the default retrieval path

[bajtos]

How do you feel about using filbeam.localhost:8080 for devnet? It won't work out of the box, but it's possible to configure your machine to make that hostname work, plus the hostname is IMO descriptive enough to make it clear what's going on when somebody tries FilBeam retrievals for devnet pieces.

[hugomrdias]

left a suggestion for the prop name

[hugomrdias]

Suggested change

	retrievalDomainName: string
	retrievalDomain: string

[bajtos]

Renamed in daa9035

[bajtos]

there is the filbeam retriever in synapse-sdk, maybe it should be pulling the base address from the chain? in that case, a better port number might be advisable because I think we include it in the default retrieval path

I will follow-up with another PR

[bajtos]

The follow-up PR:

• refactor: use Chain type for FilBeam retriever config #573