fix(env): point the devnet IPFS gateway at the Bulletin-peered node - #62
Open
al3mart wants to merge 1 commit into
Open
fix(env): point the devnet IPFS gateway at the Bulletin-peered node#62al3mart wants to merge 1 commit into
al3mart wants to merge 1 commit into
Conversation
The devnet preset resolved metadata through https://ipfs.io/ipfs. Content stored on Bulletin Paseo is not reachable that way: the collator speaks Bitswap only and does not announce to the public IPFS DHT, so a public gateway has nothing to serve. `cdm install -n devnet` times out fetching contract metadata by CID. Measured against a metadata CID from the devnet registry: https://devnet-ipfs.api.polkadotcommunity.foundation/ipfs 200, 3.4 MB in 3.1s https://ipfs.io/ipfs 504 after 28s Use the Kubo gateway the Polkadot Community Foundation runs alongside the devnet Bulletin collator, and correct the comment: Bulletin Paseo does have a dedicated HTTP gateway, it is just not a public one.
al3mart
added a commit
to Polkadot-Community-Foundation/contract-dependency-manager
that referenced
this pull request
Jul 17, 2026
) The devnet preset resolved metadata through https://bullet.sik.rocks/ipfs, which now returns 405 for any path including its own root. Contract metadata fetches (`cdm install -n devnet`) had nothing to read. Measured against a metadata CID from the devnet registry: https://devnet-ipfs.api.polkadotcommunity.foundation/ipfs 200, 3.4 MB in 3.1s https://bullet.sik.rocks/ipfs 405 https://ipfs.io/ipfs 504 after 28s Use the Kubo gateway PCF runs alongside the devnet Bulletin collator. The public gateway is not an option either: the collator speaks Bitswap only and does not announce to the public IPFS DHT, so Bulletin content cannot be served from ipfs.io. That is also why upstream's devnet preset needs the same fix -- paritytech#62. Also drop the stale "registryAddress empty until PCF deploys its own registry" comment; that registry has been live at 0x59b0245... since #18.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
devnetpreset added in #61 resolves metadata throughhttps://ipfs.io/ipfs.Content stored on Bulletin Paseo isn't reachable that way — the collator speaks
Bitswap only and doesn't announce to the public IPFS DHT — so a public gateway has
nothing to serve, and
cdm install -n devnettimes out fetching contract metadataby CID.
Measured against a metadata CID from the devnet registry the preset already points
at (
0x59b0245778917af55224e5f8fb55f7f8d452619f):https://devnet-ipfs.api.polkadotcommunity.foundation/ipfshttps://ipfs.io/ipfsThis points the preset at the Kubo gateway the Polkadot Community Foundation runs
alongside the devnet Bulletin collator — the same operator as the
devnetregistrythe preset already resolves.
It also corrects the accompanying comment: Bulletin Paseo does have a dedicated
HTTP gateway, it just isn't a public one.