Show Posts
|
Pages: [1] 2 3 4 »
|
I have not added any checkpoint reset (or ignore, whatever) to maxcoin.conf file but now I'm wondering if valid checkpoint was added after hard-fork point at all. Also, how many valid checkpoints were added to Maxcoin by now? For reference, Bitcoin developers are adding checkpoints with every few wallet updates.
You're talking over my pay grade, but, I did maxcoin-qt -reindex last night using the intermediate fix version (maxcoin-qt-0.9.3) and all is good ever since. The latest maxcoin-qt (-9.3.1) is performing flawlessly so far. 18:16:12  getinfo 18:16:12  { "version" : 90301, "protocolversion" : 70005, "walletversion" : 60000, "balance" : not enough 8-} "blocks" : 620753, "timeoffset" : 0, "connections" : 4, "proxy" : "", "difficulty" : 10319.99134975, "testnet" : false, "keypoololdest" : 1391863498, "keypoolsize" : 104, "paytxfee" : 0.00000000, "errors" : "" } I do have enforcecheckpoint=false at the end of my maxcoin.conf, as recommended.
|
|
|
So, Weblogin.Worker is just my payment address? *edited* Ah. Never mind. I see. It works like nuts2pools. Trying suprnova now...
|
|
|
Thanks. Is it maintaining synchronisation with the network.
Don't know about ocminer, but maxcoin-qt-0.9.3 is sync'ing OK here. Brilliant news. Thanks for the feedback. I don't know what ocminer means when he reports "very low hashrate," but both 1gh and dwarfpool are finding coins for me this morning at about 1/4 normal speed. on suprnova there are only 3-4 miners which give very low hashrate, thats i meant. Right now I'm using only one computer with a 260X, hash rate 160 MH/s, but if you will PM me with instructions for how to get on using cgminer-3.7.3 I'll try suprnova. *edit* Specifically, what do I need to put in for Weblogin.Worker on my cgminer command line?
|
|
|
Thanks. Is it maintaining synchronisation with the network.
Don't know about ocminer, but maxcoin-qt-0.9.3 is sync'ing OK here. Brilliant news. Thanks for the feedback. I don't know what ocminer means when he reports "very low hashrate," but both 1gh and dwarfpool are finding coins for me this morning at about 1/4 normal speed.
|
|
|
Thanks. Is it maintaining synchronisation with the network.
Don't know about ocminer, but maxcoin-qt-0.9.3 is sync'ing OK here.
|
|
|
Yes,my wallet can't sync either,i just can't figure out what happened.Dose the dev alive or can someone help me fix this situation?
Try the "resetcheckpoint / getcheckpoint" combination followed by letting maxcoin-qt re-sync as described at http://maxcoinnews.net/maxcoin-0-9-2-1-release/Worked for me. Also, here is my complete maxcoin.conf: # Seed nodes addnode=maxexplorer.cloudapp.net addnode=max.suprnova.cc # Enable RPC server=1 rpcallowip=*# RPC information rpcuser=<my rpcuser name> rpcpassword=<my rpc password> # Mining gen=0 par=2 enforcecheckpoint=false that part i underlined is a severe security vulnerability and will allow the public to rape your ass for coins. do not EVER use that command in your conf --> rpcallowip=* Please explain. That command is included in the default maxcoin.conf which is supplied with the Linux source code for every version to date, including the present one, maxcoind/maxcoin-qt 0.9.2.1. If what you are saying is true, then the developer is leaving every Linux user wide open to attack. *edit* Oh, OK, I see what you're saying. If someone could take control of my router, theoretically they could send a transfer command to my wallet. Not likely given the type of router security that I have. But I can see your point.
|
|
|
Yes,my wallet can't sync either,i just can't figure out what happened.Dose the dev alive or can someone help me fix this situation?
Try the "resetcheckpoint / getcheckpoint" combination followed by letting maxcoin-qt re-sync as described at http://maxcoinnews.net/maxcoin-0-9-2-1-release/Worked for me. Also, here is my complete maxcoin.conf: # Seed nodes addnode=maxexplorer.cloudapp.net addnode=max.suprnova.cc # Enable RPC server=1 rpcallowip=* # RPC information rpcuser=<my rpcuser name> rpcpassword=<my rpc password> # Mining gen=0 par=2 enforcecheckpoint=false
|
|
|
My maxcoin-qt (Linux, 9.2.1) was working fine for about 12 hours but hasn't sync'ed since block 610003, about an hour ago (the wallet currently estimates we're at block 610142 and has 11 active connections).
I've been paid by 1gh.com during this time, but my wallet isn't showing it.
*edit*: OK, trying resetcheckpoint/getcheckpoint and letting the wallet re-sync... *edit again* yep, resetcheckpoint/getcheckpoint and letting the wallet re-sync worked. It is once again current and up-to-date.
Wonder why it froze up at block 610003 like that?
|
|
|
So, has *anybody* of the Penguin persuasion succeeded in compiling the new wallet?
If yes, then what Linux are you using?
And, have you in any way modified (or updated) boost, php, and/or openssl along the way?
Compiles fine on a stock Ubuntu 13.10 machine. It has all of the boost libraries installed (aka "libboost-all-dev" v1.42-v1.53) and openssl 1.0.1e Aha. Thanks muchly for the clue. Finally got maxcoind and maxcoin-qt v0.9.2.1-g8c5e74e-beta to compile, using boost-1.55 (compiled from scratch, that is, bjam and b2) and openssl-1.0.1i (compiled as per LFS). The trick is to add -no-ssl2 in the config line when compiling openssl-1.0.1i. And then you need to do make depend before you do make. I gather that the standard Ubuntu build of openssl already does all that for you. If you are compiling openssl-1.0.1e, which is vulnerable to the Heartbleed attack, then you would have to insert -DOPENSSL_NO_HEARTBEATS in the CFLAGS line of the generated Makefile, after you do the config but before you do the make. Or in the DEPFLAGS line, I forget which --um, heck, just add it to both, to be safe. Thanks again for the clue. Man, this new logo sucks donkey dicks, doesn't it.
|
|
|
So, has *anybody* of the Penguin persuasion succeeded in compiling the new wallet?
If yes, then what Linux are you using?
And, have you in any way modified (or updated) boost, php, and/or openssl along the way?
|
|
|
Hmm...deja vu here...trying without success to compile the new wallet (maxcoind and maxcoin-qt 0.9.2.0) on the same machine and same (heavily modified) Puppy Linux version as I succeeded in compiling 0.9.1.0 on last April.
Both maxcoind and maxcoin-qt fail to make with messages to the effect of like
bitcoinrpc.cpp:
undefined reference to `SSLv2_method' undefined reference to `SSLv2_client_method' undefined reference to `SSLv2_server_method'
These messages are in function `boost::asio::ssl::context::context(boost::asio::ssl::context_base::method)' of build/bitcoinrpc.o
Might help to know what versions of boost and php and openssl you are using. Or, just tell me what distro and version you developed it on. TIA, boraxo
|
|
|
BTW. would anybody be interested in my patch to cpuminer-1gh, optimizing the keccak (3400 to 8100 khash/s on Core i5-2600K)? I guess nobody would care (40 W for 8 Mhash/s), but I was just testing for fun
Sure, I'd be interested. sent patch to Atrides, hopefully gets into 1gh cpuminer. kecasm.patch SHA3-512 checksum d1a2a36620e0b6b392ee6400276a8ede9b08a9ab23e2607ab6e16aeeef50d3ca679ffbcfcb19106 1f1247e1f56d1a6574818b50d7181cda739ff7d0d8aa35963 I have tested the path on one of my old server (64bit, 4core XEON E5405 2GHz with HT) Ohne path: 6600 khash/s With path: 7660 khash/s It means +16% Gibt es etwa Anwendbarkeit an cgminer?
|
|
|
BTW. would anybody be interested in my patch to cpuminer-1gh, optimizing the keccak (3400 to 8100 khash/s on Core i5-2600K)? I guess nobody would care (40 W for 8 Mhash/s), but I was just testing for fun
Sure, I'd be interested. sent patch to Atrides, hopefully gets into 1gh cpuminer. kecasm.patch SHA3-512 checksum d1a2a36620e0b6b392ee6400276a8ede9b08a9ab23e2607ab6e16aeeef50d3ca679ffbcfcb19106 1f1247e1f56d1a6574818b50d7181cda739ff7d0d8aa35963 Nowadays I've graduated from cpu mining to mining on one r9 290X plus three r7 260X's, so would like to check over your patch to see if it is somehow relevant to cgminer.
|
|
|
Found a bug in maxcoin-qt g047adead I have never experienced before: when I change desktop away and back to where maxcoin-qt was, it has disappeared from view! But it's still running and writing happily to log files. Does not show up in alt-tab list, either.
Fedora 20 qt-x11-4.8.5-15.fc20.x86_64 openbox-3.5.2-2.fc20 xorg-x11-server-Xorg-1.14.4-5.fc20.x86_64
BTW. would anybody be interested in my patch to cpuminer-1gh, optimizing the keccak (3400 to 8100 khash/s on Core i5-2600K)? I guess nobody would care (40 W for 8 Mhash/s), but I was just testing for fun
Sure, I'd be interested.
|
|
|
I can see that there are many ways the algorithms for fair work-sharing could be constructed.
So, I'll give each pool 24 hours and see if any gives a significantly higher payout than the others, relative to the overall difficulty during each's trial period.
Your 24 hours started 20 minutes ago.
|
|
|
OK, dwarfpool's at about 1 MAX every 5 hours too. So I guess it isn't your pool's fault, just the whole MAX mining world is getting more crowded and slower.
I'll crank the 290X up to full speed and point the whole 605 Mh/s at maxus.net2pools for 24 hours and see how I do.
|
|
|
Hm. 1gh is only giving about 1 MAX every 5 hours also.
Trying dwarfpool now...
|
|
|
As it happens I am already in talks with a designer for a landing page for the pools and I have scheduled in a (long overdue) service of the mail system but our doge pool has taken up the last couple of days with the fork so we've been a little slow on the support tickets etc.
Oh, and i also added MAX to the support system properly now!
Regards
Nut
Welp, I just mined at maxus.nut2pools for 50 minutes and got .173160 MAX, which implies about 1 MAX every 5 hours. I get about 1 every 3 hours at 1gh or dwarfpool. So, I'll look in from time to time, and if you ever fix your stats I'll give you another try.
|
|
|
Exactly. The other configuration (parallel to the mainboard) has proven to be much less effective (at least in my case... And in my case he he ;-) )
I probably should have mentioned that along with the fan blowing on the top of the cards, I have a 120mm high pressure fan blowing air out of the front of the case. I believe that makes the difference. Tons of heat comes off the rear of the cards and it gets pulled out by that other fan. It probably doesn't help me that the fan in my spanking-new Corsair RM850 power supply died about 70 hours into the MAX-mining. So it is not pulling air out of the case. That's the main reason why I have the case cover off. And an 80 mm muffin fan blowing on the RM850. It's a very efficient PSU, the 80 mm fan blowing on its side is adequate to cool it even when the 290X is going full blast. This weekend I'll have to take it back to Fry's for an exchange.
|
|
|
|