I agree

I am in that damned list above

I am at this forum because I got an email saying 'you gave Betcoin this information'

Eh- on one hand I don't care but on the other, why do people carry on maliciously like this?

Whoever it is who discovered the exploit- what you've done is WORSE than what seems to be sloppy work at BC.

Please stop attempting to extort money from Betcoin at the expense of the people you paradoxically are claiming you care about.

If you REALLY were white hat - you would keep it confidential and notify betcoin.  They do not OWE you for finding a bug- life doesn't HAVE to be that way.

What you are doing here BetCoinBugBounty is EXTORTION and it's lower than sloppy coding.

Now -be gone - go do something productive with your life

Try a garden or something, yeah - go find some bugs in your garden-  those slugs on my tomatoes drives me's crazy's's's this year.

That was it-

No more RPC connect curl error

I need to learn more about how these ports with using ethminer for another coin.

I was puzzled that I would be using ethminer,  thinking, hmm- wonder why it won't continue to mine ethereum if I use ethminer to mine Shift

Is it that Shift specifies a different port? than ethereum for mining?

That's a new question I suppose

I see it's building the DAG right now though

Thanks so much for your reply Shift Support

TIm

New to shift, familiar with ETH mining.

I am seeking to solo mine - Windows 7 64 bit - but that won't be too related, I do have the 64 bit release.


Step 1:  first thing I did new to Shift

Got gshift.exe and shift wallet.   Ran gshift, then the wallet, created a new account.

All good-  I see my account now



Step 2: was hoping to get up and mining, after BC sync.   

Block Chain didn't sync until I forwarded port 53900 - all good  BC sync'd.


From what I understand I need to run gshift first (similar to geth --rpc) before solo mining

Did so with

gshift --shiftbase "0" --rpc --rpcaddr "127.0.0.1" --rpcport "53901" --port "53900"  --verbosity "3" console


I myself would think no console there, so I ALSO tried gshift --rpc    as well as JUST gshift

Sits there listening - all good



Step 3 - time to start ETH Miner
C:\eth\emine>ethminer.exe --farm-recheck 500 -G -F http://127.0.0.1:53001

 The following is what comes back -  it's quite normal until the JSON-RPC error - curl error



_BEGIN PASTE_


Genoil's ethminer 0.9.41-genoil-1.0.6
=====================================================================
Forked from github.com/ethereum/cpp-ethereum
CUDA kernel ported from Tim Hughes' OpenCL kernel
With contributions from RoBiK, tpruvot and sp_

Please consider a donation to:
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d

Found suitable OpenCL device [Tonga] with 4294967296 bytes of GPU memory
miner  10:48:27|main  Getting work package...
  X  10:48:28|main  Failed to submit hashrate.
  X  10:48:28|main  Dynamic exception type: class jsonrpc::JsonRpcException
std::exception::what: Exception -32003 : Client connector error: libcurl error:
7 -> Could not connect to http://127.0.0.1:53001

JSON-RPC problem. Probably couldn't connect. Retrying in 1...





_END PASTE


So my question is, it just sits in that loop - Could not connect.


Sure looks port related, but I have 53900 forwarded.



Can anyone think of a reason why it won't connect ?  It's allowed through the FW - even tested with FW off just to make sure.


I hope this problem helps someone else who might be experiencing the same thing.

Tim Miltz