Oh fuck it... I'll offer my advice here as well, regardless of what I think of the situation.
If you aren't the sole controller of your private keys, you don't have any bitcoins.
Exactly - it bears repeating :-) |
|
|
|
mark. is that you?
who is mark? Karpeles - Of mtgox. |
|
|
|
|
Who wants to buy when you have no idea when you can transfer the bitcoins out? And when you have little faith in their technical skills.
|
|
|
|
Any coins to which you don't have the private key are not yours, they are a ledger entry, so don't store coins anywhere except your wallet (cold storage is best), unless you absolutely have to.
Does Coinbase fall in this category? I create the address using Coinbase, where is my private key?? Curious about this same question as to does Coinbase fall under this? Coinbase and many other sites are reputable, but no one is perfect. SR 2 (unless they are crooks) made a dumb error and lost a lot of coins. Ditto Gox. Ditto others. Ditto some of the pools. Has coinbase been hacked? Not yet that we know of. Have people lost coins at coinbase? People say yes, probably through Trojans, key loggers, and the like. The best practice is to use cold storage for coins you don't intend to use soon, where you have the private key(s) created using the bitcoin wiki process. Think about it like this: you send your coins to me, and I'm holding them for you. You have to trust me, trust everyone who works with me, trust everyone who has access to our network (even the NSA can screw up there) and everyone who has access to the private keys. You also have to trust each of those people to not accidentally screw up by getting malware or just making a mistake in coding. Hopefully most of coinbase's coins are offline in cold storage, but you are trusting them. They are well funded, so probably are okay, but it is pretty easy to move your coins out of there if you intend to keep them for a long while, so even if the chance of them having a problem is low, why not protect yourself? |
|
|
|
Can anyone explain how this transaction malleability bug can be exploited to steal coins from a Bitcoin address? I thought it can only happen if you are an exchange, like Gox or Stamp, and people are making withdrawals.
I can't explain it to you, because it cannot happen. This is a blatant lie, the OP stole everyone's coins and, as the other poster said, anyone stupid enough to leave coins on a hosted site dedicated to selling illegal products deserves to have their bitcoins stolen. It can happen if withdrawals are automatic, requests for re-tries are automatic, and SR 2 used a transaction ID to confirm withdrawals were successful. E.g. 1. A withdraws 10 BTC, tx ID 1 2. A successfully changes tx ID 1 to tx ID 1a (malleability) 3. A tells SR 2 that tx ID 1 never arrived 4. SR 2 checks and sees tx ID 1 is not in the block chain so reissues it. (At least MtGox had a human at this step, but they fell for it too). 5. Goto step 1 until the wallet is drained. Very poor programming since nothing is final until it is confirmed (including the tx id), and this should not have been automated. Did this happen or did they take it? Don't know. Any coins to which you don't have the private key are not yours, they are a ledger entry, so don't store coins anywhere except your wallet (cold storage is best), unless you absolutely have to. |
|
|
|
Yes, those are the Silk Road coins seized by the FBI. This guy is talking about Silk Road 2. |
|
|
|
|
Only invest what you can afford to lose. But if you believe in the benefits of bitcoin, then a lower price is always a good time to buy. No one knows if it will go down more, or rebound quickly so everything is just speculation and you have to make your own decision based on what you learn here, and your own thoughts.
:-)
|
|
|
|
Edited - based on your edit too (cut some). ;-)
For example if I look at it from the CLI (this is built with the latest changes since rc1 so will be slightly different than your's), I see lots of stuff, including:
-rwxrwxr-x 1 user group 69750836 Feb 13 10:22 bitcoind
-rwxrwxr-x 1 user group 14246918 Feb 13 10:22 bitcoin-cli
If you are at the CLI, if you type this while in the src directory, it launches. So I'm thinking this is just a GUI issue.
What do the properties show for the files?
GUI properties indicate that all 3 are executable, and the type is specified 'shared library (application/x-sharedlib)' for all 3. They are executable, but bitcoin-qt only works by launching it from the command prompt. Error if you try from the GUI: "Could not display "/home/username/Documents/bitcoin-0.9.0rc1/src/qt/bitcoin-qt - There is no application installed for shared library files. Do you want to search for an application to open this file?". Sounds like it's trying to read the contents of the file, even though it's specified as executable. Sorry, I've still got a little bit of a MS windows hangover, linux is still new to me really. The idea that a GUI bug or suchlike would cause this confusion didn't occur to me. I'm running it with Mate desktop on Mint 15, if that's useful. Perhaps Mate is known for being incapable of launching certain types of executables? If you can run it from the CLI, it is definitely compiled and so would seem to be a GUI issue or typing (mime?) issue. The bitcoind etc files in src, are definitely just "bitcoind" not "bitcoind.so" right? :-) (.so is usually shared object library). You might try a make install at the end if you haven't done that. I am not sure under Mate, but perhaps it will fix the issue. Perhaps it is only looking for executable applications in certain directories (e.g. /usr/bin/ or /usr/local/bin) The good thing is that you got it installed without a problem, just not in Mate yet. :-) |
|
|
|
Be prepared for BTC to approach single digits and possibly even fractions of a penny before this is over. They stand the theoretical probability to rebound once an agreement or framework is reached but this story is definitely over for a while. Be aware of what you are dealing with - for a period of time you may feel a BTC is worth $1000 but the market may only be giving you 1 penny.  One of your posts yesterday says you're riding BTC all the way to $8500. Which is it? Trolls can't make up their mind. |
|
|
|
|
Edited - based on your edit too (cut some). ;-)
For example if I look at it from the CLI (this is built with the latest changes since rc1 so will be slightly different than your's), I see lots of stuff, including:
-rwxrwxr-x 1 user group 69750836 Feb 13 10:22 bitcoind
-rwxrwxr-x 1 user group 14246918 Feb 13 10:22 bitcoin-cli
If you are at the CLI, if you type this while in the src directory, it launches. So I'm thinking this is just a GUI issue.
What do the properties show for the files?
|
|
|
|
|
It is nice to see facts instead of FUD. Thank you.
|
|
|
|
BTW - a word of thanks to odolvlobo for his two word inspirational contribution ("A Job?"), which helped me come up with this approach. He was actually quoting me. ;-) I think your revision is improving things btw, imo. ;-) |
|
|
|
Carlton Banks, nothing you've posted so far indicates an error. Those three lines are in fact telling you that it was successfully built. Try "make clean && make all" and pastebin the *entire* result.
That would be my next suggestion or make -f makefile.unix clean; make -f makefile.unix Also, does find / -name bitcoind show it being built anywhere odd? (I presume you did a too (assuming you just want bitcoind): ./configure --without-qt ) |
|
|
|
Miners focusing in fees is kind if stupid at this point. For the $50 they get in fees they really muck with the user experience of Bitcoin...making the average user unhappy and making the average usefulness of Bitcoin less.
Some theoretical question. Let's assume I'm a miner. A rich and altruistic one. Then I do not care that much about mined bitcoins and don't care of costs of running my miners. I have some reasonable (but not extreme) hashing power, let's say 500 Ghash/s. Is it technically possible to write mining software only accepting transactions without fees? Would my hashpower help with propagating such transactions? A miner can accept whatever valid transactions they want - from zero or up to the block size limit. Some pools have been generating blocks with no transactions, others in the middle, others larger, close to the limit. Likewise you could change the software to accept any valid transaction only if it had no fees. But 500 Ghash/s won't find many (any?) blocks per year though, you'd need much more than that to make an impact. With bitcoind you can control the mix between paid and free transactions. Some say the problem with making a huge, completely free block is that you run the slight risk of it becoming an orphan because of slightly longer propagation times as compared to smaller blocks. |
|
|
|
|
The people that run the trains will take some passengers as freeloaders (and everyone eventually) but they won't take everyone for free on the first train since they have bills to pay, including time and fuel for the locomotives.
|
|
|
|
But how do you control the means of distribution and what the public sees? I can imagine some type of zero-day attack such as where the wrong version of the code gets pushed out on mobile devices and steals everyone's private keys.
Many people building, Checksums, gitian etc. There is no "push" either for bitcoind or qt |
|
|
|
Panic selling continues.....GOX is about to fall below 500 next stop....100
... "donate2me" says while having a donate link in his footer. Lol |
|
|
|
So, after the "executing depfiles commands" you get nothing? You should see something like this after "config.status: executing depfiles commands" (I just went to rebuild it to see what I could tell): Making all in src
make[1]: Entering directory `/home/user/bitcoin/src'
(CDPATH="${ZSH_VERSION+.}:" && cd .. && /bin/bash /home/user/bitcoin/src/build-aux/missing autoheader)
rm -f stamp-h1
touch bitcoin-config.h.in
cd .. && /bin/bash ./config.status src/bitcoin-config.h
...
This is the complete configure script output: checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
checking for main in -ldb_cxx-4.8... yes
checking miniupnpc/miniwget.h usability... yes
checking miniupnpc/miniwget.h presence... yes
checking for miniupnpc/miniwget.h... yes
checking for main in -lminiupnpc... yes
checking miniupnpc/miniupnpc.h usability... yes
checking miniupnpc/miniupnpc.h presence... yes
checking for miniupnpc/miniupnpc.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnpcommands.h usability... yes
checking miniupnpc/upnpcommands.h presence... yes
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... yes
checking for QR... yes
checking for protoc... /usr/bin/protoc
checking whether to build bitcoind... yes
checking whether to build bitcoin-cli... yes
checking for QT... yes
checking for QT_TEST... yes
checking for QT_DBUS... yes
checking for moc-qt4... /usr/bin/moc-qt4
checking for uic-qt4... /usr/bin/uic-qt4
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... /usr/bin/rcc
checking for lrelease-qt4... /usr/bin/lrelease-qt4
checking for lupdate-qt4... /usr/bin/lupdate-qt4
checking whether to build Bitcoin Core GUI... yes (Qt4)
checking for operating system IPv6 support... yes
checking if ccache should be used... no
checking if wallet should be enabled... yes
checking whether to build with support for IPv6... yes
checking whether to build with support for UPnP... yes
checking whether to build with UPnP enabled by default... yes
checking whether to build GUI with support for D-Bus... yes
checking whether to build GUI with support for QR codes... yes
checking whether to build test_bitcoin-qt... yes
checking whether to build test_bitcoin... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/test/Makefile
config.status: creating src/qt/Makefile
config.status: creating src/qt/test/Makefile
config.status: creating share/setup.nsi
config.status: creating share/qt/Info.plist
config.status: creating qa/pull-tester/run-bitcoind-for-test.sh
config.status: creating qa/pull-tester/build-tests.sh
config.status: creating src/bitcoin-config.h
config.status: src/bitcoin-config.h is unchanged
config.status: executing depfiles commands
using Mint/Ubuntu 13.04 equivalent |
|
|
|
|
I presume you checked in the
~/bitcoin/src
directory to see if the new bitcoind was built in there? (Just trying to cover all the bases). :-)
(you might have to copy it to /usr/bin/ afterward if you want it globally accessible, but for testing purposes, probably not).
|
|
|
|
Perhaps I missed it, but are there any messages showing up indicating an error when you go to make it?
He got stuck on make, however it is not throwing any error but theres not output of make commands Maybe try verbose mode V=1 Or Debug: make -d I didn't try those just now though so ymmv. :-) But it might give some starting points |
|
|
|
|
Show Posts
