Topic: [ANN] [VOYA] Voyacoin - [PLUCK][Just Launched] The return of profitable mining! - page 8. (Read 23963 times)
February 21, 2015, 08:27:23 PM
The miner from my pool with username matrix100 check your miner you submit low difficulty share and the stratum will ban you
February 21, 2015, 08:20:21 PM
It is good for solominers, when Oceminer is not around! Right Shadow ? 
LOL. Yeah. I'm still trying to solo.
February 21, 2015, 08:17:54 PM
Coinminers is up and running
Good work!
It is good for solominers, when Oceminer is not around! Right Shadow ?
February 21, 2015, 08:14:46 PM
Coinminers is up and running
Solo is end now...
February 21, 2015, 08:13:04 PM
February 21, 2015, 08:12:55 PM
Coinminers is up and running
February 21, 2015, 08:12:44 PM
We appologize for the upset, but when we transferred to github permissions and files got excluded. We are truly sorry but the network itself is working fine and the Windows QT wallet was working from the start.
Github has been updated to reflect these changes and should compile fine now.
The block rewards at start were 0, so no instant mining could be done.
Github has been updated to reflect these changes and should compile fine now.
The block rewards at start were 0, so no instant mining could be done.
On Arch, I had to make the scripts executable, otherwise the compiler gave permission errors:
chmod +x {autogen.sh,share/genbuild.sh,src/leveldb/build_detect_platform}
Then it quit after building the tests, so I only managed to compile the daemon and client.
Code:
test/bloom_tests.cpp: In member function ‘void bloom_tests::bloom_create_insert_key::test_method()’:
test/bloom_tests.cpp:89:5: error: ‘CSupcoinSecret’ was not declared in this scope
CSupcoinSecret vchSecret;
^
In file included from /usr/include/boost/test/unit_test.hpp:19:0,
from test/bloom_tests.cpp:19:
test/bloom_tests.cpp:90:17: error: ‘vchSecret’ was not declared in this scope
BOOST_CHECK(vchSecret.SetString(strSecret));
^
test/bloom_tests.cpp:92:16: error: ‘vchSecret’ was not declared in this scope
CKey key = vchSecret.GetKey();
^
Makefile:5615: recipe for target 'test/test_test_voyacoin-bloom_tests.o' failed
make[2]: *** [test/test_test_voyacoin-bloom_tests.o] Error 1
make[2]: Leaving directory '/src/Voyacoin/src'
Makefile:6241: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory /src/Voyacoin/src'
Makefile:568: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
February 21, 2015, 08:09:36 PM
Strange... I don't have many orphans... 
What miner you are using guys?
I'm using ccminer30 from djm34.
What miner you are using guys?
I'm using ccminer30 from djm34.
February 21, 2015, 08:06:57 PM
Not sure. I guess my wallet doesn't receive relevant information in time from peers so all my machines keep solving old blocks. I have 119 coin wallets which I all mined at some point yet I've never seen this many orphans.
Dude, seems like you maked a fork with many machines...
In case of a fork I'd be finding blocks on the forked chain.
February 21, 2015, 08:06:35 PM
lol , nice coin dev the orphans are endless
February 21, 2015, 08:05:55 PM
I give up on this amateur nonsense. Found 1 real block and 140+ orphans while the nodes are going for as long as minutes without relaying any data whatsoever. Unfortunately the debug.log doesn't include orphans to show.
HOW it can be 140 orphans if blocks count is 72?
What's your bandwith?
I have only 9 boooo.
http://img.sc/img/7ff0dd8bb25eaaa7e6f67d6f1328989a.png
Not sure. I guess my wallet doesn't receive relevant information in time from peers so all my machines keep solving old blocks. I have 119 coin wallets which I all mined at some point yet I've never seen this many orphans.
We can't see any orphans produces, seed node has 5 connections currently so there shouldn't be any problems.
February 21, 2015, 08:05:41 PM
Not sure. I guess my wallet doesn't receive relevant information in time from peers so all my machines keep solving old blocks. I have 119 coin wallets which I all mined at some point yet I've never seen this many orphans.
Dude, seems like you made a fork with many machines...
February 21, 2015, 08:04:15 PM
I give up on this amateur nonsense. Found 1 real block and 140+ orphans while the nodes are going for as long as minutes without relaying any data whatsoever. Unfortunately the debug.log doesn't include orphans to show.
HOW it can be 140 orphans if blocks count is 72?
What's your bandwith?
I have only 9 boooo.
Not sure. I guess my wallet doesn't receive relevant information in time from peers so all my machines keep solving old blocks. I have 119 coin wallets which I all mined at some point yet I've never seen this many orphans.
February 21, 2015, 08:03:43 PM
maxminers any chance you could have another go at compiling? my miners are all still pointed at your pool
thx
thx
February 21, 2015, 07:59:29 PM
We appologize for the upset, but when we transferred to github permissions and files got excluded. We are truly sorry but the network itself is working fine and the Windows QT wallet was working from the start.
Github has been updated to reflect these changes and should compile fine now.
The block rewards at start were 0, so no instant mining could be done.
Github has been updated to reflect these changes and should compile fine now.
The block rewards at start were 0, so no instant mining could be done.
Yep.
{
"blocks" : 76,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00028650,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 318,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespersec" : 0
}
February 21, 2015, 07:57:54 PM
We appologize for the upset, but when we transferred to github permissions and files got excluded. We are truly sorry but the network itself is working fine and the Windows QT wallet was working from the start.
Github has been updated to reflect these changes and should compile fine now.
The block rewards at start were 0, so no instant mining could be done.
Github has been updated to reflect these changes and should compile fine now.
The block rewards at start were 0, so no instant mining could be done.
February 21, 2015, 07:55:18 PM
I give up on this amateur nonsense. Found 1 real block and 140+ orphans while the nodes are going for as long as minutes without relaying any data whatsoever. Unfortunately the debug.log doesn't include orphans to show.
HOW it can be 140 orphans if blocks count is 72?
What's your bandwith?
I have only 9 boooo.
February 21, 2015, 07:52:34 PM
I give up on this amateur nonsense. Found 1 real block and 140+ orphans while the nodes are going for as long as minutes without relaying any data whatsoever. Unfortunately the debug.log doesn't include orphans to show.
February 21, 2015, 07:45:37 PM
No,no it's Voyacoin!
February 21, 2015, 07:44:34 PM
{
"blocks" : 67,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024743,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 224,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespersec" : 0
}
For GTX 770
ccminer30.exe -R 1 -a pluck --throughput 0.8 -f 1 -o http://127.0.0.1:7755 -u solo -p pass
"blocks" : 67,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024743,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 224,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespersec" : 0
}
For GTX 770
ccminer30.exe -R 1 -a pluck --throughput 0.8 -f 1 -o http://127.0.0.1:7755 -u solo -p pass
Jump to: