Are miners leaving?
Interval between blocks a few days ago was 10-15 min.
Here are timestamps of last 5 blocks
18131 Sep 22, 2015 at 3:35pm (UTC)
18132 Sep 22, 2015 at 4:35pm (UTC)
18133 Sep 22, 2015 at 5:10pm (UTC)
18134 Sep 22, 2015 at 4:28pm (UTC)
18135 Sep 22, 2015 at 5:59pm (UTC)
Was block 18133 mined before 18134 and 18132? Is that even possible?
Intervals between blocks (ignoring 18134) is now > 1 hour.
Last block was mined > 2 1/2 hours ago.
What's going on?
When the difficulty spikes all of the miners flee. Then you're stuck with an extra high difficulty as well as no miners, so the block time goes up 5-10x. This problem should fade as the coin grows in rank.
I was contacted to set up a pool for Sia.
Since Sia is a bit different than other coins, can someone briefly introduce me into the mining mechanism ? are you mining with clients to a main wallet via RPC or are you all just doing "in-wallet-mining" ?
Thanks for your interest!
I do not mine myself, but here are some resources to get you started:
The Sia developers have released a CPU miner, which runs "in-wallet".
There is also a GPU miner, here:
https://github.com/NebulousLabs/Sia-GPU-MinerBinaries here:
https://github.com/NebulousLabs/Sia-GPU-Miner/releasesThey say the GPU miner has some bugs, and the miner can only mine on a single GPU at a time. You can run multiple miner instances for more processors.
Chat with miners on Slack:
https://siatalk.slack.com/messages/mining/details/Thanks for the reply, i'll have a look at those links. What I need for a pool is some sort of Wallet -> Client or Client -> Wallet communication, because i'll be acting like a "proxy" with the pool.. So it looks like Client -> Pool -> Wallet ...
Hi, dev here. We've got an HTTP API that you can use to talk with the daemon while mining. It will give you block headers, and then you can use it to submit solved block headers. The block headers will already have all the txns and whatnot. Additionally, each time you request a block header you will get a unique txn merkle-root, so you don't need to worry about stretching the nonce yourself. The nonce in a header is 64bits, if you run out just request a new header.
https://github.com/NebulousLabs/Sia/blob/master/doc/API.mdedit: looks like the documentation is out of date for the miner. Code is here:
https://github.com/NebulousLabs/Sia/blob/master/api/api.gothe api calls you want are /miner/headerforwork and /miner/submitheader. The start & stop commands are used for an internal CPU miner which is for testing only. /blockforwork and /submitblock are deprecated, only kept to preserve compatibility with older miners.
