|
Bitcoin is great, but it misses one thing that usual bank transfers have: payment title.
Perhaps it should be possible to include short (<=512 bytes) message for each transaction.
The message could be encrypted with public/private keys so only the receiver can see its contents.
What do You think ?
PS.
I might be wrong, but the messages could also be used to increase randomness of hashing process by the way, couldn't they ? If not, never mind.
|
|
|
|
There is no evidence that I've seen that Bitcoin is in a bubble.
There may be a small bubble waiting somewhere, even the hard currencies as gold and silver sometimes get overpriced by speculation. Lucky for us, bitcoin is even more deflationary than gold, silver or any bullion based currency, so it should be less suspective to price bubbles. |
|
|
|
|
Hey, here is an idea.
How about You re-enable the registrations and just disable Paypal and Moneybookers for all new users (Only "old" userbase would be able to use Paypal & Mbookers), so no SCAMs can be made ?
LibertyReserve and Pecunix are "hard" currencies as far as i know, so it is not possible to do drawbacks.
Doesn't this seem logical ?
|
|
|
|
could you tell me of what revision is this version ? It is SVN revision 171.  Thanks, i already managed to get this information by looking at logs. |
|
|
|
|
Satoshi, could you tell me of what revision is this version ?
I tried diff-ing the files (from SVN and from the binary package with sources), but there seems to be some kind of binary differences in the files, and they are marked as different when doing directory compare, but diff software cannot pinpoint what are the exact differences !!
That is the weirdest thing i have seen in a long time.
Perhaps the files from the package are encoded in UTF-8, UTF-16 or something ? In SVN, they are noticeably smaller.
|
|
|
|
|
Keynesian economy already failed miserably many times (see the latest world crisis caused by nothing else than INTERVENTIONISM), and it will fail again.
I would sooner say that fiat currency model is unsustainable.
|
|
|
|
|
I have finally succeeded to create a working makefile.
Everything emerges properly, however dependencies are not automatically solved, so the ebuild will not work on any Gentoo out of the box. It needs improvements.
Also, my ebuild replaces normal bitcoin with its cuda version (as i don't know how to make separate binaries yet), so it's probably not the way it should be done anyway.
I will be posting the ebuild soon together with modified source, after i start my account at github.
|
|
|
|
|
Never mind my previous post.
I've studied the code of the ebuild and i know what the @@GENTOO_CFLAGS_SSE2@@ is.
This "@@GENTOO_CFLAGS_SSE2@@" gets replaced by "-DFOURWAYSSE2" by emerge, which is defined in the ebuild. If it is not replaced, something wrong is going on with the ebuild.
My advice: try the older version (as it worked for me).
|
|
|
|
|
I think You should ask this question at Gentoo Forums as it seems that Your Gentoo is misconfigured somehow.
They will know why is Your SSE2 variable not set.
BTW,
Did You do $ env-update && source /etc/profile as root after changing your CFLAGS ?
Alternatively, You may restart Your computer - that should work too.
|
|
|
|
I think that Your cflags are wrong (too general). You need to set them for specifically Your processor type, so SSE2 will be detected and set. But i might be wrong. CFLAGS="-O2 -mtune=i686 -pipe"
declare -x CXXFLAGS="-O2 -mtune=i686 -pipe"
Look at mine in comparison: CFLAGS="-march=k8 -O2 -pipe"
CXXFLAGS="-march=k8 -O2 -pipe"
Those are set specifically for AMD64 processor with SSE2 support. Another thing is that perhaps Your processor does not support SSE2 ? You could post Your hardware specs. ---- EDIT: Also, here are lists for safe Gentoo CFLAGS for every Intel/AMD processor: http://en.gentoo-wiki.com/wiki/Safe_Cflags/AMDhttp://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel |
|
|
|
|
Clearly i can see that Your makefile is not reading the @@GENTOO_CFLAGS_SSE2@@ variable.
Another question is, WHY.
I am using exactly the same ebuild as You are and everything works.
Perhaps something is wrong with Your cflags. Check make.conf. perhaps You should add processor type/architecture to the $CFLAGS variable.
----
You can post Your make.conf here, i will take a look at it.
----
EDIT: Correction, I'm not using the same ebuild as You, I'm using its older version.
Perhaps something broke later ?
|
|
|
|
|
I think that the hosts which have a lot of double spents should be added to client's ban list.
First, a temporary ban list, and then a permament one.
If a host improves his behavior, it may be removed from the temporary ban list. But if it keeps double spending, then it should be added to the permament one.
To preserve anonymity, hosts could be indentified by public & private key or digital signature system or whatever.
Also, the clients could communicate between each other to exchange their ban lists. But only if the particular clients trust each other. Some trust system/network could be developed for that.
(Just thinking loud here, don't mind me).
|
|
|
|
It doesn't matter where your client resumes hashing. Chances for finding a block are the same.
Even if it repeats exactly the same work that has been done before ? Curious. |
|
|
|
|
Thank for your answers, I think i get it now.
|
|
|
|
|
Hey,
As I understand, the client is doing the hashing in an organized manner, based on some counter. I mean that when i close the client, it saves the current state, so it can continue just where it left last time. Am i right ?
I was wondering how often is the client doing backup of current state in its database, because in an event on sudden power failure, they client could forget where it was and waste some amount of time doing the same work twice when it is turned on later. Is that the case ? Or is the counter saved in real time ?
So If I hard-reset my computer or kill the client with -9 parameter and then restart the client, will it pick up hashing exactly where it left, or will it start some stage from the beginning ?
I hope i made myself clear enough, because my english surely isn't perfect.
|
|
|
|
|
Hello,
I was wondering if it would be possible to detect double spent bitcoins in the attack scenario where attacker has more than 50% of whole bitcoin network processing power ?
By "detection" i also mean situations when we know which nodes of the network spent the same coins twice without knowing which one is "cheater" and which one "honest".
|
|
|
|
I am really thinking about investing over $1000 of my savings into Bitcoin. Would this be wise? Is BTC safe and stable at this point?
Nope. Just give it a year or two though and then perhaps it will be stable. This software is in BETA stage for a reason. There are still unresolved matters with successful-and-easy attack scenarios. Those need to be resolved before BTC can become serious currency. There is also a question what will happen if quantum computers come into play in 5,10 or 15 years. It will either kill BTC totally (low probability) or render it useless and freeze all transactions until it is secured with quantum-computer encryption algorithms (more probably). |
|
|
|
Seems the the db include directory was not set correctly. Can you search your system for db_cxx.h and db.h and post the results? I'll try to look at it when I have time.
Here You go: db_cxx.h : $ find /usr | grep db_cxx
/usr/include/db4.7/db_cxx.h
/usr/include/db4.8/db_cxx.h
/usr/include/db4.5/db_cxx.h
/usr/include/db4.6/db_cxx.h
db.h : $ find /usr | fgrep '/db.h'
/usr/include/db4.7/db.h
/usr/include/htdig_db/db.h
/usr/include/db4.8/db.h
/usr/include/db4.5/db.h
|
|
|
|
I continued with the Gentoo ebuild approach, and got around most of the library dependencies problem. I will probably not continue with CMake way, because it is very gentoo-incompatibile. However, now i get this while trying to compile code: obj/bitcoinminercuda.o: In function `CUDARunner::RunStep()':
bitcoinminercuda.cpp:(.text+0x301): undefined reference to `cudaMemcpy'
bitcoinminercuda.cpp:(.text+0x332): undefined reference to `cuda_process_helper(cuda_in*, cuda_out*, unsigned int, unsigned int, int, int)'
bitcoinminercuda.cpp:(.text+0x351): undefined reference to `cudaMemcpy'
bitcoinminercuda.cpp:(.text+0x3e5): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x41c): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::AllocateResources(int, int)':
bitcoinminercuda.cpp:(.text+0x48c): undefined reference to `cudaMalloc'
bitcoinminercuda.cpp:(.text+0x49c): undefined reference to `cudaMalloc'
bitcoinminercuda.cpp:(.text+0x4d1): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x508): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::DeallocateResources()':
bitcoinminercuda.cpp:(.text+0x544): undefined reference to `cudaFree'
bitcoinminercuda.cpp:(.text+0x574): undefined reference to `cudaFree'
bitcoinminercuda.cpp:(.text+0x591): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x5c8): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::~CUDARunner()':
bitcoinminercuda.cpp:(.text+0x5f1): undefined reference to `cudaThreadExit'
bitcoinminercuda.cpp:(.text+0x60c): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::~CUDARunner()':
bitcoinminercuda.cpp:(.text+0x661): undefined reference to `cudaThreadExit'
bitcoinminercuda.cpp:(.text+0x675): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::~CUDARunner()':
bitcoinminercuda.cpp:(.text+0x6d1): undefined reference to `cudaThreadExit'
bitcoinminercuda.cpp:(.text+0x6e5): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::CUDARunner()':
bitcoinminercuda.cpp:(.text+0x76a): undefined reference to `cudaGetDeviceCount'
bitcoinminercuda.cpp:(.text+0x79c): undefined reference to `cudaSetDevice'
bitcoinminercuda.cpp:(.text+0x7c0): undefined reference to `cudaSetDevice'
bitcoinminercuda.cpp:(.text+0x7cb): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x7f8): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x82f): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::CUDARunner()':
bitcoinminercuda.cpp:(.text+0x88a): undefined reference to `cudaGetDeviceCount'
bitcoinminercuda.cpp:(.text+0x8bc): undefined reference to `cudaSetDevice'
bitcoinminercuda.cpp:(.text+0x8e0): undefined reference to `cudaSetDevice'
bitcoinminercuda.cpp:(.text+0x8eb): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x918): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0x94f): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `CUDARunner::FindBestConfiguration()':
bitcoinminercuda.cpp:(.text+0xa7b): undefined reference to `cudaGetLastError'
bitcoinminercuda.cpp:(.text+0xaab): undefined reference to `cudaMemcpy'
bitcoinminercuda.cpp:(.text+0xad0): undefined reference to `cuda_process_helper(cuda_in*, cuda_out*, unsigned int, unsigned int, int, int)'
bitcoinminercuda.cpp:(.text+0xae5): undefined reference to `cudaMemcpy'
bitcoinminercuda.cpp:(.text+0xaf2): undefined reference to `cudaGetLastError'
bitcoinminercuda.cpp:(.text+0xc1e): undefined reference to `cudaGetErrorString'
bitcoinminercuda.cpp:(.text+0xc55): undefined reference to `cudaGetErrorString'
obj/bitcoinminercuda.o: In function `cutGetMaxGflopsDeviceId()':
bitcoinminercuda.cpp:(.text._Z23cutGetMaxGflopsDeviceIdv[cutGetMaxGflopsDeviceId()]+0x46): undefined reference to `cudaGetDeviceCount'
bitcoinminercuda.cpp:(.text._Z23cutGetMaxGflopsDeviceIdv[cutGetMaxGflopsDeviceId()]+0x66): undefined reference to `cudaGetDeviceProperties'
bitcoinminercuda.cpp:(.text._Z23cutGetMaxGflopsDeviceIdv[cutGetMaxGflopsDeviceId()]+0xca): undefined reference to `cudaGetDeviceProperties'
collect2: ld returned 1 exit status
It seems I am missing some library or something. Also, my libraries paths & include paths in the makefile are as follows: INCLUDEPATHS= \
-I"/usr/include" \
-I"/usr/include/crypto++" \
-I"@@GENTOO_DB_INCLUDEDIR@@" \
-I"/opt/cuda/sdk/C/common/inc/" \
-I"/opt/cuda/include/"
LIBPATHS= \
-L"/usr/lib" \
-L"/opt/cuda/lib64" -lcufft -lcudart -Wl,-rpath,/opt/cuda/lib64
LIBS := ${LDFLAGS} -dead_strip \
-ldb_cxx -lboost_system -lboost_filesystem -lboost_program_options -lboost_thread -lgthread-2.0 -lssl -lcrypto -lcrypto++ -lgmp -ldl -lz
Once again, I am not a C++ programmer (too bad). EDIT: To be clear, i have moved all of the *.cpp, *.h and *.cu files from the data/ & gpucommon/ directory, to the root directory to make it easier resolving dependencies.You may also find this part of the makefile useful: 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 bitcoinminercuda.h \
cudashared.h gpucommon.h
all: bitcoind
OBJS= \
obj/util.o \
obj/script.o \
obj/db.o \
obj/net.o \
obj/irc.o \
obj/main.o \
obj/rpc.o \
obj/init.o \
obj/bitcoinminercuda.o \
obj/gpucommon.o
# cryptopp/obj/sha.o
# cryptopp/obj/cpu.o
bitcoind: $(OBJS:obj/%=obj/nogui/%) obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(LIBPATHS) $(LIBS)
bitcoin: $(OBJS) obj/ui.o obj/uibase.o obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(WXLIBS) $(LIBS)
#cryptopp/obj/%.o: cryptopp/%.cpp
# g++ -c $(CFLAGS) -O3 -o $@ $<
obj/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) $(WXDEFS) -DGUI -o $@ $<
obj/sha256.o: sha256.cpp
g++ -c $(CFLAGS) @@GENTOO_SHA256_SSE2@@ -o $@ $<
obj/nogui/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -o $@ $<
I promise to make the Gentoo cuda ebuild public after i make this work. |
|
|
|
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.
I will contribute a CUDA ebuild, once i get the damn makefile to work. I guess perhaps this weekend. |
|
|
|
|
Show Posts
