This was a nice surprise to see when I logged in.
Thanks for running this for so long.
1PVxnBfNZqmrpskVQvXEf8pzSvJSTnD37h
|
|
|
I've updated bitcoind (and bitcoin-cli) to version 0.9.0! It builds on Mavericks easily.
I'm still working on the --with-coinpunk flag.
|
|
|
I've updated https://github.com/WyseNynja/vanitygen with 2 bug fixes reported on GitHub. If you already have vanitygen installed from my OSX homebrew tap: brew update brew prune brew upgrade vanitygen
If you don't: brew tap WyseNynja/bitcoin brew prune brew install vanitygen
|
|
|
kernel file calc_address.cl is erroring when opening, apparently, any solution? "calc_address.cl"
On windows, using the oclvanitygen executable
I got that on OSX when it tried to build the .oclbin file (which it does on first run if the file does not exist) without being in the same directory as calc_address.cl. I'm not sure how to resolve this on windows, but in OS X, that file is installed by my brew tap to /usr/local/opt/vanitygen/include/ nevrending I think the -D flag you are using is wrong. Try this, brew reinstall vanitygen cd /usr/local/opt/vanitygen/include oclvanitygen -d 1 -k 1111111
|
|
|
samr7 doesn't seem to have touched his repo in a while. I went ahead and forked his repo and merged in pretty much all the public branches on github. I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things. https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now. I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red. It worked for me on Mavericks and it uses brew's openssl. I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching. Hi. I'm getting the following error MacBookLive:vanitygen y458m$ oclvanitygen -D 0:1 -k 1111111 Difficulty: 281474976710656 Compiling kernel, can take minutes...vg_ocl_context_callback error: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: Build Program driver returned (517) vg_ocl_context_callback error: OpenCL Warning : clBuildProgram failed: could not build program for 0x1021b00 (ATI Radeon HD 6750M) (err:-2) vg_ocl_context_callback error: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log: Error returned by cvms_element_build_from_source
failure. clBuildProgram: CL_BUILD_PROGRAM_FAILURE Build log: Error returned by cvms_element_build_from_source Device: ATI Radeon HD 6750M Vendor: AMD (1021b00) Driver: 1.2 (Sep 19 2013 22:22:06) Profile: FULL_PROFILE Version: OpenCL 1.2 Max compute units: 6 Max workgroup size: 256 Global memory: 536870912 Max allocation: 134217728 Could not open device '0:1', ignoring Available OpenCL platforms: 0: [Apple] Apple 0: [Intel] Intel(R) Core(TM) i7-2675QM CPU @ 2.20GHz 1: [AMD] ATI Radeon HD 6750M How can I resolve this? Thanks Hmm. I'm not really sure. I don't have a mac with a graphics card and haven't been able to test the opencl pieces I made an issue on github, lets continue this conversation there. https://github.com/WyseNynja/vanitygen/issues/2samr7 doesn't seem to have touched his repo in a while. I went ahead and forked his repo and merged in pretty much all the public branches on github. I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things. https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now. I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red. It worked for me on Mavericks and it uses brew's openssl. I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching. I see you pulled in (among other things) my compressed-key fixes. I spend most of my time in Linux, but I had a request come through for a Windows build. After tinkering with the makefile a bit, I got Visual C++ 2008 to build vanitygen. The result is here: https://dl.dropboxusercontent.com/u/57535575/vanitygen-0.23-red-win32.zipoclvanityminer is not included, as libcurl was built against a different OpenSSL DLL than what was used for building the other tools. If you need oclvanityminer, set up a Linux box...building from source on Linux is much easier than building from source on Windows. vanitygen, oclvanitygen, and keyconv have been built. Thanks for the fixes If you submit a patch for the Makefile, I'll probably merge it in, too. samr7 doesn't seem to have touched his repo in a while. I went ahead and forked his repo and merged in pretty much all the public branches on github. I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things. https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now. I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red. It worked for me on Mavericks and it uses brew's openssl. I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching. Do you have a precompiled OSX build of Vanitygen? I can upload the one that I've built on my laptop. No guarantees it's portable though.
|
|
|
Greetings. According to oclvanitygen.c : '"By default, <pattern> is interpreted as an exact prefix.\n"' But is there any possibility to use the vanitygen on an OpenCL device to find address not only by prefix, but, for example, by suffix or postfix or regex.
For example not like "1Love.*" but like "1.*Love"?
I think it would be possible, but I know regex would be a lot slower.
|
|
|
Hi forrestv and all contributors of p2pool,
Many thanks to this fantastic mining pool. It's really fun to tuning p2pool to maximize miner's income for geeky users like me.
But I wonder if you have any plan to enable IPv6 support of p2pool? Since official bitcoin client has IPv6 enabled by default, I think enabling IPv6 support will make p2pool network even more pervasive and well connected. More importantly, IPv6 will help those users with both v4 & v6 network, but behind firewall or NAT in v4 network, just like me. I do have a very good connectivity to v6 network and can accept income connections. But v4 network is NATed with high latency, and I think that might be the source of my high orphan rate.
I have checked that twisted library used in p2pool support IPv6 network, at least partially. I'm not familiar with python, so I don't know for sure. I wonder if it is possible to enable IPv6 network in p2pool?
Thanks again to this great mining pool. :-)
I'm all for IPv6, but will adding IPv6 support be enough for you? I think you will still likely need to talk to IPv4 peers for a while since I doubt everyone in the pool can make the switch.
|
|
|
samr7 doesn't seem to have touched his repo in a while. I went ahead and forked his repo and merged in pretty much all the public branches on github. I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things. https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now. I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red. It worked for me on Mavericks and it uses brew's openssl. I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.
|
|
|
And for usability, I think it should say "Fast use for Internet transactions." I can hand you a paper wallet pretty quickly if we are next to each other I don't know. Getting a paper wallet from someone doesn't seem transacted until the coins are removed from it. Who knows who else may have seen it or have a copy of it. Until exclusive control of the coins it contains is established, is it a completed transaction? That's reasonable. Although it takes virtually no time to sweep a wallet, and then the transaction is completed. The funds aren't in a paper wallet anymore, but the transaction is complete and it can be fast. I still think this should say "Fast use for Internet transactions." Also, what stops a USB Flash drive from being BIP 32? Seems like it should be "possible"
|
|
|
I'm not quite sure your comparison chart is fair to paper wallets. With split keys (Armory) or encrypted keys (BIP38) they should be at least a "possible" in a couple more categories. I'd also say "Phishing protection" is "n/a" for paper wallets since you have "no" for transaction signing. And why is BIP32 not listed under paper backup? You have the Trezor listed as "yes" for BIP32 and "yes" for disaster recovery saying it uses a paper wallet, so it seems like BIP32 should be "possible" for paper wallet. And for usability, I think it should say "Fast use for Internet transactions." I can hand you a paper wallet pretty quickly if we are next to each other That said, I'm super excited for my Trezor!
|
|
|
I stopped mining awhile ago, but I've left my p2pool node up. It's averaged 36 peers in the last year and it's bitcoind node is well connected. It has a high speed internet connection and has had excellent uptime.
Is a node like mine actually helpful for p2pool? I'm assuming that having a well connected node is good for spreading transactions and protecting p2pool from some kind of network attack. Am I right, or is a non-mining node not helpful? It's just a git pull and a restart ever now and then, so it's not much effort.
If a non-mining node is helpful, is there anything else I can do to make it more useful? Maybe set the max connections to something a lot higher so the pool sees more transactions? I'm just guessing.
|
|
|
OS X app crashes for me on Mavericks after a few minutes of use, too
|
|
|
I've updated the tap to install bitcoind 0.8.5. It only works on mavericks if you install with `brew install wysenynja/bitcoin/bitcoind --HEAD`
I expect 0.8.6 to work with Mavericks without issue.
|
|
|
I can't manage to get bitcoind built on OSX 10.9 My tap ( https://github.com/WyseNynja/homebrew-bitcoin) doesn't seem to be working anymore. I've downloaded the official bitcoin-qt binary and am getting the blockchain with it now.
|
|
|
I'm testing out the .app now. Awesome work! I haven't had any time to play with Armory recently. Hopefully bitcoind works for me without crashing and corrupting the block chain like it was last time I tried bitcoin on OSX.
|
|
|
Congrats. Love to see Armory live up to its full potential. Grats! I'm excited to see the project move forward like this.
|
|
|
Got word back from the university. Unfortunately, if a club wants to take donations it has to go through a web page on the university site. We can't have deposits going directly into the chapter's bank account. Side note: Legally, SSDP consists of two separate, distinct entities – Students for Sensible Drug Policy Foundation and Students for Sensible Drug Policy Inc. The former, as a 501(c)3 organization, engages in education and outreach. Donations to SSDP Foundation are tax-deductible. SSDP Inc, as a 501(c)4 organization, engages in advocacy, or attempts to effect change to law and policy. Accordingly, donations to SSDP Inc are not tax-deductible...
|
|
|
|