Swarm Community Call — September 2025

All right. Hello. Hello. I see people are entering the call. Um and so let's kick it off.

Welcome to Swarm Community Call. For those of you who are tuning in on X, please know that this call is being broadcast from Swarm's Discord server, which means that if you would like to post a question or join the conversation later on, you'll need to switch to Discord as uh X is audio only for you. With that said, you know, feel free to leave a comment as a reply and it will be reviewed after the call finishes. But for those of you joining on discord um there's an in call chat window in the top right corner as well as the stage chat where you can post questions at any time and they will be brought on stage live as we go. Uh in today's so September's call the agenda is as follows.

First as per usual we'll start with core development updates with Nikki and Callum and I'll have to search for them here in the audience. Uh next we'll move to community talk section where first Nidish will present the file manager and then Joah will join us to make a brief introduction to meta provide and explain why we need IPSH the interplanetary swarm hive. So let's kick things off um by me first inviting Nikki to stage. Hello Nikki.

Hello. Hello. Can you hear me?

Oh, yeah. I can hear you. Nice.

Nice. Nice. So, hey, Mina. Hello, everyone. Welcome to the September community uh call.

Great to have you all here once again. This month, we've got a lot of exciting progress to share, especially as we gear up for the upcoming uh 2.7 uh B release. So, let's get into it. So we are now in the final stretch for preparing our next release and the list uh seems to be uh the list of the items uh to be part of it is finalized.

We have already mentioned some of uh the important changes and more are in the pipeline. Each of them helping to make the faster more robust and easier to run. So here is a quick overview of what's already in and what's coming next. So what's already there? um as erasure coding improvements are now included which strengthen the way swarm handles uh data redundancy and recovery.

This makes the network more resilient and helps on data reassembling. We've also improved fields by introducing uh better support for legacy uh payload formats which helps with better uh compatibility with different uh field uh payload formats while making legacy resolution uh behavior more explicit than implicit. Uh what's in progress? We are introducing uh support for multiple underlay addresses which improves how nodes announce themselves uh to the network and uh to their peers and connect to the network. This is particularly important for nodes that uh may be reachable via u different network interfaces and it plays a critical role and supports the big bounty that's worked on uh by pavl um in the context of this um and alongside autols is being finalized this feature will enable nodes especially browser based ones to automatically establish secure encrypted connections And it's a key step towards um seamless secure bin nodes running uh directly in the browser.

Also uh a pin for a fix for um a pin eviction bug uh is also in the works. This improves how B manages uh pinned content ensuring that important data remains properly protected from garbage collection. Um we're actively of course working on uh improvements to uh pool syncing according to the poolsync sweep. Um a core part of how uh nodes keep data in sync. The next version is a refined approach currently under review that should improve consistency and performance.

And finally uh we're adding uh a new uh a new feature uh the so replica that enhances the way replicated chunks are handled in the network helping ensure uh better reliability and that availability. Um so that's the part for the 2.7 release which is the strong one not just uh bug fixing and improvement performance but also laying the uh the ground for exciting new capabilities uh including being a browser and while the B team is preparing for this um on the research side uh there are also ongoing uh deep dives into how to handle multiple um personas in on uh the identity management. These discussions are still evolving and quite preliminary but we are already unlocking new ways of thinking about it and access in a fully uh decentralized environment. And also last uh we are also running test to understand how checkbook funding checkbook funding impacts uh upload and download speeds.

um early results are in and now we are uh diving uh deeper into what means for performance optimization and potential uh future improvements. Uh this was a long one uh but the that's it from my side and the engineering teams this month. Thank you as always for being part of this where whether you are testing our releases, running nodes or just following the project. your involvement of course help us uh move forward with confidence and clarity. Stay stay tuned um and on my side see you next month with more updates.

Dr. Humina.

Thanks Nikki. Please stick around for any potential questions that would emerge in stage chat or this in in call chat window. But I would like to ask Callum to come to stage to just provide more a bit more clarification on a couple of things that you've mentioned. Not so much on the entity management which is really exciting but uh since it's in the uh early stages uh let's focus on the other item that you've mentioned which is helping you progress on the bandwidth incentives. Uh let's let's hear Callum's lovely voice describe what are we talking about when we're talking about that.

Well, sorry to let you down. I'm going to have to speak now and ruin that. But hopefully you can hear me.

Yeah, we can. We can.

Okay. Well, yeah, as you said, the identity management and kind of a lot of the recent stuff. This is the the new era of things which Nikki's um channeling at the minute. And for me, I spend most of my time dealing with the classics. So, with that, that's the incentive systems, that's the bandwidth incentives as well.

That's been here for quite a long time. Probably some of the oldest parts of the codebase as it stands. And equally over the last couple of weeks, you know, I've been and months, sorry, I've been mainly focused on performance of everything. And obviously that's coming usually from the research team and then spreading out with Nikki to the B team as well. And part of that is what's going on with the bandwidth incentives as well, which is why it's become a bit of a focus for us in the research team.

So obviously if you're running a node you can upload, download, request different files and as per the the network it obviously forwards that message on to other nodes and you basically get a timebased allowance for that. You get a free amount that you can basically request from other nodes for and once that's done you basically have a debt to prepaid to other nodes by providing the same service back. That's pretty much how the network exists as a whole. Obviously, we have the checkbook in the background of that as well, which you can of course basically pay your way. So, after you've used your time based settlement or your time based allowance um and you basically still need to perform, you want to perform faster immediately, you can use the the checkbook as well.

Now, interestingly enough, that when it's turned on or off seems to have implications to performance as well. So that's what gets my interest where I want to basically focus on we can do in the research team to pinpoint those numbers much like the benchmark tests for using different network scenarios different levels of eraser codes different file sizes etc etc so this is more optimizations in the name of performance and that's going back to first principles and looking at the incentive systems from the ground up. So we are Did we lose? Did we lose Callum or is it just me?

Holy. It was getting really interesting. Wait, wait, wait. He's He's lost. Lost.

Yes, he's lost.

Uhhuh.

Sorry.

Oh. Oh, you're back, Colum. We lost you. The most interesting part is the

That would be that would be classic. Okay. Well, I'll recap the last the last minute. So, so to sum up anyway so I don't ramble, what we have is a large part of the incentive systems that needs to be investigated and looked at again in my mind all in the name of performance. We've done that with the eraser codes.

We've done it with different file sizes with the benchmarking tests and the B team have done a really good job and the infert team have done a really good job of showing us what that looks like. When it comes to the bandwidth incentives, this is an old part of the codebase that when you have the checkbook either turned on or off to be to pay your way basically for the resources of the network that that can impact speeds and performance most likely due to more steps required, more signatures required that basically there there is a higher overhead to do that. So that could be part of the the issue there. And we don't know anything definitive yet. So I don't have any interesting metrics to report as of yet that are definitive that inspire us to have a road map for things to change but we are investigating everything from the top down and the incentives on the name of performance and we should have very soon some interesting metrics to describe and kind of put out here to the community as well so that we can advise the most optimum way to use the network and then in the short term and then of course in the long term make our incentive systems as robust and as performant as possible in a competitive landscape across all different protocols.

Um, equally in the same vein, we're looking towards the staking protocol that we talked about just a couple of weeks ago as well that we may try to look into changes there that have come from external contributors also. So, it's nice that none of our incentive systems while it's a core part of the network, everything is subject to change if it improves the performance, security or reliability of the network. So that's everything that we're investigating for the bandwidth and some staking changes as well. Um if and when we have definitive tasks and outcomes that mean that we're going to change something then the community will be the first to know and equally if you have any anecdotal evidence as well from using the network we would please love to hear that and love your test as well as ours inside the discord. So always doors always open to hear metrics and what your experience is like and hopefully that answers your questions and I'm here to add any details that you might need.

Hopefully that was concise in my network as I kept up Mina back to you.

Yeah perfect we perfectly audible now. Thanks. Yeah. So that's the same as I wanted to uh make sure you all here. So if anybody would like to uh chat or like discuss these topics further uh discord is always here and there is this research channel where you can pop in to follow up on what colum is has now been saying but let's now move on to the community talk section where I would first like to invite to stage Nidish.

Can you please raise your hand so I get you on stage? And here is Nidish. He will present us something very exciting. It's a major UX improvement. So I assume people here are familiar with how you have to navigate hashes with handling in handling files.

Um now that all is also Oh sorry now I'm losing connection or not. Oh okay. Now can you hear me? I hope you can hear me. Um so what I wanted to say that with file manager this is becoming more intuitive basically as using any operating systems file explorer you drag you drop you search you view but let's uh allow Nadish to walk us through Nadesh.

Yes uh hello everyone and uh thank you Mina. Uh so I'll just quickly share my screen. Let me know once you can see it. I think it's up.

Yes, it's up.

So thank you uh thank you for that quick introduction, Mina. And u thank you everyone for uh joining in today. And before we dive into the new stuff, let's take a quick moment to look at how things work right now for file uploads. So we have the rough way of uh add file then we add an existing or

just a second just a second uh I don't think that we can still see your screen shared can you because it was there but now it disappeared or at least for me

let me reshare

and this is something that we would want to see I can tell you that I already

Oh yeah that's that's that's great

is that visible now Yeah.

Yep. Um I hope it's still on.

Is it?

Yes. Okay. Awesome. Uh sorry about that guys. So, uh like I was just saying um before we, you know, take a look at the new file manager, we'll take a moment to, you know, see how things are right now when we want to upload a file.

So you know we have the old way of uh you know adding a file adding your existing or old postage stamp or buying a new one and uh you know uploading it to your node. But let's fast forward to today which brings us to the file manager. So think of this as your uh regular OS file explorer but on swarm. So you have the same comfort that you always add but it's decentralized. So this is the first screen you see.

It's as simple as setting up a new admin account on your OS but on swarm. So just select the lifetime and the security level which is you know how many copies you want across the network from off to paranoid and this is technically a postage stamp. So this gets applied you know under the hood. This is uh responsible for making your life much easier in managing the file so that you know you don't have to shuffle your file hashes ever again. So when we hit purchase, we get the admin stamp.

It doesn't store the files directly, but it's sort of your identity. It manages all your file information and permissions. So now let's create some drives where we can actually store the files, right? So just like your old C and D drives, I'll make a drive for work. So um you know with a capacity and uh a desired lifetime and then the security level and then similarly I can you know create a space for personal stuff with you know a similar uh setup with an initial capacity uh lifetime and the security level.

So security level just means you know the number of copies uh and uh now let's maybe throw in some files. So, no more, you know, selecting on a picker or attaching stamps. You can, you can if you want, but it's as simple as dragging files from, you know, your desktop folders. And I have this funny cat image here that'll upload to the drive. And, uh, it's tracked with progress bars.

And each file lands with its timestamp and expiry tag to the drive that we created. So, we can upload one or multiple files. Let me just pick the remaining and drag them to. And while that happens, I'll also add in some files to the other work drive and I'll upload some of the videos that we have here. And that's it.

I mean, it's that simple. And uh we can also check the right click where on a on a file item. So we can see a few options which is basically we can you know open it. Let's quickly take a look. We can download it locally um and obviously go through the process.

We can also rename it directly on swarm. So not so funny cat now that we've looked at a couple times. And we can also track the version history of all the changes that we've made. So the renames and even a version control, but we'll just circle back to that in a moment. And we also have delete.

Of course, once you upload to swam network, you cannot delete a file. But if you just want it to disappear from your view, we can do that in three ways. Um the trash, the forget or destroying the entire drive. So basically trashing works like a delete action where you still have it in your bin or your trash but it's not in your, you know, drive view anymore. Forget is like deleting the file permanently.

But again, it's just that it disappears from your view. You cannot delete your file and it's still there. Or you can destroy the entire drive and take all the other files along with it. So let's not do that for now. We can also check the file versions, the number of versions we have and other swarm related metadata.

And we also have a spotlight search. But um you know you can type in any um keyword like cat or pet and search across your drives or in the active or trash section that we just saw through the filters and nothing slips through. So let's take a very quick example of how version control works. So we have this Hulk image in our personal drive. Let's quickly take a look and uh let's rename it to Trey um you know strongest Avenger and maybe a couple minutes later we decide no I mean uh Thor is maybe the strongest Avenger.

So we have this other image in our system um that we can just quickly view and drag it again to the file manager to upload. And this time the file manager will ask us if we want to upload it as a new file or

pause. Pause again.

Some discord action. Yeah, we lost the screen. Can you just Sorry, we we lost it. I I guess the

so insulted that you or the other guy so insulted that you named Hulk the strongest Avenger that the whole screen disappeared. Can you just please uh rewind and and go from from Hulk's picture? Let me just rewind.

Yeah, Hug got very angry. No, the other guy once you can see the screen again if

Oh, yeah.

Are we able to see?

Right here. Yes, exactly.

Awesome. Yeah. So, just circling back to where we left off. So, um another image um of Thor as the strongest Avenger. And let's just, you know, drag and drop it to the file manager.

This time we can save it as a new basically a fresh upload or you know we can make it a new version of the old file itself. So if we go with that this allows us to travel back to any version whenever we want and even restore any of the earlier versions. So before that let's take a quick look at our uploaded strongest avenger image. So we can see that it's updated and we can also restore it to the first version in like just two simple clicks and that's it. So we can check the version history and that's about a wrap of you know everything with the file manager.

So you know in one quick run I know we've covered a lot. We've onboarded, we've created an admin stamp, set up drives, uploaded files and managed them uh deleted restore files and even handled version conflicts. So uh it's intuitive. It feels like a regular file explorer but every action is stamped and you know powered on swamp. So with that I will end the demo and once again thank you everyone and I'll pass it back to Mina.

Thanks Nidish. There are a couple of questions that pop out first. Okay mine is so van swarm desktop integration. Hello Nidish.

Hello. Yes.

Yeah. Yeah. Do do we hear you? Okay. So is the when when is the integration to swarm desktop happening?

If you can give us like an approximate.

Right. So we are uh in the process of the final um you know reviews and we should be able to see it in the coming week or so and um yeah I mean all most of the thing is done and um we we should have a uh ready piece to release soon.

Awesome. And then MCB is asking two things. First is what does this security level do? And this has already been replied in the chat but for those who are just listening um applying eraser encoding right?

Yes. Yes. Exactly.

Okay. And the other question is uh about the new version of old file does it overwrite the old chunks in the network?

No. So we upload a very fresh file that is uh you know at a you know incremented feed index. So it doesn't do anything to the old file or the old file references or anything. It's still there. So that's how we can still retrieve it or restore it and download it.

But yeah in essence we are still creating a new file or new reference. So feeds are not involved because this is what a question from Henry uh if the version control working under the hood is involving the feeds or I guess that would be a no.

No. So for the version control we do uh use the feeds. That's how we maintain. Yeah. For each file there is a different topic that's created and uh each have their own feeds and that's how we maintain the version.

Thanks Nidish for for clearing this for us. Um if any other questions appear I will make sure that they get answered. Oh let's let's let's clear this one. Can drive creation uh and file uploads be incorporated in an app?

Sorry uh can can you please repeat that? So Alan is asking if uh drive creation and um file uploads can be incorporated in an app.

So when we say an app it does it mean a separate app apart from the you know the B dashboard that

I'm asking myself but Alan please. Oh yeah that's what it means. Yeah.

Okay. Yeah. So I mean we have all the uh building blocks for it. I mean we have the file manager library that abstracts all these methods so that you know it can be implemented in any other app but uh B dashboard is uh where we can see it working right now. So yeah I mean it can technically be used in any other app too.

Fantastic. Uh all right so stick with us Nidish or just check please the uh in in um in call chat for for any further questions. But now I would like to invite to stage. Please raise your hand. Oh, you have done so.

And why are you not on stage? Invite. Okay. Welcome.

Okay.

Yeah.

Oh, yeah. It's working.

Perfect. Uh, thank you, Mina. Thank you all and uh thank you Nidish. Um actually your file develop your file manager um is very similar a lot of concepts to the things that we are developing on meta provide with a um but actually we we did not develop anything related with the file uh management uh we did use uh next cloud to do that um u UIUX part uh so actually what I'm going to talk a bit about today is what disable it and what were the problems that we are facing right now and um why uh this idea of IPH appeared and uh why it is uh useful for us and also for the community but um starting the the I'm Jeanos from meta provide I'm the product lead and um our first product around swarm is a bit um and our idea is to bring the decentralization benefits to people that don't know anything about uh web three. They don't know how to talk nothing about wallets uh nothing.

They can what they can do with a subscriber service and then connect it to xcloud and use it uh like a normal uh file manager um without touching anything related um with uh with web 3. So the plan here today is to talk about uh a bit what was our strategy initially um and why we need right now. So our idea initial was to target the next cloud um market. This was the market that we were trying to to to target and um working around education pharmaceuticals and organizations with critical data privacy and autonomy concerns. So all of this that I'm going to sh to share around the first slides this is what actually swarm is about and that's why under the hood edit is um is is swarm is and is the technology that we choose.

Uh so education we um people are concerned about uh maintaining the information about the lectures everything about the that content and they don't want to breaches of course um pharma about sensitive data and um privacy critical organization institution um this is around institutions that are very uh compliance driven or they are prioritizing protection from government data access. So this is the market that we try to target. What are the problems that we are solving the same about swarm? We just add the layer about um being easy to anyone that is not literate on uh web three. But um the idea is to avoid single point of failure.

Um to avoid attacks like the echifats or solid sunny breaches. um to maintain data sovereignty um so no one can use your data uh access it minity or freeze your accounts um avoid catastrophic data loss. We see that swarm can be a very good solution to the disaster recovery plannings. Um because we talk about having two the the data centers in two or three geo geo locations but swarm can do more than that. So that is a good solution and um also solve problems around political data control.

So what we uh try to achieve is through data sovereignty. The benefits is innate security as a chance encrypted distributed around um swarm network resilience and integrity and this is the layer that we had web three without the any complexity. what how a works uh is like I explained before right now it's just working with this next cloud plug-in we are considering to expand but right now to use IB we need next cloud to use the interface I can if is is interesting for the community I can do a quick uh demo on how it works uh but we create a it's very similar to the pre previous presentation we create a folder we everything that we put on the folder goes to swarm and then we can get the ashes this and do normal file operations uh around it. We do use spinning to uh avoid bandit costs and um also um to be more uh efficient in terms of speed. So this is very uh uh there are advantages um from centralized services uh all about data sovereignty over decentralized services uh like APFS or storage um we abstract the technical complexity about the usage and about uh cell phones to next cloud of of course we have this next layer of security and redundancy and everything that swarm uh offers.

So what was our plan? Our plan was to convert part of the next cloud websites and secure some high value customers have a subscription model and establishes as uh ourself as a web three guide to the web to uh people in the a bit more further. We wanted to go um get more B2C customers and a bit of B2B and be like the Trojan horse or of traditional industries like we were putting our product uh they were start using it and they did don't even notice that I was using web three they're just using the benefits but the rest is very similar to normal web tool this was the initial plan what we did until today is the we created a appab com that is actually uh a a payw wall system where um anyone can just uh grab a subscription and then they have the license key that can use on nextcloud and after that they can just upload download the files and of course we have the next cloud swarm integration and this is the plug-in that we call a bit plugin and this is what you needed to aid to work they installed the plugin they put the license and and start working and We also develop a WordPress uh plug-in to anyone that has a a WordPress website and a next cloud also and they can just um have a automated backup of the website to a a bit folder on next cloud. So we do decentralize the WordPress backup and this runs um on a schedule. Uh so every uh any WordPress website that uh has our the plug-in and of course having the next cloud also we can um do the backup decentralization.

So this is a bit about the how it looks. Uh the uh the payw world system is like this. So we can just subscribe what we want with the level of different redundancy that is the different things that we offer. The next cloud swarm integration is like this is normal next cloud but uh when we put our plugin there uh the files are decentralized on swarm. We did add a bit of extra feature.

uh we were thinking about um how to do the delete because we don't have the delete the same problem that was uh mentioned on the previous uh talk. Uh we did choose the archive feature because we talked about forget or something but we have a archive um uh feature since the files never disappear and we have the a centralized backup and what happens is that um on a schedule like you're seeing on screen uh the old website we do a a zip of the website and from the database uh SQL and uh we send it to a folder that is on an XC cloud that is connected to swarp. So the backup is decentralized and with extra security but yeah we did all of this uh but we do have one problem uh that uh we we still have this problem is that u we do we don't have uh user adoption. Um we are doing the marketing uh we are um doing a lot of different kind of motions but we don't have enough users um to uh sustain our product. So the first thing we did was remove the credit card.

It was mandatory to try the free trial. So we remove it and we already see some changes on the on the on the application. um at least we have more movement there. Um and we talk and we think about uh u expanding the market or maybe increasing the plug-in exposure or maybe uh explore some new use cases. So in terms of expanding the market uh there is a lot of options of course but the two ones that we are we think that make more sense is to uh tap into the IPFS market and um why do we think this is a good idea first because the IPFS market has large amount of data and there's large amount of usage and the other thing is that uh Actually if we connect IPFS with swarm we we can um have the best of the both worlds.

So we have the market and we have the data there on IPFS. uh but there are some problems that IPFS uh has um like things about speed, redundancy, availability of the file that um what normally the people does is to have a centralized service like pinata to solve this kind of problems with our solution this we we could avoid this u thing when I say our solution is actually with IPFS IPSH solution we don't have this kind of problem and Another thing that we think um is that um we can right now we don't have we have a free trial but we don't have a free tier. Why? Because to have the free tier um if we just use swarm uh that would mean some cost for us in terms of maintaining the stamps and also maintaining the data there and the bandwidth. But maybe we are talking about stamps and uh bandwidth that's that's the cost around it.

Uh but if we um direct this kind of files um that are on the free tier to IPFS um and we would we could offer a a a free tier that doesn't cost us any money and um maybe that can also uh people if they test more about product they probably can um this could be an idea to to to get more users. Of course, there's other ideas that we have like developing a rest API to have S3 support to have a bigger market or even create another uh solution. But I will quickly pass through these ones because then it's not um the the main uh topic of this call. But we um think about the increasing exposure of the plug-in and some new use cases that I'm not going to talk about it. there's someone that this is probably thinking more on blood

term and why IPF um IPH is uh so good u connecting to the why this is so good for us connecting with the IPFS market we are uh talking about picturing um grabbing the market that is there but having more security uh a very more faster the retrieval of the files because we can add some um swap performance in some of the tiers and yeah we can touch the data that is already on IPFS and very easy to migrate with IPSH and um and the idea is to IP if anyone is using a pinata service or any kind of service um the IPS would have the same um endpoints uh so they would respond to the same endpoint So if we needed to change uh quickly from IPSS IPFS to IPSH it would be very just easy just changing the URL everything would work. But yeah here is about uh a bit more about the the advantages or of integrating IPFS on uh our AIDS solution. But actually this is this is what I already uh talk about the dropping replacement of pinata and get access to the the services uh the in performance around speed redundancy availability and also because of the economic incentives incentives that um make the notes online and also the data online and uh with this Um we do also have some advantages around the tapping the IPFS market and our idea is to have this three tiers. The first tier would be mainly IPFS. It would be the ship tier maybe the free tier and the last tier would be just swarm um with some connections with the IPFS to migrate files easily.

And in the middle we can choose about if we want to to touch more about to to improve the speed or maybe just improve the redundancy. This is still onward. We are thinking about what what's the best solution uh for for us and also for the community and the idea that we have to develop IPH uh is to build open source. So um we don't control anything. Uh the idea is to if anyone else wants to run an IPSH node they can do it because they can just run their own node.

Um and uh if they want to put it on their own services no problem. um if uh if they want to develop something on top of it also. So the community continues to have full control over their infrastructure with having this um IPS edge on working. it will be um easy to just migrate um apps that are working with IPFS to IPSH and adding this part of the features because we maintain the URLs the the the end points and um of course again uh we do offer the we we and IPSH offers the advantages of swarm to IPFS uh community right Now we have an idea on how it's work. We have a Romesh here that um that can talk a bit about more technical details.

Um but the idea of the node right now would be uh the architecture right now that we are thinking is a Google client to connect to IPFS IPFS and as a B light note on on top as orchestrator to communicate with both of the nodes do you want to want something things

yeah no I I was just uh wondering I think we probably missed the slide somewhere like what IP T FH actually stands for and like sort of um and I think there are also some questions about uh why make protocol your

yeah the questions but just before I do that just to uh sum up so basically this interplanetary swarmhive that's what IPSH stands for is uh if I got that correctly like an IPFS compatible protocol that enables seamless migration right from IPFS to swarm by exposing familiar familiar IPFS uh IPFS and IPNS endpoints while persisting data on the swarm network would that be pro correct right just to to have like a sum up of what we heard here um but now we can go to the questions so one is from Peter do you see the possibility of cooperating with Swarm desktop developers. As you mentioned, some features are duplicated and they also have IPFS to Swarm migration tools. So, do you see the possibility of cooperation?

Of course, we are. Yes, we do um like to work closely with the community and also with the swarm um team. So, we are always available meta provide team. we can um we are very open to collaborations and talk about developments and road maps and of course don't do duplicated um features or something like this. So and now from MFW that's probably more for Romesh uh you can yeah probably see it Romesh right so why mix protocols here IPFS really sucks for discoverability time till the IPFS hash is accessible ultimately given that IPFS seems more like a CDN where the CDN is really only holding on what's paying for bandwidth and it doesn't ensure availability on all nodes some level of redundancy why not just uh adjust the swarm protocols to include something like global pinning whereby people could opt in to pin certain chunks or BZ hashes and then have some method of discoverability so that they can exchange data provide access via CD and and therefore it's incentivized via bandwidth incentives.

Well, that's interesting and we need to break this down but Romesh can you pick this one up? Yeah. So, uh, okay, there's a lot of questions there. So, first, uh, regarding why mix protocols, um, I think we're not mixing protocols. Uh, IPFSH is more of a, um, of a bridging of a easy way to bridge data from IPFS onto swarm.

Uh, given that legnos swarm currently doesn't have a a free tier, uh, protocol in itself. So I do agree that there might be benefits in having it directly on swarm as well. But in this case for meta provides particular case. uh the IP FSbased solution uh is a much better uh much more simpler and uh because it has a large target market already say things like uh Pinata and IPFS service providers. So that is a bear.

Oh dear. Now we lost him. Sorry. Sorry. Can you can you repeat the last uh the last two sentences please?

But but try to keep the stable connection close to the mic please.

Oh my sorry. So uh with respect to IPFS and uh with solutions like pinata the there are piata has like a lot of already paying so it's not about mixing protocol but providing a smooth transition or like targeting the IPFS market and providing a smooth transition to uh for people who already have uh projects that are integrated with IPFS or PIATA uh for uh to provide a solution for them which can uh be a easier transition to move their data from IPFS onto swarm and so in that context uh to provide uh also a free tier that uh uses IPFS currently because you don't really have free tier on swamp but I do agree with the other point that like um to have something on the native swarm protocol all to include something like a global pinning that would be great. Um I think that's up to the B team to also decide and uh that um and I think if that when if and when that comes it should probably also uh IPS should be able to take advantage of that again make global pinning great again indeed. Okay.

I agree there. I hear you.

Yeah. And I think uh this was um I think that is part of the plan to to also like if it if if it lands if global pinning lands on swarm, IPSS can also take advantage of that. uh but currently uh this is like so instead of trying to integrate each and every project that already has an IPFS integration and then try to move that data or readapt your entire project onto uh to to make it work with swarm IPSH provides a much simpler drop in replacement for uh your existing IP FS integrations or pinata integrations so at least that's that's the direction that idea that you're trying to I hope that's clear.

I guess but I see uh both MFW and Henry typing in the in the in chat. Um maybe let's wait let's give them what like 20 seconds to type their questions but uh really everybody is more than welcome to also post after the call is finished in in the stage chat and uh the team will be around to pick those questions up uh and Henry and Romesh and also Nidish.

Um please please just uh stick around for for a couple of more minutes after we finish the call. Um. Uhhuh. Okay. So why not MFW continues?

Why not an IPFS light client built into B and then on the retrieval protocol allow for BCZ and IPFS hash retrieval and would then allow for bandwidth incentives on both and therefore can use one node for both. What is your comment on that? Oh, a bit too much for the B code base. Okay, that's what Romesh thinks. So now I'm just reading what's happening in the chat.

That's exciting. That's exciting, guys. Thanks. Uh yeah. Uh okay.

So I I assume you will be nice and fine continuing in the chat. And for everybody uh who's only hearing this in audio over X and uh they can't see this chat here um let's invite them to come to Discord next time

or join us u you know live where the action is happening um but thank you at this point. Yes. Just to I I just the final slide was just to share the contacts to see to if anyone wants to contact back we we can um at least have the contacts on the

All right. Yes, please.

On your side.

Yeah.

Okay. Sorry. So yeah, the final slide was about just to reinforce what we already said. A is doing the connection between web two and web three and of course IPSH that I need to slow down a bit to say links IPFS2 swarm and um if you want to know uh more about it um we are meta provide the website is there and um I dropped two links I'm not sure if the presentation is shared or not but there's at least two links to know more about a know more about our latest developments or IPSH or maybe the protocol will be the new name that we just decided a couple of hours ago.

And thank you all.

Thank you. Thank you for joining us. And thanks also for everybody else uh all the uh spectators, all the listeners and of course all the speakers. Uh the next swarm community call will be held uh on last Thursday of October, always the last Thursday of the month and that is October 30th. Uh, see you then and have a great rest of the week.

Bye-bye.