What nodes/peer should we have in the config.
I am running the 0.30.17.5 wallet but no connections at all. Stuck on block 206553.
Thanks.
|
|
|
I am no expert in this psu/riser stuff but I read that when using the daisy chain power molex connectors to never use more than 2 connecting for power.
Something about they are not designed to have a lot of power running through them.
|
|
|
The spreadcoin, cryptonight and lyra2v2 are all memory hard algorithms.
But I still have managed to optimize them.
I believe I can optimize the Ether miner as well, but I am waiting for stratum support and a gui wallet.
I believe the GUI wallet comes out next year. It is supposed to be well after the POW for Eth is done. If I remember correct Eth POW is over in October sometime. Don't quote me on any of that.
|
|
|
Silly question as I am behind and just catching up.
Which is the current version of working wallet we should be using? Wallet Links -- Current Version 0.30.17.2 from the OP or 0.30.17.2.-fixssl from the last version in the thread?
|
|
|
Whirlpoolx is almost unique in how it was conceived: it really looks like it was made to favourite smart developers. The large part of the optimisations come from "shortcuts", more than general algorithm speedup. In the end it's just reiterated whirlpool (which in turn is similar to groestl and other aes derived algos). So I guess that a 970 with all the "shortcuts" in place, should be about as good as a 280x (500 Mh/s).
Thats why x11 is safer. Supported by Daesh.. I wonder why the poor NVIDIA miners are skipping the ETHER algo... Such Profit loss Right now AMD does a lot better on hashing. At least Nvidia does better on Linux than Windows. Unfortunately I am on Windows.
|
|
|
Trying 0.30.17.1 and I know I sound like a broken record.
Deleted everything in appdata but wallet.dat, config and back up.
Started wallet at least 30 times and it just force closes without running.
Going back to 0.30.17 and hope it works.
At me works ... I am on Windows 7 64 bit. What OS are you running? Edit: I seen it is Windows 64 build. Edit 2: Maybe I have bad nodes. Is there a current list of working nodes. I have a ton in my config file. Window 10 64 bit Windows 2012 Server 64 bit 82.211.1.181:8877 91.230.123.101:8877 41.191.238.189 Thanks, Got 1 connection so far but it is downloading the blockchain again.
|
|
|
Trying 0.30.17.1 and I know I sound like a broken record.
Deleted everything in appdata but wallet.dat, config and back up.
Started wallet at least 30 times and it just force closes without running.
Going back to 0.30.17 and hope it works.
At me works ... I am on Windows 7 64 bit. What OS are you running? Edit: I seen it is Windows 64 build. Edit 2: Maybe I have bad nodes. Is there a current list of working nodes. I have a ton in my config file.
|
|
|
Trying 0.30.17.1 and I know I sound like a broken record.
Deleted everything in appdata but wallet.dat, config and back up.
Started wallet at least 30 times and it just force closes without running.
Going back to 0.30.17 and hope it works.
|
|
|
Wich version is it working in?
You can try to set:
LP_SCANTIME 60
instead of 25 in ccminer.cpp
I'll try and find the version but none of the .60's have worked solo mining for me.
|
|
|
I am still getting the
JSON call failed Invalid parameter submit_upstream_work json_rpc_call failed
while trying to solo mine.
No issues solo mining with any other dev's miner.
Using the exact same bat on all dev's miner and same wallet.
|
|
|
Just curious. Is this the correct wallet to use now? I see the OP still has v0.30.16.x
|
|
|
I am mining on the pool. My PC has a single GPU which is an ASUS AMD R9 290x.
I am getting 22,370kh according to the pool but my GPU isn't making any more noise usual.
How can I be sure it's mining on the GPU and not my inbuilt graphics or something like that?
GPUz is saying the GPU load is ~100% but my hashrate still seems low compared to the others.
With 22 Mh/s that is for sure your GPU and not IGP. You are doing it correct.
|
|
|
Even after adding all the nodes I still get "admin.peers" = null
This coin is still in pre pre pre alpha stage, so, it is normal I had over 20 nodes, woke up this morning and - null Edit: We need pools ASAP, so those problems with loosing all the nodes will not happen Thewre was testing done for what, 3 or 4 days? With the issues that was present then and still at the end of test net period then the coin should have been delayed on launch. it's enought. Most ppl interested by the project (at least miners) mined ETH first. That was a good training... You had several weeks to set-up and test mining on ETH. In fact clone coins are more easy ..see the .bat files I've been mining Eth for the last few weeks. There was NO issue with connections. Not even Shift. I am not the only one on Windows who has connection issues. It has been stated many times.
|
|
|
Even after adding all the nodes I still get "admin.peers" = null
This coin is still in pre pre pre alpha stage, so, it is normal I had over 20 nodes, woke up this morning and - null Edit: We need pools ASAP, so those problems with loosing all the nodes will not happen Thewre was testing done for what, 3 or 4 days? With the issues that was present then and still at the end of test net period then the coin should have been delayed on launch.
|
|
|
Anyone having problems should search on google or ask on the ethereum board. This is the exact same thing as ethereum. different ports and data directory.
Except there was not this mass issue of non working gexp for half the people with Ethereum or Shift at launch. I mined ethereum. There was all kinds of problems. It took me over 24 hours to get ethereum to mine. Hmm. Sorry. I was up and running after reading up. No issues at all with connections or mining. Well the 750ti issue but that is it.
|
|
|
Anyone having problems should search on google or ask on the ethereum board. This is the exact same thing as ethereum. different ports and data directory.
Except there was not this mass issue of non working gexp for half the people with Ethereum or Shift at launch.
|
|
|
command to see block?
and how to add nodes? dont sday i have to write all this to command line
LOL. Just copy this in the console: admin.addPeer("enode://4055ec69e53df4bfecb95e3b65c28e4f2a1145a3bdc4d85d077b552248cf159951afd649f044783bebf48b902fbc0e96978c76236fd4ab3d5ef7d95d72b84ee5@[::]:42786") admin.addPeer("enode://f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e397ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1@74.196.59.103:42786") admin.addPeer("enode://d4ad71ef4251c4d7b07424526dea7a4205b19e24cdb3c44e22ece9e48a38c57f1eb917df67cc93db7a21e9d2aafa016601d0787f200ddac2804608f6c740fe94@[::]:42786") admin.addPeer("enode://6a1e4409f358ba71622f9573d4f1eefd922040c11f860d613a0b6183701bc4a5a9314e98474669473c30efca7d821ae1904e31eb0326579bca34daabe7e01d52@[::]:42786") admin.addPeer("enode://4055ec69e53df4bfecb95e3b65c28e4f2a1145a3bdc4d85d077b552248cf159951afd649f044783bebf48b902fbc0e96978c76236fd4ab3d5ef7d95d72b84ee5@[::]:42786") admin.addPeer("enode://d98e814b2310bef6b07ca6d72b1982938c13702336e9a0c6004a562d6b8c2f5360850df714143c28f65c0d690d90341bbc72f953e232cf5673cc7b7db7fd665c@[::]:42786") admin.addPeer("enode://261da6789b8720fc61a17c532022f9ac8d25c82680caeaf3f68f67e723deac190000847f276dfa9e4ac503b6d8c13bd77aae724b263479cafc8808ede0f1deb9@18.97.7.22:42786") admin.addPeer("enode://2444ddb2aa1c34d55f9b28a1e2b57f1d6c381250776574432381db6984996a2a05f560f0a751443d5a5df4c608a8dc6acc0bdb19bea5905edf643d2c9b44d159@85.217.235.15:63117") admin.addPeer("enode://f3223bf8ea731e569a27318f00f4cc3696ec7d45005604f2731efc21f95028d230671dfc907f44cbed3f7fa0033e1111ffd8f9db1286b3721641d77afd500ade@54.72.197.108:46741") admin.addPeer("enode://15a6ddec7c2e7fc67686557975b41c6308525a69c8ce56747d6ae9c7e9dc8910a4624443ffc127001f72f8f8fca4a67d04906e72d725d7b39dbff4454b8b2b28@68.197.12.14:42786") admin.addPeer("enode://25b8304b5a7977e5478057e5f60f3a7f0da32702f0e5d0174c84ab2a9fb270fb37ef73aba2c682d4283d617e073fdc61e082d7f277474ea64fde055e17d86814@71.62.31.72:49568") Last question from me. Do I add this in the gexp attach console? If so with the gexp closed then run or add with it open and running?
|
|
|
What should the correct port displayed?
42786 or 9656?
|
|
|
Not getting many answers but hopefully this will.
Ran the new gexp but it says connecting to port 42786. Isn't this the test port?
|
|
|
Why not just create this and put it for down load for those of us who don't know how so we have a working gexp.exe to start mining?
|
|
|
|