It's stuck until it's including in a block unfortunately  Was afraid that that would be the case.  |
|
|
|
No tx fee included although the amount isn't that tiny and the size is minimal: https://blockchain.info/tx/072b41c0b11ff88b454e3a0c9c3a3810a74c3fa25d92209a856554d6fe26092aWas sent nearly 24 hours ago and queue position seems to move and up then move back (now saying another 10 hours). Is it likely to get "dropped" if I make sure my client doesn't broadcast it again (so I could try another spend attempt with a fee) or is it stuck until it's included no matter how long that takes? |
|
|
|
No, Armory.
Armory may be the way to go in a while but currently unless you are using a beta it requires a *huge* amount of memory (and bitcoind). |
|
|
|
So what I've done is I've gone to bitaddress.org. Generated an address and private key. Screenshotted the page and saved the screenshot as a file on my laptop. Is this now a secure address that I can send some btc to so long as I don't lose the private key file? As far as I can see the only risk is someone hacking my computer and stealing that file, the private key has never been typed, so no keylogging issue. Yes?
Bad move - using bitaddress.org (online) is risky enough but then also saving screenshots of your private keys on your laptop means that you are just going to have to "hope" that no-one else is going to find them. Key logging is a major problem but it isn't the only one. The only way to really safely secure your bitcoins is to generate your keys *offline* (and best to do that with a computer that *never* connects to the internet again). For non-techies I think that the Trezor (or some similar) device might be the best answer. |
|
|
|
Seems like the txid referenced in the vin doesn't exist. Both my localbitcoind and blockchain.info don't know about it.
Ah - thanks for that (I know what I've done wrong now). It's a pity the error handling for the raw transactions API is so minimal. |
|
|
|
I have the following raw transaction (which was created via "createrawtransaction" and successfully signed with "signrawtransaction"): 0100000001c6689b75fcd871d1ed428e4630163601183288628d5fbe5c76c7339003b0e828000000008b48304502203deb0b9f61c88bc2bb5df24acb330b6cf1f2b9b8140203cafbf5db29935dd2a60221009c7c5fc049daf358ec392c0387022218b971a2f0c50386947e3b30c71f4bd2d201410408dc1b7167df71b68c12ec0a7e77ccb602cbcb1966f3bff773c925530905d3996e7a6c7eb8a404d5dbebff428ed36d1b9c8ab70dfebe9e80e0bd6b1dd298b677ffffffff01807c4301000000001976a91407dd428c4c6f8752d5ded10edabab12d912de14e88ac00000000
which if I paste after decoderawtransaction gives me the following: {
"txid" : "c4b58d28e59e08c6cfa6272a8b56471896833aa20a5f2b05a952e6f9f0421e46",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "28e8b0039033c7765cbe5f8d6288321801361630468e42edd171d8fc759b68c6",
"vout" : 0,
"scriptSig" : {
"asm" : "304502203deb0b9f61c88bc2bb5df24acb330b6cf1f2b9b8140203cafbf5db29935dd2a60221009c7c5fc049daf358ec392c0387022218b971a2f0c50386947e3b30c71f4bd2d201 0408dc1b7167df71b68c12ec0a7e77ccb602cbcb1966f3bff773c925530905d3996e7a6c7eb8a404d5dbebff428ed36d1b9c8ab70dfebe9e80e0bd6b1dd298b677",
"hex" : "48304502203deb0b9f61c88bc2bb5df24acb330b6cf1f2b9b8140203cafbf5db29935dd2a60221009c7c5fc049daf358ec392c0387022218b971a2f0c50386947e3b30c71f4bd2d201410408dc1b7167df71b68c12ec0a7e77ccb602cbcb1966f3bff773c925530905d3996e7a6c7eb8a404d5dbebff428ed36d1b9c8ab70dfebe9e80e0bd6b1dd298b677"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.21200000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 07dd428c4c6f8752d5ded10edabab12d912de14e OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a91407dd428c4c6f8752d5ded10edabab12d912de14e88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"1iankj4HSpksoUgXSm8G7Gf7dkvLP3V9d"
]
}
}
]
}
but if I attempt to send it using sendrawtransaction then I get the TX rejected (code -22) error (which I think is normally for badly formatted JSON data). |
|
|
|
By the way, the strategy was called "selfish" mining, in the sense of being selfish or acting in only one's own interest potentially on the expense of others.
It's a pity that the OP thinks that "shellfish" is more interesting (seriously OP - could you edit your title as it just looks plain silly). |
|
|
|
They are stored by blockchain.info in encrypted form, encrypted with the password that you provide on the wallet. If you choose a weak password, then it will be crackable by a hacker. It is therefore important to choose a strong password.
Oops - I hadn't actually realised that (guess the .js stuff they use is not to store the private key locally but to do the encryption of it). Also very important not to *forget* your password either! |
|
|
|
On blockchain.info are the private keys stored online? If so, isn't it better to store them offline on a paper wallet?
The keys are generated in your browser (presumably stored in 'localStorage' or similar) so not "online" in terms of being in blockchain.info's possession.EDIT: (see below) |
|
|
|
|
Only wallet.dat has sensitive information - the blockchain files are what is shared across the P2P network (so are entirely public).
If paranoid then you might want to also check about BDB files - as presumably some wallet changes could be kept in those and not cleaned up if the client didn't close down properly.
The only other possible file to be concerned with (in regards to security) could be the config file (if you've edited it to put in the RPC credentials).
|
|
|
|
|
A "hot wallet" (i.e. one running on a server connected to the internet) is always going to be problematic.
Depending upon your needs you'd be better of having coins put into "cold storage" and signing transactions *offline* although that may not be suitable due to delays (especially if you process the *offline* transactions manually).
Typically sites like exchanges use a combination of "hot" and "cold" wallets to provide for quick response but with added security (better to only lose say 10% of the BTC due to a hacker than 100%).
|
|
|
|
|
The issue of "dormant bitcoins" has been flogged to death many times before.
No-one is going to find it any more interesting to raise it again (and no-one is interested in doing this - there are alt coins that do though so perhaps try using them instead).
If ECDSA or some other core technology that Bitcoin depends upon is broken in the future then at that point a migration to new addresses might be required but that is not likely to be something that would occur for years.
|
|
|
|
|
I use postfix/dovecot on my VPS but the distro is SUSE - wouldn't call myself a wizard at all but might be able to help you out with some configuration settings if that's the issue.
|
|
|
|
The point that is being missed is insurance - if you're computer gets hacked and you lose all your BTC then it's simply "tough luck".
You're assuming that it's possible to create workable deposit insurance for BTC. Insurance would most likely only be in the form of fiat - but I would rather get back 90% of the current fiat value of my BTC than to lose it all to a hacker. |
|
|
|
|
The point that is being missed is insurance - if you're computer gets hacked and you lose all your BTC then it's simply "tough luck".
Devices like the Trezor may get us there without the need of a 3rd party but I think given the option quite a few people (especially the elderly and non-technically minded) would rather trust a bank than themselves.
|
|
|
|
|
Wow - quite a few replies - and some good points.
Where I see *banks* fitting in is simply giving you the convenience to transfer funds in and out of BTC via online banking and in insuring your BTC asset (something that I think might be important to those less tech savvy than many of the members of this forum).
|
|
|
|
I believe the paypal must be send as a gift.
Can be gift charged back?
Yes it can - and by the Paypal TOS you cannot use Bitcoin (or any other internet currency). Just read the stories of those that tried and failed creating services for Paypal to BTC (exactly why it should be stickied if it isn't already). |
|
|
|
|
Some thoughts:
1) China is unhappy with the US printing money (just Google it).
2) China seems to be warming to Bitcoin more and more (it was on the CCTV news recently and not negatively portrayed).
3) China has called for a *new world currency* (again just Google it).
4) China has the majority of ASIC production.
5) Chinese banks already let you buy PMs (gold and silver).
How long until Chinese banks let you create accounts in BTC?
|
|
|
|
Under no circumstances can you trust someone's word about not keeping logs. This applies to VPN providers, bitcoin mixers, email hosts, or any other privacy-sensitive service. If it's conceivably possible that they are keeping privacy-destroying logs then you must assume they are, and act accordingly.
I hate to do this (in fact it might be the first time I actually have) but: +1 |
|
|
|
|
Isn't there a stickied topic about Paypal and Bitcoin?
If not there probably should be (as the same questions come up often - as do people offering BTC via Paypal who end up getting screwed no matter how cleverly they think they have "worked it out").
|
|
|
|
|
Show Posts
