I was assuming the transaction would be sent out by the Green Address ( 1LNWw6yCxkUmkhArb2Nf2MPw6vG7u5WG7q ) stated by MagicalTux at : https://bitcointalk.org/index.php?topic=48170.0 , but instead I received it from: 1MVtwuuKvuzUa2mWiBnrA9UzqnP7tBaB9A (0.1 BTC - Output)
15sgsXuS7LPGPT18cjH5ecuUwPK6jTbFJZ (0.21206082 BTC - Output)
1BSX5JfYF9d4i7oU2DmQkbGFMqiQd7NoR3 (86.88689612 BTC - Output) Which one would be the green address then? Mt. Gox is robbing Peter to pay Paul! The bold address is what Mt. Gox uses to rob BTC from users accounts to satisfy outstanding BTC withdraws. I had a BTC deposit to my Mt. Gox account from mining and they took it, it shows so in the block chain, and paid it to two other addresses. Checking my account it shows the full balance, yet the block chain says different, BTC transferred from my Mt. Gox address to the Green address. They are doing the Bitcoin Shuffle big time, WTF. They could be taking our BTC and trading on the market for all we know.  I thought they were just an intermediary acting as a middle man, not pilfering my account to pay johnthedong.  Seeing this activity doesn't make me feel good about their business practices. Looks like I'm going to have to get that paper wallet sooner rather than later. Sincerely, WTF "I went to the bank to get my $0.40 back out, and it wasn't even the same $0.40, I checked the mint marks on the dimes! The bank teller told me that they have a computerized balance that shows how many dollars I have, but clearly they are just taking someone else's money to pay me back mine!" That is lame that it didn't come from the green address, but you should also understand that mtgox doesn't pay transaction fees when you withdraw, so a 0.1 BTC transfer is likely going to be a low priority transaction on the Bitcoin network; you are lucky it went through at all. Using the green address option indicates you are making a time-sensitive payment to someone; mtgox should add a .001 fee from your balance to make it go through in a timely fashion. |
|
|
|
Let me know if you decide to part it out. I'd definitely take the GPU and CPU. Plus, I'm in Seattle, so you're quite close  The CPU and MB would go together if I parted things out, one by itself is not too useful to me. I would do CPU+MB+5830 for $140 + FedEx ground (in mtgox BTC or USPS money order; paypal or dwolla with rep + fees). (feels like killing the money tree for it's wood...) I also have several 160gb hdd, hdtv tuner cards, etc. that I need to part with sometime too. |
|
|
|
You cant.
I knew if we waited long enough, there would finally be someone informed enough to answer this six-month old thread. |
|
|
|
|
Funny now, considering how the thread I created here where I posted links to a Dwolla employee's Facebook and the information gleaned from there got deleted by mods (the same employee that called me on my home phone telling my my funds were locked and wanted photo ID in color). Maybe if they had some more pushback after holding people's money for ransom (with no policy detailing what they were going to do with personal data) we wouldn't be here now...
We basically have another layer removed that further reveals these are inept midwest college students who started this "service" without the slightest idea about how banking works.
|
|
|
|
|
edit: GPU/mainboard/CPU are sold.
I have a mining PC that has been running 24/7 for the last six months, all set up. I need to turn it into cash now instead of in six months of mining. I'll unplug it and send it to you, you put your pool username and password in the startup bat file, and you are making 345Mhash+ (currently at 1060MHz, 1.250V).
It has a 200mm quiet fan in an improvised case side to keep it at 60C, I'll include the original side of the case along with this fan (you probably don't need an old piece of foam mailed to you).
- "White box" case
- Cooler Master 460w PS
- Biostar MCP6P M2+ Motherboard (onboard nVidia GPU, 6ch audio, 100mb Ethernet, 4xSATA raid + IDE)
- AMD Sempron 140 2.7Mhz AM3 CPU
- SAPPHIRE ATI Radeon HD 5830 Xtreme 1GB GDDR5 PCI Express 2.1 x16 (w original box + acc)
- 1GB Corsair XMS2 DDR2 PC6400 800MHz
- Hitachi Deskstar 180GXP 7200RPM 40GB HDD
- LG 40x12x40 CD-RW
- Sony 1.44" Floppy
Software config:
XPSP3 all updates (no lic included), Catalyst 11.6/SDK2.1, Phoenix 1.7.4 source running from Python 2.7, Trixx
42 BTC shipped USA, or cheaper w pickup Portland OR.
Damn sure cheaper and faster to ship than a BFL single...plus you can play Portal 2 on it...
|
|
|
|
A few considerations to analyze: - + With merged mining, generating namecoins is much more difficult - 40% of Bitcoin (although more people are getting them now). It is probable that many merge-mined namecoins are being discarded by uninterested miners,
- + You can redeem namecoin for domain names (although they are approaching free now), in addition to it being a currency,
- + Namecoins used to purchase domain names are destroyed and removed from the money supply forever,
- - It is doubtful that many have or ever will commonly use namecoin as DNS. It may be more practical as a place to register names for other purposes,
- the exchange rate is also affected by BTC-USD value fluctuation.
|
|
|
|
That die is aweseome. Only thing I'd change is 59-60 get replaced with a penis.
or 0x04, plus roll 64 times for a hexadecimal key:  |
|
|
|
I laser engrave my wallets on metal plates, cut them up into jigsaw puzzle pieces, and hide the pieces around my house.
Try to cut tungsten...  And how to generate "5J" + 50 base58 characters for a private key?:  Obviously 59 and 60 mean "roll again"... |
|
|
|
I thought I would put these up for sale for your power projects. 120V AC Solid State Relays 3-32VDC control voltage 10 Amp - 3 BTC each (7 available) 5 Amp - 1 BTC each (4 available) Contact me for current price ~$10USD ea in bitcoin + priority mail shipping per order (USA). In case you can't do math, 10A = 1200W.    |
|
|
|
and I think I just won...  |
|
|
|
I read the rules...  |
|
|
|
A Satoshi won't get you very far with these ladies... |
|
|
|
aka LABIA (Ladies and Bitcoin in Arms)
My PENIS (People Encouraging Nudity of Internet SLUTS) would like to get in touch with your LABIA, in hopes of stimulating more CLITS (Coin Ladies In Threads Stripping). Here's to all the SLUTS (Sexy Ladies Using Tipping Smartly!) |
|
|
|
I tried again, this time having ~/.bitcoin/ be a ram disk. $ mv .bitcoin .bitcoin.real
$ mkdir .bitcoin
$ sudo mount -t tmpfs -o size=1600M tmpfs .bitcoin
I thought 1600 megabytes would be big enough, but forgot to take the database logfiles into account, and it ran out of space after about downloading 136k blocks in 26 minutes. The shape of the curve is still the same. The CPU very rarely was flat out during the download, and so I'm thinking the limit now is how quickly the blocks are coming over the network. The blocks get bigger with time, so take longer to transmit. If you want to try something for giggles, set up another Bitcoin "server" machine on your local 1gig+ Ethernet network using PCIe network cards (or verifying the onboard MAC is PCIe), with the blockchain on a RAM disk on that machine too. Then instead of hitting the Internet to connect to a mystery peer, you can use the connect=192.168.0.xxx:8333 option in your bitcoin.conf to connect to only that machine (this is the best way to run multiple Bitcoins behind NAT, BTW.) Have that server be the faster machine, so you know the disk/cpu/ram latency limitations are on the machine downloading the blockchain. You will probably be able to copy the blockchain files between the machines' ramdisks in about 20 seconds. You will find that with the network limitation clearly removed, it still takes a few orders of magnitude longer than the network speed. If the Bitcoin client cached the whole block index in memory, this might save a few disk read operations per blockchain transaction. |
|
|
|
The hard part is not downloading or storing the block chain. It's building, maintaining and guaranteeing the on-disk consistency of the block and transaction index that is necessary for validation.
Well, I suppose you've given it a lot of thought already. But I still have a hard time believing downloading the block chain and creating an index requires all that disk hammering. On my computer, the .bitcoin directory is 1.6GB big. It's big, but not that big. It even fits in the memory of most computers! How can building it require hammering the disk for hours? You'd believe how much it writes to the disk if you make a new ~8gb disk image, defrag & push all the data to front, and then simply install and run Bitcoin. The blockchain will be fragmented all over the disk from all the writes and erases to the database. |
|
|
|
Strange, the difficulty of 1Firo is significantly lower than that of 1Sivo - why?
vanitygen.exe 1Firo
Difficulty: 4476342
vanitygen.exe 1Sivo
Difficulty: 264104224
The change happens at a particular address: Prefix difficulty: 77178 1QLa Prefix difficulty: 78362 1QLb Prefix difficulty: 4553521 1QLc This is a quirk of how the 25-byte (50 digit hexadecimal) Bitcoin address is converted into Base58 (represented by numbers and letters), and the different maximum values that can be stored in 25 base256 digits vs 34 base58 digits. The Bitcoin address in it's native binary form (that you never see) is 25 bytes, it's parts are: byte 0: Network ID Byte (0x00 for main bitcoin network) byte 1-20: ripemd160 hash (20 bytes) of sha256 hash (32 bytes) of 0x04+public key (65 bytes) byte 21-24: checksum: first four bytes of sha256 hash of sha256 hash of bytes 0-20 above This would be 50 hexadecimal characters long (base16), with a possible digit value between 0-F. We will ignore byte 0, it is always 0x00, and Base58 conversion always preserves this leading 0 byte by directly encoding it as a "1". That means the "vanity" part of the address is bytes 1-24, 24 bytes of random hash output, or 48 hexadecimal digits. The maximum value that this can be is 0x FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF ffff ffff (the lower case "f"s are the checksum, and won't be all FFFFs for the maximum ripemd160 value.) We can guess from the output below that this maximum possible address value encoded in Base58 becomes 1QLbxxxxxx.... something:
1QLa8LNNFeYs7KJWvxMdR5YtRjkwtQtkyb
1QLabhman6ZQyz3musbqV1RjFmE3pyT29j
1QLaJHv2LCSYo8WgT9qPf4rdttduRGyozX
1QLarwzJCUWGuQEZ4uWPsYVz8N2P5XmeQU
1QLckWG2tx17suupYU2FfeWunTCZMuJKW
1QLcMk7NVLwvg8gw2ihJTuG8x7WLYCjMg
1QLcLr6AoN687CpH1JZnfeMmWvUka5NHX
1QLc47945bSCv4J1Z4yRuvUbtooQqmGJ1
1QLcU9NNxaqfvqMRXD8dFtL2SktL3YmBT
1QLc1D24uDbvy327MzifEChVvATAeDsbF
See how the 1QL a addresses are full length, but the 1QL c addresses are one digit shorter? That is because the only way to have an address starting at 1QLc or greater is by having a binary address that is 59x smaller. |
|
|
|
Got a couple of these: MSG: Server is terminating! MSG'd graet in IRC, he's working on it.. |
|
|
|
Is the pool down?
My miner was hashing away, but when I checked the web site it says my hash rate was 0 and that my miner was stopped.
Sam
The US server was down for at least a few hours, but it just came back up while I was checking other ports and other countries' servers. |
|
|
|
The buyer will file a item-not-as-described, and eBay will tell them to mail back the item. When the buyer mails back a package with a tracking number showing something was returned, regardless of whether they returned an empty box, a rock, or a piece of paper with a now-empty bitcoin address, the scam buyer gets their refund. |
|
|
|
|
Show Posts
