|
I'll bid 1 BTC + shipping to canada.
|
|
|
|
https://en.wikipedia.org/wiki/Ticket_resaleIn Ontario, Canada, re-selling the tickets above face value is prohibited by the Ticket Speculation Act and is punishable by a fine of $5,000 for an individual (including those buying the tickets above face) or $50,000 for a corporation. I guess you're ok if you sell it at face value.
|
|
|
|
That would make sense, if that address showed ANYWHERE in the bitcoin-qt install, but it doesn't. That's why I'm confused.
The only way I could find the 1Dkd7... address to begin with was to go like I was going to sign a message or request a payment. Seems odd the Address Book won't show your own address by default.
Yep, they are hidden on purpose, probably in a (misguided?) attempt to not confuse the user. Every time I read a thread like this, I become more convinced that change addresses should be disabled by default. Users who want the pseudo-anonymity offered by random change addresses, and who understand it, can re-enable it. it was excluded because it breaks the absraction of a "wallet". users do not need to know what a change address is, nor do they need to know what inputs or outputs are. this is the same reason why paypal/ach/sepa transfers do not disclose their internal implementation details. having that feature in the client complicates application design, and adds the burden of wannabe power users asking for support. |
|
|
|
|
run as admin?
install opencl drivers?
|
|
|
|
|
it's not enforceable at the protocol level because there is no script to check the current number of blocks. the best you can do is encrypt it with some random key that takes a long time to crack.
|
|
|
|
|
>bitcoin
>PetaFLOPS
LOL
you do realize bitcoin uses 0 floating point calculations, rite?
|
|
|
|
|
vmware works fine for me. you just have to configure the virtual network properly.
|
|
|
|
[...] - 99.9% Uptime Service Layer Agreement
[...] it's service level agreement |
|
|
|
|
the developer of litecoin has announced that he is upgrading litecoin to 0.8. he was not given an ETA yet.
|
|
|
|
why would it get contamination from other appliances??? The meter would show exactly what is plugged into it. The appliances on other sockets wouldn't matter.
he forgot to decontaminate the power strip with a class 3 UL certified electromagnetic interference removal solution. |
|
|
|
|
you need to rescan the wallet. either start bitcoind with --rescan after you have imported they keys, or set the rescan parameter for the last imported key to "true".
|
|
|
|
Is called you can hookup a monitor to it and it won' lag when you are mining on the GPU. implying the motheboard doesn't have a integrated GPU |
|
|
|
|
Does ASICMiner have publicly available financial statements? If so, you can look there.
|
|
|
|
|
Out of the 40 topics on the first page of Technical Support, 7 are about confirmations. That's 18% of the questions. We need a FAQ for the section. Either as a link to bitcoin wiki FAQ or as a stickied topic.
|
|
|
|
confirmed  |
|
|
|
your transaction was either too "spammy" (too big, not enough fees), or it was an attempted double spend. if it's the latter, all attempts to resend the transaction will fail. if it's the former, you can leave bitcoin-qt running and it will automatically rebroadcast the transaction (wait at least 3 hours). what a fuck bitcoin.
lol |
|
|
|
learn to search. there are at least 3 threads about this.
They all say the same thing, either: - install rate limiting software (I've been down that road before, no thanks)
- use trickle (I'm not on Linux, and trickle isn't on cygwin)
- reduce maximum number of connections (which just reduces the likelihood of saturation, it can still occur)
The default client should have limiting support built-in, otherwise only people with fast and high-capacity Internet connections can ever use Bitcoin (or at the very least, be a full node, increasing network security). I can only run the client a few hours a day now. yes, there's also discussion on that on github. the reason is something along the lines of not easy to implement. edit: https://github.com/bitcoin/bitcoin/issues/756 |
|
|
|
|
what's preventing a malicious registrar/ISP/government from intercepting the dns request? this is currently worse than posting the address on a https page.
|
|
|
|
|
Show Posts
