I googled for TG797n and found this thread
http://forums.modem-help.co.uk/viewtopic.php?p=5894

Memory: 61380k/65012k available (1428k kernel code, 3564k reserved, 420k data, 68k init, 0k highmem)
Calibrating delay loop... 297.98 BogoMIPS

64mb ram and 297 bogomips (a core 2 duo does around 5000 bogomips). Running a bitcoin client on such a thing would be ludicrous, it would take a month to load the blockchain if you were able to rewrite Bitcoin to run with less than the 100MB RAM it uses.

If you mean just using USB to power some other network computing device, the USB power limit is 5V @ 500 mA = 2.5 watts. If you compiled an ARM Bitcoin for a $700 Galaxy S3 phone (2GB ram, 1.4 GHz quad-core Cortex-A9, 2000 BogoMIPS if it will stay running at that without melting), you could keep it charged off USB, but you can get a PC cheaper that would actually work.

This thread is full of why?

Or just quote this post for some code to replace the first post.

...
OP makes a good point - come here for crypto-currency, get politics.

More interesting:
http://amibehindnat.com

If I can get you to follow a similar link to my server, I can see your real IP address regardless of VPS, and I could log it and show it to everybody. That uses Java, which could even send traceroutes out from the user and report back their full IP route to the server. Of course if you have Java and follow a link, you are now PwnD anyway.


It was a bulanula-style con trying to claim credit for the previous discovery and get free BTC, posts now deleted.

That whole thread is full of fail. They can't fathom GPGPU computing at all. OP is the only one with a coherent statement. It's likely a bunch of 14 year old Call Of Duty zitfaces. They would be completely [headexploded] by the thought of underclocking and undervolting a card to maximize it's energy efficiency per work, and aren't going to understand W ∝ V^2.

MSI: "tech support is a cost center, we'll just let dumbasses talk to each other in a forum so they don't call us".

The answer is no, you aren't going to damage your card, in fact you may extend it's life by reducing electromigration. There will just be underclocks and undervoltages where the card is no longer stable.

People don't think in logarithms. They won't know how much to send to buy 5 items at 20 whatever-the-fuck-BTC. Bitcoin is already established, 1 BTC was 1 BTC at 1/10000 the current value and still will be 1 BTC in the future.

The Namecoin software is console-only, it is based on bitcoind. Running it is similar to running another copy of Bitcoin, it has it's own wallet and blockchain.

If you don't need Namecoins and only want to sell them (you don't want a Namecoin domain name etc), then you likely just want to send them to an exchange and use that like an online wallet. https://exchange.bitparking.com is the oldest and largest for NMC<->BTC, but as the previous poster alluded to, they have one-time-use deposit addresses, so you can't automate multiple pool withdrawls.

http://ozco.in pool has an option to "enable automatic Namecoin exchange into Bitcoin".

The required fee is 0.0005 per KB. If a gambler's bet is funded by many smaller payments, the transaction to send the payment may easily be more than 1 KB in size. Likewise, a winning payout back to a user, likely funded by many small payments from losers, also would need an appropriate fee related to it's data size.

This is the same factor that render's satoshidice user's wallet balance unspendable. After the wallet is full of .00000001 BTC losing confirmation payments, attempting to empty the wallet of these takes a considerable fee that is much higher than 0.0005 (or indeed the value of the dust in their wallet).

If my instructions are followed and there is still an error message when launching the lastest version of Bitcoin from a fresh start, and you need the addresses or money in the wallet, a new command was added in Bitcoin 0.7.1 which you can run like this from a terminal window:

bitcoin-qt -salvagewallet

It will do a low level scan and recovery for wallet addresses and keys, and create a new wallet with this data. Bitcoin-qt will take a considerable amount of time before the GUI appears if you start using this command.

It would be helpful for the discussion if you described what OS and which installer you used to have such an awesome experience that it was worth regaling in the thread of someone having problems...

Errors accessing wallet.dat as described above are likely from bitcoin (in one form or another) still running. Alternately, the wallet file could have been corrupted by attempting to run two different versions of Bitcoin which may concurrently access the same data directory.

Bitcoin takes a considerable amount of time to shut down after you tell it to. Bitcoin-qt (the full GUI version) will "close" when you press the close button, but it may still run in the background for a minute as it shuts down and closes the database files. Bitcoind (the daemon) may be running in a console window, but it doesn't need a window showing on your current desktop to be running.

In Ubuntu, press the superkey (Windows key), and type "System Monitor" and launch it. In the system monitor, check the processes tab to see if any copy or version of Bitcoin is running. If so you must close it and allow it to finish closing.

You do not state what version you are using or where you got it from. Either run bitcoin-qt extracted from the Sourceforge Bitcoin release bitcoin-0.7.1-linux.tar.gz (bitcoin.org -> Linux version), or follow these instructions:

Ubuntu Linux users can use the "Personal Package Archive" (PPA) maintained by Matt Corallo to automatically keep up-to-date. Just type:
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-get update

in your terminal, then install the bitcoin-qt package:
sudo apt-get install bitcoin-qt

You should first remove any bitcoind or older version you have installed. Additionally, if you have never used your wallet or the addresses in it, a good fresh start would be to remove the .bitcoin directory in your home directory, which is where all data files for Bitcoin are stored.

After installing the newest version, it can be launched by typing bitcoin-qt in a terminal window if it is not added to your menu bar. Then let it run for the day or two it requires to download 4GB of data.

If you browse here, you're not that anonymous (unless you turn off images, or connect so that your IP address being logged doesn't matter).

Here's a web bug:
(it can be a blank image too)

Here's where you can see email notifications of everybody that viewed the image, along with their IP address, reverse domain name, and browser user agent: http://spypig.mailinator.com/
Update: spypig.com only sends information about the first five views, so the fun was over pretty quick.

I'll leave this here to freak you out instead:

I have 16 connections at present and am downloading blocks off the main network. I have noticed what appears to be my copy of Bitcoin receiving the same blocks multiple times in the logs:

...
received block 000000000000011a4403
SetBestChain: new best=000000000000011a4403  height=196196  work=450654222657382946220  date=08/29/12 05:28:42
ProcessBlock: ACCEPTED
received block 000000000000026a75f9
SetBestChain: new best=000000000000026a75f9  height=196197  work=450664705297513269032  date=08/29/12 06:04:29
ProcessBlock: ACCEPTED
Added 1 addresses from 178.148.109.206: 27 tried, 8031 new
Added 1 addresses from 193.106.95.138: 27 tried, 8031 new
Added 1 addresses from 173.67.5.248: 27 tried, 8032 new
Added 1 addresses from 86.143.13.243: 27 tried, 8032 new
received block 00000000000000901487
ERROR: ProcessBlock() : already have block 196036 00000000000000901487
received block 00000000000004a374f9
ERROR: ProcessBlock() : already have block 196037 00000000000004a374f9
received block 0000000000000599d86b
ERROR: ProcessBlock() : already have block 196038 0000000000000599d86b
received block 00000000000006c2bb3c
ERROR: ProcessBlock() : already have block 196039 00000000000006c2bb3c
Added 1 addresses from 176.9.122.123: 27 tried, 8033 new
received block 00000000000006af9443
ERROR: ProcessBlock() : already have block 196154 00000000000006af9443
received block 0000000000000459c29f
ERROR: ProcessBlock() : already have block 196155 0000000000000459c29f
received block 00000000000002fd4225
ERROR: ProcessBlock() : already have block 196156 00000000000002fd4225
received block 0000000000000308ea4e
ERROR: ProcessBlock() : already have block 196157 0000000000000308ea4e
received block 00000000000003d1fe23
ERROR: ProcessBlock() : already have block 196158 00000000000003d1fe23
received block 000000000000006ebef9
ERROR: ProcessBlock() : already have block 196159 000000000000006ebef9
received block 000000000000039009c6
ERROR: ProcessBlock() : already have block 196160 000000000000039009c6
received block 000000000000020904b3
ERROR: ProcessBlock() : already have block 196161 000000000000020904b3
received block 00000000000004b8c6b0
ERROR: ProcessBlock() : already have block 196162 00000000000004b8c6b0
received block 000000000000003569d4
ERROR: ProcessBlock() : already have block 196163 000000000000003569d4
received block 000000000000032f4bf4
...
Here's a much longer log: http://www.jine.be/91310
Not an isolated case, it happens every few minutes or more often. The duplicate blocks can be a few or a hundred blocks behind.

This appears to be either multiple peers responding to a request for blocks, or the same peer resending multiple datas. This could make a 3GB download take much more bandwidth than that if I am interpreting the log correctly.

bitcoind 0.7.1 windows

Comments before I go bug-filing?

(Edit - obsolete, Bitcoin issue fixed)

I have a method for splitting the torrent so it can be successfully imported to completion. It can be split into two files using the GNU split utility with this command:

split --bytes 2147570829 bootstrap.dat

This creates two files:

10/28/2012  10:12 AM     2,147,570,829 xaa
10/28/2012  10:12 AM       344,200,733 xab

sha256sum x??
fec4aa1d5a1d07b832cb22a353a689b6bf7fcb09e4822a19d9051160f195a8ef *xaa
fc07e8d67a39152a5bf1920b3bcd99d50515817ba77a28bd7d780d4cc3aa3938 *xab

This splits the torrent at block 189205, the last block that Bitcoin successfully imports out of the full 2.32GB bootstrap.dat. You can then import all torrent blocks with bitcoind or bitcoin-qt with the command:

bitcoind -loadblock=xaa -loadblock=xab -printtoconsole

(printtoconsole so you can watch the progress of block import for several hours. Use the full path to the files if needed.)

Split should be included in any GNU/Linux distribution plus MacOS. A standalone windows compile of the utility is hosted here: split.exe (72,192 bytes) (or get the GNU coreutils and dependencies full packages at http://gnuwin32.sourceforge.net/packages/coreutils.htm).

---

I found another bug/undocumented oddity; Bitcoin first processes -loadblock commands, then it looks for a bootstrap.dat file in the datadir. That means the above command will attempt to load bootstrap.dat a second time if it is located in the datadir (but will skip through all the repeated blocks quickly).

---

BTW: How do I compress the blockchain to 56% of the original size? Have 64 bit 7-zip and lots of RAM:

All I need is a French-speaking lawyer?

Dear OVH France; Dear Patrick Strateman;

On or about 22:26 October 27 2012, my organization was slandered by a user connecting through IP address 188.165.73.235.
Please see the attached slander lawsuit and notice of pre-litigation subpoena for tortious activity demanding identification of and corroborating connections for any and all IP connections on or about this time originating from and connecting through the "Bitcoin Virtual Private Server" service momentovps.com corresponding with this access through your services.

https://en.bitcoin.it/wiki/Getwork

https://bitcointalk.org/index.php?topic=51281

http://crypto.stackexchange.com/questions/1862/sha-256-midstate

http://www.javvin.com/protocolRPC.html (reply)

http://stackoverflow.com/questions/6273201/bitcoin-calculate-hash-from-getwork-function-how-to-do-it

{"result":{"data":"00000001a4940ed3fc5812a2205111bbe1b45a50557ef8d78ed74a380000016d00000000f64f077 c8c3847ef63d9b358374c540989aecc23ad7f7bb276b463b6ab22b4dc508ce4821a0575ef000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000"

change the last four bytes of "data", which is the nonce (count from 0 to 0xffffffff if you like). Hash twice. If the hash is smaller than target, submit.
don't feel like typing.

This likely has to do with your privacy settings. If you have specified not to save form and search data, or have disabled remembering browser history, then there should be nothing to go back to. Ideally the browser would not reveal what you were just looking at even three seconds before if you navigate away from that page.

Web site bug: The chart illustrating the size of the blockchain is incorrect.

Each timespan range (last 30 days, last 180 days, etc) starts at 0 MB, although that is not the size of the blockchain at that date. The only graph that shows the correct beginning and final size is the all-time graph (which looks like the hockey stick global warning graph, btw).

Breech - The lower rear portion of the human trunk; the buttocks.