First of all, please do not hijack months old threads with your own issues. Make your own thread instead. Your blockchain looks like it is corrupted. If you run just Bitcoin Core, does it sync properly and not give you any errors? |
|
|
|
Thanks for your answer, achow101.
So as I understand, c1c is actually rejected and 34c is actually considered as my first tx.
And my BTC should be confirmed or returned in some time (3 days?).
Yes. 34c is the original transaction as considered by every other node so c1c is rejected as a double spend of 34c. Will my Transactions tab synchronize automatically later? because now I have c1c instead of 34c there.
Yes. The blockchain is what determines that a transaction is the "real" one. Once one transaction confirms, then your wallet will automatically update to fit what the blockchain says. Also, I sent more BTC with c1c than 34c, and my wallet is still showing balance minus the c1c amount.
Since you did zapwallettxes, you removed 34c from your wallet before you sent c1c. Thus your wallet saw c1c first and uses that as the "real" transaction and not 34c which is what all other nodes will think is the "real" one. Once one of those transactions confirm, your wallet will automatically update to fit what the blockchain says. |
|
|
|
I thought that Satoshi gave the github keys to Gavin ?
No. Satoshi did not even have the project on Github originally. Gavin took over the project after Satoshi disappeared since he was the most experienced and active contributor at the time. I have found no evidence for Satoshi handing anything over except for Gavin's own statements. There is no indication from Satoshi that there was any plan for a "line of succession". It is true that an implementation is a precise definition, but is such a precise definition necessary? You write as if Bitcoin does not have a mechanism for resolving disputes between nodes, but it does of course.
A precise definition of the consensus rules are necessary. Everyone must be following the exact same consensus rules, with its bugs, intricacies, and undefined behavior, in order to not have any accidental hard forks. The 2013 accidental hard fork is an example of such failure of different consensus implementations. On paper, all nodes were following the same rules. But in implementation, one version of the implementation had a bug which in turn caused an accidental chain fork. If everyone follows precisely the same rules, then this cannot happen. The only way for everyone to follow precisely the same rules is for every node to be share the same consensus implementation. |
|
|
|
|
Addresses are not single use. They can be used many times. If two people send money to the same address at the same time, then everything will work fine and nothing bad will happen. Both transactions will arrive.
|
|
|
|
|
Since you used zapwallettxes, your transaction made at p.3 is a double spend. The transaction fee for your other transactions is not so low that they are rejected from many nodes' mempools. Because of that, your p.3 transaction is rejected by nearly all nodes since it is considered a double spend. Thus that transaction did not propagate well so you won't find it on block explorers.
Your Bitcoin is safe. Bitcoin does not just "disappear". It will either go to who you sent it to (i.e. the transaction will confirm) or it will not and you can spend it again (i.e. the transactions are dropped from the network after a while).
|
|
|
|
|
Your forum account? If that is the case, then you are just doing everything wrong. All of those campaigns are not affiliated with Bitcointalk in any way whatsoever. If you are not telling the operators of those campaigns that you have performed the task and that they should pay you, then you are not going to be paid. Furthermore, you will need to give them a Bitcoin address since the forum has no functionality to pay accounts. The issue is between you and the campaign managers. Contact them for help.
|
|
|
|
In Armory, uncheck the "Let Armory run Bitcoin Core in the background" Checkbox. Stop Armory. Start Bitcoin Core. Let Bitcoin Core sync. Then start Armory again.
Let me get this straight: "Let Bitcoin Core sync." - Start syncing or finish syncing? Finish syncing. |
|
|
|
gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406
Can you try using gcc 5.x? I think there is some incompatibility between gcc versions for cryptopp. We haven't tried compiling on anything newer than gcc 5.x yet. |
|
|
|
I'll reuse this thread, as I have compile-problems as well: Freshly installed native (non-VM) Ubuntu 17.04 with XFCE, 64 bit. I installed git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil and autoconf libtool pkg-config libcrypto++-dev for good masurement. Do you have automake and autotools-dev installed? Compiling fails with many of In file included from cpu.h:31:0,
from rijndael.cpp:74:
/usr/lib/gcc/x86_64-linux-gnu/6/include/smmintrin.h: In member function ‘virtual void CryptoPP::Rijndael::Base::UncheckedSetKey(const byte*, unsigned int, const CryptoPP::NameValuePairs&)’:
/usr/lib/gcc/x86_64-linux-gnu/6/include/smmintrin.h:447:1: error: inlining failed in call to always_inline ‘int _mm_extract_epi32(__m128i, int)’: target specific option mismatch
_mm_extract_epi32 (__m128i __X, const int __N)
^~~~~~~~~~~~~~~~~
rijndael.cpp:223:44: note: called from here
rk[keylen/4] = rk[0] ^ _mm_extract_epi32(_mm_aeskeygenassist_si128(temp, 0), 3) ^ *(rc++);
~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Full output is on https://pastebin.com/qWjMSma3Are there more dependencies I am missing? What version of gcc are you using? |
|
|
|
I will need to update the website with new build info. Thanks for reminding me. After you have cloned the repo, you need to run git submodule init
git submodule update
from the repo root in order to get the fcgi stuff. Then you do ./autogen.sh
./configure
make
to actually build the thing. You will need to have automake installed. The command to run the qt client is still the same. |
|
|
|
Try running ArmoryDB in the terminal with the arguments that you use for running ArmoryQt in the terminal. Then run ArmoryQt and it should work. And also repeatedly printing this in the terminal:
(python2:28385): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
I'm pretty sure that error is benign. |
|
|
|
|
The fastest way to sync Bitcoin Core is to let it download the blockchain normally. There is currently no way for you to get the blockchain in any compressed form.
|
|
|
|
- It looks like you're slowly getting rid of Python and moving to C++ only. Is this true?
I think the plan is to have all of the backend, crypto, and computationally intensive stuff in C++ and have all of the frontend GUI stuff as python. - How do you recommend we upgrade to the new wallet format, including for our wallet file backups? (I prefer to backup wallet files and memorize password.) Should I just launch Armory 0.96 to update it automatically and export the wallet file from there?
Nothing needs to be done to upgrade. The current python wallet format is still the primary format. The C++ watching only wallet will be created automatically and automatically mirror the current python wallets. - Are you expecting more wallet file updates in future versions?
Definitely. The goal is to eventually move to the C++ wallet format which is supposed to be built from scratch so that multisig, compressed keys, BIP 32, etc. can be properly supported instead of the current format which isn't really extensible. |
|
|
|
|
Please post the debug.log file.
Make sure that you cross compiled Qt correctly.
|
|
|
|
I'd rather not trust websites with my wallet. Is there any other bitcoin software that lets me use my wallet from my pc directly?
Certainly, and I recommend that you do use a desktop wallet. I recommend that you use Electrum. Any wallet listed here: https://bitcoin.org/en/choose-your-wallet under the "Desktop" category is a good choice for a wallet. |
|
|
|
But of course I have set the connection parameters rpcuser and rpcpassword. But why this error  Are you sure that you have spelled the option properly? Are you sure that the bitcoin.conf file is located here: /home/seclinux/.bitcoin/bitcoin.conf? |
|
|
|
|
If you did not set an rpcuser and rpcpassword in the bitcoin.conf file, then that is why bitcoin-cli is not working. That has nothing to do with your internet connection. Read the error that it is telling you. Make sure that either both rpcuser and rpcpassword are set, or they are not in the bitcoin.conf file at all. With the latter case, if neither option is set, it will use an automatically generated rpc credentials which are also stored in a different temporary file in the datadir.
|
|
|
|
There is a translation in the desciption of the wallet security settings missing. Where it says "Encryped" it should be in German "Verschlüsselt". :-)
Not everything has been translated yet, and some translations seem to be broken (particularly with the Secureprint strings because of unicode). If there are no translations for a string, it will just default to the English strings. |
|
|
|
I guess my pc isn't good enough for bitcoin anymore, but how do I get my bitcoins back? The wallet.dat file is only usable with a working bitcoin.
You can have Core be offline and export the private keys to be used elsewhere. Start Core with -connect=0 so it is offline. Then go to Help > Debug Window and click on the console tab. Type to get the private key of <address>. Do that for all of your addresses and record the private keys down somewhere. Then get a different wallet software that allows you to import private keys and import or sweep your private keys into the new wallet. |
|
|
|
|
Show Posts
