1920 BTC win; max bets on "less than 1" to "less than 64" would win you 6400 BTC ($461,000 at $72). Or just as likely lose you 6524 BTC. |
|
|
|
I would recommend contacting Timothy Lee or Jon Matonis at Forbes with your story of being denied clarification, and see if they can get a response, being from big financial media. If the ruling is all that is published, it can be interpreted as a law, where you should get legal advice from a lawyer, and decisions on violations of the ruling will be made by a judge. Your lawyer would probably advise you not to get on FinCEN's radar. FinCEN is likely used to strong-arming big banks with their play-ball tactics into handing over unfettered back-door access to individuals, not dealing with the individuals directly. It is likely the "new" MtGox now includes a nice government portal for downloading customer transaction data. The "Bank Secrecy Act" is the "your bank account is no secret to the government act". The secret is that telling people about it is punishable, and records are exempt from the freedom of information act. Title 31 of the United States Code, section 5324, provides (in part): No person shall, for the purpose of evading the reporting requirements of section 5313 (a) or 5325 or any regulation prescribed under any such section, the reporting or record keeping requirements imposed by any order issued under section 5326, or the record keeping requirements imposed by any regulation prescribed under section 21 of the Federal Deposit Insurance Act or section 123 of Public Law 91–508— [...] (3) structure or assist in structuring, or attempt to structure or assist in structuring, any transaction with one or more domestic financial institutions. Section 5324 further provides that a violation of this provision may be punished by a fine or up to five years in prison, or both.[6] http://overlawyered.com/2012/04/structuring-who-can-get-away-with-it-and-who-cant/ |
|
|
|
When you register for a new account, the very first paragraph says: RESTRICTIONS FOR NEW MEMBERS
After registering, you will be unable to post in any section except "newbies" until you have spent some time on the forum and have published a few posts.
If you are registering to ask a question, please ask it in the newbies section. Do not wait to ask it just because you must post it in "newbies": the question is very likely to have already been asked. If you don't end up getting good responses, you can ask it again elsewhere after you are established, or you can move the entire topic.
If you are commenting on Bitcoin, use your newbie wait time to read more about Bitcoin. If you are criticizing Bitcoin, find similar criticism using the search tool to see which points have already been covered. A good use of your newbie wait time is reading Satoshi's old posts.
Then the checkbox you must check at the bottom to register says: ☑ I understand that I will initially be unable to post to most forum sections, as explained above. Then there is a sticky note at the top of the newbie forum. It is impossible to make people read, apparently. |
|
|
|
|
Positive correlation: Bitcoin mining causes temperatures to rise six months later.
|
|
|
|
This transaction will never confirm. The unconfirmed transaction that funds it was double-spent elsewhere: Feb. 8, 2013, 5:19 p.m.
9e3dd4340b0136398770e2098ccb61ce1b560e841862ea4419e71b2fa516789b
This transaction includes 0.00100000 BTC as fee.
size: 520 bytes
priority: 418,117,180
input: 0.36190040 BTC
0.04811640 BTC from unconfirmed 61c18c117de198a80ba6ae7842b329cb702122faae379eb9b38a3f58985af1b7:0 (1xe98RWBYNTi89tYVtUqeeXeZnb1FwLVN)
0.01386000 BTC from e44b9e860111182b3fb548a98271eb561a7ab201d0b2154987c214c8a26eb88a:0 (1La2HUcX6vgUVdyzVbLbphqWAVL8vAgXEb)
0.29992400 BTC from 3761b53bd0f924e022a6d4654dee8ae3bd4d10fc77b2e8c562903b3b76767f49:0 (1Gga4nXPfq4eQG3EopXDsTqVN4KeyCFgHy)
output: 0.36090040 BTC
0.01090040 BTC to 1GoKgKw26amVVxYeYiij4aDK4FqQz8oufD
0.35000000 BTC to 1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYDp This is the "unconfirmed" transaction listed above: Jan. 31, 2013, 2:09 a.m.
61c18c117de198a80ba6ae7842b329cb702122faae379eb9b38a3f58985af1b7
This transaction includes 0.00100000 BTC as fee.
size: 374 bytes
priority: 1,669,287,721
input: 0.74911640 BTC
0.34965440 BTC from ab914f7bec20001d13ebec5813ba20438bb8c37cf3a0dbf10aec4d5dfcad2252:0 (1GAAZqMSZtnVDKde8EBYe169YvLxY4QvJW)
0.39946200 BTC from 56d9c7e42f4096f42f58fee793f78ba1b7cf5f027e74fcbcc5331ca3ae72c7c4:0 (1NndCUx4hUgyBa6WdmxTnU1jtxnwbfJJXe)
output: 0.74811640 BTC
0.04811640 BTC to 1xe98RWBYNTi89tYVtUqeeXeZnb1FwLVN
0.70000000 BTC to 1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYDp The 0.34965440 BTC and 0.39946200 BTC inputs of that transaction are already spent here: http://blockexplorer.com/tx/77f7a56d32275fe59cff04fc5fd2babf11a3810a4bb2cfdcf299ff42ba13aadf#i25740008It appears that all transactions above are you sending to satoshidice with a client other than the official bitcoin-qt (which doesn't allow sending of unconfirmed coins). The procedure to remove both of the above unconfirmed transactions from your wallet to restore your balance will depend on what wallet you are using. |
|
|
|
I've got a conundrum: What's the best way to generate bitcoin notes securely, assuming that I don't trust myself? I've read the https://www.casascius.com/controls.aspx "Statement of Controls" as a starting point, but as a matter of pedantry, I don't want to see the private key. To create the notes, I do the following, which I don't consider to be an issue for the purposes of this discussion: - On an offline PC, generate bitcoin notes using the Bitcoin Address Utility.
- Print them to paper.
- Export list of bitcoin addresses (not private keys) to USB
- Secure Erase hard drive
However, the issue is the next few steps: - I guillotine each note, face up so I can see where to cut - The private key is facing me during the slicing.
- Take the list of bitcoin addresses, and mail-merge onto Avery Sticky Labels with human readable and QT Code.
- For each note, I place between a piece of black folded card. (So that it can fit into a DL Sized Windowed Envelope)
- Find the appropriate label for each note, and adhere to window position on card above -Private key can be glanced
- Put folded card, containing note into windowed envelope, so address/QT code are visible from the outside.
- Adhere a tamper-evident security hologram (with individual serial number) across envelope seal
As you can see, there are a number of stages above I can view the private key! Is there a way to mitigate this problem? For example, is there secure note generator which can create a single bitcoin note on an entire sheet of A4, A5 etc...), with all the private details are on one side, and the address on the other, and when folded, it will be visible through the envelope window? Anyone purchasing a physical spendable bit bill knows that a malevolent creator can know the private key data contained in the bill, and there must be trust in the creator. Nothing can make a spendable/redeemable independent store of bitcoin more trustworthy than the trust placed in the creator, since all the secret information enabling spending must be known by the creator to create the bills. "Being able to glance at the key" is not a concern for the purchaser, as they know you can do so. To earn such trust, you must have procedures to effectively remove the private keys from anywhere they were used except the printed bill. I see a few problems in your original post: 1. USB/flash memory is not reliably erasable, you should only trust rotating hard drives supporting the SATA secure erase feature (and know how to use it). 2. Private key data should not be stored anywhere but the securely erasable media. 3. Access to private key data should not be extended to any printing company or any individuals other than the trusted person. 4. You must make detection of the private key more difficult than a note in an envelope (unless you are making your envelopes out of sheet metal). Anything that circulates as currency must not allow even the most determined man-in-the-middle to observe the private key or create a facsimile of an unredeemed note after obtaining it's key. |
|
|
|
hmm maybe i should prof read befor i hit post...
anyone really familure with the pci-x expansion slots and what cards they all accept?
Not an ATI Radeon HD 5xxx - 7xxx, which is the only GPU that makes sense to mine with. You could also just buy 2 BTC and have it double in value before a GPU costing 2 BTC would earn you back your investment. |
|
|
|
The biggest change is a new central location storing lots of information about Bitcoin. Oh, wait, that's not new: https://en.bitcoin.it/wiki/ChangelogDevelopment on pywallet has continued also. |
|
|
|
|
In your wallet, you have a collection of previous payments you have received. If you have sent out other payments (creating change), these individual balances may be stored in differing amounts in various addresses not shown to you.
When you create a transaction sending Buddy a payment, one or several of the previous payments you received will be used to fund the transaction paying Buddy.
When Buddy creates a transaction sending you a payment, one or several of the previous payments he received will be used to fund the transaction paying you back. There is no guarantee that he will be sending the same "input" payment back to you as an "output". Since transaction fees will alter the amount, the Bitcoin client may combine different input amounts to find an ideal amount to send, or the particular payment may have already spent, so you will get back some other coins from different funding sources.
An outside observer may not be able to readily observe what's going on. When you send a payment, it may come from other addresses than your published addresses, and when you get your refund, you can also create a one-time-use address just for that. Never using the same address twice makes it very hard for someone to have any idea what's going on between two individuals.
|
|
|
|
www.ubuntu.org just install it onto another partition on your hard drive and only use it for bitcoin client. Not the best advice, only better. If you have a dual-boot machine, and your Windows machine gets infected with a remote admin toolkit, which can be as simple as clicking on a zero-day exploit site link like this one while browsing the forum, then the attacker can simply run his "scan the raw disks for private keys and ftp them" utility to steal your address balances. An ancient shitbox wiped and used only as a Bitcoin wallet will be safer than a multipurpose day-to-day computer with more exposure surfaces. I think the OP was referring to stuff like this: http://www.cbsnews.com/8301-205_162-57511962/some-new-pcs-infected-before-boxes-even-opened/ |
|
|
|
However, most transactions do not contain a *public* key.
Fixed. https://en.bitcoin.it/wiki/TransactionsA Bitcoin address is only a hash, so the sender can't provide a full public key in scriptPubKey. When redeeming coins that have been sent to a Bitcoin address, the recipient provides both the signature and the public key.  Is it still true that, Vanitygen won't work with the latest Catalyst drivers?
Is the best advice still to go back to an older version of Catalyst, or is a modification of VanityGen being worked on to work? Still true as of the beta v13 driver from a month ago, and not likely to change. Vanitygen is open source, so it can be fixed by anybody, although it will be about 1000x easier to install a different driver version than to learn OpenCL programming and discover what changes need to be made. Samr is known for popping back into existence with a new version of vanitygen with new features though. |
|
|
|
correct me if I'm wrong. according to my records, 3 people have not payed.
I'll correct you. The correct spelling is paid.  |
|
|
|
I would guess that for most systems just bashing on the keyboard and moving the mouse a bit before you start generating is sufficient, but I wouldn't take my word for that.
Some rand generators use this method to obtain entropy data, but that doesn't do anything by itself. Vanitygen uses OpenSSL to generate it's random private keys, which is pretty well vetted. If you have concerns that the startup state may be deterministic, you can use something like gpg key generator which does use random keyboard input to increase entropy, and then feed the gpg key data into vanitygen as a random seed. There are rare hardware platforms that include a real hardware random number generator, notably VIA C3 processors and Intel 840 chipsets. These can feed urandom true hardware randomness with a kernel patch. extra credit: spot the bitcoin developer https://www.kernel.org/doc/Documentation/hw_random.txt |
|
|
|
The files, after you've booted can be found in /lib/live/mount/medium/vanitygen if you used WinISO (On Windows 7) to put it in the root of the iso-image.
To prepare the USB disk (make it bootable and add iso), I used Universal USB Installer 1.9.3.0. (On windows 7)
..
Consider: -Your windows machine is completely PwnD, making any code that touched it untrustable and/or -Your adversary can remotely access or physically steal the USB device and recover anything you've deleted or had in RAM (swap file). Better still would be to disconnect all hard drives and storage media on the target machine, and only boot and run off a live CD with a compile environment. You then only have to figure out how to get vanitygen code to the machine securely (removable non-writable media), and how to get the address/privkeys off the machine securely (print, burn CD) without creating any persistent digital copy whatsoever. If you don't actually need vanity addresses, easier is just to use the bitaddress HTML/JavaScript generator code offline. |
|
|
|
Where is the bitcoin.conf file located?
https://en.bitcoin.it/wiki/Data_directoryThere won't be a conf file created by default. You need to create a text file, and save it as bitcoin.conf. Here is a default bitcoin.conf template for you to modify and use: ### bitcoin.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.
## JSON-RPC options (for controlling a running bitcoin-qt/bitcoind process)
# server=1 tells Bitcoin to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.
rpcuser=bitcoinrpc
rpcpassword=3QtnxrB7P5y4EpBdad1MkCeB2RHmArvcarw7udgXsAce
# How many seconds bitcoin will wait for a complete RPC HTTP request
# after the HTTP connection is established.
rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.*
#rpcallowip=192.168.1.*
# Listen for RPC connections on this TCP port:
rpcport=8332
# You can use bitcoind to send commands to bitcoin-qt/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1
# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem
## Network-related settings:
# Run on the test network instead of the real bitcoin network.
#testnet=1
# Connect via a socks proxy
#proxy=127.0.0.1:9050
# Select the version of socks proxy to use (4-5, default: 5)
#socks=5
# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=<ip:port>
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it.##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to attempt connection to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333
# or use as many connect= settings as you like to connect ONLY to specific peers:
#connect=69.164.218.197
#connect=192.168.1.20:8333
# Do not use Internet Relay Chat to find peers.
noirc=0
# Maximum number of inbound+outbound connections.
#maxconnections=125
# Miscellaneous options
# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100
# Add an optional transaction fee every time you send bitcoins.
#paytxfee=0.01
# Add timestamps to debug.log
#logtimestamps=1
# User interface options
# Start Bitcoin minimized
#min=1
# Minimize to the system tray
minimizetotray=0 |
|
|
|
|
After the zombie apocalypse, guns will be currency.
|
|
|
|
|
You could contact the pool admin and see if they have a log of the reject reason. There are basically two reasons for rejects:
1. You submitted work for a block number that has already been found, or
2. You submitted a hash that is invalid or below the minimum difficulty
#1 happens for everybody occasionally, a new block happens about every 10 minutes, so some miners keep working on the old block for a few seconds until they get new block information from the pool
#2 the pool might be requesting higher difficulty than 1 but your software still sends all difficulty 1 shares. You might have hardware problems that result in invalid hashes being found.
|
|
|
|
|
Better would be the fork blockchain up to block 225453 (or another set of bad 225430-225453 that can be imported), so that it included the bad block and it can be fed to different version of clients and they can replicate the BDB freakout. We all have the blockchain up to 225429, but the bad chain went "poof" upon reorg.
|
|
|
|
|
Show Posts
