Beeport: Demo by Aron

So I'm going to talk about Bport. But uh before we do that, I would like to travel back in time a bit to the beginning of this year and talk a bit about what options there were to upload something to Swarm. So on the left you'll see running your own B node and I'm going to talk about issues here. So in the beginning of this year we had some issues with running your own B node. One of them was the long syncing times.

That meant when you started your bnode for the first time. It uh took about 40 minutes to synchronize from the blockchain and that happened even after you managed to fight your way through the documentation. And the other issue with that was theosis funding. So you not only had to have BZZ, you had to have XBZ on the Agnosis chain. But undeniably running your own B node is the decentralized approach.

It is always the primary recommended approach. It's also healthy for the network to run your own B node. Now the other option was and it wasn't really a good option was using this warm gateway but uh it had very obvious issues like only small file sizes were supported. uh the duration of uploads were unpredictable and it was guaranteed to be a short time span but still we could see that this was a very convenient way to upload content on swarm just go to a page select your files upload and without running uh your bnode you had them on the network after seeing the issues that I mentioned before we had a plan for this year to improve the UX in these areas as so on the left as part of the node spin up UX uh improvements uh we embedded the postage snapshot to the uh B binary which got rid of that 40inut uh synchronization time uh upon the first launch now you can run your own B node in like under 5 minutes we also got rid of some other artificial waiting time that was for stabilization it made it even faster to be able to start and use your B node. So these items are delivered.

Now to address the second problem with uh running B nodes, this nosis lock in or the inconvenience of getting XBZX die bridging them somehow over to Nosis. We were working on projects related to multi-chain funding or multi-chain payments. This is uh currently in progress. Two projects under this umbrella are a so-called multi-chain widget that can be used anywhere. It can be either statically hosted or embedded in applications.

And this purpose is to make it easier to fund your own B node and get get both XTI and XBZ. This is again to promote the decentralization of this warm network to make it not only fast to run your B node but also make it have good UX uh by eliminating the funding issues. Now on the other side uh and we are here for this today is Bport. So Bport is a standalone application. You can think of it as Swarm Gateway but on steroids.

So with B for you don't need to run a node uh you only need a wallet uh some funds from many uh Ethereum compatible chains and it requires the least effort and it's the fastest way to upload to the network. So again you can see that uh on the left running your own B node the decentralized option and on the right the convenient option and this brings us to Bport starting with a uh screenshot on how the main screen looks like and we are going to explore the use cases uh through several small clips. So the first one what which we are going to do is purchasing storage uh through Bport and in this main form you can select the chain that you want to use, the token that you want to use, the storage capacity and the storage duration. You get a quote for that that you can execute. Uh MetaMask pops up or your wallet of choice.

Uh you confirm the transaction and then a spinner starts. uh that deposits your funds, waits for transaction confirmation and starts creating the the postage batch. Once this spinner finishes, you get to this popup where you can already upload to the swarm network. So in this first use case, we are going to start simple and then and just upload a single file. So I'm selecting a PDF.

Clicking upload get a signature request so we can authorize ourselves for the proxy uh which is between our browser and Bport. And just like that it was already uploaded. I got a link to a gateway and you can see that uh the file loads and is visible on the network. So let's get a bit more complex than that. Uh this time I'm navigating to the upload tab where my previously purchased batches are displayed.

So I'm selecting the one that I just bought and this time I'm uploading a folder. So I'm here uploading a folder uh with PNG images flags of the word confirming um the signature request upload is already done. And when you upload a folder a folder index is created. So this lists all the files that have been uploaded in that folder. Uh you can scroll through them, click on them and they load on demand.

Of course for the third use case, let's do something even more advanced and that is uploading a application or a website. So I'm doing the same flow as before. I'm doing a folder upload but this time the folder that I'm uploading is the source of a website. So in its structure there is an index html uh that that makes it very obvious for bport that it's a website and it will upload it like that. Now having done that I'm going to navigate to my history where I see my latest upload and there I can click the ENS button uh for further features uh related to ENS integration.

So what I'm going to do now without leaving Bport is registering a new uh ENS domain. I'm going with flagg guesser and starting the registration process. Uh so with the magic of video editing uh we are going to cut some some waiting times uh shorter. For example, the first step to ENS registration is always a one minute timer. That is in order to avoid default running.

Bport explains these steps in an easily understandable way and most of the time you just need to uh click the primary button to proceed to the next steps. This is the actual step where the ENS domain registration happens. uh gas fee is a bit high uh on Ethereum at the moment but you can expect that [snorts] and after some more waiting just a minute or two uh within the application you get the confirmation that your ENS name has been successfully registered. So this is not the last step. As the last step you still need to link uh your swarm reference your upload to your ENS.

So to do that you go back to the send set content hash tab and there you select uh the ENS name that you want to use. Simply again just click the primary button you get the transaction request for setting content hash for your ENS and as that transaction goes through you receive multiple options to access your content. So I'm picking E limo here. And once I navigate to that tab, you see that this content is served uh from swarm and it was fully uploaded uh through bport. So this is just a uh silly flagg guesser game that I made where I accidentally got three out of three.

So yeah, again we have seen that now uh there are multiple options to upload just a single file, a folder or a website and then even go a step further and then set it up uh with DNS uh giving you multiple options to access your content. And I want to emphasize that even though Bport is a centralized component to get your data on the Swarm network, once it is on Swarm, that content is still decentralized. Uh the URL is now uh displayed on the screen. I welcome everyone to start using Bport and please give us feedback either on Discord or using the feedback button uh within Bport for issues or ideas that you may have. And with that, I would like to thank uh you for your attention.