Dev There is any plan to add Sia on some big exchanges like Cryptsy,Bittrex,Bter or C-cex?
Yes there is, we've reached out to them all. We haven't heard anything back yet. It might help if you guys submit requests as well.
Topic: [ANN] Sia - Decentralized Storage - page 466. (Read 1382228 times)
Yes there is, we've reached out to them all. We haven't heard anything back yet. It might help if you guys submit requests as well.
Dev There is any plan to add Sia on some big exchanges like Cryptsy,Bittrex,Bter or C-cex?
To devs: it`s no problem to make a single wallet for several gpu-rigs - just copying 2 folders from one rig to another.
But is it correct to launch one wallet with the same address from several rigs to mine simultaneously?
But is it correct to launch one wallet with the same address from several rigs to mine simultaneously?
no, please don't use the same wallet file in multiple places at once. It's going to jumble your addresses. Only move the wallet around for backup purposes.
At some point we'll have better support for merging, splitting, encrypting, and backing up wallets. Right now it's a pretty simple construction though. Every 'siad' should have its own wallet file, and each wallet file should only be in use one-at-a-time. You should also backup frequently if you spend a lot of money - you'll notice that the wallet gets bigger over time.
There are ways we can make this better, but we're prioritizing other things first. We'll get to it in a few weeks hopefully.
So there are at least 2 people claim they are mining at x10 times faster than the rest of us... Wanna sell us your config ? 
not config changes, miner rewrite ;-)
EDIT: a quick run on 290x shows more than 1Gh/s
and there is a deal to be made for the dev that does the deal with us here ...
let me know ...
#crysx
So there are at least 2 people claim they are mining at x10 times faster than the rest of us... Wanna sell us your config ?
not config changes, miner rewrite ;-)
EDIT: a quick run on 290x shows more than 1Gh/s
To devs: it`s no problem to make a single wallet for several gpu-rigs - just copying 2 folders from one rig to another.
But is it correct to launch one wallet with the same address from several rigs to mine simultaneously?
But is it correct to launch one wallet with the same address from several rigs to mine simultaneously?
So there are at least 2 people claim they are mining at x10 times faster than the rest of us... Wanna sell us your config ?
try to calculate your chance to find a block - 96mh/s vs Xgh/s 
i think only pool-miner is a good idea to equalize all of us.
*tho I do not encourage that.
So there are at least 2 people claim they are mining at x10 times faster than the rest of us... Wanna sell us your config ?
try to calculate your chance to find a block - 96mh/s vs Xgh/s i think only pool-miner is a good idea to equalize all of us.
So there are at least 2 people claim they are mining at x10 times faster than the rest of us... Wanna sell us your config ?
does anyone know how to check address/balance from SIA command line (siad) thanks!
"Once a block is mined, Sia waits for 144 confirmation blocks before the reward is added to your wallet, which takes about 24 hours."
patience , patience
"Once a block is mined, Sia waits for 144 confirmation blocks before the reward is added to your wallet, which takes about 24 hours."
patience , patience
Sia-GPU-Miner Often collapse !!!!
Do you have any good solution?
Thank you
Do you have any good solution?
Thank you
Yeah, we've got parts of it fixed in the dev branch. We're fixing a few other parts, and trying to push up the hashrate a bit so we're not sooooo far behind the proprietary miners. Expect a new release for linux+windows in the next 18 hours or so.
Sia-GPU-Miner Often collapse !!!!
Do you have any good solution?
Thank you
Do you have any good solution?
Thank you
I have downclocked the gpu by 30% but that doesn't seem to affect the mining speed at all.. save your electricity! 
yes because it is limited by the ram speed.
you may even get more hashes by increasing memclock.
but the algo is very simple and should run on registers only.
that's how you get 280x do this:
Mining at 756.267 MH/s X blocks mined
Of course at this speed it doesn't "save electricity" ;-)
Did you make the block fetch async? If not, is that including the block fetch time, as the stock miner does?
I have not yet, and I kept the block fetch time included in the hashrate counter meter so that it better relates to the stock one.
I rebased my work on the new commits and left that part unchanged.
Some of the changes I did to the C code are similar to what they modified so it's not worth keeping them.
EDIT: when I removed block fetching from the hashrate calculation to the old tree, the hashrate changed by a couple percent only
280X goes above 950MH/s; still non-async.
How ? Is there a new miner or something ?
My 280x only gets to 93mh/s with the buggy miner.
my 280x only gets max 50-60 (usually more like 30) but it freezes after some seconds or i get this message "curl did not reveive enough bytes " after some time (system win7)
I have downclocked the gpu by 30% but that doesn't seem to affect the mining speed at all.. save your electricity!
yes because it is limited by the ram speed.
you may even get more hashes by increasing memclock.
but the algo is very simple and should run on registers only.
that's how you get 280x do this:
Mining at 756.267 MH/s X blocks mined
Of course at this speed it doesn't "save electricity" ;-)
Did you make the block fetch async? If not, is that including the block fetch time, as the stock miner does?
I have not yet, and I kept the block fetch time included in the hashrate counter meter so that it better relates to the stock one.
I rebased my work on the new commits and left that part unchanged.
Some of the changes I did to the C code are similar to what they modified so it's not worth keeping them.
EDIT: when I removed block fetching from the hashrate calculation to the old tree, the hashrate changed by a couple percent only
280X goes above 950MH/s; still non-async.
How ? Is there a new miner or something ?
My 280x only gets to 93mh/s with the buggy miner.
i am not able to get the mining working. i tried it with 2 different ubuntu systems, but every time the gpu-miner won't work it says:
Quote
./gpu-miner: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_4' not found (required by ./gpu-miner)
I had it too. I wasn't able to run build release but successfully compiled from source
git clone https://github.com/NebulousLabs/Sia-GPU-Miner
I had to install opencl-headers first
sudo apt-get install opencl-headers
and then just
make -f Makefile
thanks that was helpful, one on system i was succesful, on the other system i wasn't (older ubuntu version = 13) and i got this message
failed to start kernel: -52
ok nothing works right here for me nor under win nor under linux
I have downclocked the gpu by 30% but that doesn't seem to affect the mining speed at all.. save your electricity!
yes because it is limited by the ram speed.
you may even get more hashes by increasing memclock.
but the algo is very simple and should run on registers only.
that's how you get 280x do this:
Mining at 756.267 MH/s X blocks mined
Of course at this speed it doesn't "save electricity" ;-)
Any chance you can let me know how you did this i have 2 280x hashing 100mh
At this time, I have produced 40 million coins.
SCAMER DO NOT TRADE WITH clipman77
He agreed to do a trade with me and then declined using escrow, I also suggested to pay the escrow fee but he insisted that I send first to him. (4 BTC) he then canceled the trade.
100% SCAM do not trade with him!
always crashes the driver on the win 8.1 x64,cards 3x7870 and 1x290
Yep.Mine screen also goes black every 5 minutes or sometime even less. Any solutions?this - https://bitcointalksearch.org/topic/m.11568111
and you can also try lowering your gpu/mem clocks
I have downclocked the gpu by 30% but that doesn't seem to affect the mining speed at all.. save your electricity!
yes because it is limited by the ram speed.
you may even get more hashes by increasing memclock.
but the algo is very simple and should run on registers only.
that's how you get 280x do this:
Mining at 756.267 MH/s X blocks mined
Of course at this speed it doesn't "save electricity" ;-)
Did you make the block fetch async? If not, is that including the block fetch time, as the stock miner does?
I have not yet, and I kept the block fetch time included in the hashrate counter meter so that it better relates to the stock one.
I rebased my work on the new commits and left that part unchanged.
Some of the changes I did to the C code are similar to what they modified so it's not worth keeping them.
EDIT: when I removed block fetching from the hashrate calculation to the old tree, the hashrate changed by a couple percent only
always crashes the driver on the win 8.1 x64,cards 3x7870 and 1x290
Yep.Mine screen also goes black every 5 minutes or sometime even less. Any solutions? Jump to: