What Is Obyte (GBYTE)?
To begin developing any app which is based on headless-Obyte, first thing to do is to set up your machine, install Node.js and tools. Complete guide of preparing your blank Debian-based machine for development. You can skip this step if you are familiar with Node.js development and already know how to do it in your way. Full configuration options are described in Configuration section. As for now, in your configuration file (conf.js in project folder or conf.json in user folder) switch your app to light node and add hub URL. They wrapped all of your code in ‘headless_ wallet _ ready’ event handler, at this point the private keys of your wallet are encrypted and are ready for use.
Obyte Storage Key Points
|Circulating Supply||802,634.84 GBYTE|
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
Simple chat bot
Every Obyte wallet can be paired with any other wallet, because every wallet has it’s unique pairing code. Headless wallet will print it’s pairing code to console right after the launch. Depending on what kind of app you want to build, you will or will not need this pairing code. Simplest operations on platform require no chat bot (like sending /receiving txs, for example). For more handy interaction with your user base, you mostly surely need to write a chat bot, to set up direct interaction between your clients apps and your wallet (this process is called ‘pairing’).
Chat bot is Obyte wallet which can receive chat messages and react to them. Clients can pair and chat with your chat bot inside their wallet app, your task is to handle incoming messages and act accordingly. Through chat, users can provide to your chat bot their addresses, KYC profiles, or any other information with couple of clicks. When a user pairs his device with your bot (e.g. by clicking the link to your bot), you receive a pairing notification and can welcome the user.
Sometimes you might want to suggest the command without actually sending it immediately, so user could have the possibility to edit the command before sending, this could be done like this. Now you are ready to make something useful, go ahead to your Tutorials section and carefully read all of them to get better understanding of code API. At some point you’ll surely want to have a peek into the database, or even make a modification in it. Default SQLite database file and Rocks DB folder are located near the config file, you can find the correct paths for each platform above.
Storage Obyte – mysql or sqlite, the default is sqlite. If sqlite, the database files are stored in the app data folder. If mysql, you need to also initialize the database with initial. To lower disk load and increase sync speed, you can optionally disable flushing to disk every transaction, instead doing it once a second. Benefit of light node is that you can start using it immediately, but the downside is that you might not get updates about new transactions and confirmations as fast as full node does.
If your node accepts incoming connections, this is its URL. The node will share this URL with all its outgoing peers so that they can reconnect in any direction in the future. By default the node doesn’t share its URL even if it accepts connections. Settings for connecting through optional Obyte proxy. Use them to connect through TOR and hide your IP address from peers even when making outgoing connections. This is useful and highly recommended when you are running an online wallet on your server and want to make it harder for potential attackers to learn the IP address of the target to attack.
Accepting incoming connections
Obyte network works over secure Web Socket protocol wss://. To accept incoming connections, you’ll need a valid TLS certificate (you can get a free one from letsencrypt.org) and a domain name (you can get a free domain from Freenom). Then you accept connections on standard port 443 and proxy them to your locally running daemon. This can be executed with cron tab with the command mentioned in and when the email is properly configured on the server and the node crashes, this script will notify you that the node went down.