Search content
Sort by
Showing 20 of 23 results by inglian
I've killed all led in my reach. From sat receiver over PC to smartphone dock... 
Why is that?Oh, but if they are bright blue LEDs, especially if they flash, then that's really cool. Circuit designers had to wait so long for blue LEDs to become cheap that we should be happy to get as many of them as possible, per dollars spent on electronics.
Re: Anyone else having trouble with Bitstamp Ripple transactions?
I just tried depositing 100 XRP, and it bounced right back to my Ripple wallet one minute later. I see the send and receive in Ripple, but no indication at Bitstamp.
v0.8.1-beta 2013-03-17 15:35:36 -0400 on Win7, after running for several days on testnet. Nothing suggestive in debug.log. Restarted fine, still running an hour later.
http://i.imgur.com/xEaXnGr.png
http://i.imgur.com/xEaXnGr.png
Yes, I am using the release 0.8.1 Win7 build. Looking in the debug log, there are two testnet IP addresses consistently claiming "blocks=140700".
This is under discussion at https://github.com/bitcoin/bitcoin/issues/2398 Final comment from gmaxwell is, "...its due to some testing phantomcircuit is doing."
This is under discussion at https://github.com/bitcoin/bitcoin/issues/2398 Final comment from gmaxwell is, "...its due to some testing phantomcircuit is doing."
I've got something like this happening, as well, where the problem seem to be a bogus block height. Twice now, letting 0.8.1 (Win7-64) run overnight on testnet, I come back to see the display showing ~80,000 blocks remaining. Debug shows the valid current testnet block height loaded, out of estimated total blocks 140,700 (!!).
Here is a log snippet just prior to shutting down, which appears to show the bogus block height conversation:
About 20 minutes after restarting, it's imagining there are about 20K blocks over actual testnet height, again.
Here is a log snippet just prior to shutting down, which appears to show the bogus block height conversation:
Code:
received block 000000006d7ee37ba38b4c4226b5b635bd06faedda5273eac6e03ee647ff7a21
Committing 29 changed transactions to coin database...
SetBestChain: new best=000000006d7ee37ba38b4c4226b5b635bd06faedda5273eac6e03ee647ff7a21 height=63403 work=6294868716572339 tx=135252 date=2013-04-02 01:09:46
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 103ms
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
received getdata for: block 000000006d7ee37ba38b4c4226b5b635bd06faedda5273eac6e03ee647ff7a21
Flushed 11237 addresses to peers.dat 90ms
ResendWalletTransactions()
Flushed 11237 addresses to peers.dat 68ms
Flushed 11237 addresses to peers.dat 90ms
accepted connection 75.119.251.161:46145
send version message: version 70001, blocks=63403, us=96.241.62.47:18333, them=75.119.251.161:46145, peer=75.119.251.161:46145
receive version message: version 60000, blocks=140700, us=96.241.62.47:18333, them=0.0.0.0:0, peer=75.119.251.161:46145
socket closed
disconnecting node 75.119.251.161:46145
Committing 29 changed transactions to coin database...
SetBestChain: new best=000000006d7ee37ba38b4c4226b5b635bd06faedda5273eac6e03ee647ff7a21 height=63403 work=6294868716572339 tx=135252 date=2013-04-02 01:09:46
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 103ms
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
received getdata for: block 000000006d7ee37ba38b4c4226b5b635bd06faedda5273eac6e03ee647ff7a21
Flushed 11237 addresses to peers.dat 90ms
ResendWalletTransactions()
Flushed 11237 addresses to peers.dat 68ms
Flushed 11237 addresses to peers.dat 90ms
accepted connection 75.119.251.161:46145
send version message: version 70001, blocks=63403, us=96.241.62.47:18333, them=75.119.251.161:46145, peer=75.119.251.161:46145
receive version message: version 60000, blocks=140700, us=96.241.62.47:18333, them=0.0.0.0:0, peer=75.119.251.161:46145
socket closed
disconnecting node 75.119.251.161:46145
About 20 minutes after restarting, it's imagining there are about 20K blocks over actual testnet height, again.
Re: "Error opening block database. Do you want to rebuild the block database now?"
Same problem, immediately upon upgrading from bitcoin-0.8.0rc1-win32 to 0.8.1, on Win7-64.
Chose Cancel. The .sst file referenced did not exist, but no problem creating the .sst file with Cygwin "touch". Deleted the .sst file I had created, restarted Bitcoin-Qt, ran fine the second time, no further mention of .sst files in the debug.log. 2-month old SATA laptop drive with no problems.
Chose Cancel. The .sst file referenced did not exist, but no problem creating the .sst file with Cygwin "touch". Deleted the .sst file I had created, restarted Bitcoin-Qt, ran fine the second time, no further mention of .sst files in the debug.log. 2-month old SATA laptop drive with no problems.
Code:
Bitcoin version v0.8.1-beta (2013-03-17 15:35:36 -0400)
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 2013-03-20 12:52:37
Default data directory C:\Users\username\AppData\Roaming\Bitcoin
Used data directory C:\Users\username\AppData\Local\LargeDB\Bitcoin
Using 4 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\username\AppData\Local\LargeDB\Bitcoin\database ErrorFile=C:\Users\username\AppData\Local\LargeDB\Bitcoin\db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate
Opened LevelDB successfully
LoadBlockIndex(): last block file = 14
LoadBlockIndex(): last block file: CBlockFileInfo(blocks=789, size=119258104, heights=225479..226267, time=2013-03-12..2013-03-17)
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=00000000000002e60135b76ddd31d727f4ca44c28f142e85ff38c199b1a098e8 height=226267 date=2013-03-17 02:17:42
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: IO error: C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate\013292.sst: Could not create random access file.
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 2013-03-20 12:52:37
Default data directory C:\Users\username\AppData\Roaming\Bitcoin
Used data directory C:\Users\username\AppData\Local\LargeDB\Bitcoin
Using 4 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\username\AppData\Local\LargeDB\Bitcoin\database ErrorFile=C:\Users\username\AppData\Local\LargeDB\Bitcoin\db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate
Opened LevelDB successfully
LoadBlockIndex(): last block file = 14
LoadBlockIndex(): last block file: CBlockFileInfo(blocks=789, size=119258104, heights=225479..226267, time=2013-03-12..2013-03-17)
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=00000000000002e60135b76ddd31d727f4ca44c28f142e85ff38c199b1a098e8 height=226267 date=2013-03-17 02:17:42
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: IO error: C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate\013292.sst: Could not create random access file.
All good with bitcoin-0.8.0rc1-win32
Good upgrade from 0.7.1-353-g3afefd8-win32
With an empty data directory and bootstrap.dat, 3h 40m to current blockheight. Multithreading doesn't seem to start until after bootstrap.dat is loaded.
Good upgrade from 0.7.2. Reindexing completed through blockheight 216274 in 37m. Update to current block from the network had long periods with no data coming in, but did show good multithreading when data was arriving.
- Windows 7
- HP 8440 laptop with 4 cores
- 8GB RAM
- FiOS connection
Good upgrade from 0.7.1-353-g3afefd8-win32
With an empty data directory and bootstrap.dat, 3h 40m to current blockheight. Multithreading doesn't seem to start until after bootstrap.dat is loaded.
Good upgrade from 0.7.2. Reindexing completed through blockheight 216274 in 37m. Update to current block from the network had long periods with no data coming in, but did show good multithreading when data was arriving.
Great results with bitcoin-0.7.1-353-g3afefd8-win32
bootstrap.dat was in place. I didn't see much multithreading, but the blockchain bootstrap and update ran fast. debug.log excerpts:
Worked fine with a small transaction in and back out.
- Windows 7
- HP 8440 laptop with 4 cores
- 8GB RAM
- FiOS connection
- bitcoin-qt.exe -datadir=C:\Users\username\AppData\Local\LargeDB\Bitcoin071 -logtimestamps -dbcache=250
bootstrap.dat was in place. I didn't see much multithreading, but the blockchain bootstrap and update ran fast. debug.log excerpts:
Code:
2013-01-23 03:11:54 SetBestChain: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 work=8590065666 tx=2 date=2009-01-09 02:54:252013-01-23 03:44:50
Loaded 193000 blocks from external file in 1976602ms
2013-01-23 03:59:43 SetBestChain: new best=00000000000006a1e50bedf15148d15aafa469aa02c0e9ad1d8fa3a479bb770e height=193001 work=420251477813705134572 tx=5770265 date=2012-08-09 06:17:15
2013-01-23 04:05:29 SetBestChain: new best=000000000000046242d4984ecf2217e9afa113f2835bffbff118f2df4d80b216 height=194000 work=429298255956894417423 tx=5993959 date=2012-08-15 10:02:59
2013-01-23 04:44:27 SetBestChain: new best=000000000000034a7dedef4a161fa058a2d67a173a90155f3a2fe6fc132e0ebf height=200000 work=493482865315456673820 tx=7316696 date=2012-09-22 10:45:59
2013-01-23 05:48:37 SetBestChain: new best=000000000000048b95347e83192f69cf0366076336c639f9b7228e9ba171342e height=210000 work=628963747775700992096 tx=9344662 date=2012-11-28 15:24:38
2013-01-23 06:52:09 SetBestChain: new best=000000000000036d1e5c410c393017277f8ccb59cb30a9143e818e788ecd2515 height=217000 work=726735151411243146775 tx=11340810 date=2013-01-18 09:24:24
2013-01-23 06:58:57 SetBestChain: new best=0000000000000369ae94ccf9ac51e1b89251ba18904c1d0685f31c100d0eab59 height=217650 work=735807150813835318925 tx=11562582 date=2013-01-23 04:29:53
2013-01-23 07:00:31 SetBestChain: new best=000000000000049506cb15e13a38c2f9116d530603698d0bf3dabcb0a3bf091a height=217665 work=736016504646202830590 tx=11569307 date=2013-01-23 06:59:32
Loaded 193000 blocks from external file in 1976602ms
2013-01-23 03:59:43 SetBestChain: new best=00000000000006a1e50bedf15148d15aafa469aa02c0e9ad1d8fa3a479bb770e height=193001 work=420251477813705134572 tx=5770265 date=2012-08-09 06:17:15
2013-01-23 04:05:29 SetBestChain: new best=000000000000046242d4984ecf2217e9afa113f2835bffbff118f2df4d80b216 height=194000 work=429298255956894417423 tx=5993959 date=2012-08-15 10:02:59
2013-01-23 04:44:27 SetBestChain: new best=000000000000034a7dedef4a161fa058a2d67a173a90155f3a2fe6fc132e0ebf height=200000 work=493482865315456673820 tx=7316696 date=2012-09-22 10:45:59
2013-01-23 05:48:37 SetBestChain: new best=000000000000048b95347e83192f69cf0366076336c639f9b7228e9ba171342e height=210000 work=628963747775700992096 tx=9344662 date=2012-11-28 15:24:38
2013-01-23 06:52:09 SetBestChain: new best=000000000000036d1e5c410c393017277f8ccb59cb30a9143e818e788ecd2515 height=217000 work=726735151411243146775 tx=11340810 date=2013-01-18 09:24:24
2013-01-23 06:58:57 SetBestChain: new best=0000000000000369ae94ccf9ac51e1b89251ba18904c1d0685f31c100d0eab59 height=217650 work=735807150813835318925 tx=11562582 date=2013-01-23 04:29:53
2013-01-23 07:00:31 SetBestChain: new best=000000000000049506cb15e13a38c2f9116d530603698d0bf3dabcb0a3bf091a height=217665 work=736016504646202830590 tx=11569307 date=2013-01-23 06:59:32
Worked fine with a small transaction in and back out.
Re: BitcoinCoffee.com | New coffee inventory in a Week (Pre-order Now and SAVE)
I placed order #77 on Nov 10, based upon your apparently good forum.reputation. I've received nothing but the order ack. No response to my email on Dec 9 via your website "contact us" page. bitcoinCoffee@tormail.com bounces.
I tracked down the old owner on IRC, and he just cheerfully refunded my purchase.
The new owner should be posting shortly to confirm the shop remains in operation.
More to follow in saddambitcoin's thread.
Thanks to all who helped by response, PM, and IRC, including the new and old owners. It was a great intro to #bitcoin-otc. Nice to see a reputation system working that links to the BTC e-commerce world.
Re: BitcoinCoffee.com | New coffee inventory in a Week (Pre-order Now and SAVE)
I placed order #77 on Nov 10, based upon your apparently good forum.reputation. I've received nothing but the order ack. No response to my email on Dec 9 via your website "contact us" page. bitcoinCoffee@tormail.com bounces.
I installed https://github.com/downloads/etotheipi/BitcoinArmory/armory_0.82.4-alpha_win32_and_win64.msi which runs for a few seconds and then silently dies without logging anything. Same immediately after a reboot with bitcoin-qt running and up to date on blockchain. Any troubleshooting I should do?
Odd... can you create a new shortcut for it and run it with the " --debug" flag? That might reveal a little more information. Unfortunately, it sounds like a seg-fault...
I got nothing with --debug, either. Uninstalled, deleted all files in C:\Users\[uname]\AppData\Roaming\Armory\, reinstalled, and now everything works, including sending the transaction after signing it offline.
Thanks again!
My first attempt at broadcasting an offline transaction with Armory kept silently failing. Logs show "ConnectionError: Connection to localhost DNE" despite Armory showing "Connected" status on the main screen and current block number.
This problem has come up quite a few times in the past, but it was so long ago I honestly don't remember if it was ever resolved. However, there have been some networking-related bug fixes since then. Please download 0.82.4 and try again: https://github.com/etotheipi/BitcoinArmory/downloads
I installed https://github.com/downloads/etotheipi/BitcoinArmory/armory_0.82.4-alpha_win32_and_win64.msi which runs for a few seconds and then silently dies without logging anything. Same immediately after a reboot with bitcoin-qt running and up to date on blockchain. Any troubleshooting I should do?
inglian, are your network connections limited on bitcoin.conf? If so, take out the limit.
I faced similar problems when I had the number of connections limited to 25, so Armory would only connect to the bitcoin client when one of the regular network clients dropped it's connection.
I faced similar problems when I had the number of connections limited to 25, so Armory would only connect to the bitcoin client when one of the regular network clients dropped it's connection.
Connections are default (125), though with NAT I have none incoming and just my default 8 outgoing. So I should be able to accept another 117 connections locally.
Thanks to you both for the help.
My first attempt at broadcasting an offline transaction with Armory kept silently failing. Logs show "ConnectionError: Connection to localhost DNE" despite Armory showing "Connected" status on the main screen and current block number.
I finally had to use command line bitcoind sendrawtransaction on the full tx hexcode in the log. Would be nice if the "Copy Raw Tx" button included the signature.
Thanks for creating Armory; small tip included in tx 4e347493f888f21d2f4163171c5ec20bc7c965df0aba83934e7880e9e5c829c2
Using Armory 0.82.2 on Win7-64 with Bitcoin-qt 0.7.1.
I finally had to use command line bitcoind sendrawtransaction on the full tx hexcode in the log. Would be nice if the "Copy Raw Tx" button included the signature.
Thanks for creating Armory; small tip included in tx 4e347493f888f21d2f4163171c5ec20bc7c965df0aba83934e7880e9e5c829c2
Using Armory 0.82.2 on Win7-64 with Bitcoin-qt 0.7.1.
Code:
2012-10-28 22:22 (ERROR) -- armoryengine.pyc:479 - Traceback (most recent call last):
File "qtdialogs.pyc", line 6122, in broadTx
File "ArmoryQt.py", line 1896, in broadcastTransaction
File "armoryengine.pyc", line 9154, in sendTx
ConnectionError: Connection to localhost DNE.
File "qtdialogs.pyc", line 6122, in broadTx
File "ArmoryQt.py", line 1896, in broadcastTransaction
File "armoryengine.pyc", line 9154, in sendTx
ConnectionError: Connection to localhost DNE.
Unlike last year, I see no Bitcoin events at Dragon*Con 2012.
Thinking ahead to costumes, it seems a Bitcoin tee shirt would be apropos. Not just a shirt that mentions Bitcoins, but one that would be valuable, spendable Bitcoin and could be used to beg coin from any bitcoiners who might pass by.
My first thought is to use T-Shirt transfer inkjet paper to print one of the Bitcoin banknote designs on the shirt. Spend QR Code on the inside of the shirt, of course.
Any other suggestions? Been done before?
Thinking ahead to costumes, it seems a Bitcoin tee shirt would be apropos. Not just a shirt that mentions Bitcoins, but one that would be valuable, spendable Bitcoin and could be used to beg coin from any bitcoiners who might pass by.
My first thought is to use T-Shirt transfer inkjet paper to print one of the Bitcoin banknote designs on the shirt. Spend QR Code on the inside of the shirt, of course.
Any other suggestions? Been done before?