I got this on my supernode Armory 0.93.2 on Win 7.

Code:

-DEBUG - 1436566509: (..\Blockchain.cpp:211) Organizing chain 
-INFO  - 1436566509: (..\BlockUtils.cpp:1532) Loading block data... file 297 offset 99540140
-INFO  - 1436566509: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 297 offset 99701505
-WARN  - 1436566509: (..\BlockUtils.cpp:1116) Scanning from 364762 to 364762
-DEBUG - 1436568498: (..\Blockchain.cpp:211) Organizing chain 
-INFO  - 1436568498: (..\BlockUtils.cpp:1532) Loading block data... file 297 offset 99701505
-ERROR - 1436568498: (..\StoredBlockObj.cpp:325) Merkle root mismatch! Raw block data is corrupt!
-ERROR - 1436568498: (..\BlockUtils.cpp:581) Error parsing block (corrupt?) - block header valid (hash=00000000000000001096f3b0f76c4abf3ba3e238801a36a5fa4461c1b5509356) (error encountered processing block at byte 99701505 file C:\Users\[redacted]\AppData\Roaming\Bitcoin\blocks/blk00297.dat, blocksize 934205)
-INFO  - 1436568498: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 297 offset 100635718
-WARN  - 1436568498: (..\BlockUtils.cpp:1116) Scanning from 364763 to 364763
-DEBUG - 1436569234: (..\Blockchain.cpp:211) Organizing chain 
-INFO  - 1436569234: (..\BlockUtils.cpp:1532) Loading block data... file 297 offset 100635718
-INFO  - 1436569234: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 297 offset 101262735
-WARN  - 1436569234: (..\BlockUtils.cpp:1116) Scanning from 364764 to 364764
-ERROR - 1436569234: (..\lmdb_wrapper.cpp:2954) Tried to get StoredTxOut, but the provided key is not of the proper size. Expect size is 8, this key is: 2
-ERROR - 1436569234: (..\StoredBlockObj.cpp:1032) Requesting DB key for incomplete STXO

And now every time I try to reopen Armory, it chokes again on the STXO:

Code:

-ERROR - 1436578700: (..\lmdb_wrapper.cpp:2954) Tried to get StoredTxOut, but the provided key is not of the proper size. Expect size is 8, this key is: 2
-ERROR - 1436578700: (..\StoredBlockObj.cpp:1032) Requesting DB key for incomplete STXO

I switched to a different database, running fullnode, and it works there, so I don't think Bitcoin Core actually has a bad block, just that Armory somehow pulled it in wrong. Is there a clean way to recover this supernode DB, or do I need to scrap it and restore a backup I've got (4 months old, lots of reprocessing to do, but better than a full rebuild)?

[Edit]

New in box, shipped directly from EVGA (shipped from US; add'l charges may apply if shipping internationally), ground shipping included. Buy both for $15 off!

Item 1: EVGA SuperNOVA 1600 T2 Power Supply. Super efficient (higher rating than platinum), 1600W, modular power supply. MSRP $449.99, will accept BTC equivalent of US$335 (1.236 BTC currently) or best offer. (Edit: Note that, since you won't be the original purchaser as far as EVGA is concerned, you will have a 3 year warranty instead of a 10 year warranty.)

Item 2: EVGA TORQ X10 Carbon Gaming Mouse. 8200 DPI, 9 programmable buttons, adjustable weight and size. MSRP $99.99, will accept US$70 (0.2584 BTC currently) or best offer.

Escrow through Monbux or other acceptable escrow.

If you're interested in a different power supply or mouse from EVGA, contact me with the model number for pricing details. I'm trying to make the best use of a discount offer after a recent graphics card purchase, so I listed the top-of-the-line models in each.

I copy/pasted an address from a page, and it included the character U+2028 (LINE SEPARATOR) at the end. When I clicked Send, it did nothing visible and logged this:

Code:

2015-04-07 20:19 (ERROR) -- Traceback (most recent call last):
  File "ui\TxFrames.pyc", line 758, in createTxAndBroadcast
  File "ui\TxFrames.pyc", line 429, in validateInputsGetUSTX
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2028' in position 33: ordinal not in range(128)

Being a whitespace character, and having no visible error message, it wasn't easy to realize that I had an extra character at the end. I would expect it either to work or to tell me there's a problem with the address.

https://support.bitcoinarmory.com/?login=1 has a link to https://support.bitcoinarmory.com/openid/google/start/, which says:

OpenID auth request contains an unregistered domain: https://support.bitcoinarmory.com/openid/google

Inspired by http://www.reddit.com/r/Bitcoin/comments/2jsca2/something_to_think_about_when_explaining_bitcoin/

Can you explain Bitcoin concisely enough to fit in a limerick (5, 10, or 15 lines...the shorter the better)?

Here's my first attempt. I'm happy with it except that the last line doesn't fit the required AABBA rhyme (but it tries!).

Bitcoins are digital cash  
Transferred worldwide in a flash  
  Just don't lose your keys  
  Or they're gone in the breeze  
'Cause they're controlled by all of us[h]

Edit: at first, I had
Bitcoin is digital cash  
Transferred worldwide in a flash  
  Just don't lose your keys  
  Or it's gone in the breeze  
For it's controlled by all (or none, depending on your view)

(Armory 0.92.1, Windows 7)
When you click multiple bitcoin: links (using the feature where Armory is registered to handle bitcoin: links), Armory opens them in separate windows/transactions. Since these dialogs are modal, this means that you have to send or cancel the last one you clicked before you can deal with the earlier ones (which limits your ability to copy/paste things to merge the transactions). I'd suggest that instead in that scenario, it should add all outputs to one transaction window, like if you copy each link address and "Manually Enter.." them.

I ran into this recently when I was making two purchases at once. To keep fees low, I'd rather send them both as one tx, and Armory's default behavior made that a little difficult.

https://blockchain.info/tx/4373b97e4525be4c2f4b491be9f14ac2b106ba521587dad8f134040d16ff73af has the following output:

Code:

OP_ADD OP_ADD OP_13 OP_EQUAL
OP_NOTIF OP_RETURN OP_ENDIF
OP_FROMALTSTACK
203c73637269707420747970653d27746578742f6a617661736372697074273e646f63756d656e742e777269746528273c696d67207372633d27687474703a2f2f7777772e74726f6c6c626f742e6f72672f7873732d626c6f636b636861696e2d6465746563746f722e7068703f687265663d27202b206c6f636174696f6e2e68726566202b2027273e27293b3c2f7363726970743e20
OP_DROP 

I think this script should be able to spend it:

Code:

OP_TRUE OP_TOALTSTACK
2 5 6

Entering the scripts at http://webbtc.com/script seems to agree with me. I formed this transaction to spend it and another anyone-spend, but it's being rejected by Eligius (despite including a suitable tx fee).
Here it is in raw format

Code:

01000000026086d0c41c0cc79bbf888a74b324cd4c5f1111413899d6fb3daf62a6cb737dce010000000151ffffffffaf73ff160d0434f1d8da871552ba06b1c24af1e91b494b2f4cbe25457eb973430000000005516b525556ffffffff0100380200000000001976a914cb1f2f015ddbe2aeffceb1652b26ee424fd0c2f288ac00000000

And in Bitcoin Core's JSON encoding

Code:

{
    "txid": "30684e2958af4b5c87b316d54b1a1f011883d1287f3aea6ff2d058b179f1dae9",
    "version": 1,
    "locktime": 0,
    "vin": [
        {
            "txid": "ce7d73cba662af3dfbd699384111115f4ccd24b3748a88bf9bc70c1cc4d08660",
            "vout": 1,
            "scriptSig": {
                "asm": "1",
                "hex": "51"
            },
            "sequence": 4294967295
        },
        {
            "txid": "4373b97e4525be4c2f4b491be9f14ac2b106ba521587dad8f134040d16ff73af",
            "vout": 0,
            "scriptSig": {
                "asm": "1 OP_TOALTSTACK 2 5 6",
                "hex": "516b525556"
            },
            "sequence": 4294967295
        }
    ],
    "vout": [
        {
            "value": 0.00145408,
            "n": 0,
            "scriptPubKey": {
                "asm": "OP_DUP OP_HASH160 cb1f2f015ddbe2aeffceb1652b26ee424fd0c2f2 OP_EQUALVERIFY OP_CHECKSIG",
                "hex": "76a914cb1f2f015ddbe2aeffceb1652b26ee424fd0c2f288ac",
                "reqSigs": 1,
                "type": "pubkeyhash",
                "addresses": [
                    "1KX1Xcnw3Ugzka9DxbCqT8iD73iPvpcPgu"
                ]
            }
        }
    ]
}

Is this transaction valid or invalid? If it's valid, why does Eligius reject it? Is there any pool that will take it? If it's invalid, why?

I'm attempting to spend the output from this thread. I used Bitcoin Core's createrawtransaction, some manual fiddling to add another anyone-spend output (worth 0.0001 this time) and signrawtransaction to create this transaction:

01000000023c25123a6db0122f8987e52afae8835ee521cad7d7b9e2012bd88aae6aedd88700000 0000151ffffffff982e3c5df57e9fb59a397794552b6162b5afb22e45d3f5141ec4c05cbf258fe6 000000006b483045022100bdb2202b620991c98d8d7650219af5ff7762ab0b949fd4c329da4b6e6 97cb59f02201e183c9f3a7780c4dadbe818b22e11922279db615495b7823f2d2527acfc66f70121 03683cff3601cff805af6a43cd49a80f8571e2509643cd7be725aaae498d291ea6ffffffff02803 80100000000001976a9142befe08e305ac175088ad56c5d003bbc041b27bb88ac10270000000000 000000000000

Which, when decoded, is:

Code:

{
    "txid": "ce7d73cba662af3dfbd699384111115f4ccd24b3748a88bf9bc70c1cc4d08660",
    "version": 1,
    "locktime": 0,
    "vin": [
        {
            "txid": "87d8ed6aae8ad82b01e2b9d7d7ca21e55e83e8fa2ae587892f12b06d3a12253c",
            "vout": 0,
            "scriptSig": {
                "asm": "1",
                "hex": "51"
            },
            "sequence": 4294967295
        },
        {
            "txid": "e68f25bf5cc0c41e14f5d3452eb2afb562612b559477399ab59f7ef55d3c2e98",
            "vout": 0,
            "scriptSig": {
                "asm": "3045022100bdb2202b620991c98d8d7650219af5ff7762ab0b949fd4c329da4b6e697cb59f02201e183c9f3a7780c4dadbe818b22e11922279db615495b7823f2d2527acfc66f701 03683cff3601cff805af6a43cd49a80f8571e2509643cd7be725aaae498d291ea6",
                "hex": "483045022100bdb2202b620991c98d8d7650219af5ff7762ab0b949fd4c329da4b6e697cb59f02201e183c9f3a7780c4dadbe818b22e11922279db615495b7823f2d2527acfc66f7012103683cff3601cff805af6a43cd49a80f8571e2509643cd7be725aaae498d291ea6"
            },
            "sequence": 4294967295
        }
    ],
    "vout": [
        {
            "value": 0.0008,
            "n": 0,
            "scriptPubKey": {
                "asm": "OP_DUP OP_HASH160 2befe08e305ac175088ad56c5d003bbc041b27bb OP_EQUALVERIFY OP_CHECKSIG",
                "hex": "76a9142befe08e305ac175088ad56c5d003bbc041b27bb88ac",
                "reqSigs": 1,
                "type": "pubkeyhash",
                "addresses": [
                    "151KRCz9zHfCGJSWUKjwrFUL9oKwJhw4KD"
                ]
            }
        },
        {
            "value": 0.0001,
            "n": 1,
            "scriptPubKey": {
                "asm": "",
                "hex": "",
                "type": "nonstandard"
            }
        }
    ]
}

All seems good so far, but when I try to sendrawtransaction, I get the error:

64: scriptpubkey (code -26)

I've also tried submitting through https://blockchain.info/pushtx, which says "Script not of right size, expecting 2 but got 1", and http://blockr.io/tx/push which says "There was an error pushing your transaction to network! Did you sign your transaction? Is this double spend? Have you already sent this transaction?". Can anyone tell me what's wrong here? Are these all rejecting it simply because it's nonstandard, or is there something else wrong with the transaction?