I made a screenshot of the GUI error I mentioned earlier. Perhaps someone can point a dev at this: http://picpaste.com/btc-VIcsfQft.png
In this example, I had the forum open and then brought bitcoin to the foreground and moved it a bit. As you can see, a part of the forum got "stuck" to the GUI.
When I try to start the current client, I receive this error:
bitcoin.exe - Entry Point Not Found
The procedure entry point freeaddrinfo could not be located in the dynamic link library ws2_32.dll
Topic: A bunch of questions/suggestions from a newbie, please read (Read 1211 times)
6. How can I display smaller fractions in the client? I've seen people discuss 0.0000001btc transactions, but I only see 2 decimals.
See #7, full decimals were introduced in recent versions. 3. Can I invalidate an address I have so that every transaction to it gets rejected? Those addresses could then also be purged from the blockchain to keep it at a reasonable size and only need to be stored in some sort of rejectchain. Perhaps the client could even suggest to purge addresses which have not been used in any transaction for x months. That way you could sort out addresses you never need anymore and make sure nobody accidentally still sends money to them.
That's actually really annoying now that I think about it. That means that you have to keep every wallet.dat that you create if you've given out any of the addresses in it. You can't just transfer everything to a new wallet and forget about the old one, you still have to keep it just in case someone has an old address and sends to you.
My answers in bold.
Hope those help!
I'm new to Bitcoin and spent some time to read through the informations on this site and play around with the client. Now I've got a few questions/suggestions now and hope to get some replies.
1. Why isn't the wallet encrypted by default? A lot of effort was put into making transactions secure, but anybody who has your wallet has your money. It should be trivial to add a strong encryption so that you can only open a wallet when you enter a password. Then people would not have to use eg Truecrypt for that. It would also be a good idea to confirm each transaction with the password, like you do with the normal online banking systems.
Wallet encryption is coming in the next version
2. Are messages added to a transaction public? Or could I use this message to send back confidental information, like passwords or private links?
Everything in a transaction is public, so if you put a message in a transaction it will become public too. Please note that (standard) transactions sent to other bitcoin addresses can't have messages included with them. Transactions to ip-addresses can contain messages, but those are disabled.
3. Can I invalidate an address I have so that every transaction to it gets rejected? Those addresses could then also be purged from the blockchain to keep it at a reasonable size and only need to be stored in some sort of rejectchain. Perhaps the client could even suggest to purge addresses which have not been used in any transaction for x months. That way you could sort out addresses you never need anymore and make sure nobody accidentally still sends money to them.
This is not (currently) possible. Every address you generate with the bitcoin client will be stored in your wallet.dat file, so if someone sends you bitcoins to an old address you will still receive them.
Old addresses can be purged from the blockchain if they don't hold any bitcoins anymore, but this is not implemented yet (there are some topics about this, but I didn't read those in details to see how it would work)
4. Are collisions possible? It works for MD5 and SHA1, so is it theoretically possible that someone creates a new address which is already used by someone else and that way also gets access to his bitcoins?
Collisions are possible in theory, but in practice it's so improbable that we'll probably see the end of the universe before this happens.
5. Can wallets be merged? I could set up a miner on another system and now I'm asking myself how to join both wallets later. I know I can just transfer the coins, but don't you also get fees for the blocks you've mined? How can that be transfered?
Wallets can be merged just the way you suggested: by transferring all the bitcoins from one wallet to another. The fees you gain from mining are just like normal bitcoins that you can transfer, so there is nothing special about those.
6. How can I display smaller fractions in the client? I've seen people discuss 0.0000001btc transactions, but I only see 2 decimals.
The display will adjusts itself
7. Can't the Windows release be compiled as static? I have an older system where the current release (0.3.23) won't start (some error about freeaddrinfo); client 0.3.20.2 still works however. Only problem with that version is that the background of the "transfer/addresses" block shows the underlying window, as if it's transparent when switching to it.
I'm not familiar with Windows, but you might want to report this as an issue on github
Tips are welcome: 1HGvvuyYoRHmXM2VQZdQvVaCSCnPKRArZS
1. Why isn't the wallet encrypted by default? A lot of effort was put into making transactions secure, but anybody who has your wallet has your money. It should be trivial to add a strong encryption so that you can only open a wallet when you enter a password. Then people would not have to use eg Truecrypt for that. It would also be a good idea to confirm each transaction with the password, like you do with the normal online banking systems.
Wallet encryption is coming in the next version
2. Are messages added to a transaction public? Or could I use this message to send back confidental information, like passwords or private links?
Everything in a transaction is public, so if you put a message in a transaction it will become public too. Please note that (standard) transactions sent to other bitcoin addresses can't have messages included with them. Transactions to ip-addresses can contain messages, but those are disabled.
3. Can I invalidate an address I have so that every transaction to it gets rejected? Those addresses could then also be purged from the blockchain to keep it at a reasonable size and only need to be stored in some sort of rejectchain. Perhaps the client could even suggest to purge addresses which have not been used in any transaction for x months. That way you could sort out addresses you never need anymore and make sure nobody accidentally still sends money to them.
This is not (currently) possible. Every address you generate with the bitcoin client will be stored in your wallet.dat file, so if someone sends you bitcoins to an old address you will still receive them.
Old addresses can be purged from the blockchain if they don't hold any bitcoins anymore, but this is not implemented yet (there are some topics about this, but I didn't read those in details to see how it would work)
4. Are collisions possible? It works for MD5 and SHA1, so is it theoretically possible that someone creates a new address which is already used by someone else and that way also gets access to his bitcoins?
Collisions are possible in theory, but in practice it's so improbable that we'll probably see the end of the universe before this happens.
5. Can wallets be merged? I could set up a miner on another system and now I'm asking myself how to join both wallets later. I know I can just transfer the coins, but don't you also get fees for the blocks you've mined? How can that be transfered?
Wallets can be merged just the way you suggested: by transferring all the bitcoins from one wallet to another. The fees you gain from mining are just like normal bitcoins that you can transfer, so there is nothing special about those.
6. How can I display smaller fractions in the client? I've seen people discuss 0.0000001btc transactions, but I only see 2 decimals.
The display will adjusts itself
7. Can't the Windows release be compiled as static? I have an older system where the current release (0.3.23) won't start (some error about freeaddrinfo); client 0.3.20.2 still works however. Only problem with that version is that the background of the "transfer/addresses" block shows the underlying window, as if it's transparent when switching to it.
I'm not familiar with Windows, but you might want to report this as an issue on github
Tips are welcome: 1HGvvuyYoRHmXM2VQZdQvVaCSCnPKRArZS
Hope those help!
I'm no expert, but I'll answer what I can:
1. Have seen the same criticism from elsewhere! Surely it's coming soon...
5. Can't answer about merging, but fees received from mining a block appear to be gained at the same time as the 50BTC from the block, so you might get 50.04 BTC for example.
6. Smaller fractions will be displayed when you have them.
1. Have seen the same criticism from elsewhere! Surely it's coming soon...
5. Can't answer about merging, but fees received from mining a block appear to be gained at the same time as the 50BTC from the block, so you might get 50.04 BTC for example.
6. Smaller fractions will be displayed when you have them.
I'm new to Bitcoin and spent some time to read through the informations on this site and play around with the client. Now I've got a few questions/suggestions now and hope to get some replies.
1. Why isn't the wallet encrypted by default? A lot of effort was put into making transactions secure, but anybody who has your wallet has your money. It should be trivial to add a strong encryption so that you can only open a wallet when you enter a password. Then people would not have to use eg Truecrypt for that. It would also be a good idea to confirm each transaction with the password, like you do with the normal online banking systems.
2. Are messages added to a transaction public? Or could I use this message to send back confidental information, like passwords or private links?
3. Can I invalidate an address I have so that every transaction to it gets rejected? Those addresses could then also be purged from the blockchain to keep it at a reasonable size and only need to be stored in some sort of rejectchain. Perhaps the client could even suggest to purge addresses which have not been used in any transaction for x months. That way you could sort out addresses you never need anymore and make sure nobody accidentally still sends money to them.
4. Are collisions possible? It works for MD5 and SHA1, so is it theoretically possible that someone creates a new address which is already used by someone else and that way also gets access to his bitcoins?
5. Can wallets be merged? I could set up a miner on another system and now I'm asking myself how to join both wallets later. I know I can just transfer the coins, but don't you also get fees for the blocks you've mined? How can that be transfered?
6. How can I display smaller fractions in the client? I've seen people discuss 0.0000001btc transactions, but I only see 2 decimals.
7. Can't the Windows release be compiled as static? I have an older system where the current release (0.3.23) won't start (some error about freeaddrinfo); client 0.3.20.2 still works however. Only problem with that version is that the background of the "transfer/addresses" block shows the underlying window, as if it's transparent when switching to it.
Tips are welcome: 1HGvvuyYoRHmXM2VQZdQvVaCSCnPKRArZS
1. Why isn't the wallet encrypted by default? A lot of effort was put into making transactions secure, but anybody who has your wallet has your money. It should be trivial to add a strong encryption so that you can only open a wallet when you enter a password. Then people would not have to use eg Truecrypt for that. It would also be a good idea to confirm each transaction with the password, like you do with the normal online banking systems.
2. Are messages added to a transaction public? Or could I use this message to send back confidental information, like passwords or private links?
3. Can I invalidate an address I have so that every transaction to it gets rejected? Those addresses could then also be purged from the blockchain to keep it at a reasonable size and only need to be stored in some sort of rejectchain. Perhaps the client could even suggest to purge addresses which have not been used in any transaction for x months. That way you could sort out addresses you never need anymore and make sure nobody accidentally still sends money to them.
4. Are collisions possible? It works for MD5 and SHA1, so is it theoretically possible that someone creates a new address which is already used by someone else and that way also gets access to his bitcoins?
5. Can wallets be merged? I could set up a miner on another system and now I'm asking myself how to join both wallets later. I know I can just transfer the coins, but don't you also get fees for the blocks you've mined? How can that be transfered?
6. How can I display smaller fractions in the client? I've seen people discuss 0.0000001btc transactions, but I only see 2 decimals.
7. Can't the Windows release be compiled as static? I have an older system where the current release (0.3.23) won't start (some error about freeaddrinfo); client 0.3.20.2 still works however. Only problem with that version is that the background of the "transfer/addresses" block shows the underlying window, as if it's transparent when switching to it.
Tips are welcome: 1HGvvuyYoRHmXM2VQZdQvVaCSCnPKRArZS
Jump to: