|
Do you have a backup of your wallet? If so, restore that backup.
The problem here is that the wallet file is corrupted so Core is not able to read parts of it and get the information it needs.
|
|
|
|
One last clarification in the spirit of not trusting BTC private keys to a non-core wallet:
I assume it is possible to first transfer all BTC out of a wallet (after the fork has occurred) and then copy the wallet.dat file to the ABC wallet, rescan and all BCC should show up. Is that correct?
Yes. |
|
|
|
Oh, must had been a misclick or something.
Anyways.
Armory is now installed but it is stuck at "Preparing Databases". I am in the process of downloading the blockchain via Bitcoin Core. Once downloaded will this fix things?
Possibly. Wait for Bitcoin Core to sync before trying to run Armory. |
|
|
|
Only copying the output to paste it here and show you. No intention of running the output.
The output you pasted shows you running the output. |
|
|
|
!!! Armory installed successfully !!!
Armory can be removed at any time, either through your package
manager, or through the following command:
sudo dpkg -r armory
Processing triggers for libc-bin (2.24-9ubuntu2) ...
root@ophidion-ThinkPad-T430:~# (Reading database ... 237367 files and directories currently installed.)
Reading: command not found
root@ophidion-ThinkPad-T430:~# Preparing to unpack .../armory_0.96-gcc5.4_amd64.deb ...
Preparing: command not found
root@ophidion-ThinkPad-T430:~# Unpacking armory (0.96-1) over (0.96-1) ...
-bash: syntax error near unexpected token `('
root@ophidion-ThinkPad-T430:~# dpkg: dependency problems prevent configuration of armory:
No command 'dpkg:' found, did you mean:
Command 'dpkg' from package 'dpkg' (main)
dpkg:: command not found
root@ophidion-ThinkPad-T430:~# armory depends on python-qt4; however:
/root
Log file doesn't exist [yet]
(ERROR) ArmoryUtils.py:1236 - Error getting system details:
Traceback (most recent call last):
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1234, in <module>
SystemSpecs = GetSystemDetails()
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1229, in GetSystemDetails
out.HddAvailB = getHddSize(BTC_HOME_DIR) / (1024**3)
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1226, in getHddSize
s = os.statvfs(adir)
OSError: [Errno 2] No such file or directory: '/root/.bitcoin/'
(ERROR) ArmoryUtils.py:1237 - Skipping.
(ERROR) ArmoryUtils.py:3747 - Unsupported language specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
"sni-qt/4833" WARN 18:48:22.295 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
(ERROR) BDM.py:275 - setSatoshiDir: directory does not exist: /root/.bitcoin/
(ERROR) ArmoryQt.py:1840 - Failed to setup SDM
Traceback (most recent call last):
File "/usr/local/bin/../lib/armory/ArmoryQt.py", line 1835, in startBitcoindIfNecessary
TheSDM.setupSDM(extraExeSearch=self.satoshiExeSearchPath)
File "/usr/local/lib/armory/SDM.py", line 188, in setupSDM
if self.failedFindExe: raise self.BitcoindError, 'bitcoind not found'
BitcoindError: bitcoind not found
(ERROR) BDM.py:275 - setSatoshiDir: directory does not exist: /root/.bitcoin/
(ERROR) ArmoryQt.py:1808 - Failed to start Armory database: Invalid blockdata path
Traceback (most recent call last):
File "/usr/local/bin/../lib/armory/ArmoryQt.py", line 1793, in startArmoryDBIfNecessary
TheSDM.spawnDB(ARMORY_HOME_DIR, TheBDM.armoryDBDir)
File "/usr/local/lib/armory/SDM.py", line 368, in spawnDB
raise self.BadPath, "Invalid blockdata path"
BadPath: Invalid blockdata path
Why are you copying output of the terminal into commands and running them? Of course that will get you errors, those aren't actually commands. Armory should be installed now anyways and you should be able to run it with just How do you even log as root on Ubuntu? I thought that was disabled entirely.
|
|
|
|
Starting on August 1st, will ALL transactions in the blockchain be in segwit format? Is it a format imposed if you want your transaction included in the blockchain? Or is it optional?
Segwit is completely optional. If you don't want to use it, you don't have to and you can use Bitcoin as you normally do now. It is completely backwards compatible so you can use non-segwit software even after segwit activates. The current transaction format, script types, and addresses aren't going anywhere. They will remain the same and unchanged and will function as they do now. Also, segwit is not activating on August 1st. Segwit will be activating some time around August 24th as that is around when the lock in period will end. First it has to become locked in though. Over the next 2016 blocks, 1915 of them must signal for segwit in order for it to become locked in. Or there is no transaction format change at all and it is just about the way it will be stored in the blockchain by the miners?
There is a format change, but only if you are spending from segwit outputs. |
|
|
|
Ohh...
Can you please tell me how can I launch a complaint and to whom?
There is no way to make a complaint with. Is there any way I can get my money back or at least teach him or her a lesson kindly guide me. Thanks
No, your money is not recoverable. Once a Bitcoin transaction has confirmed, it is irreversible. If you send money to the receiver as part of a trade, you should let him know that the transaction has been confirmed and that it was paid to the address that he asked you to pay to. If he can't see the money, that is his problem; the blockchain shows that it was paid and the trade should continue. |
|
|
|
OK great thanks I got the Transaction to go into my Electrum Balance. In the History part of Electrum its showing as not verified... ? But my Balance is correct for the transaction.
You will need to wait for the transaction to confirm. What is the best way now to transfer the remainder of my bitcoin in Multibit Classic wallet to Electrum ?
Get an address from Electrum and just send all of your Bitcoin to that address. |
|
|
|
... That looks like neither a wallet nor anywhere near legitimate. That is almost definitely a scam. I highly suspect that the person you are transacting with was just scammed. He should not use that wallet. In fact, the only wallets you really should use are ones that are listed on Bitcoin.org here: https://bitcoin.org/en/choose-your-wallet. Those wallets have been vetted to be pretty safe and are legitimate. |
|
|
|
OK I have found the correct private key transaction it sweeps on electrum and gives the transaction details then what is it BROADCAST COPY OR SAVE ?
Click Broadcast. That will broadcast the transaction to the network so that it can be confirmed. |
|
|
|
Open the terminal and go to the folder where the .deb file is downlaoded. Then run where <filename> is the filename of the Armory .deb file. Hi, attempting this again now. I get the following errors. Unpacking armory:i386 (0.93.3-1) over (0.93.3-1) ...
dpkg: dependency problems prevent configuration of armory:i386:
armory:i386 depends on python (>= 2.6).
armory:i386 depends on python-qt4.
armory:i386 depends on python-twisted.
armory:i386 depends on python-psutil.
armory:i386 depends on libc6 (>= 2.11).
dpkg: error processing package armory:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Errors were encountered while processing:
armory:i386
Run |
|
|
|
but my question is are the balances of btc and bcc always synced if you do transfers on btc network and transfers on bcc network?
No. Transactions that you make on BTC will not be valid on BCC and vice versa. So your coins are not "synced". |
|
|
|
OK so from the offline https://github.com/iancoleman/bip39 I have generated a BIP32 Extended Private Key and a BIP32 Extended Public Key. Also it has generated a number of DERIVED addresses from the Multi BIT HD wallet I see the first address was the address I used to send my 0.1 bitcoin from my classic wallet to my multibit HD wallet. There are alot of other address's and private and public keys with them. Which of these private keys can I import etc into Electrum ? downloading the Electrum wallet now. Mark You can import all of the ones you see, but if you had only used one address, just import the private key for that address. Also, you should be sweeping the address, not importing. When you make the Electrum wallet, make a standard wallet from scratch. Then go to Wallet > Private Keys > Sweep and enter the private keys that you want the Bitcoin from. This will make a transaction sending the Bitcoin from those keys to addresses in your new Electrum wallet. |
|
|
|
Yes. You will need to enter your wallet words into the BIP39 Mnemonic box. Then scroll down and choose the BIP 32 tab. Then in the dropdown for Client, choose MultiBit HD. You should then see the addresses and private keys that you used from your multibit hd wallet. Also, don't use the website directly. Instead, download it from github: https://github.com/iancoleman/bip39 and then open the src/index.html file in your browser. You can use it from there and it will be all offline. |
|
|
|
Extract the private key from MultiBit HD.
That's very hard to do since MultBit HD does not provide any private key extraction utilities. To do so requires using this site: https://iancoleman.github.io/bip39/ (download the source code and run locally of course) to derive the private keys used by MultiBit from the MultiBit wallet words. |
|
|
|
|
Since the transaction has confirmed, then the receiver's wallet is either not in sync with the network or it is broken (assuming they aren't lying to you). There is nothing that you can do since the transaction is already sent and confirmed, which means that it is final and immutable now. What wallet software is the receiver using?
|
|
|
|
|
Try starting Bitcoin Core with the -salvagewallet option.
|
|
|
|
KeepKey, the company that has been supporting MultiBit for the past year or so, has decided to stop supporting and developing MultiBit. As many of you know, MultiBit currently has many issues which may cause a loss of funds or an inability to access your funds. With MultiBit no longer being developed, you should switch to using a different wallet software immediately. |
|
|
|
If multiple node/mining types can support Bitcoin how do these same types then also support different currencies, e.g. Bitcoin Cash and Bitcoin Unlimited, along with Bitcoin?
It isn't hard to write software that can support multiple consensus rules, they just need to be separated and know that they are separate coins. However Bitcoin ABC and Bitcoin Unlimited are not clients which support multiple currencies. Rather they are clients which support different consensus rules but, for the time being, are compatible with Bitcoin's consensus rules. If Bitcoin isn't a democracy then is it exposed if one entity controls >50% of node/mining CPU power + the developers of the leading node/software type e.g. Bitcoin Core. Maybe the entity could implement whatever protocol changes/consensus rules it wants?
Again, Bitcoin isn't a democracy, nor is it any other type of governance system. It is a consensus system. You are either following the consensus rules and are thus using the coin, or you are not following them and are not using the coin. The consensus rules only change if everyone agrees to change them and simultaneously does so. Even if some entity controls the developers of the reference implementation and a majority hashrate, they can't change the consensus rules at will. It requires that the users agree to the change as well. Otherwise there will be a fork and the coin will split in two. There will be some users, miners, and developers on one chain and some users, miners, and developers on the other chain. They become two distinct coins with each one having its own consensus rules. It seems after all coins are mined then transaction fees will be the only motivational force for mining.
Yes. That is the point. The idea is that there will be enough transactions and fee pressure that transaction fees will be what pays miners, not the block subsidy. |
|
|
|
I'm fairly sure that the so-called "priority" system has been (or is due to be) deprecated...
Not only is it deprecated, it has also been entirely removed in Bitcoin Core 0.15.0 which will be released in a month or two. |
|
|
|
|
Show Posts
