I always thought that blocks were like trees where one transaction creates a branch. Is it more like a line and where one fork or double spending creates a branch?
It's a line, more specifically, it's a chain since each block is chained to the one behind it. I ask this because I thought hashPrevBlock would stay the same for a transaction when trying to mine it until the transaction in the block has been mined but now I'm assuming it changes everytime someone mines a block unassociated to that transaction?
Transactions don't have a hashPrevBlock, blocks do. A block's hashPrevBlock is always the same, regardless. Also, on a side note, if I were to start mining would my machine also be 'listening' to blocks which have been mined in order to update itself and 'pass' on the work and get more work as the block it was trying to mine has already been discovered? If we say 50% of machines are needed to confirm correct nonce for your discovered block are we waiting on these 50% to agree and then you will get the reward? How does this reward process begin and end ie discovered block > sent to all machines > 50% confirm (how can my machine decide what 50% of the machines are?) > they've confirmed > the reward is assigned to my address (how does this get assigned via blockchain?)
It doesn't work like that at all. There isn't any need for any percent of the network to confirm anything. Rewards are not assigned to addresses by other people. If you are a miner, you create the block. In your block, the first transaction is the coinbase transaction. That transaction is one that you create yourself. It is the only transaction in the block that is allowed to have a blank input and it must output at least 12.5 Bitcoin. This can be split among multiple outputs and it goes to whomever you want; usually yourself. When you create that block, you broadcast it to the network and then immediately start working on the next block. If you receive another block, you are supposed to validate it (check the proof of work and the transactions). If it is the same height as the one you just broadcast, you keep it but keep working on the block you already started. If it is a higher height (longer chain, more PoW) then you discard whatever you are working on and begin building a new block on top of the one you just received. |
|
|
|
Some posts show old dates so I'm not sure IF you guys imported the posts from the old website or they are new , If it's new then there is something wrong with the dates. As for this : https://btcarmory.com/transifex/ (which I'm pretty sure It's new) , It shows 28 August for some reasons while we are 22 (and I guess you wrote it few days back) The dates can be set when the post is written. I back dated some of them to match when the release was made. The one that says August 28 is a mistake. I meant to type 18 and I didn't see it until goatpig merged in that post and I was to lazy to change it. |
|
|
|
hmmm, seems it's not working today. every time i send a request, it returns "Request Queuing failed. Please try again." any idea what could be going wrong? thanks in advance!
I often encounter that error but it eventually fixes itself at some point. Just try again later. At the moment I can also get the same error. Should be working now. Removed the DB. |
|
|
|
I would recommend forcing https for the website and enabling HSTS preloading to prevent MITM downgrade attacks. These options should be configurable from the cloudflare interface. It should already be forcing https. When I go to http://btcarmory.com/ I always get redirected to the https site. I've added it to the preload. |
|
|
|
The OP hasn't been updated in over a year.
Has anybody figure out how to build Bitcoin 0.12.1 or the 0.13 RC?
Try Bash for Windows on the Linux Subsytem in Windows 10. Then just use that as if you were using Ubuntu and cross compile for windows. I'm trying to see if this works now. In theory it should. |
|
|
|
Is this True value of my account ?
No, not really. There is no set value of an account. The price is subjective because it depends upon the post quality. The prices of accounts are also non-linear, even though the calculation is linear. The estimate is based upon what I saw in the market a few months ago and never bothered to actually update it. |
|
|
|
|
Hmm. Latest build of dev. I don't see any of my transactions now and no balance. The dashboard tab says I am online but the right hand corner says offline.
|
|
|
|
The main site is actually https://bitcoincore.org/. The developers don't like having everything in the same place (i.e. github). It makes it a central point of failure and a huge target for attacks. |
|
|
|
|
No, you would have to make the CSV your self. However, you can get JSON data of each block from most block explorers and from Bitcoin Core.
|
|
|
|
It could be an SPV wallet. That would certainly save on space. It could also use pruning.
But are there SPV wallet for all coins? Can they be done? I don't know that much. First thing that comes into my mind is Cryptonote/Monero: there the simple wallets I know of use a "trusted" public daemon, which I am almost certain it has the whole chain. From what I've read SPV wallet is a quite different thing.... I don't know as I haven't studied all coins. For coins that are based upon Bitcoin, SPV wallets are possible. |
|
|
|
Is it technically possible to create a desktop wallet where we can store all crypto including bitcoin and all existing and to be launched coin in one wallet? I know one can keep them in online exchanges but it is risky.
To be launched? If it doesn't have a blockchain, it cannot have a wallet. Now, for the existing ones, it can be done, but it's quite some work and nobody will use it. Just imagine how big is the blockchain for Bitcoin to load. Now, each coin has its own chain, which has to be downloaded. Each coin has its own daemon in a way or another which will have to stay in memory. The result will be something big that needs a lot of resources and which nobody will fully use, since nobody cares of ALL cryptos. Even the small exchanges de-list the coins with low volumes to free resources... It could be an SPV wallet. That would certainly save on space. It could also use pruning. |
|
|
|
Is it technically possible to create a desktop wallet where we can store all crypto including bitcoin and all existing and to be launched coin in one wallet? I know one can keep them in online exchanges but it is risky.
It is possible to do so, but AFAIK, no such wallet exists. |
|
|
|
When i try to go on the account price estimator it is loading and we can't use it.
Please fix it, thanks
I noticed when I was search using a UID number it gave a red error message saying your request can not be processed try again later.
Never saw that message displayed before.
I do not see any such errors. |
|
|
|
|
All you can do is check each account's posting history and see if they have posted the signed message or the address that the message was signed with.
|
|
|
|
Say, I am using MultiSig2 & MultiSig3 for cold storage, while using MultiSig1 for regular usage. Will the cold storage be secured in that case?
It would not be a good idea to do that. By doing so, when you spend your Bitcoin, you are revealing the public keys to your cold storage. If someone were to figure out the private keys to that cold storage, they could spend the Bitcoin. Furthermore, it wouldn't even be cold storage since the private keys to spend from your cold storage address are online and thus vulnerable to malware attacks to steal the keys. |
|
|
|
|
Unfortunately no, that address is now lost. Bitcoin Core currently randomly generates the addresses. It does not (yet) generate them deterministically. That means that old backups will not have any newly generated keys.
|
|
|
|
So, for what you guys tell me here, the BIP32 Extended Key is the true address structure to generate from (the first address list). So what does the second Derived Private Key represent, since it seems to generate a valid address child chain?
The derived key is an extended key that is derived from the first extended key. |
|
|
|
If the binaries hosted on bitcoin.org are compromised or down, some of the developers host their own builds of the binaries. Since these are deterministically built, the hashes should all be the same. These hashes for all of the files are stored in the gitian.sigs repo and they are all signed with the PGP keys of all the signers. The organization of that signature repo is self explanatory. I host my gitian build on my GitHub repo here: https://github.com/achow101/bitcoin/releases. IIRC Jonas Schnelli also hosts the binaries on his website, but I don't remember where they are. |
|
|
|
Are you speaking about scenarios that could happen ? or there is an actual threat going on, because I don't understand why It became suddenly important to verify signature while we didn't see such a thread in the past.
Wondering too. Cobra made an alert on bitcoin.org: https://bitcoin.org/en/alert/2016-08-17-binary-safety but no one knows why he did it and what he means by it. So right now now the assumption is that something nasty have been compromised, but there is no proof of any such compromise yet. |
|
|
|
An extended private key is a format. A derived private key is any private key that is deterministically generated from another private key. Any private key can use the extended private key format to give wallets information about how to derive that key given the master private key that it was derived from. So, which key do I use to import into Electrum or something?
To import a deterministic wallet into Electrum, you would use a private key in the extended private key format encoded with the base58 check encoding. |
|
|
|
|
Show Posts
i don't have a compiler to use a "source" code ...
