Jump to content

Saronite

Sign in to follow this  
  • entries
    22
  • comments
    0
  • views
    94

Entries in this blog

Snider

mndown.com-logo-1.png

New Partnership! https://MNDown.com

Hey Saroknights,

 

mFridge here: I would like to formally introduce my latest project and spend a little bit of time talking about a few topics, primarily the project itself, its integration with Saronite, and how my involvment intertwines with the two.

 

Over the past few weeks I have noticed a sort of upset with Service nodes going offline for one reason or another, and people forfeited their right to continue receiving Service Node rewards. I had a Snode of my own go offline, actually just after registering it, it went offline by no fault of my own. Having this happen is extremely discouraging and I think pushes people away from the Saronite project. I have come up with solution not only for myself, but for the Saronite community to utilize. While I would love to offer the service free of charge, there are cost involved to mataining this project: Dedicated VPS hosting for myself and clients Snodes, Web Hosting, Monitoring Software costs, and of course my life points 🙂

 

What is https://MNDown.com?

Basically, I have come up with a way of insuring Snode uptime & uptime proof submission to a 100% success rate. MNDown.com serves as a web portal to access the online snode health portal, information on the project, and a customer portal to update preferences for monitoring.

 

How does it work? How does it insure 100% success rate?

As much as I would like to elaborate on this lengthy topic, I believe a nice flow chart presents the information in a more orderly fashion. I have tested very thoroughly (recklessly on live net) and this formula does in fact work.

 

mndown-flow1-min.jpg

 

Isn’t this sort of a conflict of interest?

 

While I believe it is not, some might say otherwise. As a Saronite developer I am 100% at your disposal for help on anything Saronite. The reason I created MNDown.com is to help bridge the gap between vetted Saronite members who can set up a node in 5 minutes & those who have very little background knowledge on Linux, Servers, Staking – just to name a few. Just because you don’t have the technical know how, doesn’t mean you shouldn’t be able to easily obtain a service node.
Anyhow, if you’re interested in setting up a service node on your own of course we are here to help! However, if you want to relieve that work to me come visit https://MNDown.com

Thank you all and happy holidays
mFridge_


View the full article

Snider

We have partnered up with MNTrend.com!

Come check out our listing here: https://mntrend.com/en/currencies/XRN

MNTrend.com was launched in September of 2018 and has around 3,400 monthly users. Because of it’s young age, MNTrend has yet to reach the monthly numbers of Masternodes.pro. However, we believe MNTrend.com shows great potential for long term growth and is an excellent platform to use. We welcome MNTrend.com into the Saronite family. 

I am going to cut this update short. On a side note, we are still in the process of being listed on Escodex.com – We are waiting on them to finish the back end development work.

 


View the full article

Snider

Over the past month the Saronite team has made some very progressive steps forward.

 

As the Saronite project continues to grow we have many objectives.

Here are some things that are currently in the works behind the scenes:

  • Listing on a second exchange https://www.escodex.com/ (Application has been submitted!)
  • New PHP Developer joining the team who will solely work on development of Sarowrite.
  • Sarowrite + Saropay.
  • New Forum section added to website (soft launch) https://saronite.io/forum
  • Getting listed on CoinMarketCap
  • Saronite Blockchain Explorer complete rework / redesign
  • New Discord bots (Node Down Alert Bot + Others)
  • New “Exchange Listing Progress” bar.
  • Marketing outreach / guerilla PR
  • Back end code changes as usual.

 

 


View the full article

Snider

Black Falcon Update is here! Saronite successfully forked and now looking for at the road ahead.

In this update we will discuss the following:

  • Black Falcon Update
  • Network Stability
  • New exchange
  • What’s next for Saronite

The Black Falcon Update

The Black Falcon update took place 16 hours ago, Saronite moved to a new hashing algorithm and started to make use of a new difficulty algorithm. This was mainly to get rid of Nicehash and also our older difficulty adjustment algorithm. Going forward, Saronite will always move away from Nicehash support in the case where the currently hashing algorithm will become Nicehash friendly. This may or may not happen in the future.

Network Stability

After forking to our latest changes, the network stabilized quite nicely and block times are now much more frequent like it is supposed to be. The main reason for this is that Nicehash has left our network and our new difficulty algorithm is more responsive.

New Exchange

We all knew that Saronite will need to get onto a new exchange eventually, we feel the time is right to do so. Our team are currently saving up to get listed on Escodex. We should reach our saving goal within the next 35 days. It might even be sooner depending on the price. The governance are being listed as sell orders currently, if you would like to contribute towards this goal, you can buy the governance at current market price directly and pay the Bitcoin into the exchange fund for Escodex.

What’s next for Saronite

In the next few weeks we will be working on the following

  • Getting Saronite listed on a new exchange
  • Adding Bulletproofs on the Saronite Blockchain (lower fees and smaller blockchain) and other developments
  • Working on the SaroWrite platform(coming early 2019)
  • Start working on SPCL (Saronite Protocol Communications Layer)

That’s it for the the Black Falcon Update, until next time SaroKnights!


View the full article

Snider

How to fix error message “Bind address already in use” when starting server daemon.

So, if you do not have a cronjob created, all you have to do is run the server daemon with these arguments: ./saronited --service-node --zmq-rpc-bind-port 34236 --p2p-bind-port 42158 --rpc-bind-port 32915

If you have a cronjob setup and are using the “Saroscript” you will have to update it to something like the below code.

Saroscript should look something like this:
#!/usr/bin/env bash
set -eux -o pipefail
[[ $(pgrep -fu $(whoami) 'saronited') ]] || screen -dmS saronited -- /media/md0/YOURUSERNAME/saronite-linux64-v1.2.0.0/saronited --service-node --zmq-rpc-bind-port 34236 --p2p-bind-port 42158 --rpc-bind-port 32915

You will have to adjust the direct path and your username obviously.

That’s it, the cronjob stays the same, just the script needed updating to run with the new arguments. If you get an error saying the bind address is already in use, try changing the port numbers: 34236 42158 32915 to something random in range 1100 – 65535 range. If the error continues to occur, change the ports again until it works.


View the full article

Snider

Windows

To updated your Saronite daemon for Windows, follow the steps below

  • Go to your folder where your Saronite daemon is
  • Deleted your current saronited.exe
  • Upload the latest saronited.exe
  • Open command prompt as administrator
  • cd <enter your directory> > press enter
  • type saronited.exe –service-node
  • Press enter

That’s all you need to do for Windows

Ubuntu / Linux – Quick Notes

  • wget https://github.com/Saronite/saronite-protocol/releases/download/v1.2.0.0/saronite-linux64-v1.2.0.0.tar.bz2
  • tar xvf saronite-linux64-v1.2.0.0.tar.bz2
  • cd saronite-linux64-v1.2.0.0
  • ./saronited --service-node

Ubuntu / Linux – Long Notes

Here’s an overview of what needs to happen in order to update your daemon.

Firstly, you need to SSH/Connect into your server, login and navigate to your home dir – You’ll typically be put in your home dir, if not use command: cd ~/

(If you have a cronjob running, you need to temporarily disable it while updating your server daemon)

To do this, use command: crontab -e

Remove the entire line just after the marked out content (#) it should start with a * –  I would save this line into a notepad as you will need it later to update your cronjob.

(If you DO NOT have a cronjob running, skip the above section)

In order to run the new server daemon you need to kill / turn off the old server daemon, which should be named “saronited”. You can list all running processes by running this command: ps x

Once you have identified the running “saronited” process, it should have a “PID” (Process ID) typically a number.

To kill the process, use command: kill (process ID here)

Once the old daemon is stopped, you need to wget the latest server daemon release – for this example the command would be: wget https://github.com/Saronite/saronite-protocol/releases/download/v1.2.0.0/saronite-linux64-v1.2.0.0.tar.bz2

Once you have downloaded the most recent rev, you need to decompress it using this command: tar xvf saronite-linux64-v1.2.0.0.tar.bz2

Now, if you type “ls” you should see  your newly decompressed server daemon folder named “saronite-linux64-v1.2.0.0” – You’ll want to use this command to change directories: cd saronite-linux64-v1.2.0.0

Once inside “saronite-linux64-v1.2.0.0” you should see “saronited” by typing command: ls

Simply run this command to start your new updated server daemon: ./saronited --service-node

Everything should sync up and you should have the same service node ID – check this by running this command once the daemon has fully started: print_sn_key

This “updating service node” guide should apply to future releases as well, the concept is the same.

Congrats, you’ve successfully updated your service node – If you need assistance feel free to join our Discord or Telegram and ask for assistance. Discord: here Telegram: here

 


View the full article

Snider

In this update we will discuss the following:

  • Service Nodes
  • Whitepaper
  • Hashing algorithm and difficulty algorithm fork
  • Exchange
  • Community Questions
  • Twitter giveaway
  • The Swap

Service Nodes

Service Nodes has been live on the Saronite blockchain since block 5000. Since the start of service nodes, there was a total of 46. Three of them has been de-registered from the network. We ask everyone that’s running a service node currently or plans to run one, to run them on stable servers and avoid home computers at all cost. When a service node de-register. At the time of writing there is a total of 1.9 Million XRN has been locked away. We are also proud to now be listed on Masternodes.pro. You can visit the Saronite statistics by following this link https://masternodes.pro/stats/xrn/statistics

Whitepaper

The Saronite whitepaper has been updated to v1.1

The following sections in the whitepaper has changed

  • SaroWrite (Adjustments were made and added feature list)
  • Algorithm update

The whitepaper will be updated a few times a week to show new features after we have tested some functions. We will have a permanent testnet pool running. Please note that these coins are testnet coins and not XRN.

Hashing algorithm and difficulty algorithm fork

Saronite will fork to a new algorithm on block 20000 , this new algorithm will move Saronite from being Nicehash friendly and help with better decentralization. Saronite will also implement a new difficulty algorithm provided by Zawy, LWMA Version 4. These changes will help making the block time more accurate and help the network against attacks on the blockchain. We have decided to use the same custom variant of Cryptonight Haven as all miners already supports it. After the fork block you will need to mine with algorithm cryptonight_haven. 

PLEASE NOTE THAT ALL SERVICE NODES NEEDS TO BE UPDATED TO THE LATEST BINARIES BEFORE THE FORK BLOCK. THERE WILL BE MORE THAN ENOUGH TIME AFTER WE HAVE ANNOUNCED THE FORK BLOCK HEIGHT.

Exchange

Saronite will be running polls to see if the community would like one of the following options before we decide on our next exchange listing

  1. List Saronite on an exchange that’s on CoinMarketcap (This exchange will be cheaper to list and it has lower volume, this will be achieved faster)
  2. List Saronite on a bigger exchange that’s on CoinMarketcap (This will take longer to save up for and it has much higher volumte)

 

Community Questions

In every update we will post questions from the community and answer them.

  • Q: What can the community do to help Saronite?
  • A: The community can help with social promotion (Sharing Tweets, links etc)

 

  • Q: When can we expect a new exchange for Saronite?
  • A: As mentioned above, we will give the community the opportunity to vote on what would they want to do

 

  • Q: Are you planning to host another Twitter competition because it destroyed the price?
  • A: Twitter competitions in the future will be done differently and the giveaway was bigger than what it normally would be, this was just to help Saronite slight exposure while on our road to recovery

 

  • Q: Can I run my service node on my computer
  • A: Technically yes, but it’s advised not to. A stable VPS provider will be much better.

 

Twitter Competition

The Twitter competition winners was voted for by the public, below are the winning images

First Place

first.jpg?resize=285%2C506&ssl=1

Second Place

DrHCKYOWwAASYP7.jpg?resize=640%2C534&ssl

Third Place

DqqcQJHXQAAEUe4.jpg?resize=639%2C360&ssl

 

The Swap

The blockchain swap did not go as smooth as we would have liked. We apologize to those that missed out on the swap. The following happened while swapping:

  • Some miners was mining on the old daemon and came to swap coins thus the “premine” for the swap was not enough and some people gotten more than what they should have.

This could have been avoided by taking a snapshot of the old chain, asking for viewkeys and other ways.

That wraps up the update for this week.

Special thanks to:

  • Zawy (Difficulty algorithm)
  • Cryptodude (This weeks featured update image)
  • Community managers (VultureX2, JackRyan and Serg)

 


View the full article

Snider

Masternodes.pro listing, complete website overhaul and custom Saronite algorithm – November 9th, 2018

GIFMaker.org_soo61H.gif?resize=248%2C225

 

In today’s update we will be discussing the following topics: https://MasterNodes.pro listing and the complete website redesign of Saronite.io

The Saronite team has been very busy over the past few weeks working through the process of getting listed on Masternodes.pro, completely overhauling the website and actively working on our new custom Saronite algorithm.

 

master.jpg?resize=933%2C525&ssl=1

 

 

To start, Saronite is now officially listed on MasterNodes.pro! Masternodes.pro has roughly 4.9 million views per year, 400,000 monthly and about 13,300 views per day. We believe this will drive more traffic and interest to Saronite. Which will drive more growth, more developers helping with the project and more people running service nodes. The Saronite team is also interested in getting listed on MasterNodes.online which has a comparable stats, but has a higher Alexa rank and more traffic overall. This listing will come at a later date. If you would like to check out Saronite’s MasterNodes.pro page, click here.

 

 

masterscreen.png?resize=1080%2C494&ssl=1

 

 

Next on the list, the website overhaul. Saronite’s current website is very functional and provides all of the necessary information very easily. Functionality is a key part of any website, without that the website is useless. The current site does this well. However, the visual aspect of the website is a bit rough around the edges.

 

If you have visited the site more recently, you may have noticed some smaller changes such as: the new social sidebar, our new logo animation, the primary menu system has been reworded & reworked, a new pre-loader and page transition effect. These are site wide changes that cannot be hidden while the new homepage was being redesigned. Overall, the new website should be just as functional if not more so, and be much more visually appealing. (For the full visual experience I recommend using Chrome or Opera while browsing Saronite.io)

 

homescreen.png?resize=1080%2C553&ssl=1

 

We are excited about the future of Saronite and have made significant progress over a short period of time. We will continue to put one foot steadily in front of the other, join us on this adventure.


View the full article

Snider

Creating a cronjob to auto check if service node is running.

 

 

Firstly, I would like to reiterate the importance of chosing a high quality reliable VPS provider. Running the server daemon off of a home computer, or any computer / network that is not 99.9% stable presents problems. We highly discourage you from running the server daemon on an unreliable computer – If your home computer turns off, disconnects, reboots, etc, most likely your XRN will be locked for the remainder of your staking period. (< 30 days) If you are reading this and have the server daemon on a home pc, stop right now. Go purchase a reliable VPS and redeploy the server daemon.

 

 

 

Quick Notes before starting.

My VPS is running: Linux 4.16.14-feral x86_64

Use terminal command “pwd” to determine direct path.

Use terminal command “ps x” to show running procs, to kill a process type “kill” and then it’s process ID “kill 33333”.

 Use terminal command CTRL + X to save nano files, or other information.

 

PS; Through this guide I will be replacing certain pieces of information for security purposes, typically my username for my server.

What needs to happen.

 

Here’s what needs to happen in order for this automated process:

1:) You must create a script to run screen + saronited —service-node 2:) You must create a “job” to run to check to see if “saronited” is running. “saronited” is the identifer we are going to attach to the “screen” and it will be an automated process which will run the server daemon; AKA “saronited –service-node” AKA the important part of your server 🙂

 

In this example, I am using the VPS provider FeralHosting.com – some variables may be different according to your vps host. I have had 100% uptime with FeralHosting, just saying.

PART 1 – SCRIPT CREATION

Firstly, log into your VPS and type “ls” this will print your current (typically home) directory. The name of the script we’re going to create is “saroscript” (our script we’re going to make for our autoamted cron job) in the base directory (( AKA ~/ (short key to get to your base dir is “cd ~/” ))

 

Once in a directory where you can create files, lets say your home directory, type “nano saroscript.sh” (You may be prompted to select a text editor, I use Nano)

 

Once inside your new “saroscript.sh” get ready to paste the text below. BUT FIRST, you need to correct the location to the full path. This information can be obtained by typing  from the terminal command “pwd”. My example is on Pastebin at the link below, you will have to adjust it accordingly.

Example is here: https://pastebin.com/TDmukUPr

 Once you’ve made the nesscary changes hold CTRL + X -then hit “y” to save your nano document.

 

After saving your new script, run this command in the directory where you created the script:  chmod 700 ~/saroscript.sh

 

This script is basically first a check (which is indicated by [[     ]] – It’s say “Check if “saronited” is running, if no then run the next line : screen -dmS saronited — /media/md1/YOURUSERNAMEHERE/saronite-linux-64-v1.1.1.0/saronited –service-node

 

The script above firstly runs “screen” (as you learned from the node setup guide screen creates a detached screen that will run in the background.) The script then gives the “screen” a name of “saronited” and then it calls this path /media/md1/YOURUSERNAMEHERE/saronite-linux-64-v1.1.1.0/saronited –service-node     (which if everything works, should turn on your service node)

 

Before moving forward, I would test this script by simply typing “./saroscript.sh” in the directory it’s located.  For our example the dir it will run out of it is  your home dir (~/ ) “/media/md1/YOURHOMEDIRECTORY”  – – – Assuming your service node daemon (saronited –service-node) it not already running, it should start in a detached screen.

 

If it’s already running, you will get something like

“+++ whoami
++ pgrep -fu YOURUSERNAME saronited
+ [[ -n 38333 ]]”

 

Which means the script found “saronited” (or a similar process) already running as process ID 38333.
(optional) To list all detached screens type “screen -ls”.

 

To switch to a running an already running “screen” type screen -x 36234 (<- this would be your PID number, not necessarily 36234

If you want to kill a screen process, type “ps x” then “kill yourprocessid here”. 

 

PART 2 – CRONJOB CREATION

OKAY! Now you have created the script, and you know how to move between screens and understand the context of the situation lets move to creating the cronjob.

In any area in linux, type “crontab -e
You should be presented with a window with some marked out content indicated by ### symbols. Ignore these.
Arrow down to an area with no # symbols.
Get ready to copy and paste this, but before you do, you need to adjust it accordingly.

 

Example is between dashed lines. Pastebin here: https://pastebin.com/7hM7beBP

————
*/5 * * * * /media/md1/YOURUSERNAME/saroscript.sh >/media/md1/YOURUSERNAME/saroscript.sh.cronoutput 2>&1
————

Remember what we did earlier? Correcting the direct path? We have to do that again. Remember, command “PWD” gives you the full path of your current terminal location. Also recall that I created my “saroscript.sh” in my home directory of  “media/md1/YOURUSERNAME” – – – Once everything is correct, hold CTRL + X then hit “y” to save your cronjob.

 

The above cronjob runs our “saroscript.sh” every 5 minutes. If the script detects that a process or screen is already running with the name “saronited” you will get a message like so:

“+++ whoami
++ pgrep -fu YOURUSERNAME saronited
+ [[ -n 38333 ]]”

 

If you would like to see the most recent log output of your cronjob, simply browse to the location your created your “saroscript” probably in your home dir “cd ~/”, type “ls” and you’ll see “saroscript.sh.cronoutput” – type “nano saroscript.sh.cronoutput” to see log.

 

If the server reboots, or loses power, the cronjob will automatically start within 5 minutes of the server booting up, it will check if screen / process “saronited” is running, when it detects it isn’t it will create a new screen and run the script “saroscript.sh” which will then run this command “/media/md1/YOURUSERNAMEHERE/saronite-linux-64-v1.1.1.0/saronited –service-node” which will start your service node 🙂

 

If you have questions or spotted an error in this guide feel free to ping mFridge_ on Discord.


View the full article

Snider

What is a cryptocurrency?

A cryptocurrency is a digital asset designed to work as a medium of exchange that uses strong cryptography to secure financial transactions, control the creation of additional units, and verify the transfer of assets. Cryptocurrencies are a kind of alternative currency and digital currency. -Wikipedia

CryptoNote

CryptoNote is an application layer protocol that powers several decentralized privacy-oriented digital currencies. There are quite a few cryptocurrencies making use of the CryptoNote protocol such as Monero, Bytecoin, Dash and many others. You can read more about CryptoNote by following the link > https://en.wikipedia.org/wiki/CryptoNote

What is Saronite?

Saronite is a CryptoNote cryptocurrency that enables fast and private transactions on the blockchain. Saronite is a Loki fork, and inherited Proof of Work and Service Nodes. Saronite also vouches to stay ASIC resistant (Application-specific integrated circuit) until the day comes where we can have fair mining between ASIC’s and GPU’s on an even level. Please read below about Saronite specifics.

Specifications

  • 90 Million supply
  • 120 Second block time
  • CryptoNote Cryptocurrency
  • Proof of Work (Cryptonight Heavy) and Service Nodes

Inherited from CryptoNote

  • Stealth addresses
  • RingCT
  • Anonymity
  • Untraceable Payments
  • Unlinkable transactions

The Saronite Protocol  

Saronite Proof of Work

Saronite started as a Proof of Work cryptocurrency and later inherited Service Nodes. To mine Saronite you will need mining software and a mining pool of preference. Saronite has a blocktime of 120 seconds. Please note at the time of the whitepaper, we are using normal Cryptonight Heavy for mining. This will change in the near future to a different variant algorithm based on Cryptonight Heavy.

Here is the current list of Saronite Mining Pools:


http://xrn.fairpool.xyz/

https://xiaopool.com/xrn/

https://pool.saronite.info/

https://xrn.crypto-pool.pro/#

https://www.waterparkmining.com/pools/

https://cryptoknight.cc/saronite/

https://saronite.herominers.com/

http://saronite.hashvault.pro/

http://saronite.smartcoinpool.com/

Service Nodes

Saronite inherited service nodes on the blockchain. Service nodes rewards those running a full node of the Saronite blockchain. It becomes a service node when the holder of XRN locks away a certain amount of coins for a period of 30 days. These nodes help to keep the circulating supply under control and decreases the risk of market manipulation.

For some this might just be a way to earn XRN without buying heavy mining equipment and not having to worry about the cost of electricity.

To read more about the reward of Saronite Service Nodes, please read the block reward section below.

SaroWrite

Saronite plans to create a blogging platform where an external advertising company such as Taboola (after getting approved or an alternative will be used). This will enable bloggers to earn XRN on the SaroWrite platform.

How will it work?

Once Saronite has enough bloggers, we will enable quality native advertisements on the platform. Each blogger will be rewarded every time a viewer clicks on one of the native ads on the platform. Bloggers will be paid in XRN with the equivalent of their earnings on the ad network.

The initial idea was to implement Browser mining on SaroWrite, however that might turn off some readers and some Anti-Virus programs will detect this as malware on the SaroWrite platform.

We have started contacting different ad agencies and pitched our ideas.

There will be sponsored ads and ads from a third party ad network.

The Saronite Block Rewards

Saronite uses dynamic block rewards. The block rewards of Saronite reduces over time, please see below how block rewards are rewarded.

Proof of Work (45% of block rewards)

Saronite uses a custom Cryptonight Heavy algorithm for “mining”. This is an ASIC resistant algorithm. Saronite can be mined using a CPU and GPU. 45% of the block rewards goes to miners on the network.

Service Nodes (50% of block rewards)

The Saronite Network has inherited service nodes where the community can be rewarded for running full nodes of the Saronite blockchain. This requires the holder to lock away an x sum for 30 days at a time and run a full node. 50% of the Saronite block reward goes to everyone running a Saronite service node.

Saronite Governance (5% of block rewards)

Saronite has a 5% governance. This fee is to get Saronite listed on new exchanges, marketing and paying external developers of Saronite. Currently (at time of writing this) 100% of the governance Saronite will use these funds to get listed on new exchanges and masternode platforms. You can see the Saronite Bitcoin funding address here: 142si1o7BirfvXyquCuceQAou7YG8YGMm8. You can enter this address in any of the Blockchain explorers to see what funds are being received and spent.

 

The roadmap (Whitepaper will be updated as tasks are completed)

The Saronite roadmap for Quarter 4 – 2018 will be as following in no order. 

  • MacOS GUI wallet (Completed and released)
  • Promotion of Saronite (Starting 15 November 2018)
  • Whitepaper (Version 1.1 released)
  • Service Nodes activates at Block 5000 (Activated)
  • Website rebuilding with lots of added information (Completed)
  • Recruit at least one more developer to the team (Completed)
  • Getting listed on masternodes.pro (Completed)
  • Nicehash resistant algorithm (In progress)

In Quarter 1 of 2019 we plan to complete the following:

  • Getting Saronite listed on more exchanges
  • Change to a custom Saronite algorithm
  • SaroWrite blogging platform

Quarter two of 2019 will be revealed at a later stage

  • Saronite payment modules for popular e-commerce platforms/scripts

The past and the future

The past of Saronite

Without addressing the past of Saronite, there cannot be a future. In the past there were many wrongs and only some good. We started Saronite with four developers. From the start of Saronite, only two of the developers knew each other and the other developers was recruited.

Before announcing Saronite on Bitcointalk, all of us had the discussion of what to implement on Saronite and who does what.

One of the developers gained our trust and promised the world. However, through bad judgement, the world that was promised was non-existent. We then realized it, but it was already too late as we set out everything to the community that trusted the project.

The New Saronite

The rebirth of Saronite has made us stronger in all aspects. We now have gained another developer to the Saronite team. We are currently in a discussion of adding a forth developer to the team, that is still to be seen and this section will be updated if that so happens.

The team of Saronite

Cloud

Saronite management, social media, marketing, community management, mobile development, php development, server management and not limited to all mentioned.

Community Assistance with:

  • General support
  • Service Node Support
  • Pool Support
  • Mining Support

TheArchangel

Blockchain related queries, C++ development, community management, server management and not limited to all mentioned

Community Assistance with:

  • Blockchain related issues and errors
  • Service Node Support
  • Pool support
  • Mining support

mFridge

Website and PHP related development, community management and not limited to all mentioned

Community Assistance with:

  • General Support
  • Service Node Support
  • Mining Support
  • Website Support

Links

Bitcointalk: https://bitcointalk.org/index.php?topic=4004235.0

Twitter: https://twitter.com/SaroniteNetwork/

Discord: https://discord.gg/EpxZbRE

Telegram: https://t.me/joinchat/HxNMMA8wrHzGpInxq0FwIQ

Official Website: https://saronite.io/

Blockchain Explorer: http://saronite.info/

Livecoinwatch: https://www.livecoinwatch.com/price/Saronite-XRN

We will continue to update the whitepaper as we move forward.


View the full article

Snider

In the following update we will discuss a new team member, Coinmarketcap listing and Teamspeak for the community.

We have added mFridge to the dev team, he will help with the following aspects:

  • Web development
  • Community management and support

Coinmarketcap listing

In order for Saronite to be listed on Coinmarketcap we need to be listed on at least two exchanges. Please see the exchange discussion below.

Exchange listing

Saronite will now start using the governance fee to get listed on an exchange. You can see the Saronite Bitcoin wallet here: 142si1o7BirfvXyquCuceQAou7YG8YGMm8

This funding will be used for our next exchange listing, we have contacted Mercatox and asked for specifics on listings, we will still look further depending on listing prices.

Teamspeak for the community

You can now connect to the Saronite Teamspeak, the sever link is: ts.saronite.info

Please note we will give specific times for the community and developer chat over Teamspeak, we will establish that in the next few days.


View the full article

Snider

With this update we will update you on the current state of the network and how everything is doing.

The attack on the Saronite Network

There was an attack on the Saronite network where the attacker tried to steal a lot of block rewards(and got some), This lead to the confirmation on the exchange to be increased quite massively. This was also the reason hard forked sooner and reached “Hardfork V9” that activated service nodes on the network. With the assistance of Zawy we have made the Saronite network more secure. The confirmation time on TradeOgre will soon be made smaller.

Service Nodes

Service nodes has been running since block 5000, There are now a total of 10 service nodes on the network. (Time of posting this update) In order to run your own service node it will require about 45 000 XRN. You can view the current service nodes on the network by visiting http://saronite.info/service_nodes

If you need any assistance with service nodes, feel free to visit the Saronite Discord or Telegram channels.

The next week for Saronite

During the next week, we will be working on the following

  • Getting more information on the website
  • Updating the Saronite announcement thread
  • The Saronite Whitepaper with updated roadmap

Current list of Mining Pools (Please spread hashrate to different pools)

We would like to thank all mining pool owners for keeping their Saronite pools operational.

Thanks to Cryptodude for the featured image


View the full article

Snider

Full Guide on Service Nodes

This document will tell you exactly how to set up and operate a Service Node for Saronite. This document was written with non-developers in mind, so people new to linux or command line operations should be able to follow along without any trouble.

If you feel confident around servers and the CLI, then skip to the Express Setup Guide

You can of course run the Saronite software on any operating system that you can get it to build on, but for the purposes of this document, the instructions apply to running a Service Node on a remote Ubuntu 16.04 server. If that isn’t what you want to do, syntax and server set up will of course differ according to whatever OS you choose to run your Service Node from.

Firstly, I would like to reiterate the importance of chosing a high quality reliable VPS provider. Running the server daemon off of a home computer, or any computer / network that is not 99.9% stable presents problems. We highly discourage you from running the server daemon on an unreliable computer – If your home computer turns off, disconnects, reboots, etc, most likely your XRN will be locked for the remainder of your staking period. (< 30 days) If you are reading this and have the server daemon on a home pc, stop right now. Go purchase a reliable VPS and redeploy the server daemon.

 

Summary of Saronite Service Node Requirements

Full summary of Saronite Service Node Requirements. This may change depending on Service Node functionality, so you should check here regularly, or follow our telegram/discord announcements channel.

Spec Note
Latest Binary saronite-linux64-v1.1.1.0
Software Ubuntu 16.04
Memory 30-50gb
Ram 2-4 gb

Table of Contents

  • Overview of Service Nodes
  • New User Guide
    • Step 1 Server
    • Step 2 Server Prep
    • Step 3 Download Binaries
    • Step 4 Run the Saronite Daemon
    • Step 5 Open a Saronite Wallet
    • Step 6 Register Node
    • Step 7 Check Registration
  • Express Setup Guide
  • Updating Saronite
  • Additional Functions

Overview

For now, all you need to know is that:

  • Service Nodes are full nodes on the Saronite network
  • Full nodes become Service Nodes when the owner locks the required amount of Saronite for 30 days (2 days on testnet) and submits a registration transaction
  • Once accepted by the network, the Service Node is eligible to win block rewards
  • Multiple participants can be involved in one Service Node and can have the reward automatically distributed

New User Guide

This section of this guide is for new users to servers and the CLI interface.

Step 1 – Get a Server

Righto! Let’s get started. Choosing where to set up a Service Node is the biggest choice you will make when running a Service Node. There are a number of things to consider. Because you will be locking up funds for 30 days (2 days for testnet) at a time, you will want to ensure that your server has:

  • A stable, relatively fast connection to be able to respond to ping requests to avoid being booted off the network
  • We recommend 2GB of RAM to cope with running the software reliably (Note: This requirement may be much greater once services are live). 1GB is fine for testing.
  • At Least a 20GB SSD or Hard disk drive, this will be used to store the blockchain (Note: to future proof yourself against blockchain growth and message storage we recommend a 30 – 40 GB drive)
  • A stable power supply. If your server goes down during the staking period, you may get kicked off the network, and not receive rewards while your funds are still locked for the remainder of the staking period.

For most users, we assume that your home internet connection is relatively slow (< 4MB/s down and up) and probably lacks support for external connections. If this is the case, you will probably not want to run a Service Node from your home in the long term, as this could cost you if and when you get booted off. Since we’re just testing at the moment, you could run it from home anyway, but for this guide we’ll avoid it.

Typically, the easiest and cheapest way to host a server outside of your home is to use a Virtual Private Server (VPS). There are thousands of options when it comes to VPS providers, but for now, just about any one will do. In the future, selection will be made more difficult because most providers will not allow exit node traffic, so we have compiled a list of exit node friendly providers to choose from if you want to stay with your provider for more than a few months.

Hosting Provider Product Name Cost Per Month $USD Bandwidth Provided Exit Friendliness Rating
Netcup VPS 1000 G8 10.50 30 – 35 MiB’s 5 / 10
Online.net Start-2-S-SSD 13.99 15 – 17 MiB’s 9 / 10
Scaleway START1-M 9.33 20 – 25 MiB’s 7 / 10
OVH VPS SSD 2 7.61 10 – 15 MiB’s 9 / 10
Leaseweb Virtual Server XL 34.45 30 – 35 MiB’s 5 / 10
Digital Ocean 2 GB, 2 vCPUs 15 9 – 11 MiB’s 8 / 10
Feral Hosting Neon Capability 19.68 9 – 11 MiB’s 9 / 10
Trabia VDS-8G 38.54 9 – 11 MiB’s 8 / 10
Hetzner EX41-SSD (30 TB) 39.71 80 – 40 MiB’s 4 / 10

Try not to pick the first one off the list. Do some digging and see which one looks the best to you, what your budget is, and what the latency is like for you based on the server location that you choose.

When selecting your VPS’ operating system, choose Ubuntu 16.04 64 bit or Ubuntu 18.04 64 bit if you want to follow this guide. If you feel more confident or wish to run your server on another distribution or operating system, the Saronite commands in this guide will still apply.

Step 2 – Prepare your Server

Every provider has a slightly different way of issuing you access to your new VPS. Most will send an email with the IP address, root username, and a root password of the VPS.

To access your server, you will need a SSH client for your operating system. Because we’re on Windows today, we’ll download PuTTY, Mac users can also use PuTTY. If you’re a Linux user, you probably don’t want us telling you where to get a SSH client from.

To connect to our VPS we will need to paste the IP address into the SSH client’s “Host Name (or IP address)” input box and click the “Open” button. The Port number can usually just be left as 22.

68747470733a2f2f6c68352e676f6f676c657573

A terminal window will now appear prompting for your log-in details, username(root) and password, which were provided by your VPS provider. When entering your password, nothing will visually appear in the terminal. This is normal. Hit enter when it’s typed or pasted, and you should be logged in to your VPS.

Hot Tips for using the Console

Consoles don’t work like the rest of your computer. Here are some basic tips for navigating your way around the command line!

  • Don’t try copying something by using the usual Ctrl + C hotkey! If you want to copy something, do so by highlighting text and then right clicking it. Pasting works by right clicking a blank area in the console.
  • If you want to kill a process or stop something from running, press Ctrl + C. This is why you shouldn’t try copying something with this hotkey 😉
  • You can always check the directory you are in and its contents by typing ls
  • You can always return to your home directory by typing cd ~
  • You can move into a given directory by typing cd <name> or move back up one level by typing cd ..
  • PuTTY allows you to easily duplicate or restart a session by right clicking the top of the window. Handy if you’re trying to do a few things at once.

Once we have logged in correctly to the VPS for the first time, the terminal may prompt us for a new password for our root account. The terminal will require you to enter the new password twice before we can start running commands.

Optional – Set up Non-root User

Best practice when running a public server is to not run your software as the root user. Although it is optional, we will create a non-root user to our VPS by running the following command.

sudo adduser <username>

Replacing <username> with a name you will log-in with. For this user-guide we will use snode as our username.

sudo adduser snode

The terminal will prompt you for a new password for our newly created user. Use a different password to the root password.

Once the password has been set, the terminal will prompt for a few details about the individual running the user. You can hit enter through each of the inputs as the details are not important for the purposes of running a Service Node.

Once that’s done, run the following two commands to give our new account admin privileges and to change to such account.

sudo usermod -aG sudo snode

su - snode

Before we proceed further, it is advised to close your terminal and reopen PuTTY to set up a saved session with our snode user. Your SSH client will have a load and save session function. For PuTTY we will need to type in our VPS IP address again, on the same screen type snode under “Saved Session”. Click on “Data” under the drop-down menu “Connection”, and type in snode (or your username defined before) into the input box “Auto-login username”. Go back to your session screen, where we entered the IP address, and click “Save”. You can load this session whenever you want to check on your Service Node.

Server Preparation Continued

We should update our package lists, the below command downloads the package lists from the repositories and “updates” them to get information on the newest versions of packages and their dependencies. It will do this for all repositories and PPAs.

sudo apt-get update

You will notice a bunch of package lists were downloaded, once this is complete run the below command to fetch new versions of any packages we currently have installed on the system.

sudo apt-get upgrade

You will be prompted to authorise the use of disk space, type y and enter to authorise.

If you are prompted at any time that a version of any file is available then click the up and down arrows until you are hovering over install the package maintainer’s version and click enter.

Alright, good to go. Our server is now set up, up to date, and is not running in root. On to the fun part!

Step 3 – Download the Saronite Binaries

First download the Linux binaries by running the following command:

wget https://github.com/Saronite/saronite-protocol/releases/download/v1.1.1.0/saronite-linux64-v1.1.1.0.tar.bz2

NOTE: If this link no longer works, or you need Windows or Mac versions, check https://github.com/Saronite/saronite-protocol/releases to find links to the latest releases.

If wget is not installed you may need to run sudo apt-get install wget

To get to the binaries, we need to unzip them.

tar xvf saronite-linux64-v1.1.1.0.tar.bz2

You should see 8 files unzipped:

  • saronite-blockchain-export
  • saronite-wallet-cli
  • saronite-blockchain-usage
  • saronited
  • saronite-blockchain-blackball
  • saronite-wallet-rpc
  • saronite-blockchain-import
  • saronite-gen-trusted-multisig

Check they are unzipped by running:

ls

If not, sometimes unzip will dump the binaries in a folder. In our case the folder would be called saronite-linux64-v1.1.1.0, so to get into it we can type:

cd saronite-linux64-v1.1.1.0

To check that they are in that folder, once again, type:

ls

Excellent! We now have all of the necessary files to get this show on the road!

Step 4 – Run the Service Node Daemon

Let’s start up the daemon so we can sync the blockchain and register our Service Node.

The problem with the terminal we currently have open is that once we close PuTTY the program running inside it will also shut down. We can run a program called screen which can keep our Service Node running for 30 days without having to look at it all the time.

The screen command is generally included in Ubuntu by default. If it isn’t, run sudo apt install screen. Running it opens up a terminal shell inside your session that will continue to run in the background once you detach it from the session. Type the following command:

screen

Enter through the information that the terminal shell is providing until we get back a blank screen awaiting an input.

To begin the Service Node daemon we must launch saronited with the flag --service-node.

./saronited --service-node

If you are testing the daemon on testnet run the following command ./saronited --service-node --testnet

The daemon will now start syncing. You won’t be able to do much if it hasn’t synced.

To have the daemon to continue to run in the background hold Ctrl and type ad. To test your screen is still running in the background run the command screen -ls and take note of the port number at the start of the screen. This number will help us re-enter the daemon at future times. Typing screen -x <port number> will reattach the session so we can see what’s going on inside. Hold CTRL and type “ad” again to detach the screen once more.

For now, we can just leave the session open to see the daemon messages while we set up the Service Node. Just don’t forget to use CTRL + A + D to detach the session before you close PuTTY later on.

Step 5 – Get/Open A Wallet

While we wait for the daemon to sync, we can now get a wallet going.

*** You do not have to run this wallet on the server and you should not! Download the software and run it from elsewhere for security reasons! ***

You can run the CLI wallet (Command Line Interface wallet) on any other computer, including your home computer to avoid leaving your wallet on the server.

However, if you do want to run the CLI wallet on another computer, you will either need to run another daemon on that local machine or use a remote node (node1.saronite.info:33333, for example). When you run ‘saronite-wallet-cli’ locally and wish to use a remote daemon, use the syntax:

./saronite-wallet-cli --daemon-address <insert address here>

Or on windows:

saronite-wallet-cli.exe --daemon-address <insert address here>

If you are made of money and are willing to take the small risk of losing all of your funds, you can continue running the wallet inside the Service Node VPS. So we don’t have to talk about a myriad of other operating systems or potential user cases, the rest of this guide will assume you are running the wallet in the same VPS.

As such, it’ll probably save us time to open a second PuTTY session. You can do this by right clicking the window of the current PuTTY session and clicking “Duplicate Session.”

Log in to your non-root user that we set up before, in our case snode, and once in we should open a new screen by typing screen and hitting return twice.

Change directory to where our binaries are saved:

cd saronite-linux64-v1.1.1.0

Then to launch the wallet run the command:

./saronite-wallet-cli

If you are on testnet run the command with the –testnet flag: ./saronite-wallet-cli --testnet

When saronite-wallet-cli first runs, it will request for you to specify a wallet name. Assuming we haven’t created one yet, we will use the e.g. name MyWallet

Because this is the first time we have used the name MyWallet the client will prompt us to create a new wallet. Type y and click return to continue.

The saronite-wallet-cli has generated us a wallet called MyWallet and is now prompting us for a password.

Note:

  • When typing the password, the characters will not appear. It will seem as if you are typing and no text is appearing however the terminal is logging every character you type including if it is capitalised or lowercase.
  • Write down your wallet name and password on a piece of paper as this information will be required every time we want to enter our wallet.
  • Use a password with uppercase letters, lowercase letters, numbers, symbols and make the password at least 9 characters long.

Once we have chosen our password for the wallet we must choose our language. For the purposes of this user guide I suggest you use English by typing in 1 and clicking return.

The CLI will generate and spit out several lines of text. The first two lines of text show your wallet public address. This address can be shared, will be used to receive Saronite to your wallet, and will be used during the preparation and registration of our Service Node. All Mainnet Saronite public addresses start with an L and are followed with a string of characters, Testnet Public addresses start with a T. The public address shown will be your primary address, however multiple public addresses can be generated from this primary address.

Line 13 to 17 show your 25-word mnemonic (“new-monic”) seed. The seed is used to easily backup and restore your wallet without needing any other information. At this stage, grab a pen and paper, and write down your 25 words in order. Store the piece of paper in a safe and secure place, if your words are stored in a text file on your computer or stored online, you increase your risk of someone else getting control of your wallet.

It is at this point that we should get some Saronite in the wallet. The amount of Saronite required to run a node is 45 000 XRN.

If you are staking please do not use Subaddresses. They are currently unsupported by the Saronite wallet

We will need our address to register our Service Node later, to get your primary address type the following command:

address

Highlight the string of characters that were outputted and save this in a notepad for later use, your public address should look similar to:

PAoiZQ43qG18FzKq7WhEbk3gfNNiemGsd7REdSQaFv4RdB8E97RxP8WFLRR2xHQStiSM61EFEicXU3EEPj7GEHdz8WHUrWRkbGeQ1r8ro8

NOTE: Do not use CTRL + C to copy your address, it will close the wallet down. Simply highlight the address and this will automatically save the portion you highlighted into your clipboard.

Once you have enough Saronite in this wallet, just leave it open, we’ll come back to it in a minute.

Step 6 – Service Node Registration

The next part of the guide will split into two sections:

  • If you are an individual staker and do not require any other contributors to run your Service Node jump into 6.1 – individual Staking.
  • If you want to run a pooled Service Node or contribute towards a pool jump into 6.2 – Pool Staking

6.1 – Individual Staking

If you want to run the Service Node as an individual you will require the following things.

  • A Saronite daemon running with --service-node flag (see step 4).
  • saronite-wallet-cli primary address with enough Saronite in your account to meet the Service Node Staking Requirement (see step 5).

Now if we have the two above items we can proceed to our daemon to register our Service Node.

Type screen -ls to get a list of the screens running. Your daemon will normally be the bottom one on the list. To enter our daemon run the following command, replacing <port number> with the number that corresponds with your daemon.

screen -x <port number>

To start the registration process we are going to run the following interactive command within the daemon terminal:

prepare_registration

The daemon will output the current staking requirement and prompt you with an input to clarify if you are an individual staker or you will be running a pool. Type y and click enter as we will be the sole staker.

The daemon will now prompt us for the Saronite address of the operator. If you followed step 5 you should have this address saved in a notepad, if not run through step 5 again to find your Saronite Address. Once we have the Saronite Address copied to our clipboard we can then right click the terminal screen to paste the address. Double check the address matches the one of your wallet then click enter if it is the same.

The daemon will now ask if you wish to enable automatic re-staking. Type y and click enter if you would like to have your Service Node re-stake automatically for you at the end of every 30 days. Type n if you would like to re-stake manually.

The daemon will now ask for a final confirmation, if you agree to the information provided type y and click enter.

The daemon will output a command for us to run looking similar to:

register_service_node 4294967292 T6TCCyDgjjbddtzwNGryRJ5HntgGYvqZTagBb2mtHhn7WWz7i5JDeqhFiHqu7ret56411ZJS7Thfeis718bVteBZ2UA6Y7G2d 4294967292 100.000000000 1535677391 ec3895ea70a4a91b5ec4b5e1df96a45e07046f1fb0123c754d98fb2d70f4529d 5bb35d7b8ab1acb943bc47913ada8f9d2e6d6e22264e57484a04c1bbfd461f0ee2e5435454cd9b7059b221eb506ce9ea4537ddd9faf1f1757e0ef611a41c0609

Copy the whole line of text and paste it into your notepad as we will need to run this command in our saronite-wallet-cli. if registering multiple nodes, please wait at least 10 blocks between Service Nodes before running the register Service Node command in the wallet

You have 2 weeks from the moment of registering the Service Node to run the register_service_node command, however it is advised to do it as soon as possible.

We do not require our daemon terminal anymore, however we do need to daemon to be running. Hold CTRL and type ad to detach the screen.

Run through step 5 once more to open our Saronite wallet. Once we are in our wallet run the command the daemon outputted for us when we prepared our Service Node.

Alternatively, you can also include the auto command, this will create a wallet which runs as a background process and automatically signs a register transaction each 30 days, so the contributor need not sign a new transaction manually each registration period.

register_service_node auto args.....

If you run the auto command the wallet will close pushing the process into the background. See additional information at the end of this guide to learn how to stop the auto command.

The wallet will prompt us to confirm our password, then the amount of Saronite to stake. Confirm this by typing y and clicking enter. Well done! Let’s continue to the next step “Step 7 – Service Node Check” to check if our Service Node is running.


6.2 – Pool Staking

Service Nodes can be split between multiple parties. At a minimum, the operator must stake at least 25% of the total required amount. The operator can also reserve contribution slots for specific addresses to prevent random users from adding to the pool.

In any given pool, there will be at most 4 contributors including the operator. After the operator, each new participant must also contribute 25% of the minimum, except the last one. So for example, valid splits might be:

Operator Contributor 1 Contributor 2 Contributor 3
25% 25% 40% 10%
65% 25% 10%
90% 10%
99% 1%

Depending on the individual and their circumstance they will need to:

  • Jump into section “6.2.1 – Operator” if they are running the daemon and hosting the pool;
  • Jump into section “6.2.2 – Pool Contributor” if they are contributing to someone’s Service Node.

NOTE: It is advised to read both sections of “6.2 – Pool Staking” to have a better understanding of the process.


6.2.1 – Operator

The Operator is the individual who will be hosting the pool and running the Service Node daemon, thus incurring the operating expenses encompassed by running a node.

The Operator will need to have:

  • A Saronite daemon running with --service-node flag (see step 4) at all times.
  • saronite-wallet-cli primary address with enough Saronite in their account to meet 25% of the Staking Requirement.
  • 1-3 other contributors who also have a saronite-wallet-cli with enough Saronite in their accounts to meet 25% of the staking requirement.
  • The address and contribution amounts the 1-3 contributors will stake.

NOTE: The other contributors addresses are optional to have as you can create your pool to be open to anyone to contribute to, however they are recommended to have to avoid any issues of other individuals stealing their spots.

Now if we have the three/four above items we can proceed to our daemon to register our Service Node.

Type screen -ls to get a list of the screens running. Your daemon will normally be the bottom one on the list. To enter our daemon run the following command, replacing <port number> with the number that corresponds with your daemon:

screen -x <port number>

To start the registration process we are going to run the following interactive command within the daemon terminal:

prepare_registration

The terminal will prompt the operator to specify if they will contribute the entire stake, because we are running this as a pooled Service Node we will type n and click enter.

Next the terminal will request the input for the operator cut. This value is between 0-100 and represents the percentage of the reward the operator will receive before the reward is distributor to the share holders. If you have agreed to a 10% operator cut with the other contributors you would type 10 and click return.

The terminal will now display the minimum reserve the operator can contribute and request the operator to input the amount in Saronite they wish to contribute. Type your desired <operator contribution> and click return.

Once we have set the operators desired stake amount we have the option to either leave the pool open for anyone to contribute or lock a reserve for individuals that have agreed with us to stake within our Service Node.


Reserved Pool

If the operator wishes to have their pool closed they should type y and click continue.

The terminal will now prompt the operator for the number of additional contributors they have organised to be apart of this Service Node. They must type in the number of contributors, not including themselves, and click return.

The daemon will now prompt us for the Saronite address of the operator. If you followed step 5 you should have this address saved in a notepad, if not run through step 5 again to find your address. Once we have the Saronite Address copied to our clipboard we can then right click the terminal screen to paste the address then click return to confirm your address.

Next the operator must input each of the contributors amount of Saronite they will stake and each contributors address.

The daemon will now ask if you wish to enable automatic re-staking. Type y and hit return if you would like to have your Service Node re-stake automatically at the end of every 30 days. Type n if you would like to re-stake manually.

You will now be asked to confirm the information above is correct.


Open Pool

If the operator wishes to leave their pool open they should type n and click continue. The terminal will prompt the operator to input their address. Once the address has been inputted the terminal will display the remaining portion that needs to be contributed by others. If you agree click y and hit return.


The daemon will display a summary of the information we entered. This is our chance for a final check over to make sure we entered in the right information. If you confirm the information is correct type y and click return.

The daemon will output a command for us to run within our wallet, looking similar to:

register_service_node 214748364 T6UCEoWvJHCJq5biK3LMQZ4CRXAaqiPda2kCRRYYYEMFfxYoqnUo7Nx88RL3wmENwN4kfjDSp2jMN1g6PSErKrSu2EEp8UMy5 1073741823 T6TCCyDgjjbddtzwNGryRJ5HntgGYvqZTagBb2mtHhn7WWz7i5JDeqhFiHqu7ret56411ZJS7Thfeis718bVteBZ2UA6Y7G2d 3221225469 25.000000000 1535692249 5dac247e90ced2dcd9e51faec8792acb0c11b4c700640d9104b17c868ea167e3 cc11eef804c11d3e93cf8c488c10d97b8cec9ee2b38e6666ff07749c2911aa06ce310edc926a4d2f50a588e9c15afcc20e935a0f188aa7caa764a62058dec80d

NOTE: You must run the command outputed in your daemon and not the command shown above.

Copy the whole line of text in your daemon and paste it into your notepad as we will need to run this command in our saronite-wallet-cli.

You have 2 weeks from the moment of registering the Service Node to run the register_service_node command, however it is advised to do it as soon as possible.

Before we leave the daemon run the following command to get our <Service Node Public Key> and save it in your notepad:

print_sn_key

Run through step 5 once more to open our Saronite wallet. Once we are in our wallet run the command the daemon outputted for us when we prepared our Service Node. The wallet will prompt us to confirm our password, then the amount of Saronite to stake. Confirm this by typing y and clicking enter.

Alternatively, the operator can also include the auto command, when staking this will create a wallet which runs as a background process and automatically signs a register transaction each 30 days, so the contributor need not sign a new transaction manually each registration period.

register_service_node auto args.....

If you run the auto command the wallet will close pushing the process into the background. See additional information at the end of this guide to learn how to stop the auto command.

We must now send the <Service Node Public Key> to our contributors with the amount of Saronite they are required to stake.

At this point the we will need to wait until all contributors have staked before rewards will be received.


6.2.2 – Pool Contributor

The pool contributor must first receive the Service Node Pubkey and the requirements (amount of Saronite to send) from the Service Node Operator.

If you are staking please do not use Subaddresses. They are currently unsupported by the Saronite wallet

The pool contributor must have downloaded the necessary binaries, is running a daemon or is connected to a remote node, has generated a wallet through the saronite-wallet-cli, and has enough Saronite to stake. They can then run the following command in their saronite-wallet-cli .

stake <Service Node Pubkey> <address> <contribution amount>

Where the <Service Node Pubkey> is the Pubkey provided from the Service Node operator, the <address> the service node operator will likely reserve an address for which they want you to stake for, this will usually be the same address as the wallet you are planning to stake from, in the case of an open pool this will always be the address you will you stake from and you will also receive rewards here too. <contribution amount> is the amount of Saronite they are going to stake which they agreed to with the Service Node Operator.

The Pool Contributor can also include the auto command, when staking this will create a wallet which runs as a background process and automatically signs a register transaction each 30 days, so the contributor need not sign a new transaction manually each registration period.

stake auto <Service Node Pubkey> <address> <contribution amount>

If you run the auto command the wallet will close pushing the process into the background. See additional information at the end of this guide to learn how to stop autostaking.

The auto command does not work with a multsig wallet as there is a requirement for the party who is staking to have the transaction signed by another signer. Thus is it advised if you are using a multisig wallet to maintain the staking once a month when the funds are unlocked.

At this stage you will need to wait for the other contributors to provide their collateral. Once everyone has staked you can refer to “Step 7 – Service Node Check” to see where your Service Node Operator’s node is in the list.

Congratulations, you are now staking.

Step 7 – Service Node Check

After we have locked your collateral we will need to check if our Service Node Pubkey is sitting in the list with the other Service Node’s on the network. This will prove our Service Node is running, recognised and will receive a reward if it keeps running.

Let’s go into our daemon screen by typing screen -x <port number>. To find the port number use screen -ls and your daemon should be sitting at the bottom of the list.

Once we are in the daemon again we can run the following command to see our Service Node Public Key:

print_sn_key

The Service Node Public Key is used to identify our Service Node within the list of Service Nodes currently on the network.

You can jump onto https://saronite.info/ to see if your Service Node is in the list or we can continue in the terminal to output the same information.

We will want to know the current block height, type status into the daemon and it will output this information. Once we have the block height we can then check the current Service Nodes on the network at our specified block height.

Run the command print_quorum_state <block height> replacing <block height> with the number minus 1 that was outputted when running status command.

If your <Service Node Pubkey> is sitting in the list you know you are now staking.

Additional Functions

Creating a cronjob to auto check if service node is running.

Autostaking – Checking/stopping autostake command

To check the processes running in the background, run the command:

top -u <username>

Under the COMMAND column we should see a process called saronite-wallet-cli. If you do not see this process you are either looking at the wrong <username> or your autostake command is not running.

If you want to stop the autostake then run the following command while logged on to the specific <username> which has saronite-wallet-cli running in the background:

pkill saronite-wallet-cli

Running Autostake on startup

If the host machine your VPS is running on shuts down or restarts unexpectedly then so to will your your autostaking wallet, you can use the following command to start the autostaking wallet again, you can also include these commands in your startup scripts, ensuring if your node goes down it automatically restarts the wallet process.

saronite-wallet-cli --testnet --wallet-file <PATH TO WALLET FILE> --password <WALLET PASSWORD> set ask-password 0

register_service_node auto ...

Running this command if you have already staked will not stake over the top of an already staked node

Express Setup Guide

This section is for power users who are more familiar with servers and the CLI interface. There’s a couple of things your going to want to do before you commence.

1. Get a Server that meets requirements 2. Run the Daemon on a server from a non-root user account, then stake from a local wallet (or a wallet on a separate server).

where <VERSION> is mentioned replace with the latest version, example 1.0.3

3. Connect via SSH to your server 4. add new user

sudo adduser snode

<enter>

Y

exit

5. login to your new user account via SSH

snode@<ipaddress>

6. Update necessary security patches and system utilities

sudo apt-get update

sudo apt-get upgrade

7. Download & unzip Saronite

wget https://github.com/Saronite/saronite-protocol/releases/download/v1.1.1.0/saronite-linux64-v1.1.1.0.tar.bz2 

sudo apt-get install unzip

unzip saronite-linux-x64-<VERSION>.zip

8. Run Saronite in a screen and Detach

Screen <enter>

cd saronite-linux-x64-<VERSION>

./saronited --service-node

Ctrl +AD

Wait for the Saronite Daemon sync the blockchain (1 – 8 Hours depending on internet speed)

9. Open a Wallet

This wallet can be in a screen on the Service Node machine, or a wallet on your local computer (assuming you have downloaded the binaries).

cd saronite-linux-x64-<VERSION>

Linux/MAC – ./saronite-wallet-cli Windows – saronite-wallet-cli

Enter Name: Name your wallet

Enter password

Language: 1 (for English)

Securely store:

  1. Address
  2. Seed Phrase
  3. Pass-phrase

Send enough Saronite to fund a node, wait for Balance to be unlocked (20 mins, 10 confirmations)

10. Register your Service Node

On your Service Node reattach to the screen which has the Service Node running.

screen -r

prepare_registration

Contribute entire Stake: Y/N

Enter Saronite Address

Enable Restaking: Y/N

Confirm: Y

Copy green registration message

Ctrl +AD

11. Reattach to Service Node or local wallet

Paste in registration message <enter>

12 Attach Back to Service Node Daemon

screen -r

print_sn_key

Copy service node key, and search for it on: http://saronite.info/

CTRL +AD

ctrl +ad detaches screen and runs your Saronite Service Node in background this is critical

Updating Saronite

To update your Saronitei node the process is:

  1. Find the latest update binary latest version, example 1.0.3
  2. Connect to your server via SSH
  3. Attach to the screen running the Saronite Daemon screen -ls to view current screens screen -x <process> to attach to the screen running the Daemon
  4. Exit the Daemon, and return to home directory exit cd ..
  5. Run an update on your machine (Linux based systems) sudo apt-get update sudo apt-get upgrade
  6. Download and unzip the latest Binary
  7. Start the new Daemon cd saronite-linux-x64-<VERSION> Linux/MAC – ./saronited --service-node Windows – saronited --service-node
  8. Find and search for Saronite Public Address print_sn_key Search: http://saronite.info/
  9. Detach screen and logout CTRL +AD exit

Conclusion

Well done! You will receive a block reward when your Service Node has been active for some time and the network chooses you within the list.

 

This guide was forked from the the Loki repository, we had to do an emergency hard fork and ran out of time to complete the Saronite documentation


View the full article

Snider

The first question many might have, what is a service node?

A service node is basically the same as running a full node of the Saronite blockchain. It becomes a service node when you lock away your XRN for 30 days. Once your service node is accepted by the network, you will gain rewards from it. Saronite will split the block rewards and 50% of the block reward will be given to those running a Saronite service node.

How can I have my own service node?

To run your own service node, you will require 45 000 XRN (More or less) and your own virtual private server. In the service node documents, it will guide you through running your own service node.

Your service node will be able to run on a VPS with good internet connection, 2GB of ram and at least 20 Gigabyte of hard drive space.

The next documentation to be released is the installation of your service node.

Service Node Activation (More or less)

Day(s)

:

Hour(s)

:

Minute(s)

:

Second(s)


View the full article

Snider

Service Node Update

Saronite will move the activation of Service Nodes to an earlier date, please see the countdown below. Please note that the count down timer is more or less. Documentation will be ready 4 days before the activation of Service Nodes.

 

Service node activation (More or less)

Day(s)

:

Hour(s)

:

Minute(s)

:

Second(s)

The Saronite Service Node documentation will be ready in:

Day(s)

:

Hour(s)

:

Minute(s)

:

Second(s)

Mandatory Update

We have added a different fork height to activate, and therefor you will have to download the latest releases of wallets.

Windows GUI

Windows CLI

Linux GUI

Linux CLI

Mac GUI

Mac CLI

 

Old Saronite Blockchain

The old Saronite Blockchain will be stopped soon, most of the swaps are completed. And we can now focus on the new and one and only Saronite blockchain. The remaining coins will be used for promotion of the new and improved Saronite. The last few swaps are now under way. (People that have contacted and(or) sent their old coins already)

 

Twitter Contest

The twitter contest will still run for another 9 days, and voting is under the way on our Discord channel.

MASSIVE #GIVEAWAY! We will be giving away 45 000 $XRN! 3 random Winners! How do I enter? Post an image of yourself doing something with Saronite in the comment, Follow Saronite Twitter and Retweet this Tweet! Use #SaroniteIRL in your post! #Altcoin #Saronite #BTC #XRN pic.twitter.com/K8rSD8GTeZ

— Saronite (@SaroniteNetwork) October 21, 2018

Please read the Tweet details to enter correctly to enter.

 

SaroWrite Network

Saronite will launch SaroWrite, a place where bloggers can earn through their content views. This platform will go live by the end of 2018. This is a platform where bloggers can earn $XRN for their blog posts.

 

To Always be updated first, Join the Saronite Discord and/or Telegram.


View the full article

Snider

The Saronite roadmap for 2018 will be as following in no order. 

  • Bulletproofs implementation
  • Android wallet
  • MacOS GUI wallet (Completed and released)
  • Promotion of Saronite
  • Whitepaper (In progress)
  • Service Nodes activates at Block 23100 (Activated)
  • Website rebuilding with lots of added information (In progress)
  • Recruit at least one more developer to the team

In Quarter 1 of 2019 we plan to complete the following:

  • Getting Saronite listed on more exchanges
  • Change to a custom Saronite algorithm

Quarter two of 2019 will be revealed at a later stage

  • Saronite payment modules for popular e-commerce platforms/scripts
  • Saronite blogging platform for bloggers to earn, <proof of content>

This roadmap will be updated as we work on our objectives. More features to be added.

 


View the full article

Snider

Saronite will implement Service Nodes at block 23100

A service node acts as a full node on the Saronite network. It becomes a service node when the holder of XRN locks their coins away for 30 days and registers it to the network. Once the network accepts this lock, your service node will gain from the network rewards. A pool of four participants can be created to form a Saronite Service Node.

Questions received so far:

How much will a service node cost to start? 45 000 XRN (more or less)

How much of the block reward goes to service nodes? 50% of the block rewards

Can me and a friend split the cost for a service node? Yes, service nodes can have four participants

How to run my own service node? There will be more documentation available closer to the launch of Saronite Service nodes. You will require at least a virtual private server and 45 000 XRN.

SERVICE NODE DOCUMENTATION

Day(s)

:

Hour(s)

:

Minute(s)

:

Second(s)

SERVICE NODE ACTIVATION V9 Hardfork (More or less)

Day(s)

:

Hour(s)

:

Minute(s)

:

Second(s)


View the full article

Snider

The road ahead!

In this post we will discuss the road ahead, block rewards, service nodes and questions from the community.

The road ahead

The road ahead will be long and challenging, but as long as we have our community behind us we will be more than capable.

  • Saronite will recruit more developers (contact us and tell us what you can contribute to the team)
  • Mass promotion starting soon

Block Rewards

Saronite is now on a new blockchain and everything has changed slightly. The block rewards are much higher than usual, this is because of three reasons.

  • Saronite block time is now 120 seconds (was 60 seconds)
  • The blockchain is brand new and will take time to adjust
  • The implementation of service nodes will reduce the block reward for miners by half

Service Nodes

Saronite will implement service nodes on the blockchain, this will enable our community to register their own service node and get rewarded from it every block. Below is a few key factors you need to know

  • A Saronite service node will require you to have 45000 XRN (more or less) in your node
  • Service node`s cost can be shared by up to 4 individuals
  • 50% of the block reward will go to everyone running a node
  • The Saronite service nodes can be hosted on a VPS

MASSIVE PROMO COMPETITION

Saronite-promo.png?resize=971%2C587&ssl=

Link to Tweet

Questions

I still have old Saronite, how do I swap? You can contact Cloud on DiscordTelegram or on Twitter

What happened to my coins on TradeOgre? The exchange swapped it out automatically

When will service nodes start? It will start when the network reaches 23100

 


View the full article

Snider

Blockchain Swap

Saronite will move to a new blockchain on the 22nd of October 2018. 

Why would we do that?

  • The Saronite blockchain currently runs on Sumokoin code
  • We are moving Saronite to Monero code base
  • To undo wrongs in the past
  • Implementation of service nodes

Even though the code will be completely different and be  a complete new currency, everything will be exactly the same. Please take a few moments to read how this will be done.

Firstly, a new genesis block will be created, the current coins in existence will be mined on the first block. Everyone in the Saronite community will have a fair chance to exchange their existing Saronite coins to the new Saronite coins. We already notified TradeOgre of the swap and all the funds on TradeOgre will be safe and be swapped within the exchange. After the new blockchain goes live, we will announce that you can now swap your coins around, this can only be done via, Twitter, Telegram, Discord or the website with the assistance of Cloud. You will then send your old Saronite and receive your new Saronite currency. Because nothing changes and only the coins in existence will be mined the coin will be exchanged 1:1.

After announcing, everyone will still have 1 week to exchange their existing Saronite to the new Saronite. If any coins goes unclaimed during this 1 week, it will be given away to the community with Twitter promotions

What happens to the dev fee that was already mined in the past?

The development fee that was mined in the past will be given away in 4 separate Twitter promotions of the new Saronite. This will be done transparently.

I would like to swap my coins, how do I start? 

 

SWAPPING START

Day(s)

:

Hour(s)

:

Minute(s)

:

Second(s)


View the full article

Snider

How to mine Saronite

Saronite is a Proof of Work currency and can be mined, the only things you will need is a mining pool of your choice and mining software to get started.

Saronite Mining Pools

Once you have your choice of mining pool, you will need software to mine. There are various of software types to mine, some of them are better than others, but it’s your choice at the end.

There are others, however the ones mentioned above are the most popular

On the pool getting started page, you will be able to see the pool address and port you should mine to. Please note that each pool is different.

For example: mine.xrn.fairpool.xyz:5599

Your mining software will ask you to enter the pool address and port like the example given above.


View the full article

Snider

The return of Saronite

It’s been a while; a lot has changed and the blockchain never dies. Saronite will be making a return into the cryptospace and it’s here to stay! Please take a few minutes to read through what happened and how we will move Saronite forward.

How did Saronite start?

Saronite started with one developer, that had ideas and ambitions for a great privacy cryptocurrency. Even though there were so many ideas, one developer was just not going to be enough. Three other developers were recruited and another one at a later stage. While Saronite started to look good and one of our developers were giving feedback on his work, the ambitions were on an ultimate high, just to find out that we had a developer with no real knowledge and a bunch of false promises. Whilst all this was happening, the overall management was dysfunctional and the community was not being kept up to date.

What went wrong?

  • Bad management (emission & supply confusion)
  • Network attacks that lead to network splits (These were dealt with quite well)
  • Bad judgement with recruiting
  • Too much negativity that wasn’t helping in any way.

Positives of Saronite in the past

  • First currency to change from camel to linear emission
  • Great community building
  • Fast at solving blockchain attacks

Moving Saronite forward

While we know it will take a lot to move Saronite forward, it’s a task that is certainly possible. We are going to take it slow and steady, we aim to have the products out on the day we have stated, actions will speak louder than words and in time we hope our actions will cement the future of Saronite and what it can be in the future. There will be no premine in the future of Saronite, the governance fee is still in tact.

Going forward, what will Saronite be?

Saronite aims be a leading CryptoNote cryptocurrency, while we will be recruiting more developers, we also plan on implementing the following on the Saronite blockchain in the near future

  • Changing our code to be Monero based (Monero code are much more stable than the current code, as well in front with implementations of bulletproofs)
  • Implement service nodes on the Saronite blockchain (Mining rewards will be reduced when nodes are implemented, this is to reward everyone running a Saronite node. A minimum of +-11000 XRN will be required to run your node)

The wallet was changed and fixes were implemented to resume the trading on TradeOgre.

 


View the full article

Sign in to follow this  
  • HashVault Stats

    • Global Hashrate
      61.42 MH
    • Avg Hashrate
      21.42 KH
    • Total Miners
      2,867
    • Miners Paid
      63,036
    • Total Payments
      945,448
    • Total Hashes
      1.89 PH
    • Blocks Found
      340,139
×