If you have a lot of RAM (4 or more), you can open the bitcoin.conf file and add the following line: where <n> is an amount of memory in MB. If you have 4 GB RAM, I suggest you set it to 1000 so dbcache=1000. If you have 8 GB, I recommend 4000. If you have more RAM, you can set it to be higher, but after around 8000 setting it higher stops being any more helpful. |
|
|
|
Your question is incredibly hard to understand. What is "tx_hex"? Do you mean the hexstring of the raw transaction or the txid? If you have a hexstring, you can use decoderawtransaction to decode the raw hex of a transaction. or tx_hex a key, and value is stored in the data directory of bitcoin ?
more like
key => value pair
where tx_hex is key and hextransaction is stored on disk ?
No. That is completely incorrect. When you have ask for a transaction with getrawtransaction, you must have txindex enabled. The txindex means that Bitcoin Core's databases will have records with txids and the location of where the transaction data is stored in the blk*.dat files. When you request a transaction, it looks up the txid in the database and pulls it from the disk. Then it represents the binary data as a hex string. |
|
|
|
|
Bitcoin Cash has implemented two way replay protection so any transactions created with a Bitcoin Cash wallet (e.g. Bitcoin ABC) will be invalid to the Bitcoin network and anything created with a Bitcoin wallet (e.g. Bitcoin Core) will be invalid to the Bitcoin Cash network.
|
|
|
|
|
Different block versions are present in both testnet and mainnet. It is used for signaling to activate soft forks. The first block version is version 1. Previous soft forks used a system called IsSuperMajority (ISM). These used fixed version numbers, consuming numbers 2, 3, and 4. We now use a new soft fork mechanism called BIP 9 Versionbits. BIP 9 specifies that all version numbers must have the top 3 bits of the version number be 001, which results in a version number of 0x20000000. From there, other bits are set for various soft forks, and unset once the fork has activated. For example, segwit uses bi 1, so setting bit 1 results in a version number of 0x20000002.
|
|
|
|
|
The alert system was removed for several reasons. First of all, it is a source of centralization. It was something which, as a protocol message, burdened other developers who needed to write in support for the alert system and the alerts could only be issued by few people. Secondly, it is actually not known who holds the alert key (even by those who are known to hold the key). Since there is only one key, as the key is given out to more people, the more people can get their hands on the key (by attacking someone who has it) and potentially cause trouble for the network. Lastly, the alert system actually has several DoS vulnerabilities which can be exploited by whoever has a copy of the alert key.
The alert system was a centralized source which imposed things on users, which is against the ideals of decentralization. Instead of forcing users to use the alerts system, a more decentralized approach has been adopted. Users are now supposed to choose where they wish to receive their information from. These can be from various Bitcoin news outlets, websites, forums, Reddit, etc. The user gets to choose how he wishes to stay up to date on the latest Bitcoin news. If there is a network emergency event, it is extremely likely that users will learn of it very quickly as all platforms will be warning of that event as soon as it is found out about. There is no need for an alert system when such information about network wide events will be posted to all Bitcoin forums and Bitcoin news sites will be publishing stories about it as soon as they hear of it. Even mainstream media may write stories about network-wide emergencies as Bitcoin is becoming popular enough for that to happen.
|
|
|
|
|
No. The fee only matters for the first confirmation. Confirmations after that are simply the count of blocks that have been built on top of the block that your transaction was included in. You have no control over how quickly you receive additional confirmations as that is all part of the Bitcoin mining process.
|
|
|
|
what of the private key itself..hope it is safe ??
The private key is never revealed in signatures. Otherwise Bitcoin wouldn't be secure as signatures are used in transactions. |
|
|
|
I have taken your suggestion. If I were to delete all of the block files (blk00000.dat, blk00001.dat, blk00002, etc.) would the program start the block loading over, only consuming less space?
No. Do not delete any files. That will corrupt the databases and require you to redownload and verify the entire blockchain. Just set the line I told you to set and restart Core. It will do everything automatically. If it is not, then you have created the file incorrectly. In that case, make sure the file is just bitcoin.conf. Make sure there is no extension like .txt on the file. If you are using windows, you should enable the "Show File Extensions" option so you can see the entire filename. |
|
|
|
Use pruning. Go to the Bitcoin Core datadir (the path to which you can find by going to Help > Debug Window > Information and next the the "Datadir" label) and create a file named bitcoin.conf (just a text file, but without a .txt extension). Then add the following line to it: Restart Bitcoin Core and you should see that it is no longer taking up so much space. |
|
|
|
|
Yes. Signing anything will reveal the public key.
|
|
|
|
I have 2 things I need to know about the fork that I don't think have been documented (or I haven't yet found them).
By "the fork", I assume you mean the Bitcoin ABC hard fork. 1. Can transactions be reused on both chains? If I send bitcoin from one address that has a private key with both types of bitcoin on it, can that transaction be cloned and broadcast to another chain?
No, they have implemented two way replay protection. 2. What is the probability of the fork to produce an actual split in the chain?
100%. The fork is scheduled to occur when the median time is at or after August 1st, at 12:20 PM UTC. As I understand it, bip91 was supposed to help prevent this?
Not this one. BIP 91 was supposed to prevent BIP 148 from activating and potentially causing a fork. Bitcoin ABC's fork is not BIP 148 (in fact it doesn't even have a BIP). BIP 91 itself could have caused many forks. |
|
|
|
|
Your wallet files are corrupted, and that is what is causing the crash. Specifically, some keys are able to be decrypted, others are not, so the program exits out of an abundance of caution. This generally means that your wallet file is corrupted. To fix that, you use --salvagewallet, pywallet, or restore a backup. If none of those work, then the coins are lost.
|
|
|
|
Can i delete last block?
No, you cannot do that or you will end up reindexing the whole database. The post that told you to do that was deleted for spamming and being outrageously incorrect and bad advice. Downloading all from 0 again seems rather pointless.
Resyncing the entire blockchain usually fixes the problem. It isn't pointless, it makes sure that you have a non-corrupted copy of the blockchain. You can't just use the data you already have if it is corrupted. |
|
|
|
|
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. |
|
|
|
|
Show Posts
