[ANN] SpreadCoin | True Decentralization (No Pools) | Testing New Masternodes

[pokeytex]

thank you  
And how would i send my hash to the same wallet from my 2nd computer through the internet ?

Here is how:

Also you can mine to a specific address (this is useful if you are mining on several computers). To do so:
1. Use existing or better generate a new address.
2. Open debug console (Tools -> Debug Console) and enter:

dumpprivkey SYourSpreadCoinAddress

3. You will get your private key. Then open spreadcoin.conf or create it if it doesn't exist (D:\Users\<username>\AppData\Roaming\SpreadCoin\spreadcoin.conf on Windows) and add the following line:

miningprivkey=YourPrivateKey

4. Restart your wallet if it was running.
In the Mining tab you will now see notification that all mined coins will go to this address.

Of course you need to generate address and get privkey on one computer and edit spreadcoin.conf on the other.

What is the difference between mining in one wallet with privatekey with several computers and mining with a more wallets especially?

the wallet uses electricity = $

This part confuses me - I need to open my wallet on the second computer in order to solo mine.  If I don't open the wallet I get json errors.  Does the wallet have to be open on both rigs in order to solo mine?  And at this point aren't I still burning electricity?

You only need one wallet running. On the computer running the wallet you point your miner to 127.0.0.1 and on the other computer you point it to the computer that's running the wallet.

Computer 1, with wallet: miner.exe -o 127.0.0.1:41677
Computer 2: miner.exe -o ip.of.wallet.computer:41677

Don't put gen=1 into the conf, that makes the wallet run the internal CPU miner and that's a waste of electricity at these network hash rates. Something like this would do the trick, add the miningprivkey parameter if you want, personally I don't use it.

Code:

server=1
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcuser=yourrpcusername
rpcpassword=yourrpcpassword

The first rpcallowip allows RPC connections from the same computer that is running the wallet. The second rpcallowip is needed to allow connections from the other computer, change the IP to whatever your local network is.

Or you can run the wallet on both computer, as long as you don't use gen=1 it doesn't really hurt but you'll have to deal with having two separate wallets and moving coins from them separately.

Ok - so just to confirm - I do not need my wallet running on the second machine to get it to mine?  I will try this setup and see if it works - thank you.

Edit - ok I tried it without the wallet on the second machine running and it gets the json error when I open the miner.  I must be missing something?

If you are on Windows. Go to the computer with wallet and open the command window and type ipconfig then look for your IPv4 Address. Make sure you use that ip address in your bat on the non wallet computer.

Example. If wallet computer ipv4 address is 192.192.1.921 your bat should look something like this:  spreadminer -o http://192.192.1.921:41667 -u USERNAME -p PASSWORD

I also use rpcport=41667 in my config file. If you change anything in your confige file you must restart the wallet.

NOTE: I am a rookie compared to tsiv but this is how I solo mine from multiple computers to the main with the wallet. I have other steps that I must do but they are not the most secure way that I have read about how I do it but it works fine for me. Been mining at time a total of 3 computers into the one with the wallet.

Ok - let me explain how I am doing it now and maybe someone could tell me if it is wrong.  I am running windows 8.1 on (2) rigs.  One rig has (4) 750ti's and the other rig has (6) 750ti's.  The (6) card rig is headless in my garage while the other rig is in my basement.  I use teamviewer to keep both rigs up on my screens.  I have my main computer with the (4) 750tis and mine in the background.  So far I have been mining with no problems on both computers to the same wallet.  The way I did it was to start the process on one rig.  When the .conf and miner were set up properly I copied all folders (spreadcoin & spr Miner) to the other computer.  I run both with the same settings, wallet, and miner.  Every time one miner finds a block the wallet on the opposite rig updates.  There is some lag (like 15-30 seconds) but it always updates.  Is there a problem with doing it this way?  Please advise.  Thank you.

[firefighters]

SPR is most innovative and fair (no IPO,no ICO,no premine and no pools,which can prevent the muliti-pool ) coin in the second half year of 2014,I think.

[Mikolo]

I thinks one of problems with publicity of this coin is lack of pools. Usually when coin goes to big pools people start noticing it. But we cannot do that, for obvious reasons. So maybe we should register our coin to some of rig rental sites? Such as miningrigrentals.com or betarig. It may attract more miners to us. And Mr. Spread, could you please add threads about miner and logo to OP? And other thread about our coin too, so it's would be more easy to find them.

[Mr. Spread]

I thinks one of problems with publicity of this coin is lack of pools. Usually when coin goes to big pools people start noticing it. But we cannot do that, for obvious reasons. So maybe we should register our coin to some of rig rental sites? Such as miningrigrentals.com or betarig. It may attract more miners to us. And Mr. Spread, could you please add threads about miner and logo to OP? And other thread about our coin too, so it's would be more easy to find them.

Link to logo thread is already in OP, almost at the top.

Mining thread - do you mean this one https://bitcointalk.org/index.php?topic=869289 ? I will add it.

[tbearhere]

thank you  
And how would i send my hash to the same wallet from my 2nd computer through the internet ?

Here is how:

Also you can mine to a specific address (this is useful if you are mining on several computers). To do so:
1. Use existing or better generate a new address.
2. Open debug console (Tools -> Debug Console) and enter:

dumpprivkey SYourSpreadCoinAddress

3. You will get your private key. Then open spreadcoin.conf or create it if it doesn't exist (D:\Users\<username>\AppData\Roaming\SpreadCoin\spreadcoin.conf on Windows) and add the following line:

miningprivkey=YourPrivateKey

4. Restart your wallet if it was running.
In the Mining tab you will now see notification that all mined coins will go to this address.

Of course you need to generate address and get privkey on one computer and edit spreadcoin.conf on the other.

What is the difference between mining in one wallet with privatekey with several computers and mining with a more wallets especially?

the wallet uses electricity = $

This part confuses me - I need to open my wallet on the second computer in order to solo mine.  If I don't open the wallet I get json errors.  Does the wallet have to be open on both rigs in order to solo mine?  And at this point aren't I still burning electricity?

You only need one wallet running. On the computer running the wallet you point your miner to 127.0.0.1 and on the other computer you point it to the computer that's running the wallet.

Computer 1, with wallet: miner.exe -o 127.0.0.1:41677
Computer 2: miner.exe -o ip.of.wallet.computer:41677

Don't put gen=1 into the conf, that makes the wallet run the internal CPU miner and that's a waste of electricity at these network hash rates. Something like this would do the trick, add the miningprivkey parameter if you want, personally I don't use it.

Code:

server=1
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcuser=yourrpcusername
rpcpassword=yourrpcpassword

The first rpcallowip allows RPC connections from the same computer that is running the wallet. The second rpcallowip is needed to allow connections from the other computer, change the IP to whatever your local network is.

Or you can run the wallet on both computer, as long as you don't use gen=1 it doesn't really hurt but you'll have to deal with having two separate wallets and moving coins from them separately.

Ok - so just to confirm - I do not need my wallet running on the second machine to get it to mine?  I will try this setup and see if it works - thank you.

Edit - ok I tried it without the wallet on the second machine running and it gets the json error when I open the miner.  I must be missing something?

If you are on Windows. Go to the computer with wallet and open the command window and type ipconfig then look for your IPv4 Address. Make sure you use that ip address in your bat on the non wallet computer.

Example. If wallet computer ipv4 address is 192.192.1.921 your bat should look something like this:  spreadminer -o http://192.192.1.921:41667 -u USERNAME -p PASSWORD

I also use rpcport=41667 in my config file. If you change anything in your confige file you must restart the wallet.

NOTE: I am a rookie compared to tsiv but this is how I solo mine from multiple computers to the main with the wallet. I have other steps that I must do but they are not the most secure way that I have read about how I do it but it works fine for me. Been mining at time a total of 3 computers into the one with the wallet.

I get this  from other computer  http request failed  error  403 forbidden json_rpc_call failed
I dont get it..I have sent my hash from other coins to pools why cant i send my hash to my other computer that has the wallet.

[tsiv]

I get this  from other computer  http request failed  error  403 forbidden json_rpc_call failed
I dont get it..I have sent my hash from other coins to pools why cant i send my hash to my other computer that has the wallet.

Seems like there are two possibilities. Incorrect username/password (unlikely but check anyway) or incorrectly configured rpcallowip in the wallet conf and the wallet is denying connections from the other computer. Are you sure you've got the right network or IP address in the conf?

[th00ber]

rpcallowip=*

will disable any filter on ip.
And disable your firewall in the wallet PC to be sure that INCOMING connection will be allowed.

I did this, 2 rigs on linux mining on my laptop windows wallet

[tsiv]

rpcallowip=*

will disable any filter on ip.
And disable your firewall in the wallet PC to be sure that INCOMING connection will be allowed.

I did this, 2 rigs on linux mining on my laptop windows wallet

Just be damn sure your local network isn't accessible from the outside if you allow connections from any IP.

Shouldn't need to mess with the firewall, since he's getting a 403 reply from the wallet there shouldn't be any connectivity problems, just authentication.

[tbearhere]

rpcallowip=*

will disable any filter on ip.
And disable your firewall in the wallet PC to be sure that INCOMING connection will be allowed.

I did this, 2 rigs on linux mining on my laptop windows wallet

Just be damn sure your local network isn't accessible from the outside if you allow connections from any IP.

Shouldn't need to mess with the firewall, since he's getting a 403 reply from the wallet there shouldn't be any connectivity problems, just authentication.

yes i believe its an authentication problem

[tbearhere]

rpcallowip=*

will disable any filter on ip.
And disable your firewall in the wallet PC to be sure that INCOMING connection will be allowed.

I did this, 2 rigs on linux mining on my laptop windows wallet

ok finally  rpcallowip=*  worked but how can I make it safer?

[Mr. Spread]

Here is the compiled Windows binary of girino miner: http://spreadcoin.net/files/Spread-GPU-miner.7z
For me it is actually slower than my miner but maybe this is just because I'm only using low intensity values.
This miner gives higher hashrate. If you have previously used old version of the miner then you should add 6 to your intensity, e.g. -I 13 corresponds to -I 19 in new miner.

[girino]

Here is compiled Windows binary of girino miner: http://spreadcoin.net/files/Spread-GPU-miner.7z
For me it is actually slower than my miner but maybe this is just because I'm only using low intensity values.
I updated readme, original miner is also included.

since there is no loop, you are actually running an intensity 6 times less than you were before. (-I 11 becomes -I 17 in my miner)

[girino]

Here is compiled Windows binary of girino miner: http://spreadcoin.net/files/Spread-GPU-miner.7z
For me it is actually slower than my miner but maybe this is just because I'm only using low intensity values.
I updated readme, original miner is also included.

since there is no loop, you are actually running an intensity 6 times less than you were before. (-I 11 becomes -I 17 in my miner)

I get the best results in my 280x with -w 256 and -I 22

[Mr. Spread]

since there is no loop, you are actually running an intensity 6 times less than you were before. (-I 11 becomes -I 17 in my miner)

That makes sense, I will update readme to include this information.

EDIT: Wow, it is really fast.

[zeca pagodinho]

The intensity of 22 reached 2MH, already with 23 intensity only reach 1.3 mh, intensity 24, was just 900kh and video card stopped working.
Because the speed decreases when increasing the intencidade? 

[girino]

The intensity of 22 reached 2MH, already with 23 intensity only reach 1.3 mh, intensity 24, was just 900kh and video card stopped working.
Because the speed decreases when increasing the intencidade? 

in the modified version, more intensity means more memory. What happens on -I 24 is that your card runs out of memory and crashes.

Above 22, what is probably happening is that you have not enough memory to run more than one thread at a time, so you have threads waiting for the memory to be freed so they can run, and thus, less speed. 22 is possibly the value that uses best the amount of memory available to your GPU.

[girino]

EDIT: Wow, it is really fast.

I told you so. GPUs don't like loops, so removing the loop is a big step. Then, using "#pragma unroll" in all loops in the multiplication/reduction code also improved a lot (10%) the speed. And finally, by spliting it into several kernels the compiler is better able to fit all the variables into registers, and use less of (slow) global memory (local memory is scarce, so only used when explicitly required).

[zeca pagodinho]

The intensity of 22 reached 2MH, already with 23 intensity only reach 1.3 mh, intensity 24, was just 900kh and video card stopped working.
Because the speed decreases when increasing the intencidade? 

in the modified version, more intensity means more memory. What happens on -I 24 is that your card runs out of memory and crashes.

Above 22, what is probably happening is that you have not enough memory to run more than one thread at a time, so you have threads waiting for the memory to be freed so they can run, and thus, less speed. 22 is possibly the value that uses best the amount of memory available to your GPU.

Now I understand! The quality of his work is exceptional, I am pleased with the new speed of mining.

Thank you for your attention and success to you! 

[girino]

I'm trying now the NVidia miner, but i can't get it to work correclty. I can find a lot of blocks (running  on testnet), but they are never accepted by the wallet:

Code:

[2014-11-29 11:23:07] Thread 0 found a solution
First nonce : 00000000
Found nonce : 004ccf70
Threadidx   : 315248
Threadidx64 : 4925
VTX         : 0101000000010000000000000000000000000000000000000000000000000000000000000000ffffffff020101ffffffff01f39eb627000000001614a082af4ce9f81ba9f2be1c16f36ac2a32d9719a3ac00000000

[2014-11-29 11:23:07] Final hash 256 : 742ef17bd2bd4800291d2f5f98e04af5d40a812cdc98338cae3c332562000000
[2014-11-29 11:23:07] Submit data    : 02000000f3dc0278624b9b0c0f1796b21dc07115a52a165a23e635577be4625bda56c08078b0002107a0872873359a82bee1f3b46860955e4b23a958afdc2b729916c4d6b6c8795400000000eae57f1d1309000070cf4c00dadacba57842eaacd731ba7e89d748e2594d123f8f703ff84cba9e18ebdac2181c407c1133e8f71338c1e65dde7f1880002621236a944fe2574337e1d692247a87bddf5f3b6427938359df5362e2cd13b9628c6e6ee3f7c4bc954769139cc0728d
[2014-11-29 11:23:07] HashWholeBlock : dadacba57842eaacd731ba7e89d748e2594d123f8f703ff84cba9e18ebdac218
[2014-11-29 11:23:07] MinerSignature : bddf5f3b6427938359df5362e2cd13b9628c6e6ee3f7c4bc954769139cc0728d
[2014-11-29 11:23:07] GPU #0: GeForce GTX 750 Ti, 1148 khash/s
[2014-11-29 11:23:07] accepted: 0/11 (0.00%), 1148 khash/s (booooo)

Anyone knows how to fix it? (running on ubuntu 14.04 64bits, GeForce GTX 750 Ti).

[tsiv]

I'm trying now the NVidia miner, but i can't get it to work correclty. I can find a lot of blocks (running  on testnet), but they are never accepted by the wallet:

Code:

[2014-11-29 11:23:07] Thread 0 found a solution
First nonce : 00000000
Found nonce : 004ccf70
Threadidx   : 315248
Threadidx64 : 4925
VTX         : 0101000000010000000000000000000000000000000000000000000000000000000000000000ffffffff020101ffffffff01f39eb627000000001614a082af4ce9f81ba9f2be1c16f36ac2a32d9719a3ac00000000

[2014-11-29 11:23:07] Final hash 256 : 742ef17bd2bd4800291d2f5f98e04af5d40a812cdc98338cae3c332562000000
[2014-11-29 11:23:07] Submit data    : 02000000f3dc0278624b9b0c0f1796b21dc07115a52a165a23e635577be4625bda56c08078b0002107a0872873359a82bee1f3b46860955e4b23a958afdc2b729916c4d6b6c8795400000000eae57f1d1309000070cf4c00dadacba57842eaacd731ba7e89d748e2594d123f8f703ff84cba9e18ebdac2181c407c1133e8f71338c1e65dde7f1880002621236a944fe2574337e1d692247a87bddf5f3b6427938359df5362e2cd13b9628c6e6ee3f7c4bc954769139cc0728d
[2014-11-29 11:23:07] HashWholeBlock : dadacba57842eaacd731ba7e89d748e2594d123f8f703ff84cba9e18ebdac218
[2014-11-29 11:23:07] MinerSignature : bddf5f3b6427938359df5362e2cd13b9628c6e6ee3f7c4bc954769139cc0728d
[2014-11-29 11:23:07] GPU #0: GeForce GTX 750 Ti, 1148 khash/s
[2014-11-29 11:23:07] accepted: 0/11 (0.00%), 1148 khash/s (booooo)

Anyone knows how to fix it? (running on ubuntu 14.04 64bits, GeForce GTX 750 Ti).

Doesn't seem to work on testnet and CBA to try figure out why, just go live