Superalgos Trading Signals Sender Storage Node

A few more other details that Im going to go through now is the user profile. You will notice that I have my user profile in this new section that is called user storage. This is related to the open storage project and its mission is to enable users to have storage containers on the open Internet. Which are reachable by anybody because they have public IP addresses or whatever and in order to facilitate the storage of information there that then can be retrieved from other users. Why do we need this? The peer-to-peer network is not handling the transport of the signals per se. The way that this work is the following. When your Bot is sending a signal to the peer-to-peer Network. In fact it is not sending the information. What it does is the bot has this available storage and it has a storage container that is pointing to one of the storage containers that you have defined here. In this case my trading signals. You can Define one or more storage containers so far we have GitHub as a storage container provider but later we are going to develop more providers including a Superalgos provider so we can have our own system. If you run it at the open internet to store information for you. But to come back to the explanation of how this works. When the bot produces the signal its going to look at which are the available storages you have defined for this bot. You can have one or more containers. If you have more containers that means its going to be saved at many different places or more than one places at the open internet at the same time. That is good for resilience because if the information is deleted from one of the places. Maybe the storage provider doesnt want you to have that kind of stuff there then its still going to be available some other place or if GitHub is down. Maybe we can still retrieve the signal from some other place that is not GitHub. Not today GitHub is the only storage container provider but in the future we might have more than one. In this particular case I Define this storage container which is a repository that I created on GitHub and take into account that this is not automated yet the creation of this repository so far. Under your user account create a repository. You can call it like this or however you want even in other user accounts too. Create your storage containers and then link the available storage into your storage containers that you want to record the information of the trading signal. But what is going to happen is when the system needs to send the signal that it doesnt send it signal by signal but it packages all together in a group of signals that when is trading live is one candle worth of signal or the signal related to one candle as sent together. When it is on backtesting its all the signals of the backtest. If we are talking in a market time scale like one hour and above or all the signals of a single day. If we are practicing in a time frame of 45 minutes on below its going to package all the signals of one day and send it all together for efficiency. The signals are not going to do this packaging of information. The system does it and save it in whatever place you define here. Its going to encrypt it before it saves it. And its going to send the file key or the information needed to locate these containers for that signal. And there on the password to be encrypted sent via the peer-to-peer Network to all the people or all the Bots that are following the your bot. The other Bots when they get this file key. Theyre going to look for these containers download the data decrypt the data and then start processing the signals okay! Thats how this works. Lets go and check this out. I have to remember to show you that there is a file you need to create so far that is not automated yet at this version. That is one of the two Secrets file. Where youre going to store essentially your GitHub or whatever storage provider access token. So that the bot can access these containers and put there the signals files or retrieve them. So in order to create that file you need a codename that is unique and to create a container that is unique. I just put this GitHub storage container plus my username plus the name of repository. Making sure that Im not duplicating the codename of any of my containers. Even putting random stuff it would work the same. At that secret file you will see that we have for example my secrets. I will open this file it has my GitHub token which Im going to delete it later. API tokens allows bots that needs to put information in the container but the one who has to get the information. They dont need these keys because they read the information not via the GitHub API but via the Publics interface of the web interface. So only to store the data you need this file in this format. We have covered almost everything at a basic level okay.,

#