[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/rsnel/geistgeld.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "geistgeld_dirty_fix"] remote = origin merge = refs/heads/geistgeld_dirty_fix
Yup, that's the same as mine, so at least I'm using the right one. The main problem I have with p2pool that isc specific to GeistGeld is that until I get GeistGeld's difficulty high enough p2pool makes so many requests to it so fast that the operating system runs out of connection handles, then p2pool cannot open connections to anything.
Exactly what I'm experiencing too. This would be solved of course if umpteen people all merged it.
Maybe a synchronized mining start would solve this? It never occurred to me to try cpu mining it actually.........interesting.
|
|
|
Silicon Valley Bank are scared. Good. They should be.
|
|
|
The Bitcoin Foundation is FAIL.
Can we get rid of it now please? Everyone pretty much ignores it anyway.......corrupt as banks.
|
|
|
As req I deleted the unnecessary duplicate repo on github & renamed my fork of the other Groupcoinmaster
I edited my posts in the thread here with updated url's since when you rename a repo those url's are no longer valid.
Cheers :-)
That's great work, thanks! Would you be at all interested in having a look at the Geistgeld (XGG) client? I've been trying to get it running with my merge mining p2pool node for yonks, I eventually managed to get it compiled & running, but it sends my memory usage into overload & eventually clogs the system up. It's a shame not to use it...... Any ideas or suggestions would be very much appreciated - it's beaten me
|
|
|
The logo was actuallay pretty cool One of the best I've seen around imo. Would be cool to see some life back into it. We can all wish Yeah, the website is good too - it's strange that they put so much work into the project then immediately abandon it......
|
|
|
Hmmmm....no git repo either. Dev?
|
|
|
Nice coin. Needs to be merge-mined though, then it'll take off....... No?
|
|
|
Heads up: So, including BTC, I'm currently merge mining 11 coins BTC, DVC, FSC, HUC, I0C, IXC, NMC, GRP, UNO, CLC & WLC........any more for any more? I never did get XGG to work properly with p2pool, memory usage went crazy, so if anyone has any hints/fixes - I'd like to make it 12........ Fun, fun, fun.
|
|
|
My bitcoind GetBlockTemplate latency is really suffering - I presume it's due to the clown who decided to "stress test" the network with spam?
|
|
|
Nice to see another merge mined coin, I've been mining it for a while on my p2pool node - it works fine - well done. I do have a question about the bazzilions of decimal places in the balance though: getinfo { "version" : 80600, "protocolversion" : 70001, "walletversion" : 60000, "balance" : "8206.0083846990987625179393583826274058742443295808063063762878395151934444713440696371475890913416151306591928005218505859375", "blocks" : 14974, "timeoffset" : 0, "connections" : 3, "proxy" : "", "difficulty" : 938786.76126016, "testnet" : false, "keypoololdest" : 1435633098, "keypoolsize" : 101, "paytxfee" : "0.00", "errors" : "" }
Can it be tidied up a notch - or is this by design? Interesting website too - you've done your homework. Merge mine on!
|
|
|
Since the last update (20 hours ago) I'm unable to build the client on Xubuntu 64bit. When I execute the command "make -f Makefile" from within the c++ folder - I get the following error: yasm -f x64 -f elf64 -X gnu -g dwarf2 -D LINUX -o crypto/sha256_code_release/sha256_avx2_rorx2.a crypto/sha256_code_release/sha256_avx2_rorx2.asm make: yasm: Command not found make: *** [crypto/sha256_code_release/sha256_avx2_rorx2.a] Error 127 Do I need to download & install dependences now? You need to install yasm, as the error indicates :p Yeah, I figured that was what I needed - just wanted to be sure. All good again, thanks for your work, great stuff
|
|
|
Since the last update (20 hours ago) I'm unable to build the client on Xubuntu 64bit. When I execute the command "make -f Makefile" from within the c++ folder - I get the following error: yasm -f x64 -f elf64 -X gnu -g dwarf2 -D LINUX -o crypto/sha256_code_release/sha256_avx2_rorx2.a crypto/sha256_code_release/sha256_avx2_rorx2.asm make: yasm: Command not found make: *** [crypto/sha256_code_release/sha256_avx2_rorx2.a] Error 127 Everything worked fine until the last update EDIT: The pre-compiled binary will also not run on 64bit system, giving the following error: relaynetworkclient: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by relaynetworkclient)
Do I need to download & install dependences now? EDIT2: I've reverted to the previous build until further news sudo apt-get install yasm
Once it's installed just run make and it'll compile just fine. Hi JB, Yeah, I saw the comment on Matts thread about it. I figured that was what was needed, but just wanted to be sure, as I'd not needed it on previous builds. It's running great again now though - thanks You will be lucky if forrestv reappears in this community, he was attacked in this thread over some seriously ignorant attitudes toward his development of this software. He has not returned since, rightly so.
I'm aware of what happened previously, I've read the entire thread & am continually re-reading sections for info. There's no reason to keep harping on about what happened - posting negative, butthurt comments is neither constructive nor helpful to anyone. Please get over it & accept it like everyone else has, including forrestv who is posting here again, thankfully.
|
|
|
Since the last update (20 hours ago) I'm unable to build the client on Xubuntu 64bit. When I execute the command "make -f Makefile" from within the c++ folder - I get the following error: yasm -f x64 -f elf64 -X gnu -g dwarf2 -D LINUX -o crypto/sha256_code_release/sha256_avx2_rorx2.a crypto/sha256_code_release/sha256_avx2_rorx2.asm make: yasm: Command not found make: *** [crypto/sha256_code_release/sha256_avx2_rorx2.a] Error 127 Everything worked fine until the last update EDIT: The pre-compiled binary will also not run on 64bit system, giving the following error: relaynetworkclient: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by relaynetworkclient)
Do I need to download & install dependences now? EDIT2: I've reverted to the previous build until further news
|
|
|
I'm running it for a few hours now - can't say I'm sure if there's any difference tbh, looks like a small code tidy up is all. It would be nice if forrestv chimed in when he updated any p2pool code to let us know what the changes are exactly - if any. Aren't we due a block or two?
|
|
|
Is anyone using the Avalon 4.1's with p2pool? I'm interested in how they perform........
Tak.
Nobody using these with p2pool? Well, that's a shame. I was thinking of buying a couple of these, but it's a bit of a risk to splash out the BTC they are charging only to find out they don't work properly with p2pool.... I know they say their firmware supports p2pool, but they're just too expensive to risk finding out for sure. Guess I'll stick with 2nd hand spondoolies gear then - getting a little thin on the ground now though......
|
|
|
Is anyone using the Avalon 4.1's with p2pool? I'm interested in how they perform........
Tak.
Nobody using these with p2pool?
|
|
|
The antpool code, like their firmware & p2pool code, is a complete mess & should be avoided at all costs. Ask any experienced pool dev/coder. Only a Bitmain employee would say such a thing Yes, their track record in the coding department is appalling I'm afraid, as are many of their claims, as I & others have touched upon elsewhere: Thank you -ck & kano for chiming in, your experience & knowledge is greatly appreciated I've read a lot about this subject throughout the thread, it seems to me that bitmain are actually working against p2pool, despite their claims in their pool thread that they actively support it: We support p2pool protocol
.....and has been significantly developed during the development of Antpool.
This is simply not true. Shouldn't forum rules/admins require them to change this statement? Doing so would also save a lot of confusion for new users of p2pool who wonder why they can't get the most out of their bitmain hardware while using p2pool. They seem to be trying to transfer p2pools unique decentralised nature for their own marketing needs - despite being an obviously centralised pool. As bitmain refuse to fix their firmware (or more likely - they're unable/don't know how to), I'd be more than willing to chip in towards a bounty for a revised & fully functional S5 firmware for p2pool - if kano/-ck would be willing? The S5's are still being sold, & will remain workable for a while yet I think, so it would certainly boost p2pools attractiveness to new users if they could simply connect & mine like any other pool. What do you think? Tak. I've posted quite a few times in their thread asking them to remove the references to p2pool. They don't. Thankfully one of the mods (I believe it was -ck) changed their thread title to get rid of the bogus "supporting decentralization" claim it spouted. I completely disagree with dogie's statements about it being a "lost in translation" thing. Bitmain took forrest's code and added some database stuff to it. They didn't create their own implementation, or attempt to fix any of the variance problems. Whatever they did was certainly not the $100,000s effort claimed, and they abandoned it since they realized they didn't know what they were doing.$100,000's.......... I'd hazard a guess that this is one of the reasons why eleuthria didn't recommend them, & rightly so.
|
|
|
No tweaking here. Two production units out of the box. No down time for 6 months. Overclocked to 1.25TH/s.
If that's the case, & you're using bitmains cgminer - you're losing potential earnings. You should use kano's cgminer for the S5 instead as mentioned a page or so back Edit: Just a heads up - Matt Corello has released an updated version of his excellent relaynodeclient with some huge performance improvements - p2pool users can benefit greatly by using his software: http://bitcoinrelaynetwork.org/https://github.com/TheBlueMatt/RelayNodeNice stuff Matt
|
|
|
|