Jump to content

Saronite

Sign in to follow this  
  • entries
    24
  • comments
    0
  • views
    3325

The last Update of 2018

Sign in to follow this  
Snider

1599 views

Greetings SaroKnight’s!

In this update we will discuss the following:

  • Upcoming fork
  • CoinMarketCap listing
  • SaroWrite
  • 2019 Goals

The upcoming fork will feature the following:

  • Activated bulletproofs(Lower fee transactions and smaller blockchain)
  • Staking from the GUI wallet
  • Add latest updates and bug fixes from Monero and Loki
  • IPV6 support for the Saronite daemon
  • Minor changes in the difficulty algorithm

CoinMarketCap listing

Saronite has applied to be listed on CoinMarketCap. We have gotten a response from CoinMarketCap and they have requested a value only output for the circulating supply. This has been done here> https://saronite.io/api/circulating/ We have provided CoinMarketCap with what they need and they will now process listing Saronite on CoinMarketCap

SaroWrite

SaroWrite blogging network is due in Quarter 1 2019. We are currently working and testing a few things, we will release the platform in stages and go live during Quarter 1 2019. We hope to be one of the biggest blogging platform in the cryptocurrency world. We will go through a lot of advertising to promote SaroWrite. In the next update we will discuss the technical details.

2019 Goals for Saronite

2019 will be an exciting year for the Saronite team and community. We are going to work on the following

  • Complete and launch SaroWrite
  • Implement a custom proof of work that will give 15% to ASIC’s and 85% to GPU/CPU miners
  • Implement online payment methods and the existence of SaroPay.
  • List on a larger exchanges
  • Marketing for Saronite
  • Get listed on masternodes.online
  • Service Node Apps with community based development

Thank you to the Saronite community and everyone assisting the project! We hope to have you with us for 2019 and the years to come!

Happy new year from the Saronite team!

The post The last Update of 2018 appeared first on Saronite.


View the full article

Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      2.38 TH
    • Avg Hashrate
      884.75 MH
    • Total Miners
      2687
    • Miners Paid
      44742
    • Total Payments
      1560105
    • Total Hashes
      9.23 EX
    • Blocks Found
      1840315
  • Posts

    • Hey guys. Can somebody help me? I wanted to have some fun and start mining Monero.  This is my config:    {     "autosave": true,     "donate-level": 2,     "cpu": true,     "opencl": true,     "cuda": true,     "pools": [         {             "url": "pool.hashvault.pro:3333"         },         {             "url": "pool.hashvault.pro:443",             "user": "-------------",             "keepalive": true,             "tls": true         }     ] }   I generated on website. Can you help me with user? What should I put there? A wallet address? (i have Coinomi wallet). Where to get it? Don't have any serious expectations about mining but i have a PC with two RTX 3060 so maybe i will dig something in free time just to be happy, even if it will be worth 1$ 🙂 Thank you in advance.
    • А куда пул вообще пропал? Нужно было посмотреть txid своих старых выплат, а страница тупо пропала.
    • Dear Community,   Reading the "Getting Started" section in the Pool area and some threads on the Forum, I still have a little question.  Whom do you recommend mining solo?  The hash rate seems to be the same whether I do SOLO mining or not.  Thanks! Bee *** My machine is a simple workstation with a slim linux running: * ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 1.1/15.6 GB (7%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
    • Update: Having applied the Script from the thread linked to above, I get another outcome. Is that as it is supposed to be?? Thanks again Bee alpinehost:/home/alp# chown root /usr/share/hugepages.sh alpinehost:/home/alp# /usr/share/./hugepages.sh enable Huge pages enabled alpinehost:/home/alp# sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 9 vm.nr_hugepages_mempolicy = 9 vm.nr_overcommit_hugepages = 0 alpinehost:/home/alp# The vm.nr_hugepages changed dramatically. What does it mean anyways?
    • Dear Community,    I would like to have these Hugepages supported now :-) I am thus referring to this thread here, which seems to be closed. I have tried the following to enable hugepages AND get them working until 1 GB.  See me output: Thanks so far! Bee *** Question: Why is HUGEpages 1 GIg not available?  How do I set the value correct? My output: sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 2349 vm.nr_hugepages_mempolicy = 2349 vm.nr_overcommit_hugepages = 0 *** and in xmrig *** ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 3.2/15.6 GB (21%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
×
×
  • Create New...