HyperCycle - Node Factory Setup Tutorial

[Music] Hello everyone, Jack here from Hype Cycle. I am with Dr Robert Moore, Chief Science Officer from Hype Cycle, as well. We are live, and I’m really excited to have you all here.

Robert, how is it going? It's going great, thanks, Jack! Great to be here.

How's it going with you? Great! I'm really excited to see this live.

You know, it's been a long working period for everyone, so to see this becoming a reality is really exciting. Absolutely, it’s been a lot of things to bring together, and I’m really excited to roll all this out. Yeah, so as you know, Robert, we’ve just published the new documentation on how to use the new features that we just released.

But today, I wanted to record a tutorial video with you on how to manage all the tools that are provided inside this new D. There are a lot of things to cover, and I believe this is a time to help everyone get started on Hype Cycle. It’s easy—if you go on the Hype Cycle dApp, everything is ready for you.

You have to follow the guide, but let's take some time to cover everything and explain how things work. And maybe, Robert, if you have some comments or insights to share with the community, feel free to interrupt me, and we'll cover this as well. Sure, sounds good.

Okay, so I wanted to start with the basics—going to the landing page—because a few things have changed, if you haven't noticed. But first of all, we have a new terminology that I would like to start with. We have this new "node factory" terminology.

So maybe you can share some quick words on that, Robert. What does this mean, and why did it change? Sure!

Yeah, so this is exactly the same thing as what was previously called a hypershare. Basically, we wanted to change the name to make it easier to understand what the core functionality of a hypershare was, which really is the fact that it gains various forms of reputation on the network, increasing its score. When the score reaches two, it can unlock two nodes from where there was one.

So we can think of this as the original node manufacturing new additional nodes over time as the node score increases, and this process iterates through different levels or layers. The metaphor of a node factory really illustrates this idea very clearly because you can understand that’s what its function is to do. The R tokens and S tokens that we explained before are still there in the background, allowing for shared ownership and management of your node factory, as well as the automated revenue distribution.

So all of that functionality is still there—nothing has changed; it’s just now we have an easier way of talking about and understanding what it is and what it does. Yes, okay, so I find it very appealing. I understand the terminology as a way to build my own mini factories of nodes, so to me it makes more sense to use this, and I’m glad we changed it.

But I know that we also changed the Hype Cycle computational node to a Hype Cycle network node. So why is that? Yes, so originally when we were thinking of how these nodes were running on the network, we thought of them as producing or providing, rather, an AI computation service.

So some kind of request comes in, it does some AI computation, and sends a request out. There are two reasons for the change: one is that the computation may or may not actually be happening where the node is because the node could provide a gateway to some other service, allowing you to pay for that other service. So it's not really doing computation.

But the more important clarification is that it’s not actually Hype Cycle that's doing the computation; it's whoever the node operator is, running that on their own hardware—whether that’s on-premises, in the cloud, or some other kind of decentralized network of computation. Wherever the device is that it's happening on is owned and operated not by Hype Cycle, but by some other party. Really, the key part that Hype Cycle is enabling is this network communication layer, allowing for AI-to-AI communication peer-to-peer and this lightweight payment system that we provide using Totem technology.

By changing from computation node to network node, it clarifies what Hype Cycle is providing, which is this network layer allowing you to operate this AI peer-to-peer communication network. Yeah, okay, because this is exactly what this tab encapsulates as well. I mean, you have all these tiny elements that are part of Hype Cycle's design, and they're all working together flawlessly on the dApp, allowing you to set up your node factories and be prepared for the moment that you will be willing to run a business on Hype Cycle.

So I like the fact that this dApp embodies our mission to create the network for AI-to-AI communication, and to have this in one single place is really a miracle to me because, well, you had to do a lot of work to make this a reality, so congratulations to you! I can't take the credit myself; it's the whole team, and the developers on the engineering side have been working really, really hard on this. Uh, so it's their achievement, and they are to be congratulated for the results.

Yeah, congrats everyone! Um, so just a quick reminder for everyone who's joining the hyp cycle adventure: if you want to get started on hyp cycle and set up your node factories, you need basically three things. You will need an NDE license; you will also need some HOPC that you will have to convert to an NFT pointer in order to marry your HOPC with your node licenses; and ultimately, you will need a hardware machine that will be responsible for not only registering your nodes' activity but also computing the tasks that are requested by the requestor on the network.

So, on the main page of the DApp, you will find all the cards that will lead you to get those assets to get started on the network. If you need to acquire more HOPC, you can click on "Exchange," and this will lead you to a node market where you have some OTC deals to acquire some HOPC. You can also acquire some licenses.

If you need some licenses, you can also go to the node market by clicking on this button. If you need to convert your HOPC into the NFT, you will have to go to this DApp, "Swap DB," and you will have to select at which level you want to convert your HOPC into the C HOPC, and then you're all set to get started with all the wizards that we have created for you in order to create your N Factory. So, if I go back, let me just quickly clarify that the level of HOPC you need corresponds to the level of license that you've purchased.

Exactly! Yes, and this is included in this short board that you have here in the FAQ. Whenever you have a certain level in your node license, you need to pair it with a certain amount of HOPC tokens.

So, for example, let's go to the license menu, and you can see here that I have some licenses listed in my wallet, which is connected to the Ethereum network, and you have a lot of information in the license menu. The first one is the level of your license, so you can refer to the FAQ to know exactly how many HOPC you will need to pair. Then, you have the total amount of nodes that your node factory, that is tied to this level, will eventually create after a certain number of series of unlocking events.

The final data that you have, and this one is important, especially for today, is the node license ID. Depending on what you plan on doing with the DApp today, you might have to choose between conserving different licenses at the same level or maybe merging them together because you don't expect to conduct many different activities in separate node factories, and you just want to manage one node factory for starters. So, what you need to do in this case is check the level of your NDE licenses, and they have to match at the same level.

Next, you have to verify that the N license ID is the same as the other license ID you want to merge with, except that they only differ by one number, right? So, for example, if I want to merge this level 10 with this level 10, I can because I share the same root ID except for the last number. This will allow me to convert this level 10 NDE license and this level 10 NDE license to one level 11 node license by just clicking "Merge" and refreshing the license page.

So, I'm saying this, Robert, because as we are inviting people to either migrate or create new node factories, we want people to save on Ethereum fees if they don't have to, you know, do the process multiple times to have the same result in the end. So, I just thought they should know that. Yeah, that's a good point.

You want to create a node factory at the highest possible level you can. So, I think depending on how much HOPC you have available, you want to max out on the HOPC or C HOPC you create from that and then have a node license at the appropriate level. MH: Yeah, there's always the option to cancel the node factory if you mistakenly created one node factory at a certain level and you want to switch, but this will again cost you a bit of a fee.

So, if we can avoid this, just be mindful before starting to know exactly at which level you want to create your node factory. So, next is the convert page, and this is where you can choose at which level you would like to operate as a merge with your C HOPC and your NDE license. So, let's say that if I have a node license level 10 and I want to create a node factory at this level, I will also need to convert some HOPC into a C HOPC NFT at the same level, which means that at this level, I will need 1.

24 HOPC tokens. In order to create CHPC and once I have the CHPC at level 10 and the N license at level 10, for example, then I can go to the creation wizard and create a new Not Factory. This was just for the basics; we have all the documentation that has already been released explaining this, but this is just a brief overview so you can understand how to get started.

The last menu, and maybe the most important one, is the Not Factory menu. This is one menu that has changed a lot. If you are in the situation where you have already created some Not Factories with a previous version of the DAP, they will be listed in the category of all NDE Factories.

Each time you either migrate from the previous version of the Not Factory to the new version or create a new Not Factory with the creation wizard that we have here, they will be listed in my Not Factory category. This part is important because we know many of you are in this precise category and will have to migrate from V1 to V2 before you can use all the new tools that have been released in the new DAP and also activate teing with the new Hyper PG and teing as a service. So maybe, Robert, what we can do now is show people how to migrate from the V1 version to the V2 version, because I believe most of the community is in this situation, right?

Okay, so let's now see how to migrate from the V1 version of your Not Factory to the V2 using what we call the migration wizard. Next, we will see how to activate tilling with another wizard called the Tiller Creation Wizard. To start that, what you need to do is go to the N Factory menu, and you will see your old Not Factories listed under this category.

You just have to pick one, so I'm going to select this one. As you can see, you can see the CHPC ID, license ID, and Not Factory number. You can also see that I own all the S tokens for this Not Factory, and I also own 70% of those R tokens because 30% of those R tokens are already reserved for the hardware operator, is that correct, Robert?

Yeah, I mean technically, it's adaptable in terms of what address you can provide those to. It's intended to be the node operator; it could be a different party depending on the configuration, and you can vary the percentage between, I think, zero and 30% of the R tokens to that other party. Okay, and from what I understood, Robert, most of the procedures for migrating and creating a Tiller involve the ownership of the S tokens, right?

So, at some point, the contract needs to check that you are the sole owner of the S tokens in order to operate the changes, which in this case are migrating and then activating tilling. If you are in this situation where you are not the sole owner of all the S tokens, we have shared a support page in the documentation, so feel free to reach out to us there. We have a team from the Hypers Squad overseeing this, so make sure to contact us.

But for now, let's just migrate and simply click on the migrate button that you can see here. This will lead you to the migration wizard, so I'm clicking here, and you have this step-by-step guide that will guide you through all the steps you need to complete in order to have your V1 Hyper Share SL Not Factory migrated to the V2 N Manager contract. The first step will be to check your ownership of the S tokens, and then you will have to approve the transfer of your S tokens to the SH Manager contract.

Since I have already done that, I don't need to do it again. Then you will need to increase the voting powers inside the contract so we can initiate the voting for the migration. So this step requires you to validate with your wallet, yes?

So this involves transferring your S tokens temporarily into the contract, which is done as a security measure, so people can't double vote, that kind of thing. Exactly. Also, a short comment on this: sometimes the wizard allows you to click on the next button, but the transaction hasn't passed completely or wasn't confirmed.

So we advise you to wait for the complete confirmation of the transaction; otherwise, you are going to be stuck, and you will have to reject one. So just be patient and wait for the confirmation from your wallet. Once this has been temporarily transferred, you can ask the wizard to create the vote for the migration.

Validate with your wallet. Once this is succeeded, you can now initiate the vote. All right, and the final step is to click on "finish migration.

" What the text is explaining here is that we've built a migration contract to help with the process of transferring from Share Manager V1 to Share Manager V2 to ensure that the transfer can happen safely and securely. So that's what this last step is doing: you've authorized the transfer to the migration contract, and then the. .

. Finished migration is actually transferring it to Share Manager B2, and what I like about this, Rob, is also that the hype cycle has no control over what I am doing with my assets, right? So, it's a fully decentralized process.

We don't have a say in what you do. Um, so then I will be asked to go to the Not Factory Manager, so I need to refresh the page. Sometimes it just does that; that's just a thing because this is hosted on an alternative server right now.

Yeah, okay. And now you see that the Not Factory menu has changed again, so I don't see my old V1 Not Factory anymore. I'm seeing only two brand new V2 hyper shares, so I believe the one I just migrated was this one.

The old Not Factory menu has disappeared now because I migrated them all. All right, so next, when I enter the new NDE Manager for this migrated N Factory, I can see that I still have the same CHPC license, operator address, and Not Factory IDs. Nothing changed.

I still have the S tokens, R tokens, and what's new basically is that I have multiple voting propositions now that I can use with my S tokens. There is also this Update Tiller, which is tied to the HTS Hyper PG, you know, TEEing as a service page, and this will allow me to initiate TEEing for this Not Factory right away without having to articulate with Hyper PG directly. So, what you will need to do now is just simply click on Update Tiller.

Once you have arrived at this page, which is called the Tiller Creation Wizard, you will be asked to either select the Tiller that you have already created or create a new Tiller. And maybe here, Robert, we could explain a bit what Tiller actually is. Sure.

So, we've probably explained this before, but it's good to elaborate a bit more so that we're clear because TEEing is this unique term in our ecosystem. We've talked a lot about uptime TEEing, which is the service that HTS currently provides, and that is one of the factors involved in computing the score for your node, determining, you know, once that reaches two, allows your node to manufacture another node or you have two from one. But there are two other factors that we'll be introducing over time.

So, compute TEEing is there, and it's only available in very limited contexts right now, but as the system develops, we'll have that more and more available to people. HTS is a service provided by Hyper PG that will evolve into a system that provides essentially delegated compute TEEing on your behalf, which means it will be a compute service taking in some form of revenue. The details of that will be worked out, but the nice aspect of how this will work right now is if you subscribe to HTS now, that subscription fee will just be covering uptime TEEing costs.

But as this evolves into a compute TEEing service, you will then gain access to that. Yes, okay, so I won't have to manage this by myself. So, yeah, right.

Okay. In my case, let's create a new Tiller because I don't have one in this wallet. So, this is where you will see the various propositions that Hyper PG offers.

So, there is both a subscription offer and also a bonus offer, right? So, if I select, for example, this one, it means that I will subscribe for 12 months of TEEing, but I will get six extra months of TEEing as a bonus. That's correct, yeah.

So, in the form of a credit that you can use towards additional services. Okay, yeah, yeah. And the novelty also is that we need to pay in USDC on the Ethereum network.

So, for this, I shared a documentation, a quick tutorial on how to add, you know, USDC on your MetaMask wallet. It's rather simple; you go to Etherscan and you type USDC. You go to the contract address of USDC, copy, paste it, and then you open your wallet.

I don't think we see my wallet. In your token category, you will go to import tokens, copy, paste the contract for USDC, and it will list your USDC into your wallet. So, I have done that already, so what I can do now is just select the formula I want to subscribe to.

Let's say I want to pay for this one. So, I click pay, I select my offer, I click pay, and I need to validate the transaction of 60 USDC with my wallet. I say yes.

All right, just waiting a bit to have the confirmation. Yeah, okay. I click sign to authorize the creation of the Tiller.

So, this one is just sending a message, so I don't have to pay anything. Next, I need to click on Create the Tiller to actually assign a Tiller to my future Not Factory. And here you go, you can see I have this Tiller number two that was already added for me.

So, what I need to do now is just click next, and here we go, we are in the process of initiating TEEing. As before, you have to go through all the steps in order to, uh, request HTS to activate the thing for you. Yes, so maybe just to explain what just happened: what we were doing was creating a new, uh, basically a slot in HTS for your particular node factory.

So you were depositing funds into, uh, the system managing HS and then creating that slot, and then, uh, assigning your share to that slot. But to actually initiate tilling, you now need to go through the process of actually saying to, uh, your node factory, "I actually want HTS to tell my node factory on my behalf," so that whole authorization process is now what we're doing, okay? And all of this is verifiable on the blockchain, which is, yes, yes, which is cool.

So I signed the message and then I need to approve a manager contract to take my S tokens to initiate the vote. So now I need to create my voting power using my—well, not mine; they are temporarily inside the contract—but I can tell the contract to create the voting powers, so it's using the S tokens that were tied to my node factories that we just migrated. All right, and now it's time to create the voting.

So each time, I have to, uh, validate and authorize the transaction with my wallet. You don't see it on the screen, but each time I have to click on my wallet and approve, and then it's time to actually vote for setting up the node factory. Yeah, so in the general case, uh, where there are multiple parties with S tokens, they all need to agree, uh, to assign their node factory to some, uh, machine to do the tilling.

So in this instance, you own all of the S tokens, so it's just you, but you still need to go through this voting mechanism, um, given the share being managed by the share manager too. Exactly, and I think most of the community is in this situation where they are the sole owners of the S tokens right now, so it shouldn't be problematic for them to achieve this process. The last part is to add a message to HTS to say, "Hey, let's start!

" All right, and now I can go to the management page. So I can either click on this or go to my node factories and just select the one I just updated, the tiller. If I want to make sure the process went through, I go down below to the voting history, and you can see that the change of the hardware operator address has been processed.

All the S token owners have been voting in favor of this proposition. Well, I was an S owner doing that, but, um, and it says, uh, here is a message that was sent through HTS. So now we know that a machine is actually measuring the tiling for this node, and that's all for this scenario.

So pretty straightforward, nothing very complicated, and as you can see, uh, you can manage this by yourself; you don't have to ask anyone for permission or whatnot. Um, so pretty cool. And now let's see how to create a brand new node factory with some HIPC and some non-licenses, and also how to activate the tiling right away, uh, using one single tool that we call the node creation wizard.

So, uh, in prep of this, I told you that you will need to own not only a node license but also some HIPC that corresponds to the amount of the level, uh, you want to create your node factory on. So let's say that I own some level 10 node licenses. I need to convert my HIPC into the CHPC at the level 10, so I'm going to do this now.

I need to approve the conversion first, uh, can set the maximum. Okay, let's—yeah, okay—uh, just to point out that you can do the conversion here, but the wizard is also set up to do the conversion for you as long as you have sufficient HIPC in the wallet that you're using. Oh, you're right!

Okay, as for this part, uh, you don't have to manage this; this is internal to HIPC. Uh, this is a part where I'm, uh, taking care of that, making sure that all the levels have enough, uh, CHPC tokens for you to swap, so you don't have to interact with this; we take care of this. Uh, so now the split in level piece you're talking about?

Yeah, so now I need to confirm the swap. Okay, and now, as you can see, I have my CHY PC at level 10. Uh, here's the ID, so we can get started in creating a new node using the node factory creation.

So you just click on it, you select first your license—so let's select—I have to, let's select this one. It's detecting that I have now CHPC at level 10, so that's good. Let's click next.

And next, we need to approve both the license and the, uh, the HIPC and next our—the two, so I'm going to approve. Yeah, so here, in order to create the node factory, you need to deposit your license and your CHYC into the contract, uh, so that's what you're approving here, and then it can, uh, perform the marriage by creating the node factory. Exactly, so I'm approving this HIPC now.

Okay, now it's time to get married again! All right, so we had this wizard—I mean, uh, a simpler version of this one, uh, Robert, but it stopped at the marriage completion, right? But now, um, you have integrated all the steps to actually continue with initiating teing inside the same tool.

That's correct, yeah. So the part was coming soon, and that initial version is now filled out to allow your being after. So we used to stop there basically, well not there, but there, uh, and this is the page where we are providing the solution to, uh, actually transfer some of the RNs tokens to some beneficiaries if you plan already on working with some people, uh, for this.

Uh, uh, not Factory, but if that's not the case for you, you can just keep this step for now by. In most cases, uh, yeah, you won't be needing to distribute. But if you do, uh, and you don't want to do it right away, like you know you're going to be distributing to other parties, but you're not sure exactly on the amounts yet, there's no problem skipping this for now because you can always access that in the management page later.

So let's skip this. And now this is a novelty that we have added, uh, so you can now deploy your not Factory by starting teing with HTF. Yes, so you have the choice to either go to the nde factory management page and click on update tiller, like we, uh, we showed you earlier, or you can just deploy with HTS right away, uh, by staying on this tool.

So let's do that, and same as before. So yeah, so this is a little detail here, Robert, because yes, it says that I have already a tiller that I created earlier, but, uh, if I'm choosing this one for my new not Factory, it means that it's going to disconnect from the previous not Factory I assigned it to, right? Yeah, that's correct.

You would override your initial setup and use this not Factory instead in that slot that I was describing before. So if you want to till them both alongside, you need to create a new slot. So you need to create a new tiller.

Okay, so let's do that. Um, and I want to try this one, uh, uh, this time. So yeah, let's pay $5 in USDC.

So it's requesting my wallet to accept the transaction. All right, so same as before, I need to sign and then create a second tiller. Okay, it's loading.

So yeah, I'm seeing now two tiers. So I remember this one is already telling my previous not Factory, so let's use this one. And next, uh, just like we've seen before, uh, we go through all the steps.

Yeah, so the menu, the drop-down menu that you just used wasn't showing up on the video there, I think, but you'll see if you go back. You went from number two to number three. Number three was the one you just created, and that's the one you select.

I'm just repeating the steps here. Yeah, this is exactly the same as what we did before, just like that. So it was easy.

Uh, I can go to my not Factory. I can go, yeah, refresh the page. So this is the eighth one, and then if I want to check that, uh, my node is actually teing, I have to, uh, check my voting history.

As you can see, a machine has been, uh, assigned to my, uh, not Factory. All in favor voted, so my node is actually te, um, so like we said, uh, like we say in France, voila! Um, everything works fine.

That wasn't really, uh, difficult, Robert. So, uh, congrats to the engineering department. Um, I mean, you just have to follow the steps, we'll pass that on.

Okay, just one thing to comment here, um, is that so strictly speaking, the existence of this voting shown in the menu here at the end doesn't with 100% confidence tell you that the tilling has actually been initiated. Um, it's like almost certain, but there is one other step that goes be, uh, that happens after setting this message, which is when you're sending the message to the tiller. That's the last step.

Um, so I don't know if we want to show this in this video, uh, but there is a way to check that it is indeed, uh, telling, but that involves going to the HTS page. So it's up to you if you want to include that or not. Maybe that's something we can show, uh, in another video, because we need to cover how to configure your node on HTS.

Sure, if you want to go further, so let's do that on another video. Okay, um, but maybe that's something that is about to happen soon, right, Robert? Because we have a lot of things done, the pipe right?

Uh, so I think, uh, yeah, we are planning on, um, you know, providing and delivering more tangible, uh, releases, uh, on a regular basis now because, uh, well, we have reached a stage where everything is working smoothly now, so we can deliver more and more. Yeah, and I think next week is probably a good time, uh, for us to go through HTS. Okay, um, maybe the week after, but certainly the next couple of weeks to show people how that works and, uh, you know, allow them to see, um, more detail on what's happening with their not Factory.

All right, okay, cool. So yeah, great job, great job for providing all this. Uh, I love this tool, honestly.

Um, it's pretty straightforward, so we encourage every one of you to just test it, share your feedback, uh, to the Telegram channel. Uh, there is always someone to answer and to relay your message to the tech department. Shouldn't be too complicated, um, so don't hesitate to test it.

Wait for the good Ethereum fees condition whenever you engage with the D. Uh, we are still relying on this, so usually what I do here in my T time zone is I do this on the weekend because it's cheaper this way. But apart from that, uh, let's meet again for another video, and also don't forget to join us in the next uh, X space that we will be hosting next Friday at 9:00 a.

m. UTC. Bye!

Sounds good. Bye-bye, everyone.