|
Bitcoin Core encrypts keys individually, i.e. the entire file is not encrypted. Each encrypted key is the roughly the same length, as are most other pieces of data in the wallet. You can tell if it is corrupted by looking at the unencrypted data and seeing if that looks corrupted. If keys themselves are corrupted, then you can't tell until you try decrypting them.
|
|
|
|
What about forcing user/pwd values via command line? Bitcoin-qt.exe -server=1 -rpcuser=<usr> -rpcpassword=<pwd> Don't use rpcuser and rpcpassword. As I said, they are deprecated now and will be removed in the future. All bitcoin.conf options can be specified on the command line. |
|
|
|
|
Those parameters are for deploying soft forks in Bitcoin. If your altcoin does not plan on deploying soft forks or these soft forks specifically, then you don't need those parameters. However removing those parameters means that you will need to change a lot of other code to not be checking for whether those forks are active or not.
|
|
|
|
|
Your scriptPubKey is wrong. You are using pushdatas to push the hex numbers 5 and 10 to stack. To push just 1 byte, you don't need to use OP_PUSHDATA1. You should only be using OP_PUSHDATA1 when you have more than 75 bytes of data to push. opcodes 1 through 75 (0x01 - 0x4b) just mean "push that number of bytes to the stack".
Also, Bitcoin Core will not be able to sign your transaction because it does not know what kind of script your scriptPubKey is so it does not know about what needs to be done in order to sign it properly.
|
|
|
|
PLEASE UPDATE THE PRICING CODE
When I price accounts, they are way too expensive.
Pull requests welcome. If you think it is broken, fix it. I see no issues with it. 3.Achow should just remove the price calculating function. (I'd do it if you are ready to accept the pull request)
I don't think the price calculation should be removed as that is the explicitly stated purpose of the site anyways. |
|
|
|
|
Try using the WIF compressed key instead.
|
|
|
|
|
Go to Help > Rescan and Rebuild Databases. Then restart Armory.
|
|
|
|
Many people thinking this will never happen and it is all just hype. I must admit it is hard to believe such technology would come this early for Bitcoin. Heck, many countries do not even have widespread internet but they will be able to transact Bitcoin. haha
It's already happening. It was already working and happening when it was announced. It isn't just hype; there are instructions for how to set up your own stuff now since it is already broadcasting now. People have already set up receivers and are receiving blocks. The satellite is best for places where you have a low bandwidth and poor internet connection. That type of internet connection is too poor to support running a full node, but is fine for sending transactions as transactions are small. The satellite then allows you to receive blocks through something other than a poor internet connection. |
|
|
|
however most wallets are mainly designed for Windows and OS X as these are the major players. Linux is often heavily neglected, unfortunately.
That's not true at all. Most wallets are developed on and designed for linux systems as most developers prefer using linux. Linux is often the best supported system since that is where development and testing happens. For both Bitcoin Core and Armory, wallets are developed on Linux and only tested on Windows and OSX briefly and by few people. OSX is often most heavily neglected. |
|
|
|
This topic has been moved to Trashcan. Duplicate |
|
|
|
And will some of them start changing their minds a little faster if the next Core release goes through with the proposal to disconnect nodes signalling 2x?
That pull request has already been merged into Bitcoin Core. It will be part of the 0.15.0 release. This means that if you run Bitcoin Core 0.15.0, you will be disconnecting all segwit2x nodes. A large part of the technical community opposes segwit2x for a variety of technical reasons. Furthermore, Bitcoin Core will not be supporting Segwit2x. The hard fork will likely still happen, just not very cleanly. If segwit2x continues to refuse to implement replay protection, refuses to set the hard fork bit, refuses to change their network magic, etc, then their hard fork will cause a lot of problems. This could result in network partitioning and replayed transactions (and thus potentially fraud). Since it is basically guaranteed to be a messy chain split, they should be working to make it as clean as possible, after all, they are the ones diverging from the status quo. |
|
|
|
Note: I am not a PHP programmer Your probably want to do something like this: $wind = $bitcoin->sendtoaddress($address,$amount1,"","",true);
|
|
|
|
Actually I don't know about Bitcoin Core 0.14.2 when I clicked on the link I get the details of the installation which shows 145GB required space I didn't understand is it need that much space? to installed please explain as a new be is it required for me to installed if yes what are the benefit by installing this version. please advise.
Yes, you need that much space for the full blockchain. Bitcoin Core is a full node; it downloads and stores the entire blockchain so that it can fully verify every single block and transaction on the network. This provides you the best security and privacy for a desktop wallet (besides privacy in transactions themselves). You can run Bitcoin Core in pruned mode so it will not take up so much space on your hard drive. However this still requires you to download the blockchain (but not store it) and sync in order to use Bitcoin Core. |
|
|
|
|
Check that Bitcoin Core is fully synced. Stop Armory and run just Bitcoin Core. If you don't see a green progress bar, hover your mouse over the checkmark or spinning circle in the bottom right hand corner and see if that matches the block height reported by block explorers like blockchain.info. It should be at least 480,891.
|
|
|
|
If you do need a bigger dish they are common and used on eBay. I saw how to use
the OuterNet via those instead. I still think this unit is likely to work on the USA Satellite in
the above links with only the small Reciever plate.
I think you could just use a DirectTV satellite dish. There are tons of those on buildings around where I live, and a lot of them probably aren't in use. But what if you are in North Korea? I was wondering if it would be possible to make the first transaction ever in Best Korea now that there are satellites broadcasting the blockchain.
But you say these devices only receive data. If so then how do you broadcast your transaction back into the blockchain if internet is blocked on the entire country and there are no wifi signals or anything? Let alone the fact that there aren't even computers or cellphones.
You would need a tourist to smuggle you a phone with wallet software installed, but even then, what do you exactly do with it?
I wonder who will be the first to manage to broadcast a bitcoin transaction in North Korea, that would be epic.
It is currently receive only because transmitting to the satellite requires a lot of power and extra stuff that most people won't be able to get. The satellite is best for those who have a poor internet connection; they can't download the blockchain because it is too big, but they can still broadcast transactions as those are tiny. The satellite allows those people to also be able to get the blockchain (well part of it, only new blocks right now) |
|
|
|
|
Your transactions have several confirmations now.
|
|
|
|
btw could you please advice any app for ios/andoid /web wallets to import private key and get my bitcoincash? wanna to convert it to bitcoin somewhere  AFAIK, there are no mobile or web wallets which support Bitcoin Cash. I only know of 2 wallet software that support Bitcoin Cash: Bitcoin ABC and Electron Cash. Both of these are desktop wallets. |
|
|
|
This is a known bug in blockchain.info's web wallet. The address that you have likely uses an uncompressed public key. However the private key that blockchain.info gave you is one that tells the wallet to use a compressed public key. This will result in a different address. To fix this problem, go to https://www.bitaddress.org and download the website (download links in the bottom left hand corner). Open the website in your browser locally (don't use the actual site) and click on the Wallet Details tab. Enter your private key and click View Details. Scroll down to where it says "Private Key WIF" (not "Private Key WIF Compressed"). Copy the string next to that; that is your private key. You can then import that into another wallet. |
|
|
|
|
I'm told that you will need a satellite dish and not just a small receiver like the one you pictured as the signal is quite weak. But if that works for you, great!
|
|
|
|
|
Show Posts
