Bitcoin Forum
February 17, 2020, 09:00:50 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 [38] 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 »
741  Economy / Marketplace / Re: Selling 50,000+ BTC at $0.04/BTC on: October 08, 2010, 05:10:01 PM
Do you have any kind of documentation from the USPS to back this up or are you just pulling this out of thin air? Also, can you explain why have I received mail addressed to "B2C, LLC" already?

Either way, I would suggest leaving the name off entirely as I've been told that it's not required.

Addressing to
Bitcoin2Cash, LLC
is different than addressing to
B2C, LLC

right?
742  Economy / Gambling / Re: Dragon's Tale - a Massively Multiplayer Online RPG/Casino on: October 08, 2010, 07:56:08 AM
Come to freenode #dragonstale if you would like to have textual intercourse regarding teh Saturday, October 9, 2:00PM EDT (GMT-0400), 90 minute play session
743  Bitcoin / Project Development / Re: Letter to the EFF on: October 08, 2010, 06:40:26 AM
I had contacted Aaron (EFF's Aaron, not Aaron name changed below) yesterday with the following message:
Quote
Hello Aaron,

Apparently your organization has not produced a response or message to the Bitcoin community regarding and a lack of attention or update is generating a bit of concern.  I have not been included in the emails that have been sent beyond the one below, however, you may see the current status of the community discussion at http://bitcointalk.org/index.php?topic=804.180

Sincerely,
Mizery

Here is their response:
Quote
Hey Aaron* and Mizery. It's taken longer to get back to you than I expected - I apologize for causing any panic.  While we like the idea of incorporating an anonymous donation system with Bitcoin, it's not a small decision for us.  Most of EFF's suppport comes from checks and credit cards so there are pros and cons to consider in adding this. I hope you don't think we left you in the dust! I have the MyBitcoin account info from before and I recently set up a Bitcoin Market account as we will likely exchange these via PayPal later on.

We are currently using the address: 1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt, however the market site states, "CAUTION: ALL BITCOIN ADDRESSES FOR DEPOSITS HAVE CHANGED" and I'm not certain what that means. What am I missing?

Once all the logistics are squared away, we plan to place this on our Ways to Help page and notify our social networks. At this time, it isn't possible to integrate it with our membership donation forms.  Thanks for taking the time to contact us again and for everyone's generosity!

* Bitcoin community member name changed since it is not identical to their forum alias.

My follow-up:
Quote
Hello Aaron,

Thank you for your prompt response.
        
Regarding https://bitcoinmarket.com's cautionary warning, you should not have any concern for it really.  What it means is, if you have previously saved into your address book or other means a Bitcoin address for depositing bitcoins from your client into your Bitcoin Market account, you may want to take caution and to verify that the address is updated since the site owner has establish a new Bitcoin wallet and therefore will not actively monitor previously established addresses.  If you have a Bitcoin Market account you may visit the "Funds" page at https://bitcoinmarket.com/home/funds/ and see a similar notice, warning you to make certain that when you send bitcoins to make sure it is the correct address.  Do keep in mind that http://bitcoinmarket.com is an exchange market and is separate service/site owner from http://mybitcoin.com  Additionally there are other exchange markets besides Bitcoin Market.  You can see which other exchange markets exist by visiting http://bitcoin.org/trade.  Mt. Gox is also popular.

Additionally, do keep in mind that the value of bitcoins are in flux.  About four months ago someone offered 10,000 bitcoins for about us$25 worth of pizza.  Just about two weeks ago 10,000 bitcoins were exchangeable for ~us$650.  About one week ago, 10,000 bitcoins were exchangeable for ~us$580.  Now, 10,000 bitcoins is exchangeable for ~us$709.  It is very likely that the value will increase in the next few days, however, it is not guaranteed.  You should also consider the likelihood that bitcoins will increase in value and for example (this is just an example and may or may not be true at any time), 10,000 bitcoins could be valued at ~us$70,000 or even beyond.  Considering that as bitcoins becomes more successful and used more by the masses, the value will increase, and therefore you may want to consider preserving donations as bitcoins and not to convert or exchange it into usd or another currency.  However, the choice is yours.
        
Sincerely,
Mizery
744  Bitcoin / Bitcoin Discussion / Re: Do You Accept Bitcoin? on: October 07, 2010, 05:54:51 PM
Response from LastPass
Quote
There's no way our average customer is going to download a P2P app to pay - they want to do everything in the browser. We have a hard enough time just getting people to use PayPal.
745  Bitcoin / Mining software (miners) / Re: OpenCL miner for the masses on: October 07, 2010, 08:31:40 AM
Slightly improved kernel (~10%). Fixed a problem with rotate() and Nvidia OpenCL. I won't upload anymore to the forum, please use the repo.

Added to http://www.bitcoin.org/wiki/doku.php?id=repositories
746  Bitcoin / Development & Technical Discussion / Re: Generating Bitcoins with your video card (OpenCL/CUDA) on: October 07, 2010, 08:22:23 AM
The ebuild-9999 is bad, don't use it.

How is it bad?  More importantly, though, without losing focus of my original question, what else do I need to do besides update the makefile?
747  Bitcoin / Development & Technical Discussion / Re: Generating Bitcoins with your video card (OpenCL/CUDA) on: October 07, 2010, 07:38:17 AM
I modified my makefile for bitcoin-9999.ebuild for svn Bitcoin and then
Code:
LC_ALL=C TZ=UTC0 diff -Naur makefile.unix makefile.gentoo > files/bitcoin-9999-Makefile.patch
ebuild bitcoin-9999.ebuild digest
emerge bitcoin

The emerge failed.  What else do I need to do besides update the makefile?
748  Bitcoin / Development & Technical Discussion / Re: Generating Bitcoins with your video card (OpenCL/CUDA) on: October 07, 2010, 06:55:54 AM
puddinpop,

You are in violation of the GPL since you CUDA is linked to the bitcoin source.

I will build a CUDA enabled build of the bitcoin client and post the source code
here.
 
Ken

This doesn't seem correct.  How does GPL come into play when Bitcoin is under MIT license?
749  Bitcoin / Bitcoin Discussion / Re: Do You Accept Bitcoin? on: October 07, 2010, 03:49:50 AM
Bumping this for info...

I came across lastpass.com and liked their service, wanted to use it to save some passwords for my phone. It is $1/mo, so I emailed them and asked if they would consider bitcoin as payment, instead of paypal.

I received a response:

"Thanks for the suggestion - right now this doesn't look very user friendly."

I sent a friendly follow-up, thanking him for his time, saying I respectfully disagree and to please consider bitcoin in the future.

I wrote to Sales Inquiry - LastPass for Consumers with the following:
Quote
A Bitcoin community member posted to Bitcoin forums suggesting they had contacted lastpass.com asking if LastPass would consider accepting Bitcoin as a method of payment.  They continued suggesting that LastPass.com had responded claiming "right now this doesn't look very user friendly."

I would like to understand this response further so as to provide opportunity for Bitcoin to improve so as to become more user friendly in the perspective of LastPass.com.  If you are willing, please elaborate and I will relay this to the community so they may further improve Bitcoin so as to potentially gain wider acceptance.

Thank you.

P.S. http://bitcointalk.org/index.php?topic=909.msg15771#msg15771
750  Bitcoin / Development & Technical Discussion / Re: [PATCH] monitoraddress/blocks on: October 06, 2010, 04:40:41 AM
Code:
$ git checkout -b mybranch origin/monitorreceived
Branch mybranch set up to track remote branch monitorreceived from origin.
Switched to a new branch 'mybranch'
$ git rebase origin/svn
First, rewinding head to replay your work on top of it...
Applying: Clean monitorreceived branch
Applying: Update README.md
Using index info to reconstruct a base tree...
<stdin>:9: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.
Applying: Renaming monitorreceivedbyaddress, adding monitorblocks, listmonitored
Applying: Send proper JSON-RPC syntax, and refactored code a bit
Applying: monitorblocks is working
Applying: Use boost::xpressive for regex support (eliminates linking with regex lib)
Applying: Oops, need to cast command-line params to correct type
Applying: Tweak some code, and tweaked listmonitored a bit
Applying: sendtoaddress return txid instead of 'sent'
Applying: Implemented getblockbyhash/number and gettransaction
Applying: monitoraddress allwallet <url>  to monitor all to-wallet transactions.
Applying: Replace getblockbyhash/number with single getblock that takes hash or number

...now you can build the new code updated to svn...
I do not understand this step.  Did my previous steps update Bitcoin svn code to revision 161?  I do not understand "rebasing."

I am a git newbie and therefore it may be worthwhile or better time spent for someone who is experienced to maintain or produce a patch.  I could learn, but I have other priorities I must tend to.
751  Bitcoin / Development & Technical Discussion / Re: [PATCH] monitoraddress/blocks on: October 06, 2010, 03:13:23 AM
gavin: A question: If I continuously generate a new diff of your source code compared to latest svn repository and claim that as a patch, wouldn't that additionally produce a patch to an outdated or previous version?  e.g. if your patch initially worked with svn 158 (example) and currently latest is svn 500 (example), producing a patch comparing your source to latest svn and making it as a patch would then convert the bitcoin client to be very outdated and similar to svn 158.  This is my understanding.  Is this accurate/true?

As of right now the patch you supplied is not compatible with svn 161 and while I could technically create a diff comparison to generate a new patch, I fear that it will additionally revert changes that are unrelated to monitor functionality and ultimately produce a monitor-specific patch that reverts data not related to monitor capabilities.

Any suggestion on how to proceed in maintaining/preserving updated patch for this feature is appreciated.

gavin: If you are too busy to maintain a patch, perhaps someone could take over?  Is a btc bounty/donation helpful?  I, for one, will offer 5btc towards someone who will actively maintain this patch.

-Update-

Here is my attempt to produce a patch for Bitcoin svn 161:

I have established Bitcoin SVN in /downloads/svn/bitcoin/.
I have established gavin's Bitcoin-git in /downloads/git/bitcoin-git/.

Reviewing gavin's initial patch I know that only the following files are patched:
db.cpp
db.h
init.cpp
main.cpp
main.h
net.cpp
rpc.cpp
rpc.h

So I will generate a diff for only these files and additionally I will manually review each diff to make sure it is similar to gavin's submitted patch and does not include reverting unrelated changes due to further changes in Bitcoin svn.

db.cpp:
LC_ALL=C TZ=UTC0 diff -Napur /downloads/svn/bitcoin/trunk/db.cpp /downloads/git/bitcoin-git/db.cpp
Comparing this diff to gavin's I see
Code:
-        if (pindex->nHeight < 74000 && !mapArgs.count("-checkblocks"))
+        if (pindex->nHeight < nBestHeight-2500 && !mapArgs.count("-checkblocks"))
which I believe should not be included in the patch.  I will figure out how to manually exclude this and to preserve the patch as being correct in syntax.  Yep, it's unnecessary, and removing that block of patch, the remaining block of patch for db.cpp is identical.

Humm, manually modifying `diff`s is difficult, especially with rpc.cpp

Okay, yeah, I definitely give up.  I was doing pretty well until rpc.cpp when I realized that gavin's code contains WAY TOO MANY other patches besides only monitoraddress and monitorblocks and I have no idea how to remove these pieces from the patch data.

Additionally, using gavin's git-diff suggestion wasn't usable considering the svn code in his git repo is outdated.

If it is of any help, here is a manually compiled collection of diffs (using same switches as link above): http://pastebin.com/tN7hRZWH up to and not including rpc.cpp  (check file list above)
752  Bitcoin / Development & Technical Discussion / Re: Gentoo Linux Ebuild on: October 05, 2010, 12:07:55 AM
I do not have an nVidia gpu and cannot afford to buy anything for the foreseeable future.  If another gentoo user is willing to provide an ebuild for the CUDA client, that would be appreciated.  I can provide access to the github repository if somene is willing to contribute a CUDA ebuild.  Otherwise instead of an entirely separate ebuild, if there are patches (just like the others) that can be applied when "cuda" USEFLAG is enabled, then you're welcome to modify my ebuild as well.
753  Bitcoin / Bitcoin Discussion / Re: Want to generate the next 2080 blocks all by yourself? on: October 04, 2010, 07:27:58 AM
Consider it as an investment into the future and the earlier you (or anyone) pursues such an endeavor the better or more quantity/value will be produced.
754  Bitcoin / Bitcoin Discussion / Re: History of Bitcoin on: October 04, 2010, 06:24:54 AM
http://www.bitcoin.org/wiki/doku.php?id=bitcoin_history

If there is to be a history, I hope people fill in some of the "standard history stuff" as well as a droll listing of security events.  When did satoshi generate the first bitcoin?  What events (ie. slashdotting) triggered large influxes of new users?  When did the first bitcoin-denominated businesses appear?  etc.

I would like to know these types of interesting things too!
755  Bitcoin / Bitcoin Discussion / Bitcoin History on: October 04, 2010, 06:00:06 AM
I created a very basic wiki page outlining some notable events in our Bitcoin community's history.  Please feel free to make it look nicer and to add to it to provide further information regarding our community and established culture.

http://www.bitcoin.org/wiki/doku.php?id=bitcoin_history
756  Bitcoin / Bitcoin Discussion / Re: Want to generate the next 2080 blocks all by yourself? on: October 04, 2010, 04:06:01 AM
Oooh, that's a good idea for multiple participants, however, those who have CUDA-based clients/code will probably desire to fund themselves to keep profits to themselves.
757  Bitcoin / Development & Technical Discussion / Re: Should patches be posted here or on the mailing list or what? on: October 04, 2010, 04:02:07 AM
Additionally you can add patches to http://www.bitcoin.org/wiki/doku.php?id=list_of_patches

For now I have maintained majority of patches that I can find.  I may have missed some, but I'm not going to look through history again.  Feel free to continue adding to this wiki page so I don't have to do all the work. ^_^
758  Local / Майнеры / Re: CUDA Linux Client on: October 04, 2010, 02:12:00 AM
Лучше и проще для патча от nelisky. Вот makefile.unix:
Code:
# Copyright (c) 2009-2010 Satoshi Nakamoto
# Distributed under the MIT/X11 software license, see the accompanying
# file license.txt or http://www.opensource.org/licenses/mit-license.php.


INCLUDEPATHS= \
 -I"/usr/local/include/wx-2.9" \
 -I"/usr/local/lib/wx/include/gtk2-unicode-debug-static-2.9" \
 -I"$(HOME)/build/boost_1_44_0" \
 -L"$(HOME)/build/boost_1_44_0/stage/lib"

# for wxWidgets 2.9.1, add -l Xxf86vm
WXLIBS= \
 -Wl,-Bstatic \
   -l wx_gtk2ud-2.9 \
 -Wl,-Bdynamic \
   -l gtk-x11-2.0 \
   -l SM

# for boost 1.37, add -mt to the boost libraries
LIBS= -dead_strip \
 -Wl,-Bstatic \
   -l boost_system \
   -l boost_filesystem \
   -l boost_program_options \
   -l boost_thread \
   -l db_cxx \
   -l crypto \
 -Wl,-Bdynamic \
   -l gthread-2.0 \
   -l z \
   -l dl \

DEFS=-D__WXGTK__ -DNOPCH -DFOURWAYSSE2
DEBUGFLAGS=-g -D__WXDEBUG__
CFLAGS=-O2 -msse3 -mmmx -Wno-invalid-offsetof -Wformat $(DEFS) $(INCLUDEPATHS)
HEADERS=headers.h strlcpy.h serialize.h uint256.h util.h key.h bignum.h base58.h \
    script.h db.h net.h irc.h main.h rpc.h uibase.h ui.h noui.h init.h

CUDAROOT = "$(HOME)/NVIDIA_GPU_Computing_SDK"

CUDALIBPATHS= \
 -L$(CUDAROOT)/C/lib \
 -L$(CUDAROOT)/C/common/lib/linux \
 -L$(CUDAROOT)/shared/lib \
 -L/usr/local/cuda/lib

CUDALIBS= -lcudart -lcutil_i386 -lshrutil_i386

CUDAFLAGS=-fPIC -Xlinker -rpath /usr/local/cuda/lib $(CUDALIBPATHS) $(CUDALIBS)

OBJS= \
    obj/sha256_kernel.cuo \
    obj/util.o \
    obj/script.o \
    obj/db.o \
    obj/net.o \
    obj/irc.o \
    obj/main.o \
    obj/rpc.o \
    obj/init.o \
    cryptopp/obj/sha.o \
    obj/sha256.o \
    cryptopp/obj/cpu.o


all: bitcoin

obj/nogui/sha256.o: sha256.cpp
g++ -c $(CFLAGS) -O3 -o $@ $<

obj/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -DGUI -o $@ $<

cryptopp/obj/%.o: cryptopp/%.cpp
g++ -c $(CFLAGS) -O3 -o $@ $<

bitcoin: $(OBJS) obj/ui.o obj/uibase.o obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(WXLIBS) $(LIBS)


obj/nogui/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -o $@ $<

obj/nogui/%.cuo: %.cu
   /usr/local/cuda/bin/nvcc  -gencode=arch=compute_10,code=\"sm_10,compute_10\"  -gencode=arch=compute_20,code=\"sm_20,compute_20\" --compiler-options -fno-strict-aliasing  -I. -I/usr/local/cuda/include -I$(CUDAROOT)/C/common/inc -I$(CUDAROOT)/shared/inc -DUNIX -O3   -o $@ -c $<

bitcoind: $(OBJS:obj/%=obj/nogui/%)
g++ $(CFLAGS) -o $@ $^ $(LIBS) $(CUDALIBPATHS) $(CUDALIBS)


clean:
-rm -f obj/*.o
-rm -f obj/nogui/*.o
-rm -f cryptopp/obj/*.o
-rm -f headers.h.gch

Пути с $(HOME) надо подкорректировать для себя. У меня в OpenSuSE 11.3 какая-то кривая сборка boost-devel, нет *.a файлов для линковки, так что собрал свой буст и положил по указанному пути. Ещё надо скачать CUDA Toolkit, Developer Drivers и GPU Computing SDK code samples. Хоть и написано, что samples, но без него никуда там cutil_inline.h и пачка библиотек. Если пути указаны верно, должно собраться, хотя на других дистрибутивах могут отсутствовать библиотеки. Я добавил для себя libdl и libz. Разумеется, если раньше вы не компилили клиент вообще, то ещё надо слить wxWidgets и у оракла слить db (Berkeley DB).

Бинарник.

I added this patch to http://www.bitcoin.org/wiki/doku.php?id=list_of_patches but I am not sure how to name it appropriately.  Will someone edit the wiki and provide the correct name?

That's not a patch, just a makefile which I run on OpenSuSE. I have no idea why Sato put so few libraries and why it builds at all on his comp. I see the obvious lack of -l dl and -l z at the very least.

Mmkay, I removed it then.
759  Bitcoin / Development & Technical Discussion / Re: integrating digital payments into p2p protocols on: October 04, 2010, 02:07:13 AM
I'll offer 5btc contribution for this project.  I know it's not much (yet!), but perhaps it will spark others to donate also.  Which address can I send to?

http://tahoe-lafs.org/trac/tahoe-lafs <= Check the nice bitcoin button on their site.
Funny, I've send 10 btc also to them yesterday.

Thanks! for pointing out obvious ^_^
760  Bitcoin / Bitcoin Technical Support / Re: How check address for validity? on: October 04, 2010, 02:03:34 AM
I will offer 5btc reward for this patch to be produced.

+5btc from me
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 [38] 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!