IPFS example with Kubo

[bkontur]

Relates to: #33
PR: #71

How to run

Install Kubo

wget https://dist.ipfs.tech/kubo/v0.38.0/kubo_v0.38.0_linux-amd64.tar.gz
tar -xvzf kubo_v0.38.0_linux-amd64.tar.gz
cd kubo
sudo bash install.sh
ipfs version
ipfs init
ipfs daemon

Output:

Initializing daemon...
Kubo version: 0.38.0
Repo version: 18
System version: amd64/linux
Golang version: go1.25.1
PeerID: 12D3KooWKZcts5N54ukoNujKXMz6J84A6cn2mtBzxaEsU8uB6uDz
2025/10/08 13:25:25 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
Swarm listening on 127.0.0.1:4001 (TCP+UDP)
Swarm listening on 172.17.0.1:4001 (TCP+UDP)
Swarm listening on 192.168.3.242:4001 (TCP+UDP)
Swarm listening on 192.168.4.241:4001 (TCP+UDP)
Swarm listening on [::1]:4001 (TCP+UDP)
Run 'ipfs id' to inspect announced and discovered multiaddrs of this node.
RPC API server listening on /ip4/127.0.0.1/tcp/5001
WebUI: http://127.0.0.1:5001/webui
Gateway server listening on /ip4/127.0.0.1/tcp/8080
Daemon is ready

Download zombienet

wget https://github.com/paritytech/zombienet/releases/download/v1.3.133/zombienet-linux-x64
chmod +x zombienet-linux-x64

Build Bulletin

git clone https://github.com/paritytech/polkadot-bulletin-chain.git
cd polkadot-bulletin-chain
git checkout -b bko-examples --track origin/bko-examples
cargo build --release -p polkadot-bulletin-chain

Download Zombienet

# cd polkadot-bulletin-chain - make sure we are here
wget https://github.com/paritytech/zombienet/releases/download/v1.3.133/zombienet-linux-x64

Run Bulletin

POLKADOT_BULLETIN_BINARY_PATH=./target/release/polkadot-bulletin-chain ./zombienet-linux-x64 -p native spawn ./zombienet/bulletin-polkadot-local.toml

IPFS swarm connect of Bulletin nodes with --ipfs-server

ipfs swarm connect /ip4/127.0.0.1/tcp/10001/ws/p2p/12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm
# connect 12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm success
ipfs swarm connect /ip4/127.0.0.1/tcp/12347/ws/p2p/12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby
# connect 12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby success
ipfs swarm peers 

Trigger authorize, store and IPFS get

# cd polkadot-bulletin-chain - make sure we are here
cd examples
npm install @polkadot/api @polkadot/keyring @polkadot/util-crypto @polkadot/util multiformats ipfs-http-client
node authorize_and_store.js

Problem does not return data - just hangs on the last command and timeouts after some time

node authorize_and_store.js
(node:532180) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///tmp/testet/authorize_and_store.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /tmp/testet/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
2025-10-08 13:48:28        REGISTRY: Unknown signed extensions ValidateSigned, BridgeRejectObsoleteHeadersAndMessages found, treating them as no-effect
2025-10-08 13:48:28        API/INIT: RPC methods not decorated: chainHead_v1_body, chainHead_v1_call, chainHead_v1_continue, chainHead_v1_follow, chainHead_v1_header, chainHead_v1_stopOperation, chainHead_v1_storage, chainHead_v1_unfollow, chainHead_v1_unpin, chainSpec_v1_chainName, chainSpec_v1_genesisHash, chainSpec_v1_properties, transactionWatch_v1_submitAndWatch, transactionWatch_v1_unwatch, transaction_v1_broadcast, transaction_v1_stop
Doing authorization...
Transaction authorizeAccount result: 0x248835f504be082bcdf92ec89874f795fd4dd2f99547f4bbcf25e4e1814ba06d
Authorized!
Storing data...
Storing data: Hello, Bulletin remote3 - Wed Oct 08 2025 13:48:36 GMT+0000 (Coordinated Universal Time)
Transaction store result: 0x1d2ae0a5b2e8e8d7e58d5d313aeefed2cf667f6bb7c6e1bdbb82a50db87e12af
Stored data with CID:  CID(bafk2bzacecyfddy3sbswudtwnrjqrtnoryo5gv4v6gcmuseylkma5icb45zls)
Reading content... cid:  CID(bafk2bzacecyfddy3sbswudtwnrjqrtnoryo5gv4v6gcmuseylkma5icb45zls)
Trying to get cid:  CID(bafk2bzacecyfddy3sbswudtwnrjqrtnoryo5gv4v6gcmuseylkma5icb45zls)

TypeError: fetch failed
    at node:internal/deps/undici/undici:13510:13
    at async Client.fetch (/tmp/testet/node_modules/ipfs-utils/src/http.js:140:22)
    at async Object.get (file:///tmp/testet/node_modules/ipfs-http-client/src/block/get.js:14:17)
    at async read_from_ipfs (file:///tmp/testet/authorize_and_store.js:60:19)
    at async main (file:///tmp/testet/authorize_and_store.js:104:19) {
  [cause]: HeadersTimeoutError: Headers Timeout Error
      at FastTimer.onParserTimeout [as _onTimeout] (node:internal/deps/undici/undici:6249:32)
      at Timeout.onTick [as _onTimeout] (node:internal/deps/undici/undici:2210:17)
      at listOnTimeout (node:internal/timers:588:17)
      at process.processTimers (node:internal/timers:523:7) {
    code: 'UND_ERR_HEADERS_TIMEOUT'
  }
}

More info for investigation

bkontur@toaster1:~/kubo$ ipfs id 12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm
{
	"ID": "12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm",
	"PublicKey": "CAESINW/Sj/M5xewOIvMJ0nrwUitmWmyP0XuG2Bf1Yd4V2rE",
	"Addresses": [
		"/p2p/12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm"
	],
	"AgentVersion": "",
	"Protocols": [
		"/ipfs/bitswap/1.2.0",
		"/ipfs/ping/1.0.0"
	]
}

bkontur@toaster1:~/kubo$ ipfs id 12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby
{
	"ID": "12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby",
	"PublicKey": "CAESIOzBtYcn8/ErMZSIGp7LneCyjOeyByMNjpMP4bznXiVs",
	"Addresses": [
		"/p2p/12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby"
	],
	"AgentVersion": "",
	"Protocols": [
		"/ipfs/bitswap/1.2.0",
		"/ipfs/ping/1.0.0"
	]
}

bkontur@toaster1:~/kubo$ ipfs bitswap stat
bitswap status
	blocks received: 3
	blocks sent: 0
	data received: 3884
	data sent: 0
	dup blocks received: 0
	dup data received: 0
	wantlist [1 keys]
		bafk2bzacecyfddy3sbswudtwnrjqrtnoryo5gv4v6gcmuseylkma5icb45zls
	partners [4]

Some logs from the Bulletin

cat /tmp/zombie-eaab4f737f4a74587da5d38d18d98feb_-457541-yTugVRRbG0gJ/alice.log | grep bit

2025-10-08 13:31:36.033 DEBUG tokio-runtime-worker sub-libp2p::bitswap: starting bitswap server
2025-10-08 13:44:53.343 DEBUG tokio-runtime-worker sub-libp2p::bitswap: handle bitswap request from PeerId("12D3KooWKZcts5N54ukoNujKXMz6J84A6cn2mtBzxaEsU8uB6uDz") for [(Cid(bafk2bzaceaicq5fdo5ojy2idfgrkx26pbiyfcqceaj7nn3gspsrupwyluldou), Have)]
2025-10-08 13:44:53.343 TRACE tokio-runtime-worker sub-libp2p::bitswap: found cid Cid(bafk2bzaceaicq5fdo5ojy2idfgrkx26pbiyfcqceaj7nn3gspsrupwyluldou), hash 0x102874a3775c9c690329a2abebcf0a30514044027ed6ecd27ca347db0ba2c6ea

And nothing else, if I run node authorize_and_store.js multiple times (generates different CID all the time), Then ipfs bitswap stat changes and I see wantlist [1 keys] with the CID, but the logs does not change, I can see just first request in the Bulletin node - looks like it stopped processing Bitswap or something.

Nodejs code

import { create } from 'ipfs-http-client';

// Connect to a local IPFS node or Infura/IPFS gateway
const ipfs = create({
    url: 'http://127.0.0.1:5001', // Local IPFS API
});

console.log('Trying to get cid: ', cid);
const block = await ipfs.block.get(cid);
console.log('Received block: ', block);

Direct IPFS commands

ipfs block get bafk2bzacebkeungwf4uyjgxawfawxcathvgq4rfud5vnhsmm4wg6jhdz4zgri
^C
Error: context canceled
bkontur@toaster1:~/kubo$ ipfs block get /ipfs/bafk2bzacebkeungwf4uyjgxawfawxcathvgq4rfud5vnhsmm4wg6jhdz4zgri
^C
Error: context canceled

[bkontur]

cc: @dmitry-markin @peetzweg guys, what am I missing?

[lexnv]

Dmitry is currently on holiday, I'll try to help as much as possible here, although I don't have the entire context.

Which network backend is the bulletin chain using? (libp2p or litep2p)

For litep2p we have several improvements added by Dmitry, which are going through a round of testing:

• kademlia: Track success of PUT_VALUE queries litep2p#427
• kademlia: Workaround for dealing with not implemented PUT_VALUE ACKs litep2p#430
• kademlia: Track success of ADD_PROVIDER queries litep2p#432

If running litep2p, could you point the cargo toml to an unreleased branch containing all improvements (ie dm-add-provider-success). I remember there is still an open question about ADD_PROVIDER / GET_PROVIDER. The providers were published successfully, but for some reason, we were unable to fetch them under certain scenarios. This might indicate that litep2p has slightly diverged from the spec, which could be true for libp2p (I don't believe we confirmed this).

[bkontur]

Which network backend is the bulletin chain using? (libp2p or litep2p)

@lexnv litep2p, libp2p is disabled:

polkadot-bulletin-chain/node/src/command.rs

Lines 214 to 221 in 85dc48d

	match config.network.network_backend {
	NetworkBackendType::Litep2p => (),
	NetworkBackendType::Libp2p => {
	return Err(
	"For `ipfs-server`, we expect only the `config.network.network_backend=litep2p` (`--network-backend=litep2p`) setting, because Bitswap support requires it!"
	.into(),
	)
	}

ok, I will try to check dm-add-provider-success also, thank you

[lexnv]

Oki doki, thanks! In case you are still experiencing problems, the litep2p=trace logs may surface the reason 🙏

[bkontur]

@lexnv I am running two validators locally with --ipfs-server and local Kubo. What does Discovered new external address for our node: mean? Is it ok?

bkontur@toaster1:~/kubo$ cat /tmp/zombie-8b9d4e38d8795fadbf757de9005cd467_-3607596-8FWGbm9kHP0n/alice.log | grep "sub-li"
2025-10-09 10:13:16.550  INFO main sub-libp2p: Local node identity is: 12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm
2025-10-09 10:13:16.550  INFO main sub-libp2p: Running litep2p network backend
2025-10-09 10:13:16.550 DEBUG tokio-runtime-worker sub-libp2p::bitswap: starting bitswap server
2025-10-09 10:13:22.804  INFO tokio-runtime-worker sub-libp2p: 🔍 Discovered new external address for our node: /ip4/127.0.0.1/tcp/10001/ws/p2p/12D3KooWQCkBm1BYtkHpocxCwMgR8yjitEeHGx8spzcDLGt2gkBm
2025-10-09 10:15:23.415 DEBUG tokio-runtime-worker sub-libp2p::bitswap: handle bitswap request from PeerId("12D3KooWKZcts5N54ukoNujKXMz6J84A6cn2mtBzxaEsU8uB6uDz") for [(Cid(bafk2bzacec7pwi6ldve5rc53gtmlocylbn7fnnkqhtrawg4ma6z32yt7pd42s), Have)]
2025-10-09 10:15:23.415 TRACE tokio-runtime-worker sub-libp2p::bitswap: missing cid Cid(bafk2bzacec7pwi6ldve5rc53gtmlocylbn7fnnkqhtrawg4ma6z32yt7pd42s), hash 0xbefb23cb1d49d88bbb34d8b70b0b0b7e56b5503ce20b1b8c07b3bd627f78f9a9

bkontur@toaster1:~/kubo$ cat /tmp/zombie-8b9d4e38d8795fadbf757de9005cd467_-3607596-8FWGbm9kHP0n/bob.log | grep "sub-li"
2025-10-09 10:13:21.799 DEBUG tokio-runtime-worker sub-libp2p::bitswap: starting bitswap server
2025-10-09 10:13:21.799  INFO                 main sub-libp2p: Local node identity is: 12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby
2025-10-09 10:13:21.799  INFO                 main sub-libp2p: Running litep2p network backend
2025-10-09 10:13:22.804  INFO tokio-runtime-worker sub-libp2p: 🔍 Discovered new external address for our node: /ip4/127.0.0.1/tcp/12347/ws/p2p/12D3KooWRkZhiRhsqmrQ28rt73K7V3aCBpqKrLGSXmZ99PTcTZby
2025-10-09 10:15:23.415 DEBUG tokio-runtime-worker sub-libp2p::bitswap: handle bitswap request from PeerId("12D3KooWKZcts5N54ukoNujKXMz6J84A6cn2mtBzxaEsU8uB6uDz") for [(Cid(bafk2bzacec7pwi6ldve5rc53gtmlocylbn7fnnkqhtrawg4ma6z32yt7pd42s), Have)]
2025-10-09 10:15:23.415 TRACE tokio-runtime-worker sub-libp2p::bitswap: missing cid Cid(bafk2bzacec7pwi6ldve5rc53gtmlocylbn7fnnkqhtrawg4ma6z32yt7pd42s), hash 0xbefb23cb1d49d88bbb34d8b70b0b0b7e56b5503ce20b1b8c07b3bd627f78f9a9

Also attaching the full log:

alice.log

[peetzweg]

A common hiccup is that people request the cid with SHA hash but I see you already did it properly with Blake2b and raw codec 👍

For me this actually worked first try following your instructions. Great instructions btw.

node authorize_and_store.js 
(node:67652) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///Users/ppoloczek/git/polkadot-bulletin-chain/examples/authorize_and_store.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /Users/ppoloczek/git/polkadot-bulletin-chain/examples/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
2025-10-10 16:52:43        REGISTRY: Unknown signed extensions ValidateSigned, BridgeRejectObsoleteHeadersAndMessages found, treating them as no-effect
2025-10-10 16:52:43        API/INIT: RPC methods not decorated: chainHead_v1_body, chainHead_v1_call, chainHead_v1_continue, chainHead_v1_follow, chainHead_v1_header, chainHead_v1_stopOperation, chainHead_v1_storage, chainHead_v1_unfollow, chainHead_v1_unpin, chainSpec_v1_chainName, chainSpec_v1_genesisHash, chainSpec_v1_properties, transactionWatch_v1_submitAndWatch, transactionWatch_v1_unwatch, transaction_v1_broadcast, transaction_v1_stop
Doing authorization...
Transaction authorizeAccount result: 0x913d7f656084ed02ee82c0d110f933149e3382f676fc1d521b26cf149b5a61b7
Authorized!
Storing data...
Storing data: Hello, Bulletin remote3 - Fri Oct 10 2025 16:52:51 GMT+0200 (Central European Summer Time)
Transaction store result: 0x3701233165b8a1de13cd2db62e9746d4ecaefc24439dca3bbf3ae67032717c96
Stored data with CID:  CID(bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo)
Reading content... cid:  CID(bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo)
Trying to get cid:  CID(bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo)
Received block:  Uint8Array(90) [
   72, 101, 108, 108, 111,  44,  32,  66, 117, 108, 108, 101,
  116, 105, 110,  32, 114, 101, 109, 111, 116, 101,  51,  32,
   45,  32,  70, 114, 105,  32,  79,  99, 116,  32,  49,  48,
   32,  50,  48,  50,  53,  32,  49,  54,  58,  53,  50,  58,
   53,  49,  32,  71,  77,  84,  43,  48,  50,  48,  48,  32,
   40,  67, 101, 110, 116, 114,  97, 108,  32,  69, 117, 114,
  111, 112, 101,  97, 110,  32,  83, 117, 109, 109, 101, 114,
   32,  84, 105, 109, 101,  41
]
Content as bytes: Uint8Array(90) [
   72, 101, 108, 108, 111,  44,  32,  66, 117, 108, 108, 101,
  116, 105, 110,  32, 114, 101, 109, 111, 116, 101,  51,  32,
   45,  32,  70, 114, 105,  32,  79,  99, 116,  32,  49,  48,
   32,  50,  48,  50,  53,  32,  49,  54,  58,  53,  50,  58,
   53,  49,  32,  71,  77,  84,  43,  48,  50,  48,  48,  32,
   40,  67, 101, 110, 116, 114,  97, 108,  32,  69, 117, 114,
  111, 112, 101,  97, 110,  32,  83, 117, 109, 109, 101, 114,
   32,  84, 105, 109, 101,  41
]
Content as string: 72,101,108,108,111,44,32,66,117,108,108,101,116,105,110,32,114,101,109,111,116,101,51,32,45,32,70,114,105,32,79,99,116,32,49,48,32,50,48,50,53,32,49,54,58,53,50,58,53,49,32,71,77,84,43,48,50,48,48,32,40,67,101,110,116,114,97,108,32,69,117,114,111,112,101,97,110,32,83,117,109,109,101,114,32,84,105,109,101,41

ipfs block get bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo
Hello, Bulletin remote3 - Fri Oct 10 2025 16:52:51 GMT+0200 (Central European Summer Time)%     ```

[bkontur]

@antkve Could you please check and test these instructions? Maybe it is related to my sever setting or sudo or I don't know :D

[dmitry-markin]

The issue is caused by downstream library upgrade in kubo. This PR in boxo (Bitswap implementation for IPFS) is breaking things for us: ipfs/boxo#984.

I will continue investigation and check what can be done.

Meanwhile, downgrading kubo to v0.36.0 depending on boxo < v0.33.1 fixes the issue locally.

[bkontur]

A common hiccup is that people request the cid with SHA hash but I see you already did it properly with Blake2b and raw codec 👍

For me this actually worked first try following your instructions. Great instructions btw.

node authorize_and_store.js
(node:67652) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///Users/ppoloczek/git/polkadot-bulletin-chain/examples/authorize_and_store.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /Users/ppoloczek/git/polkadot-bulletin-chain/examples/package.json.
(Use node --trace-warnings ... to show where the warning was created)
2025-10-10 16:52:43 REGISTRY: Unknown signed extensions ValidateSigned, BridgeRejectObsoleteHeadersAndMessages found, treating them as no-effect
2025-10-10 16:52:43 API/INIT: RPC methods not decorated: chainHead_v1_body, chainHead_v1_call, chainHead_v1_continue, chainHead_v1_follow, chainHead_v1_header, chainHead_v1_stopOperation, chainHead_v1_storage, chainHead_v1_unfollow, chainHead_v1_unpin, chainSpec_v1_chainName, chainSpec_v1_genesisHash, chainSpec_v1_properties, transactionWatch_v1_submitAndWatch, transactionWatch_v1_unwatch, transaction_v1_broadcast, transaction_v1_stop
Doing authorization...
Transaction authorizeAccount result: 0x913d7f656084ed02ee82c0d110f933149e3382f676fc1d521b26cf149b5a61b7
Authorized!
Storing data...
Storing data: Hello, Bulletin remote3 - Fri Oct 10 2025 16:52:51 GMT+0200 (Central European Summer Time)
Transaction store result: 0x3701233165b8a1de13cd2db62e9746d4ecaefc24439dca3bbf3ae67032717c96
Stored data with CID: CID(bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo)
Reading content... cid: CID(bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo)
Trying to get cid: CID(bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo)
Received block: Uint8Array(90) [
72, 101, 108, 108, 111, 44, 32, 66, 117, 108, 108, 101,
116, 105, 110, 32, 114, 101, 109, 111, 116, 101, 51, 32,
45, 32, 70, 114, 105, 32, 79, 99, 116, 32, 49, 48,
32, 50, 48, 50, 53, 32, 49, 54, 58, 53, 50, 58,
53, 49, 32, 71, 77, 84, 43, 48, 50, 48, 48, 32,
40, 67, 101, 110, 116, 114, 97, 108, 32, 69, 117, 114,
111, 112, 101, 97, 110, 32, 83, 117, 109, 109, 101, 114,
32, 84, 105, 109, 101, 41
]
Content as bytes: Uint8Array(90) [
72, 101, 108, 108, 111, 44, 32, 66, 117, 108, 108, 101,
116, 105, 110, 32, 114, 101, 109, 111, 116, 101, 51, 32,
45, 32, 70, 114, 105, 32, 79, 99, 116, 32, 49, 48,
32, 50, 48, 50, 53, 32, 49, 54, 58, 53, 50, 58,
53, 49, 32, 71, 77, 84, 43, 48, 50, 48, 48, 32,
40, 67, 101, 110, 116, 114, 97, 108, 32, 69, 117, 114,
111, 112, 101, 97, 110, 32, 83, 117, 109, 109, 101, 114,
32, 84, 105, 109, 101, 41
]
Content as string: 72,101,108,108,111,44,32,66,117,108,108,101,116,105,110,32,114,101,109,111,116,101,51,32,45,32,70,114,105,32,79,99,116,32,49,48,32,50,48,50,53,32,49,54,58,53,50,58,53,49,32,71,77,84,43,48,50,48,48,32,40,67,101,110,116,114,97,108,32,69,117,114,111,112,101,97,110,32,83,117,109,109,101,114,32,84,105,109,101,41

ipfs block get bafk2bzaceaq5etxf3vosxghbs3mlhwc532lcekmsshwv7my5qcqh5tqsumuwo
Hello, Bulletin remote3 - Fri Oct 10 2025 16:52:51 GMT+0200 (Central European Summer Time)% ```

@peetzweg could you please confirm what Kubo version did you use?

[bkontur]

@dmitry-markin you right, thank you, I downgraded to 0.35.0, and now it works like a charm.

~/cargo-remote-builds-bulletin/9907520327012243881/examples$ node authorize_and_store.js
(node:1725098) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///home/bkontur/cargo-remote-builds-bulletin/9907520327012243881/examples/authorize_and_store.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /home/bkontur/cargo-remote-builds-bulletin/9907520327012243881/examples/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
2025-10-14 14:11:49        REGISTRY: Unknown signed extensions ValidateSigned, BridgeRejectObsoleteHeadersAndMessages found, treating them as no-effect
2025-10-14 14:11:49        API/INIT: RPC methods not decorated: chainHead_v1_body, chainHead_v1_call, chainHead_v1_continue, chainHead_v1_follow, chainHead_v1_header, chainHead_v1_stopOperation, chainHead_v1_storage, chainHead_v1_unfollow, chainHead_v1_unpin, chainSpec_v1_chainName, chainSpec_v1_genesisHash, chainSpec_v1_properties, transactionWatch_v1_submitAndWatch, transactionWatch_v1_unwatch, transaction_v1_broadcast, transaction_v1_stop
Doing authorization...
Transaction authorizeAccount result: 0x9cc506b7d8b8fb1bf7c0e5406b58bec20003e244a9441ea84f8db9aba72ee7cb
Authorized!
Storing data...
Storing data: Hello, Bulletin remote3 - Tue Oct 14 2025 14:11:57 GMT+0000 (Coordinated Universal Time)
Transaction store result: 0xbc5b9a6a1889a99cc59905000957adbab1c4601fd92284a27e617abf24cd7286
Stored data with CID:  CID(bafk2bzacecy4l7vqdavtxdsxmazl5qq5d7wpal6k7yhboj4xzngy6dr2jghw2)
Reading content... cid:  CID(bafk2bzacecy4l7vqdavtxdsxmazl5qq5d7wpal6k7yhboj4xzngy6dr2jghw2)
Trying to get cid:  CID(bafk2bzacecy4l7vqdavtxdsxmazl5qq5d7wpal6k7yhboj4xzngy6dr2jghw2)
Received block:  Uint8Array(88) [
   72, 101, 108, 108, 111,  44,  32,  66, 117, 108, 108, 101,
  116, 105, 110,  32, 114, 101, 109, 111, 116, 101,  51,  32,
   45,  32,  84, 117, 101,  32,  79,  99, 116,  32,  49,  52,
   32,  50,  48,  50,  53,  32,  49,  52,  58,  49,  49,  58,
   53,  55,  32,  71,  77,  84,  43,  48,  48,  48,  48,  32,
   40,  67, 111, 111, 114, 100, 105, 110,  97, 116, 101, 100,
   32,  85, 110, 105, 118, 101, 114, 115,  97, 108,  32,  84,
  105, 109, 101,  41
]
Content as bytes: Uint8Array(88) [
   72, 101, 108, 108, 111,  44,  32,  66, 117, 108, 108, 101,
  116, 105, 110,  32, 114, 101, 109, 111, 116, 101,  51,  32,
   45,  32,  84, 117, 101,  32,  79,  99, 116,  32,  49,  52,
   32,  50,  48,  50,  53,  32,  49,  52,  58,  49,  49,  58,
   53,  55,  32,  71,  77,  84,  43,  48,  48,  48,  48,  32,
   40,  67, 111, 111, 114, 100, 105, 110,  97, 116, 101, 100,
   32,  85, 110, 105, 118, 101, 114, 115,  97, 108,  32,  84,
  105, 109, 101,  41
]
Content as string: 72,101,108,108,111,44,32,66,117,108,108,101,116,105,110,32,114,101,109,111,116,101,51,32,45,32,84,117,101,32,79,99,116,32,49,52,32,50,48,50,53,32,49,52,58,49,49,58,53,55,32,71,77,84,43,48,48,48,48,32,40,67,111,111,114,100,105,110,97,116,101,100,32,85,110,105,118,101,114,115,97,108,32,84,105,109,101,41

[bkontur]

The issue is caused by downstream library upgrade in kubo. This PR in boxo (Bitswap implementation for IPFS) is breaking things for us: ipfs/boxo#984.

I will continue investigation and check what can be done.

Meanwhile, downgrading kubo to v0.36.0 depending on boxo < v0.33.1 fixes the issue locally.

@dmitry-markin ok, so do we have also problem with our BitswapServer/BitswapHandle and/or litep2p (litep2p = { version = "0.10.0", features = ["websocket"] }) version and/or our litep2p implementation? Should I create polkadot-sdk issue?

[dmitry-markin]

@dmitry-markin ok, so do we have also problem with our BitswapServer/BitswapHandle and/or litep2p (litep2p = { version = "0.10.0", features = ["websocket"] }) version and/or our litep2p implementation? Should I create polkadot-sdk issue?

The problem is in the litep2p Bitswap implementation. Here is an issue describing it in more detail: paritytech/litep2p#444. I am working on a fix.