A slightly more open approach to bitcoin on the GPU
aceat64's reply in the thread "A slightly more open approach to bitcoin on the GPU".
aceat64, who opposed pay-to-IP transactions and offered bounties for open-source code

On September 16, 2010, a BitcoinTalk user called aceat64 started a thread asking for a feature of the Bitcoin client to be switched off.
Aaceat64 (BitcoinTalk post, September 16, 2010, 2:57:43 AM UTC)Sending transactions to IP addresses should be removed or at least disabled by default.
In 2010 the client could send coins straight to the IP address of another node. The receiving node answered with a newly generated Bitcoin address. In the post, aceat64 described what an attacker could do with that. The attacker sends a cent to IP addresses across the network and records which Bitcoin address each one gives back. With access to the records of an exchange or a shop, the attacker can then tie an IP address to a customer. Later the same day aceat64 posted a patch that turned receiving off unless the user switched it on. Three days later Satoshi Nakamoto replied.
SNSatoshi Nakamoto (BitcoinTalk post, September 19, 2010, 9:49:30 PM UTC)Probably best to disable receiving by IP unless you specifically intend to use it. This is a lot of surface area that nobody uses that doesn’t need to be open by default.
Satoshi had put the same change into the code that day. The switch was named -allowreceivebyip, because aceat64’s name for it, -allowiptransactions, sounded as if it covered sending too.
aceat64 was Andrew LeCody. He wrote 84 posts between July and September 2010, when he ran nodes on servers, built tools around the bitcoind program, and put up bitcoins for code he wanted to exist. He came back in 2013 and wrote 43 more.
LeCody registered on July 14, 2010. His first post, three minutes later, advised running bitcoind as a user other than root. Forty minutes after that he wrote that he would have to start posting instead of just lurking. He listed his hardware the same day: two quad-core Xeon processors, making 4,150 khash/s.
On July 25 he released a plugin that let Nagios, a server monitoring program, watch a Bitcoin node. In August he announced a web panel for managing bitcoind nodes, and on September 2 he released it as phpMyBitcoin 0.2beta. The panel needed features the official client did not have, so he kept his own build of the client, with other people’s patches applied, and handed out Linux binaries of it.
On August 19 he described a scheme for pooled block generation that had come out of a discussion on IRC. A server would hand out the work and pay each participant according to how much hashing that participant had done. To keep the reports honest, a client would send the server a summary hash for each batch of 1,000 hashes, and the server would redo a few batches at random to catch anyone lying. When the overflow bug appeared on August 15 he stopped generating on his nodes. The next day he argued against automatic checkpoints, because a bad chain like that one would have been locked in.
On September 9 LeCody offered 200 BTC for a patch that would let him set the IP address and port of the JSON-RPC interface in bitcoin.conf. Jeff Garzik wrote one. Ten hours after the offer LeCody reported that the patch worked and that he had sent the 200 BTC. A week later he dropped the patch in favor of the -rpcallowip setting that Satoshi had added to the main code.
The larger offer came on September 15. A closed-source program for generating blocks with a graphics card was in circulation, and a user had posted a cracked copy of it. LeCody told that user to take the link down, and added:
Aaceat64 (BitcoinTalk post, September 15, 2010, 1:39:18 AM UTC)Edit: Just to be clear, I don’t think anyone should use a closed source Bitcoin client and I would really like GPU generation to be open source. So I will put my money where my mouth is, I will donate 1,000 BTC to whoever releases the source for a GPU (CUDA or OpenCL) client that is cross-platform once the code has been vetted by people smarter then me.
Six days earlier he had thanked nelisky for publishing GPU code openly. It was in the network’s best interest, he wrote, that the fastest ways of generating blocks be freely available.
His last post of 2010 was written on September 19, hours before Satoshi’s reply about IP transactions.
LeCody came back on April 9, 2013, in a thread proposing that coins left unused for a long time be taken back into circulation. He wrote that he had dropped out of the community in 2010 with some bitcoins still in his wallet, that he had expected to find them if he returned, and that they were there when he did.
Aaceat64 (BitcoinTalk post, April 09, 2013, 9:55:07 PM UTC)Telling people something is their property and then taking it away later, is theft.
Two weeks later he paid 20.83225 BTC into a group buy of Avalon ASIC chips, for 260 chips. The chips did not come. In July, when the buyers were discussing who should take over the order, he offered to handle it himself and vouched for himself:
Aaceat64 (BitcoinTalk post, July 31, 2013, 3:35:41 PM UTC)As for trust, my name is Andrew LeCody and I’m the President of the Dallas Makerspace. So now you know how to track me down. 😁
The refund from the group buy reached him on October 22. An order he had placed in Avalon’s own store was refunded on August 29, after about two months of waiting. A third refund, about 2.12 BTC for a Klondike ASIC board, never came. In May 2014 he wrote that he had lost all hope of it.
On January 1, 2014 he published EasyBitcoin-PHP, a small library for talking to bitcoind from PHP. In April a thread claimed that virus signatures planted in the block chain would make antivirus programs delete it. LeCody ran a scanner over his copy of the test network’s data and posted the result: no infected files.
The last post collected here is dated August 11, 2014. The BitcoinTalk profile counts 307 posts and gives December 24, 2018 as the last active date. The other 180 posts date from 2016 to 2018. They are in threads for betting games and, in 2018, in announcement and bounty threads for other coins. They are not collected. Of the 127 posts through 2014, 112 are on this site.
112 entries / 23 threads
aceat64's reply in the thread "A slightly more open approach to bitcoin on the GPU".
aceat64's reply in the thread "Generating Bitcoins with your video card (OpenCL/CUDA)".
aceat64's reply in the thread "Ripple Giveaway!"
aceat64's reply in the thread "[BTCTC][[ASICMINER-PT]] - Public trading of ASICMINER shares".
aceat64's reply in the thread "[CLOSED] MtRed (PPS, LP+, API, 0 FEE) STRATUM on mine.mtred.com:3333".
aceat64's reply in the thread "Post Your Hash/Sec and Hardware".
aceat64's reply in the thread "Bounty: $50 Someone please fix the wiki for Map of Real World Shops".
aceat64's reply in the thread "Proposed solution to 'lost coins'".
aceat64's reply in the thread "need help with this php script".
aceat64's reply in the thread "[Group Buy#1] Avalon ASICs CHIPS! Using JohnK as escrow! FINISHED!"
aceat64's reply in the thread "Klondike - 16 chip ASIC Open Source Board - Preliminary".
aceat64's reply in the thread "Avalon Store Batch 3 Status just went to 'Refund Processing' - now 'Completed'".
aceat64's reply in the thread "World's SECOND Bitcoin lottery, Slashdot edition, this time stock markets!"
aceat64's reply in the thread "Official Bitcoin Unicode Character?"
aceat64's reply in the thread "PHP, jsonRPClient, bitcoind - Not able to pass multiple parameters".
aceat64's reply in the thread "Some Statistics".
aceat64's reply in the thread "U.S. Authorities Shut Down WordPress Host With 73,000 Blogs ".
aceat64 opens a new thread titled "Please Remove Bitcoin Casino Link"
aceat64's reply in the thread "Transaction fee effects".
aceat64's reply in the thread "Php and daemon".
aceat64 opens a new thread titled "FOR SALE: Kel-Tec Sub-2000"
aceat64's reply in the thread "Bitcoins on Mars".
aceat64's reply in the thread "[SECURITY] DoS Vulnerability".
aceat64's reply in the thread "Av reports viruses in sst file".
aceat64 opens a new thread titled "I Wrote A Nagios Plugin For Bitcoin"
aceat64's reply in the thread "bitcoind without wxWidgets".
aceat64's reply in the thread "Number of m-of-n ouputs per transaction".
aceat64's reply in the thread "Post your static IP".
aceat64's reply in the thread "LocalBitcoins Attack against infrastructure 3.5.2014".
aceat64's reply in the thread "[PATCH] implement 'xlisttransactions'".
aceat64's reply in the thread "Official git mirror of bitcoin SVN?"
aceat64 opens a new thread titled "[Request] Option to bind bitcoind's JSON-RPC server to a specific IP"
aceat64's reply in the thread "4 hashes parallel on SSE2 CPUs for 0.3.6".
aceat64's reply in the thread "ANN: BITMAIN has Tested Its 28nm Bitcoin Mining Chip BM1382".
aceat64's reply in the thread "What happens when network is split for prolonged time and reconnected?"
aceat64's reply in the thread "bitcoind command help (extended descriptions)".
aceat64's reply in the thread "bitcoind transaction to ip address".
aceat64's reply in the thread "block generation on the VIA C7".
aceat64's reply in the thread "Does name 'phpmybitcoin' cause confusion with name 'mybitcoin?'".
aceat64's reply in the thread "Strange block 74638".
aceat64's reply in the thread "On IRC bootstrapping".
aceat64's reply in the thread "What Make Bitcoin Different?"
aceat64's reply in the thread "Difficulty: More nodes active, or faster nodes?"
aceat64 opens a new thread titled "phpMyBitcoin Version 0.2beta Released"
aceat64's reply in the thread "HTTPS support for bitcoin JSON-RPC".
aceat64's reply in the thread "PeerBlock".
aceat64's reply in the thread "[PATCH REQUEST] Variable ports (205BTC reward)".
aceat64's reply in the thread "Switch to GPL".
aceat64's reply in the thread "Suggestions for pooled BTC mining?".
Context post by aceat64 in BitcoinTalk topic 423. after msg3867, quotes Satoshi.
Context post by aceat64 in BitcoinTalk topic 567. quotes Satoshi.
Context post by aceat64 in BitcoinTalk topic 750. after msg8140.
Context post by aceat64 in BitcoinTalk topic 753. after msg8417.
Thread started by aceat64 in BitcoinTalk topic 1048.
Quoted post by aceat64 in BitcoinTalk topic 820.
Quoted post by aceat64 in BitcoinTalk topic 834.
Context post by aceat64 in BitcoinTalk topic 689. before msg7335.
Context post by aceat64 in BitcoinTalk topic 868. before msg10275.
Context post by aceat64 in BitcoinTalk topic 299. before msg2908.
Context post by aceat64 in BitcoinTalk topic 431. before msg4073.
Context post by aceat64 in BitcoinTalk topic 691. before msg9041.
Context post by aceat64 in BitcoinTalk topic 795. before msg8960.