The web wallet will be activated very soon.

Add MN List: https://masternodecoins.me/fss-coin

Add MN Stats: https://masternodestats.com/currencies/FSS

Shuzibi began accepting overseas user's registration by e-mail only.
https://www.shuzibi.com/trade/ETH/ETZ  !

This is one of those coin that could make your $100 investment into $5000. 

you can use  POS polls aswell, so with lower stake you have  daily income, but it wont be great. There are few of those  pools, but use it on own risk

Hello, some of unclaimed coin will be burned, this is the burning address http://miningpool2.thruhere.net:11008/address/CZBURNXXXXXXXXXXXXXXXXXXXXXXagZLdR

docker should be available on centOS (https://docs.docker.com/engine/installation/linux/docker-ce/centos), in that case, just run with your right ports.


look there, it's written : https://hub.docker.com/r/steevebrush/iridiumd-container

about bandwidth : after the download of the blockchain (2,5Go), bandwidth is very low ! a block is discover every 5 minutes at this time. the node connect automatically to others node. the version compiled is the latest with new seeds.

How this works ? simple : the daemon stock the blockchain, share and confirm (or infirme) the validity of a block.
so more nodes = faster validation and safer transactions.

may be a reward can be imagined for people running nodes, it's a community, so why not asking ?

If you are using Claymore, this is what you want to see.



You want that your worker submits shares every few seconds. This is only possible if the pool allocates you a proper share difficulty.

Many pools which use auto-diff do not. They give you some ridiculous diff of say 100k, which means your worker will often not find and submit a single share before the round is over, which means you get ZERO rewards for that round.

A worker consisting of a single CPU and a worker consisting of 6 GPUs obviously need highly different diffs. When a pools is using a constant diff on a certain port, that diff fits basically nobody. It will be too high for the single CPU worker and much too low for the multiple GPU rig. Which means the single CPU worker will just heat the room by not finding a single share before a round is over, while the multiple GPU worker will bombard the pool server with shares multiple times every second putting an unnecessary load on the server.

This is why pools are using auto-diff. They have different start diffs on certain ports but then each new round after you connect they adjust the diff. What many of them however don't do, is to adjust it properly. They just increase it until max diff is reached, rendering the connected workers very inefficient with much too high diff.

Therefore a pools needs the option that a user can set a diff of his choice which works best for his rigs. Simply to overcome the badly implemented auto-diff.

Let's assume your worker has a total hashrate of 1000H/s. Try to set a diff of 3000 and see how frequently shares are found and submitted (the green lines saying "share found, share accepted"). If it is every few seconds, that's fine. If it takes longer, set a lower diff. If it is too frequent, set a higher diff. Once you have figured it out, use that diff forever for that particular algo.

However for coins where the block time is much shorter, say 15s, you want to have shares found and submitted much more frequently than 2-3s. Otherwise you will miss out all short rounds.

About the above screenshot: Claymore shows those yellow status lines with the temperatures every 30s. As you can see the diff I have configured is such that shares are found every 2-3s. Works fine for me. If you use a too high diff (manually set too high or the pool setting it for you) you will also notice that the hashrate shown in the pool is much lower than your actual hashrate (no, this isn't because Claymore is mining covertly with your rigs and such nonsense!). That's because your worker will produce many stale shares when the round is already over and he is still chewing on the old outdated work, wasting electricity for nothing. Therefore the right diff setting is essential for efficient mining.

EDIT: Here is what you don't want to see:

We had a bit to much load and upgraded it.

Do you still have any issues?

Hi all,
Please give me link to download miner for AMD 470 cards. thanks

Indeed some coins will go to masternodes, but they stated somewhere devs will burn some coins? The second thing i wonder is if B3 is hardcapped to 2 billion coins or not. Because till block 80k i think we will pass 50 billions with the 10k POS.

Windows wallet still doesn't work

We are happy to see that the wallet is working perfectly.

have a good mining  

20k is enough to start earning stakes every 1 to 3 days depending on the network weight.
Yes the more someone has the better and more chance to stake often but I think 20k is good enough to earn a few thousand coins a month.
I have 150k RAIN. I receive staking rewards everyday 8-20 times, approximately 1000-2500 RAIN.

What I've found:
https://www.coinschedule.com/icos/e1088/halo-platform-ico.html
https://www.haloplatform.tech/

people not mining,i turned off my working rigs from HUSH ,waited 10 min,saw that "fair launch" and back to HUSH again.

There will be 1 more project on same algo,HALO,will look for it,and will stay away from this scam,dev do nothing,community members post here how to solve problems,when there is clean thing written on website,that OS and WINDOWS wallets are ready.