Any more merge mine pools? Would be nice to keep a list.
Working fine with p2pool - I'm sure there are many nodes now merge mining MYR
Topic: [ANN][XMY] Myriad | Multi-Algo, Fair, Secure - page 74. (Read 850023 times)
Working fine with p2pool - I'm sure there are many nodes now merge mining MYR
Any more merge mine pools? Would be nice to keep a list.
We've moved MYR over to AUXPoW on our SHA256 ports on www.xpool.ca and is working as expected.
http://www.xpool.ca/blocks/MYR
Cheers!
http://www.xpool.ca/blocks/MYR
Cheers!
I've just pushed a fix to the myriadteam repository that fixes the issues with chain id's. We were supplying 0 as the chain id for auxpow rpc calls, instead of the intended value (90).
See https://redd.it/3mjp7c and https://github.com/myriadteam/myriadcoin/commit/e0a30bf8f7ee533c004040c85369cf457f12d36f
Note - this is only needed for merge mining pool operators. it will be included in a future release for all.
See https://redd.it/3mjp7c and https://github.com/myriadteam/myriadcoin/commit/e0a30bf8f7ee533c004040c85369cf457f12d36f
Note - this is only needed for merge mining pool operators. it will be included in a future release for all.
Thank you for the quick fix, much appreciated!
Seems as if it resolved my problems - first blocks have been found with scrypt merged mining here now
I've just pushed a fix to the myriadteam repository that fixes the issues with chain id's. We were supplying 0 as the chain id for auxpow rpc calls, instead of the intended value (90).
See https://redd.it/3mjp7c and https://github.com/myriadteam/myriadcoin/commit/e0a30bf8f7ee533c004040c85369cf457f12d36f
Note - this is only needed for merge mining pool operators. it will be included in a future release for all.
See https://redd.it/3mjp7c and https://github.com/myriadteam/myriadcoin/commit/e0a30bf8f7ee533c004040c85369cf457f12d36f
Note - this is only needed for merge mining pool operators. it will be included in a future release for all.
great job on the quick fix =)
I've just pushed a fix to the myriadteam repository that fixes the issues with chain id's. We were supplying 0 as the chain id for auxpow rpc calls, instead of the intended value (90).
See https://redd.it/3mjp7c and https://github.com/myriadteam/myriadcoin/commit/e0a30bf8f7ee533c004040c85369cf457f12d36f
Note - this is only needed for merge mining pool operators. it will be included in a future release for all.
See https://redd.it/3mjp7c and https://github.com/myriadteam/myriadcoin/commit/e0a30bf8f7ee533c004040c85369cf457f12d36f
Note - this is only needed for merge mining pool operators. it will be included in a future release for all.
Yup. SHA256 
Um, so, is anyone successfully merge mining??
Fixed...myriad is using the notation 192.168.*.* instead of 192.168.0.0/16 for .conf.
2015-09-26 10:59:36.833000 > Error while calling merged getauxblock on http://192.168.0.1:10889:
..
2015-09-26 10:59:36.833000 > twisted.web.error.Error: 403 Forbidden
..
2015-09-26 10:59:36.833000 > twisted.web.error.Error: 403 Forbidden
You might try to restart the wallet, I had similar messages in my pools log before I restarted myriadcoind today. Or try
myriadcoin-cli getauxblock
and see if you get an auxblock template or an error.
I tried merge mining MYR with scryt this morning after block was > 1402000, hower I am getting errors when I find blocks:
Is anybody successfully merge-mining MYR? Do I need more in the conf than "algo=scrypt" now?
Thanks
Code:
2015-09-26 11:02:08 ERROR: Aux POW parent has our chain ID
2015-09-26 11:02:08 ERROR: AUX POW is not valid
2015-09-26 11:02:08 ERROR: AUX POW is not valid
Is anybody successfully merge-mining MYR? Do I need more in the conf than "algo=scrypt" now?
Thanks
I could not get it to merge mining scrypt either (using p2pool). I am successfully merge mining Doge, SYS, and VIA.
Error:
Code:
2015-09-26 10:59:36.833000 > Error while calling merged getauxblock on http://192.168.0.1:10889:
...
2015-09-26 10:59:36.833000 > twisted.web.error.Error: 403 Forbidden
...
2015-09-26 10:59:36.833000 > twisted.web.error.Error: 403 Forbidden
I tried merge mining MYR with scryt this morning after block was > 1402000, hower I am getting errors when I find blocks:
Is anybody successfully merge-mining MYR? Do I need more in the conf than "algo=scrypt" now?
Thanks
Code:
2015-09-26 11:02:08 ERROR: Aux POW parent has our chain ID
2015-09-26 11:02:08 ERROR: AUX POW is not valid
2015-09-26 11:02:08 ERROR: AUX POW is not valid
Is anybody successfully merge-mining MYR? Do I need more in the conf than "algo=scrypt" now?
Thanks
Latest git will disconnect versions less than 0.9.2.16
Also, try deleting your peers.dat file. Running fine here.
Also, try deleting your peers.dat file. Running fine here.
Yea, I guess I updated bot daemon and forgot to do home one. Doh! Reindexing now
Latest git will disconnect versions less than 0.9.2.16
Also, try deleting your peers.dat file. Running fine here.
Also, try deleting your peers.dat file. Running fine here.
Quote
Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues.
Seems like most people are updated, but getting this message from myriadcoind. Is there a way to check hash on old fork v. hash on new fork?
If you're having issues syncing with 0.9.2.16:
in src/version.h, change:
to:
I would imagine there will be a future update to make this official...
in src/version.h, change:
Code:
static const int MIN_PEER_PROTO_VERSION = 70002;
to:
Code:
static const int MIN_PEER_PROTO_VERSION = 70003;
I would imagine there will be a future update to make this official...
Happy hard fork day everyone
Just a quickie - I have already performed a reindex with the latest client, will I have to reindex again after block 1400000 or can I just sit back & watch it happen?
You should be fine if you're using v0.9.2.16.
Cool, thanks.....
Happy hard fork day everyone
Just a quickie - I have already performed a reindex with the latest client, will I have to reindex again after block 1400000 or can I just sit back & watch it happen?
You should be fine if you're using v0.9.2.16.
Happy hard fork day everyone
Just a quickie - I have already performed a reindex with the latest client, will I have to reindex again after block 1400000 or can I just sit back & watch it happen?
Happy hard fork day everyone
Jump to: