I use bitcoin 0.8.6 version I can compile bitcoind but I cannot compile bitcoin-qt
It shows for bitcoin 0.8.6
Why are you trying to build Bitcoin 0.8.6? It is super old and outdated. |
|
|
|
But how can I add an address to an account in Bitcoin-core?
Don't. The account system is deprecated, counter intuitive, and broken. |
|
|
|
|
The private key is not a WIF string currently. You just have a PrivateKey object. You need to get the WIF string of the private key.
|
|
|
|
I tried generating a wallet in Electrum 3.0.3 but it does not have an option to choose a "Segwit wallet". All the choices it has is the same as the previous builds.
Then you're doing it wrong. When you create the wallet, choose "create a new seed". Then in the next window, you will choose between "Standard" and "Segwit". Plus, you are right. The Bech32 addresses which start with "bc1" are not supported and, I believe, will not be in the near future.
Electrum supports them, but few other clients do currently. |
|
|
|
Ah okay so this list of 16 addresses will never have an earlier used address back in it?
It shouldn't, although the definition of "used" is a bit ambiguous. |
|
|
|
No, there is not. P2SH-P2PK is an Armory specific script type. Should be, this script format is described in the SW BIPs after all.
You're thinking of P2SH-P2WPKH |
|
|
|
@achow101 : maybe a new update is required to avoid these kind of repeated questions...
The server was down for other reasons, but it has been brought back up. However all requests will fail. A static webpage has been setup in place of the normal page that informs of the downtime. |
|
|
|
Thanks for the explenation
when i multiply G with my secret key i get astronomical number, which is not the public key, what am i doing wrong consider those params?
var Gx = 79BE667EF9DCBBAC55A06295CE870B07029BFCDB2DCE28D959F2815B16F81798
var Gy = 483ADA7726A3C4655DA4FBFC0E1108A8FD17B448A68554199C47D08FFB10D4B8
var private key = 845ADD761F80CD7BA8AD296B262939D6191370D286D29D4F06A4F1C9A8DE4E4B
i get this public key which is not the right one
C532FC9C12D71842216394CD94771F9B72302CABD0C5D4CCCF1585131548378D1B9F08218A4E3A0 F5E06D981D74720B8F59235385F25AECE75E6FFA787AF3988DD1D215B39C94994D0600D31C1971E 88CF8623AC07DCB72279CD66038AD281049F0E028D31C40417FDD97364A8D6664AEB3437740CE41 D37928CF956E64E61E8
Since this is finite field arithmetic, everything needs to be done modulo n (n is defined in the secp256k1 spec). Doing all operations mod n (or doing all operations and then performing mod n) should fix this problem. |
|
|
|
|
Only Bitcoin Core ever makes a file called wallet.dat. Try opening the wallet in Bitcoin Core.
The wallet file will only open in the software that made it. Wallet files are not compatible across clients.
|
|
|
|
|
Bitcoin 0.1.0 is unable to connect to the Bitcoin network because various network protocol changes and peer discovery changes have made that impossible. So you are not actually connected to the Bitcoin network and do not have the full blockchain synced. The coins that you have mined are effectively a fork of Bitcoin's and are completely worthless. They will not appear in an actual Bitcoin wallet or on a block explorer because the blocks and transactions do not exist on Bitcoin.
|
|
|
|
|
The problem could be a number of possible things.
You could have malware which is messing with the clipboard and resulting in bad text being copied and pasted. In this case, you should perform a malware scan on your computer.
Your wallet file could also be corrupted so the passphrase no longer works (and also the private keys are corrupted so you may not even be able to access your Bitcoin). In this case, you should restore a backup of your wallet file (of course back up the wallet file first to another location, then restore a different, older backup) and trying to see if that works too.
|
|
|
|
|
The bitcoin consensus rules are language agnostic. You can use whatever language you want, it doesn't have to be C++ (which is what Bitcoin Core, the reference client, uses).
It is certainly possible to write a bitcoin wallet in C. As for how, you will need to figure that out yourself. Keep in mind that if you can't figure it out or are unsure about anything, you probably shouldn't be making a wallet as the code that you make without understanding everything may be more insecure than the code written in an open source project that has been reviewed and audited by many people.
|
|
|
|
|
The wallet.dat file is not a text file, it is a binary file. If you want to see what data it contains, you will need to open it in a hex editor. To actually figure out what the data is, you will need to use Berkeley DB's database tools (specifically db_dump). Otherwise the data will not be in any recognizable form.
|
|
|
|
1-Is the fees on the legacy blockchain are more likely to get lower or higher in a near future? In others words, should I wait to do the transfer to a segwit address?
You are asking us to predict the future, which is impossible to do. 2-What kind a saving aprox. in % can I get from sending BTC from a segwit address to another segwit one vs a transaction done on the legacy blockchain?
For a one input, one output transaction, a segwit transaction will cost ~1/3 less than the analogous non-segwit transaction.
Since there is no rush, the best thing for you to do is to just send the transaction with a very low fee rate and with RBF enabled and then just wait for it to confirm. If it is taking too long, you can then bump the fee since you have RBF enabled. Otherwise just rebroadcast the transaction occasionally and wait a few days. |
|
|
|
|
You are probably just using the wrong BIP 32 derivation path. What derivation path were you using? Jaxx probably follows the BIP 44 standard so it uses m/44'/0'/0'/0/i, You might be looking at m/i or m/0/i.
|
|
|
|
|
Stop Bitcoin Core. Go to the Bitcoin Core data directory. Delete the folder named "chainstate". Start Bitcoin Core again. It should prompt you about reindexing the database (if it does not, it will look like it is resyncing), click "Yes" when it does. It will now look like it is resyncing the blockchain. It is actually reindexing the blockchain, the blockchain is not being redownloaded. This will rebuild Bitcoin Core's internal databases and will take several hours.
|
|
|
|
This topic has been moved to Trashcan. Duplicate thread |
|
|
|
This topic has been moved to Trashcan. Duplicate thread |
|
|
|
This topic has been moved to Trashcan. Duplicate thread |
|
|
|
|
Show Posts
