Weekly Developer Update: January 22, 2026

[Nic_Dorman]

Over the last week, the network has experienced significant contraction and churn after the secession of emission payments. This was expected, with nodes running large scale farming operations and modified code suddenly being pulled from the network. Due to the sudden drop, the replication processes in nodes are triggering, causing a spike in network traffic. This is large (due to the scale of reduction of active nodes) and is expected to continue for as much as several days while the network stabilises.

Indelible - Large Scale Data Uploads
Work continues on our large data uploading tool, Indelible. More work has been done on the Docker images, with deployment to DockerHub directly through GitHub Actions, keeping things in sync across more platforms. There has also been a focus on stability and security, with changes made to decouple wallet encryption from JWT secrets. Finally import/export functionality has been further enhanced, with new API tests, configurations settings, and enhanced CI.

Code Quality
Further work and testing has been undertaken on Merkle tree payment methods, focused on refactoring existing code, removing hardened errors and upload predictability. The UX has also seen some improvements, with gas costs being displayed during payment selection, and API for directory uploads being exposed for use.
There have also been some minor updates to documentation covering CLI usage, as well as new API endpoints for getting quotes from specific nodes.

Network Stability and Mainnet Improvements
Some changes have been made to different timeouts across the network code, aligning client, node and KAD query timeouts to 120 seconds for the purpose of enhancing reliability when handling Merkle uploads due to their network-intensive nature. This addresses some observed mainnet upload instabilities, where partial successes in storing and retrieving chunks were noted alongside connection-related errors.
Post Emission secession shows that 80% of the nodes on the network are running the latest version of code, the remaining seem to be from very old versions (which pre-date the ability to determine exact version). We will look into strategies for mitigating any issues these present, such as protocol version mismatching, over the next few releases.

[scottefc86]

First £5 please

[aatonnomicc]

Second £10 please

[Southside]

Third.
p10,000 please.
No point asking for £ (or $) they will have little value soon and as for yer EUR…

Thanks for the update. Good to see work continues but really I guess we are in a wait and see phase for a few days. Thanks to all the dev team for your hard work as always.

Meantime, if you can upload anything useful, please do so.

[Traktion]

Thanks team! The sticky plaster has been ripped off and we can start focussing on organic growth.

I hope the money that was going to emissions will start going on merkle uploaded data, letting that add value in more ways than one.

I’ve got a bunch of new stuff for AntTP to release tomorrow too, so watch this space!

[Secretariat415]

Thanks so much to the entire Autonomi team and community for all of your hard work!

[Erik_Hedin]

@Nic_Dorman

Over the last week, the network has experienced significant contraction and churn after the secession of emission payments. This was expected, with nodes running large scale farming operations and modified code suddenly being pulled from the network. Due to the sudden drop, the replication processes in nodes are triggering, causing a spike in network traffic. This is large (due to the scale of reduction of active nodes) and is expected to continue for as much as several days while the network stabilises.

YES! Finally a real contraction test. My server that easily ran 200 nodes before is now at 100% network activity while only running 9 nodes, but only using 8 out of 100 Mbit/s network speed, never seen that one before

Going from 2.000.000 network size to 30.000 has to be some sort of record as well…

Do hope the team can collect as much data as possible on this historic event! And that the coming incentives are rewarding useful work and less of a lottery

[DavidMc0]

Thanks for the update. Cutting emissions is a big milestone, and well worth the short term network disruption. Let’s hope things improve once the network calms down, with a far larger proportion of nodes being up to date.

Still looking forward to seeing indelible when it’s ready, so good to hear work on it is progressing.

I’m also keen to know more about what Bux means by the network going ‘well beyond storage’… it’ll become clearer next month I’m sure

It’s not been an easy first year for the network in the wild, but I’m sure all of your efforts will be built upon to get closer to the goals you’re all aiming for.

Great work team!

[DavidMc0]

@Traktion

I hope the money that was going to emissions will start going on merkle uploaded data, letting that add value in more ways than one.

I’ve got a bunch of new stuff for AntTP to release tomorrow too, so watch this space!

I’d prefer tokens were used to resource you, safemedia, zettawatt, and other devs to make more great stuff for the network, focused on improved user experiences and utility.

Using tokens to upload files nobody wants to pay for and people can’t do much with seems like another poor use of tokens ahead of decent user experiences existing.

We’ll see what the plans are next month. I do hope there can be some conversation about the tokenomics & incentivisation aspects of it.

Looking forward to the AntTP update tomorrow

[storage_guy]

In the incessant striving for balance between the forces of compute, memory, storage and network usage I think there has been a change in the balance: network usage is in the ascendancy again. (As it always should have been? Answers on a postcard…) Because the peaks are higher and that is what people will notice.

I used to run 80 at home but that was a bit thin in terms of storage, fine for compute and network but now is great for storage, totally fine for compute and is a bit shaky for network. Now 20 is a sensible number because of the peaks.

I kept my old nodes running as long as I could last night but my GF (and me, I have to admit) wanted to catch up with ‘The Traitors’ on BBC iPlayer and my RPI4 with 80 nodes was murdering the bandwidth and connections on my network. How ironic.

Now that the Emission farming traitors are gone it looks like we’ll all need to be a bit more circumspect about how many nodes we run.

(Are we allowed to call the massive node runners parasites again? I think we are given what happened as soon as emissions were switched off!)

The peaks in bandwidth usage are higher and that is what will turn people and nodes off. But the absolute peaks might be smoothed by there being more nodes in future in what is essentially a new network with not enough nodes. And the more ‘quality’ nodes are run the lesser the peaks.

I’m hoping that this extreme situation is a temporary thing and we can find some equilibrium but I think that we are in for a rough ride for a few days, maybe weeks. I’m being quite circumspect in terms of the number of nodes I try to run. The peaks in terms of Mb/s in and out are way more than they used to be and I want to run quality nodes with enough compute, memory, storage and network capacity rather than pushing my luck for short term gains. It occurs to me that another mass node exit now that there are fewer nodes will cause a peak not just in network usage but also compute and storage.

The likely data loss is galling but if the learning process of the last year moves us closer to something that is consistent and sustainable in terms of people running some nodes at home I am all for it and all in. I’ll be slightly reducing the number of nodes my friends and family run to keep them ‘high quality’ but encouraging (forcing?, if you want any help with your laptop?) others to join.

[Toivo]

@storage_guy

Are we allowed to call the massive node runners parasites again?

In my mind, not. Opprtunists, yes, but that’s a given even in general population, let alone crypto folks.

Are we allowed to call the folks, who set monetary incentives to reward just “being around” without any way to enforce if those nodes did anything useful, or indeed harmful, fools? I’d say that’s too harsh and unfair, but in my opinion, it was very naive to expect anything else than full scale milking of rewards with any means possible. And at the same time Bitcoin, Ethereum etc. do survive, or even thrive in the very same environment.

[dpbaril]

@Nic_Dorman

secession of emission paymen

Presumaby you mean “cessation” of emission payments? My AI assistant informs me that this kind of payment is used to bootstrap a new network before transitioning to usage payments. As a neophyte in crypto payment systems, I sometimes find the language difficult to understand. I have been following SAFENet from a distance for a few years and am looking forward to the time when, as I naive user, I can use it to store data and perhaps, if feeling adventurous, set up some nodes with the spare space on my devices.

[Toivo]

@DavidMc0

I’m also keen to know more about what Bux means by the network going ‘well beyond storage’…

And in what timescale? I think that the network was always supposed to go beyond storage, eventually. Storage, that works flawlessly, would already be a lot and a good goal to get first. I am afraid that they may plan for realizing much more features all at the same time, and postpone getting anything truly working further to the future.

I’d be happier to hear something along the lines: “These new tools helps us so much, that we can expect the solid, working storage be around very soon.” Rather than: “we have funding for 3 more years.”

[Bux]

@Toivo

we can expect the solid, working storage be around very soon.

Yes, you can expect solid, working storage to be around very soon.

[TheGreatTit]

If there is a decent, dependable, pay once, store for a long time google cloud alternative, I know of many non-crypto, plenty-of-pics-they-never-look-at-but-do-not-wanna-erase-ever people who would snatch and gobble a thing like Autonomi. I do think there is a huge market looming just for the storage layer.

[19eddyjohn75]

Thx 4 the update Maidsafe devs

emission

solid, working storage

Jippy then bte wont be getting these anymore…

Hmmmmm
If we could only get back to 1 attos 1mb upload and signal the entire storage space, all storage belongs in the SAFE universe!

Keep hacking super ants

Hi Eddy you always say: 1 attos 1mb per upload, but did you ever consider what kind of financial impact this has on the human noderunners?
Emission clearly demonstrated that the game was being played wrong, give a lot of ants those ants get sold price crash (not that this matters)
Sure humans provide storage, do a few uploads, but it’s a two way street with traffic stops based on human time (beer, eat, sleepronx).

Noderunning all boils down to ‘data uploads’ and “time” hmmmmm probably also speed (but this falls in a different category of drugs) on a highway, #human limitations

Imagine ai as noderunner 24/7/369, imagine what you will spend vs what you will get (unexplored economics)…

Butt i guess it’s also saying Arschloch, your not controlling this Network as a whole…

[storage_guy]

I am laid up with the dreaded lurgy so off work with no energy for something proper so…

I thought I’d try to download some of the things I’d uploaded months ago. There are a few small files that still work for example:-

time ant file download dc5b307f73cc792fa5d48474c199ad4d8b4e2348611f37985343fe6ec22b2dd2 Elite_logo.jpg

but some small files failed.

And anything of any length didn’t work. None of the music files of between 17 and 31 chunks I’d uploaded worked. They tended to fail with about 1/3 of the chunks ‘not found’ but one of the ones with 17 chunks only had 2 missing.

This is obviously distressing from a continuity point of view but considering the trauma the network went through with maybe more than 3/4 of the nodes disappearing within a few hours and a good number of those within minutes I think that’s pretty good. I can’t think of any storage system that would persist this level of object availability with this kind of abuse anywhere near as well.

This gives me a good feeling for data resilience on an ongoing basis with a more stable network.

I would love to hear the results of any testing by the team either around the time of the travails the network went through or the currently smaller but more predictable state of play at the moment.

In the last few days I’ve seen uploading and downloading that looks like a small amount of churn and also some uploading and bursts of downloading that doesn’t look like churn. I think someone is doing some testing!

I’m off to re-upload the chunks and see how that goes.

[storage_guy]

The re-upload did not go well.

It realised there were some chunks already on the network which is great.

But it keeps failing to upload the remaining ones. It powered through to upload 2 of them but there are 4 that are persistently failing to upload. And worse, it seems to be charging each time! It says it keeps paying for the remaining 4 and that is borne out by the transactions on the address.

So I pulled the plug after an hour and a half.

Is it because the files were there before or is there now a general problem with uploads of files?

Connecting to the Autonomi network...
Connected to the network
🎯 Using single node payment mode (default - saves gas fees)
Encrypting file: "dirty weekend.wav"..
Streaming encryption of dirty weekend.wav ...
Successfully encrypted file: "dirty weekend.wav"
Processing estimated total 6 chunks
Uploading file: dirty weekend.wav
Processing batch of 10 chunks
Processing chunk (1/6) of dirty weekend.wav
Processing chunk (2/6) of dirty weekend.wav
Processing chunk (3/6) of dirty weekend.wav
Processing chunk (4/6) of dirty weekend.wav
Processing chunk (5/6) of dirty weekend.wav
Processing chunk (6/6) of dirty weekend.wav
Processing chunk (7/6) of dirty weekend.wav
Processing chunk (8/6) of dirty weekend.wav
Processing chunk (9/6) of dirty weekend.wav
Processing chunk (10/6) of dirty weekend.wav
Quoting for affdb6(10101111).. ..
Quoting for 25ecca(00100101).. ..
Quoting for 52a894(01010010).. ..
Quoting for 24a0ab(00100100).. ..
Quoting for bbbad9(10111011).. ..
Quoting for 32fefa(00110010).. ..
Quoting for 968869(10010110).. ..
Quoting for 52be74(01010010).. ..
Quoting for e64539(11100110).. ..
Quoting for 4cccd6(01001100).. ..
Paying for 10 addresses..
Payments of 10 address completed. 0 address were free / already paid for
(1/10) Chunk stored at: affdb6946287f4c57eb01af9293fd506b40b4b186195f90a1e2388eb11e882d3
(2/10) Chunk failed to be stored at: 25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73 (A network error occurred for NetworkAddress::ChunkAddress(25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWPKp6BEpwAELE6bgXm421nvMjPumwWbJtEAMks6J52B3J"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWGW7y1nA9TNHCeK1puhb8yxw99a398iaEffvNwKS5W4ZJ"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWAAhd5987MaPPqKus6VzhmbXYKrMfRXq6nZhcK5npvFEL"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 25ecca(c3163ae18f4400a0c131d5f989bf68cd2fb1fe893662101a04b14e4f1493bf9e), payees: [PeerId(\"12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq\")] }"), (PeerId("12D3KooWMkBCeMycq1oAh5DoDMRhWkoFBrExEKHuTi3Uk3oF15u5"), "Put record rejected: Timeout while waiting for a response")])
(3/10) Chunk failed to be stored at: 52a894f965ca4fed1e94a27421bf8b84c00371af4f143ea62d80b8dd35180a08 (A network error occurred for NetworkAddress::ChunkAddress(52a894f965ca4fed1e94a27421bf8b84c00371af4f143ea62d80b8dd35180a08): Put record failed, the following peers stored the record: [PeerId("12D3KooWEX3Rwr1xzt8nb2WNTtjdiWwbPvhyVfb8CCbe9ctbLfVR")], errors: [(PeerId("12D3KooWAHMVP31afGmUkAEAVcKqZfMHsPpxZhpkiTeBCXPsJtFf"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWAcwYAPfgo6b11d8w5uNhTUNvCEXnfpB38jD7sN1zMUp5"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWGo85YUrRCp2MMyw3UutxD2scrSF6NbsGLNyBCy7J4Fqs"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWJ1Xbtqwhm5tNjBVuLbTKxfsyA72uS9xPJvHsoR38jWR1"), "Put record rejected: IO error on outbound stream: connection lost")])
(4/10) Chunk failed to be stored at: 24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59 (A network error occurred for NetworkAddress::ChunkAddress(24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWGAhYXv3rhxyCKcuipjmSLJ32vt2Svw31RFaXdN7DU88y"), "Put record rejected: Failed to dial the requested peer"), (PeerId("12D3KooWQREmSZtuhndckuBbgwgcR2xVDmjAvuLDmKGfSSBqZtxm"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWQrprxxNGqVvXy8A6bwRKitka2C14giWwqc8Kc5Exv2Q4"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 24a0ab(7f319fce3ec392e6d16fed42d737a98b0a6ecf32d061d98906c86cafbd2605f5), payees: [PeerId(\"12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND\")] }"), (PeerId("12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND"), "Incompatible network protocol, either the client or the nodes are outdated"), (PeerId("12D3KooWGFLnh6znJeb37JKmHcgFWH8QwcQAgZDvzMrkxjRbt4Fh"), "Put record rejected: Timeout while waiting for a response")])
(5/10) Chunk failed to be stored at: bbbad942b5ee0068de226d18466dc4a33e52fc97034b5cad94b4cd6e606c26b9 (A network error occurred for NetworkAddress::ChunkAddress(bbbad942b5ee0068de226d18466dc4a33e52fc97034b5cad94b4cd6e606c26b9): Put record failed, the following peers stored the record: [PeerId("12D3KooWRbmrTSDX1y7htH7P2imqtL7aWdmcYXmQcUNcj7weceut")], errors: [(PeerId("12D3KooWFLDKUjj2ycghaNUwSsUxKZDsNFgJes4NDAumLi514Wbj"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: bbbad9(2afcc1044821792c9153c9f97ffb573c1f820fcc364e7294f9cf9e7e910abd7c), payees: [PeerId(\"12D3KooWRbmrTSDX1y7htH7P2imqtL7aWdmcYXmQcUNcj7weceut\")] }"), (PeerId("12D3KooWBvMjUvQtnoF2H93NUaSHYmvmkuxXZ4EtSRHudxAdKc8k"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWKhU9z1ewsmqCMfhoPjLVHRZAtVi4JCwXKjbFiA7zPV5p"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: bbbad9(2afcc1044821792c9153c9f97ffb573c1f820fcc364e7294f9cf9e7e910abd7c), payees: [PeerId(\"12D3KooWRbmrTSDX1y7htH7P2imqtL7aWdmcYXmQcUNcj7weceut\")] }"), (PeerId("12D3KooWRYqwYdcXKAdcdwwGpG3KjQeJY4UUdyibk2PRMordeqMb"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: bbbad9(2afcc1044821792c9153c9f97ffb573c1f820fcc364e7294f9cf9e7e910abd7c), payees: [PeerId(\"12D3KooWRbmrTSDX1y7htH7P2imqtL7aWdmcYXmQcUNcj7weceut\")] }")])
(6/10) Chunk failed to be stored at: 32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe (A network error occurred for NetworkAddress::ChunkAddress(32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWG1Li4rNvraFS6rQnMsCSuwWSNhkk16dLxQnjJPYZb17g"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWRc6DJTbmFcyPW4YytZBKptTrXE139CKLCx6zpeu9sKcr"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWG7EXeG8NLsU7sFqsCnRLvi2nUPDHAcBXXnAKfPRewkXA"), "Incompatible network protocol, either the client or the nodes are outdated"), (PeerId("12D3KooWSdNcc54TxNkNSNrmcAJUAp2ru5mMkeqSYSYh4bWtfvET"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWJ6RZcN4Butx42UsWYFHyT1Dq4u2BzGdHVBbGDAHiMmM4"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(7/10) Chunk failed to be stored at: 968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d (A network error occurred for NetworkAddress::ChunkAddress(968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWFYuDGj1ja9UaCMyLyRPVFb3EBEqag6Crky9KrTPVA412"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWMpynXGbHXZnkdGbK2GmB4gP19UAXGkDNjUt3RCmbDM3j"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWBCLY26md1GxGazzaA9Hbcf3RS7CNQEAvBBQWZ6wxmZSE"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWASoRxJb7tYp9837zGGDdUAmngBsCStQcHgC1ACx8g8SC"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWRbWX6uCkxaKzWX7Ep6iyNLFJVcqAWj1bKvYkB1667axi"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(8/10) Chunk stored at: 52be74e7f736bed91cf1371045127718dfb04e58dbc4cd183f5c75217881bbd7
(9/10) Chunk stored at: e6453960a05c0cf2ca4f66b752ab088856a3c3f42e81b4b9e3012d2a95d95b55
(10/10) Chunk stored at: 4cccd6bba93a002afa3145821c72e72de993d811c1054146578bf319f103fb3e
⚠️  ❌ Upload batch failed: 6 chunks failed. Retrying scheduled
⚠️ Encountered upload failure, take 1 minute pause before continue...
🔄 continue with upload...
Processing batch of 6 chunks
Processing chunk (2/6) of dirty weekend.wav
Processing chunk (3/6) of dirty weekend.wav
Processing chunk (4/6) of dirty weekend.wav
Processing chunk (5/6) of dirty weekend.wav
Processing chunk (6/6) of dirty weekend.wav
Processing chunk (7/6) of dirty weekend.wav
Quoting for 25ecca(00100101).. ..
Quoting for 52a894(01010010).. ..
Quoting for 24a0ab(00100100).. ..
Quoting for bbbad9(10111011).. ..
Quoting for 32fefa(00110010).. ..
Quoting for 968869(10010110).. ..
Paying for 6 addresses..
Payments of 6 address completed. 0 address were free / already paid for
(1/6) Chunk failed to be stored at: 25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73 (A network error occurred for NetworkAddress::ChunkAddress(25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWMkBCeMycq1oAh5DoDMRhWkoFBrExEKHuTi3Uk3oF15u5"), "Put record rejected: Failed to dial the requested peer"), (PeerId("12D3KooWAAhd5987MaPPqKus6VzhmbXYKrMfRXq6nZhcK5npvFEL"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 25ecca(c3163ae18f4400a0c131d5f989bf68cd2fb1fe893662101a04b14e4f1493bf9e), payees: [PeerId(\"12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq\")] }"), (PeerId("12D3KooWGW7y1nA9TNHCeK1puhb8yxw99a398iaEffvNwKS5W4ZJ"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWPKp6BEpwAELE6bgXm421nvMjPumwWbJtEAMks6J52B3J"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(2/6) Chunk failed to be stored at: 52a894f965ca4fed1e94a27421bf8b84c00371af4f143ea62d80b8dd35180a08 (A network error occurred for NetworkAddress::ChunkAddress(52a894f965ca4fed1e94a27421bf8b84c00371af4f143ea62d80b8dd35180a08): Put record failed, the following peers stored the record: [PeerId("12D3KooWAcwYAPfgo6b11d8w5uNhTUNvCEXnfpB38jD7sN1zMUp5")], errors: [(PeerId("12D3KooWAHMVP31afGmUkAEAVcKqZfMHsPpxZhpkiTeBCXPsJtFf"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWG9zydCYeCsjw4DXh8oWp2NXjAeJQQLRN3XsaKbYkDSaH"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWJ1Xbtqwhm5tNjBVuLbTKxfsyA72uS9xPJvHsoR38jWR1"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWGo85YUrRCp2MMyw3UutxD2scrSF6NbsGLNyBCy7J4Fqs"), "Put record rejected: IO error on outbound stream: connection lost")])
(3/6) Chunk failed to be stored at: 24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59 (A network error occurred for NetworkAddress::ChunkAddress(24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWJVE4tftrPpqNsTi4ChYBgCWG69BTXwzXugmM2P9GA3oX"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWQrprxxNGqVvXy8A6bwRKitka2C14giWwqc8Kc5Exv2Q4"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 24a0ab(7f319fce3ec392e6d16fed42d737a98b0a6ecf32d061d98906c86cafbd2605f5), payees: [PeerId(\"12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND\")] }"), (PeerId("12D3KooWQREmSZtuhndckuBbgwgcR2xVDmjAvuLDmKGfSSBqZtxm"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWQMgq7VWEeicR22Dh4hm2a2wLioVCg4gaTpkAdAkvZ9pz"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(4/6) Chunk stored at: bbbad942b5ee0068de226d18466dc4a33e52fc97034b5cad94b4cd6e606c26b9

(5/6) Chunk failed to be stored at: 32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe (A network error occurred for NetworkAddress::ChunkAddress(32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWG1Li4rNvraFS6rQnMsCSuwWSNhkk16dLxQnjJPYZb17g"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWJ6RZcN4Butx42UsWYFHyT1Dq4u2BzGdHVBbGDAHiMmM4"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWSdNcc54TxNkNSNrmcAJUAp2ru5mMkeqSYSYh4bWtfvET"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWG7EXeG8NLsU7sFqsCnRLvi2nUPDHAcBXXnAKfPRewkXA"), "Incompatible network protocol, either the client or the nodes are outdated"), (PeerId("12D3KooWRc6DJTbmFcyPW4YytZBKptTrXE139CKLCx6zpeu9sKcr"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(6/6) Chunk failed to be stored at: 968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d (A network error occurred for NetworkAddress::ChunkAddress(968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWRbWX6uCkxaKzWX7Ep6iyNLFJVcqAWj1bKvYkB1667axi"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWMpynXGbHXZnkdGbK2GmB4gP19UAXGkDNjUt3RCmbDM3j"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWBCLY26md1GxGazzaA9Hbcf3RS7CNQEAvBBQWZ6wxmZSE"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWLqq3x97YKUUzXPxf3mtWQg45kZKXdRPfijWrswRQXDnt"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWFYuDGj1ja9UaCMyLyRPVFb3EBEqag6Crky9KrTPVA412"), "Put record rejected: Timeout while waiting for a response")])
⚠️  ❌ Upload batch failed: 5 chunks failed. Retrying scheduled
⚠️ Encountered upload failure, take 1 minute pause before continue...
🔄 continue with upload...
Processing batch of 5 chunks
Processing chunk (2/6) of dirty weekend.wav
Processing chunk (3/6) of dirty weekend.wav
Processing chunk (4/6) of dirty weekend.wav
Processing chunk (6/6) of dirty weekend.wav
Processing chunk (7/6) of dirty weekend.wav
Quoting for 25ecca(00100101).. ..
Quoting for 52a894(01010010).. ..
Quoting for 24a0ab(00100100).. ..
Quoting for 32fefa(00110010).. ..
Quoting for 968869(10010110).. ..
Paying for 4 addresses..
Payments of 4 address completed. 1 address were free / already paid for
1 chunks were free in this batch 5
(2/5) Chunk stored at: 52a894f965ca4fed1e94a27421bf8b84c00371af4f143ea62d80b8dd35180a08 (skipping, already exists)
(1/5) Chunk failed to be stored at: 25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73 (A network error occurred for NetworkAddress::ChunkAddress(25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWCoXHnqS8Ne2hMFsT1k1tY4sHx8AEPmnkYtSvgcqoPHZk"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWAAhd5987MaPPqKus6VzhmbXYKrMfRXq6nZhcK5npvFEL"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 25ecca(c3163ae18f4400a0c131d5f989bf68cd2fb1fe893662101a04b14e4f1493bf9e), payees: [PeerId(\"12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq\")] }"), (PeerId("12D3KooWCUGFAgKhfN1qxN6u1MZ18nhFNQ9cSgXZ9ntKw3Js8AfF"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWPKp6BEpwAELE6bgXm421nvMjPumwWbJtEAMks6J52B3J"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(3/5) Chunk failed to be stored at: 24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59 (A network error occurred for NetworkAddress::ChunkAddress(24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWJVE4tftrPpqNsTi4ChYBgCWG69BTXwzXugmM2P9GA3oX"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWQrprxxNGqVvXy8A6bwRKitka2C14giWwqc8Kc5Exv2Q4"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 24a0ab(7f319fce3ec392e6d16fed42d737a98b0a6ecf32d061d98906c86cafbd2605f5), payees: [PeerId(\"12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND\")] }"), (PeerId("12D3KooWQREmSZtuhndckuBbgwgcR2xVDmjAvuLDmKGfSSBqZtxm"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWGFLnh6znJeb37JKmHcgFWH8QwcQAgZDvzMrkxjRbt4Fh"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(4/5) Chunk failed to be stored at: 32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe (A network error occurred for NetworkAddress::ChunkAddress(32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWG1Li4rNvraFS6rQnMsCSuwWSNhkk16dLxQnjJPYZb17g"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWG7EXeG8NLsU7sFqsCnRLvi2nUPDHAcBXXnAKfPRewkXA"), "Incompatible network protocol, either the client or the nodes are outdated"), (PeerId("12D3KooWNd4E2Lt3LBpDidQeg43RW1RBDqrJ2so2vqcChmiZHxxo"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWJ6RZcN4Butx42UsWYFHyT1Dq4u2BzGdHVBbGDAHiMmM4"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWSdNcc54TxNkNSNrmcAJUAp2ru5mMkeqSYSYh4bWtfvET"), "Put record rejected: Timeout while waiting for a response")])
(5/5) Chunk failed to be stored at: 968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d (A network error occurred for NetworkAddress::ChunkAddress(968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWASoRxJb7tYp9837zGGDdUAmngBsCStQcHgC1ACx8g8SC"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWFYuDGj1ja9UaCMyLyRPVFb3EBEqag6Crky9KrTPVA412"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWMpynXGbHXZnkdGbK2GmB4gP19UAXGkDNjUt3RCmbDM3j"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWBCLY26md1GxGazzaA9Hbcf3RS7CNQEAvBBQWZ6wxmZSE"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWLqq3x97YKUUzXPxf3mtWQg45kZKXdRPfijWrswRQXDnt"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
⚠️  ❌ Upload batch failed: 4 chunks failed. Retrying scheduled
⚠️ Encountered upload failure, take 1 minute pause before continue...
🔄 continue with upload...
Processing batch of 4 chunks
Processing chunk (2/6) of dirty weekend.wav
Processing chunk (4/6) of dirty weekend.wav
Processing chunk (6/6) of dirty weekend.wav
Processing chunk (7/6) of dirty weekend.wav
Quoting for 25ecca(00100101).. ..
Quoting for 24a0ab(00100100).. ..
Quoting for 32fefa(00110010).. ..
Quoting for 968869(10010110).. ..
Paying for 4 addresses..
Payments of 4 address completed. 0 address were free / already paid for
(1/4) Chunk failed to be stored at: 25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73 (A network error occurred for NetworkAddress::ChunkAddress(25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWPKp6BEpwAELE6bgXm421nvMjPumwWbJtEAMks6J52B3J"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWAAhd5987MaPPqKus6VzhmbXYKrMfRXq6nZhcK5npvFEL"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 25ecca(c3163ae18f4400a0c131d5f989bf68cd2fb1fe893662101a04b14e4f1493bf9e), payees: [PeerId(\"12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq\")] }"), (PeerId("12D3KooWCUGFAgKhfN1qxN6u1MZ18nhFNQ9cSgXZ9ntKw3Js8AfF"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWMkBCeMycq1oAh5DoDMRhWkoFBrExEKHuTi3Uk3oF15u5"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(2/4) Chunk failed to be stored at: 24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59 (A network error occurred for NetworkAddress::ChunkAddress(24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWGAhYXv3rhxyCKcuipjmSLJ32vt2Svw31RFaXdN7DU88y"), "Put record rejected: Failed to dial the requested peer"), (PeerId("12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWQrprxxNGqVvXy8A6bwRKitka2C14giWwqc8Kc5Exv2Q4"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 24a0ab(7f319fce3ec392e6d16fed42d737a98b0a6ecf32d061d98906c86cafbd2605f5), payees: [PeerId(\"12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND\")] }"), (PeerId("12D3KooWQREmSZtuhndckuBbgwgcR2xVDmjAvuLDmKGfSSBqZtxm"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWQMgq7VWEeicR22Dh4hm2a2wLioVCg4gaTpkAdAkvZ9pz"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
(3/4) Chunk failed to be stored at: 32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe (A network error occurred for NetworkAddress::ChunkAddress(32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWNd4E2Lt3LBpDidQeg43RW1RBDqrJ2so2vqcChmiZHxxo"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWJ6RZcN4Butx42UsWYFHyT1Dq4u2BzGdHVBbGDAHiMmM4"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWG7EXeG8NLsU7sFqsCnRLvi2nUPDHAcBXXnAKfPRewkXA"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWG1Li4rNvraFS6rQnMsCSuwWSNhkk16dLxQnjJPYZb17g"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWSdNcc54TxNkNSNrmcAJUAp2ru5mMkeqSYSYh4bWtfvET"), "Put record rejected: IO error on outbound stream: connection lost")])
(4/4) Chunk failed to be stored at: 968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d (A network error occurred for NetworkAddress::ChunkAddress(968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWFYuDGj1ja9UaCMyLyRPVFb3EBEqag6Crky9KrTPVA412"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWBCLY26md1GxGazzaA9Hbcf3RS7CNQEAvBBQWZ6wxmZSE"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWMpynXGbHXZnkdGbK2GmB4gP19UAXGkDNjUt3RCmbDM3j"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWASoRxJb7tYp9837zGGDdUAmngBsCStQcHgC1ACx8g8SC"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWRg4DkHUZn6j4KaHPFQ27aZYVN4TkuF9Z1qgmeThUyj6t"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0")])
⚠️  ❌ Upload batch failed: 4 chunks failed. Retrying scheduled
⚠️ Encountered upload failure, take 1 minute pause before continue...
🔄 continue with upload...
Processing batch of 4 chunks
Processing chunk (2/6) of dirty weekend.wav
Processing chunk (4/6) of dirty weekend.wav
Processing chunk (6/6) of dirty weekend.wav
Processing chunk (7/6) of dirty weekend.wav
Quoting for 25ecca(00100101).. ..
Quoting for 24a0ab(00100100).. ..
Quoting for 32fefa(00110010).. ..
Quoting for 968869(10010110).. ..
Paying for 4 addresses..
Payments of 4 address completed. 0 address were free / already paid for
(1/4) Chunk failed to be stored at: 25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73 (A network error occurred for NetworkAddress::ChunkAddress(25eccaf6d210545989b8ae1d7be7afbd3a98dec41896e7de5f6dad06a482aa73): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWAAhd5987MaPPqKus6VzhmbXYKrMfRXq6nZhcK5npvFEL"), "Put record rejected: Error handling record put: PaymentQuoteOutOfRange { record_key: 25ecca(c3163ae18f4400a0c131d5f989bf68cd2fb1fe893662101a04b14e4f1493bf9e), payees: [PeerId(\"12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq\")] }"), (PeerId("12D3KooWCUGFAgKhfN1qxN6u1MZ18nhFNQ9cSgXZ9ntKw3Js8AfF"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWSMFWM227jZVBbPzw5XHren4F5ajVUwP8LV1fkoh3Jyaq"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWMkBCeMycq1oAh5DoDMRhWkoFBrExEKHuTi3Uk3oF15u5"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWGW7y1nA9TNHCeK1puhb8yxw99a398iaEffvNwKS5W4ZJ"), "Put record rejected: Timeout while waiting for a response")])
(2/4) Chunk failed to be stored at: 24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59 (A network error occurred for NetworkAddress::ChunkAddress(24a0ab112cc9e967aa0d06fb3d11f588bc29fe955100b97ed32d3e7c18e59c59): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWJVE4tftrPpqNsTi4ChYBgCWG69BTXwzXugmM2P9GA3oX"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWQrprxxNGqVvXy8A6bwRKitka2C14giWwqc8Kc5Exv2Q4"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWCguiatMc2Yc46F1vb68u9r6dDcRh8FGGsbPVNq7RryND"), "Put record rejected: Timeout while waiting for a response"), (PeerId("12D3KooWQMgq7VWEeicR22Dh4hm2a2wLioVCg4gaTpkAdAkvZ9pz"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWQREmSZtuhndckuBbgwgcR2xVDmjAvuLDmKGfSSBqZtxm"), "Put record rejected: Timeout while waiting for a response")])
(3/4) Chunk failed to be stored at: 32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe (A network error occurred for NetworkAddress::ChunkAddress(32fefac8aa976ea6d385a180ca27db55a36751b3b0d1af2fefe4fa8da46ad1fe): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWG7EXeG8NLsU7sFqsCnRLvi2nUPDHAcBXXnAKfPRewkXA"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWSdNcc54TxNkNSNrmcAJUAp2ru5mMkeqSYSYh4bWtfvET"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWNd4E2Lt3LBpDidQeg43RW1RBDqrJ2so2vqcChmiZHxxo"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWG1Li4rNvraFS6rQnMsCSuwWSNhkk16dLxQnjJPYZb17g"), "Put record rejected: IO error on outbound stream: 6c817495/1: connection is closed"), (PeerId("12D3KooWJ6RZcN4Butx42UsWYFHyT1Dq4u2BzGdHVBbGDAHiMmM4"), "Put record rejected: Timeout while waiting for a response")])
(4/4) Chunk failed to be stored at: 968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d (A network error occurred for NetworkAddress::ChunkAddress(968869945a030c2be5c5ccba00353b1788d48bb9b72768dafbecbe89f916a81d): Put record failed, the following peers stored the record: [], errors: [(PeerId("12D3KooWRg4DkHUZn6j4KaHPFQ27aZYVN4TkuF9Z1qgmeThUyj6t"), "Put record rejected: IO error on outbound stream: connection lost"), (PeerId("12D3KooWMpynXGbHXZnkdGbK2GmB4gP19UAXGkDNjUt3RCmbDM3j"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWASoRxJb7tYp9837zGGDdUAmngBsCStQcHgC1ACx8g8SC"), "Put record rejected: Connection was closed before a response was received"), (PeerId("12D3KooWFYuDGj1ja9UaCMyLyRPVFb3EBEqag6Crky9KrTPVA412"), "Put record rejected: IO error on outbound stream: sending stopped by peer: error 0"), (PeerId("12D3KooWBCLY26md1GxGazzaA9Hbcf3RS7CNQEAvBBQWZ6wxmZSE"), "Put record rejected: Connection was closed before a response was received")])
⚠️  ❌ Upload batch failed: 4 chunks failed. Retrying scheduled
⚠️ Encountered upload failure, take 1 minute pause before continue...
🔄 continue with upload...
Processing batch of 4 chunks
Processing chunk (2/6) of dirty weekend.wav
Processing chunk (4/6) of dirty weekend.wav
Processing chunk (6/6) of dirty weekend.wav
Processing chunk (7/6) of dirty weekend.wav
Quoting for 25ecca(00100101).. ..
Quoting for 24a0ab(00100100).. ..
Quoting for 32fefa(00110010).. ..
Quoting for 968869(10010110).. ..
Paying for 4 addresses..
Payments of 4 address completed. 0 address were free / already paid for
^C
ant file upload 'dirty weekend.wav'  236.80s user 274.13s system 8% cpu 1:43:39.75 total

[Mightyfool]

Uploads are failing across the board, the main issue is that a large number of nodes are on old versions that are not (yet) being excluded on the network. This is causing all sorts of issues (especially with merkle).

Rumors are there might be a new release this week and I expect that to return the network to a very healthy and amazing state.