Blockchain.info - Bitcoin Block explorer & Currency Statistics - page 35.

Vitalik Buterin

sr. member

Activity: 330

Merit: 397

Quote from: piuk on October 25, 2013, 05:03:11 AM

Is it redeeming a multisig transaction? Signature validation for P2SH/multsig scripts is untested, i'm not sure if bitcoinj can validate them or not.

Yes, it was a multisig. It's strange that validation is failing now; I remember it working just fine before. Or maybe my memory is bad and it was just the single-sig transactions that worked.

rme

hero member

Activity: 756

Merit: 504

Quote from: Lohoris on October 27, 2013, 04:00:39 AM

I've opened the Chrome app and I've received a popup suggesting me to switch to a newer version of the app: https://chrome.google.com/webstore/detail/blockchain/glaohkkooicollgefkkmndjcbblominl/reviews

Also, I've found on twitter that a native app for OSX has just been released: https://itunes.apple.com/gb/app/blockchain/id688882038

Are these legit?

yes

Lohoris

hero member

Activity: 630

Merit: 500

Bitgoblin

I've opened the Chrome app and I've received a popup suggesting me to switch to a newer version of the app: https://chrome.google.com/webstore/detail/blockchain/glaohkkooicollgefkkmndjcbblominl/reviews

Also, I've found on twitter that a native app for OSX has just been released: https://itunes.apple.com/gb/app/blockchain/id688882038

Are these legit?

HostFat

staff

Activity: 4270

Merit: 1209

I support freedom of choice

Can you add on the android app the possibility to take brainwallets / privatekeys from clipboard? (now it is possible only from qr codes)

waxwing

sr. member

Activity: 469

Merit: 253

Quote from: piuk on October 25, 2013, 05:03:11 AM

Is it redeeming a multisig transaction? Signature validation for P2SH/multsig scripts is untested, i'm not sure if bitcoinj can validate them or not.

theymos's answer here from September seems to suggest it doesn't (although I certainly don't know).

piuk

hero member

Activity: 910

Merit: 1005

Quote from: ThePiachu on October 20, 2013, 03:48:08 AM

Feature suggestion - Blockchain Wallet API List Addresses should include an optional field $confirmations

Quote from: mb300sd on October 22, 2013, 01:32:35 PM

Is there any way to pull full raw transaction or block data in hex? I'm trying to use http://blockchain.info/rawtx/$tx_index but the scriptsig and scriptpubkey are missing. Being able to pull the information is the same format as sendrawtransaction would be very useful.

I'v added a scripts parameter and confirmations parameter to /rawtx and /merchant/list.

Quote from: Vitalik Buterin on October 25, 2013, 04:34:23 AM

Bug report, since I can't find a logical place to put this under http://github.com/blockchain:

When I tried to push the following transaction to http://blockchain.info/pushtx:

Code:

010000000125b98a02b8eb1ef3efb471cc87d6f028b53eadf29fe1cfb73fd0151188b6fe9300000000fd5f0100493046022100bcb0e128a7f4f39575f538979ecce4d49142ef6b613b4a98609bc14a7ae5ee0c02210094aca62aeae8301711560171087d8f069b79016d037f4e806df6c2efe12354e3014830450220257a3130f1d47ddf06b6a33882a1f1295cd8506f1ba1383b8b4cb5a40813c7ff022100ccea8cf93c54540f770e805a61585fb0ae82d6b6f68929b65afb0d6a9c0aa4ab014cc9524104b469d4fafd936e8630a5377223c5b7acfa9d2948b96845cc332607ec8528e6018abe46af616567ca44fca2d703a400dfdae73d0e21265c4dbeaf09e6294aa41941048ac7607d833aedb50c7be390955513f40327ff83891b53db2b241af64526ac17b37e7599f5ab2d4c7152779470dbc95c91526217de7bc002197ded7410526bfe4104cad74f0cf89dca7e13f37257e81308772fe3c7280f656ac88367867c54256ed606aa4dd2dc8ce4e73abb3159974f11657d2a365cee6fe86eeec4a8ce529cecd153aeffffffff0110270000000000001976a91405778c85c60c69598ea5bc896f872415fa7100b288ac00000000

I got an "Invalid Signature" error.

The transaction worked just fine when I sent it through the electrum sendrawtransaction CLI option. Here's the transaction deserialized:

Code:

> pybtctool deserialize `cat tx`
{"locktime": 0, "outs": [{"value": 10000, "script": "76a91405778c85c60c69598ea5bc896f872415fa7100b288ac"}], "version": 1, "ins": [{"script": "00493046022100bcb0e128a7f4f39575f538979ecce4d49142ef6b613b4a98609bc14a7ae5ee0c02210094aca62aeae8301711560171087d8f069b79016d037f4e806df6c2efe12354e3014830450220257a3130f1d47ddf06b6a33882a1f1295cd8506f1ba1383b8b4cb5a40813c7ff022100ccea8cf93c54540f770e805a61585fb0ae82d6b6f68929b65afb0d6a9c0aa4ab014cc9524104b469d4fafd936e8630a5377223c5b7acfa9d2948b96845cc332607ec8528e6018abe46af616567ca44fca2d703a400dfdae73d0e21265c4dbeaf09e6294aa41941048ac7607d833aedb50c7be390955513f40327ff83891b53db2b241af64526ac17b37e7599f5ab2d4c7152779470dbc95c91526217de7bc002197ded7410526bfe4104cad74f0cf89dca7e13f37257e81308772fe3c7280f656ac88367867c54256ed606aa4dd2dc8ce4e73abb3159974f11657d2a365cee6fe86eeec4a8ce529cecd153ae", "outpoint": {"index": 0, "hash": "93feb6881115d03fb7cfe19ff2ad3eb528f0d687cc71b4eff31eebb8028ab925"}, "sequence": 4294967295}]}
> pybtctool deserialize_script `cat script`
[null, "3046022100bcb0e128a7f4f39575f538979ecce4d49142ef6b613b4a98609bc14a7ae5ee0c02210094aca62aeae8301711560171087d8f069b79016d037f4e806df6c2efe12354e301", "30450220257a3130f1d47ddf06b6a33882a1f1295cd8506f1ba1383b8b4cb5a40813c7ff022100ccea8cf93c54540f770e805a61585fb0ae82d6b6f68929b65afb0d6a9c0aa4ab01", "524104b469d4fafd936e8630a5377223c5b7acfa9d2948b96845cc332607ec8528e6018abe46af616567ca44fca2d703a400dfdae73d0e21265c4dbeaf09e6294aa41941048ac7607d833aedb50c7be390955513f40327ff83891b53db2b241af64526ac17b37e7599f5ab2d4c7152779470dbc95c91526217de7bc002197ded7410526bfe4104cad74f0cf89dca7e13f37257e81308772fe3c7280f656ac88367867c54256ed606aa4dd2dc8ce4e73abb3159974f11657d2a365cee6fe86eeec4a8ce529cecd153ae"]

The sigs all validate just fine. Lost the privkeys unfortunately. Any idea what's up?

Is it redeeming a multisig transaction? Signature validation for P2SH/multsig scripts is untested, i'm not sure if bitcoinj can validate them or not.

Vitalik Buterin

sr. member

Activity: 330

Merit: 397

Bug report, since I can't find a logical place to put this under http://github.com/blockchain:

When I tried to push the following transaction to http://blockchain.info/pushtx:

Code:

010000000125b98a02b8eb1ef3efb471cc87d6f028b53eadf29fe1cfb73fd0151188b6fe9300000000fd5f0100493046022100bcb0e128a7f4f39575f538979ecce4d49142ef6b613b4a98609bc14a7ae5ee0c02210094aca62aeae8301711560171087d8f069b79016d037f4e806df6c2efe12354e3014830450220257a3130f1d47ddf06b6a33882a1f1295cd8506f1ba1383b8b4cb5a40813c7ff022100ccea8cf93c54540f770e805a61585fb0ae82d6b6f68929b65afb0d6a9c0aa4ab014cc9524104b469d4fafd936e8630a5377223c5b7acfa9d2948b96845cc332607ec8528e6018abe46af616567ca44fca2d703a400dfdae73d0e21265c4dbeaf09e6294aa41941048ac7607d833aedb50c7be390955513f40327ff83891b53db2b241af64526ac17b37e7599f5ab2d4c7152779470dbc95c91526217de7bc002197ded7410526bfe4104cad74f0cf89dca7e13f37257e81308772fe3c7280f656ac88367867c54256ed606aa4dd2dc8ce4e73abb3159974f11657d2a365cee6fe86eeec4a8ce529cecd153aeffffffff0110270000000000001976a91405778c85c60c69598ea5bc896f872415fa7100b288ac00000000

I got an "Invalid Signature" error.

The transaction worked just fine when I sent it through the electrum sendrawtransaction CLI option. Here's the transaction deserialized:

Code:

> pybtctool deserialize `cat tx`
{"locktime": 0, "outs": [{"value": 10000, "script": "76a91405778c85c60c69598ea5bc896f872415fa7100b288ac"}], "version": 1, "ins": [{"script": "00493046022100bcb0e128a7f4f39575f538979ecce4d49142ef6b613b4a98609bc14a7ae5ee0c02210094aca62aeae8301711560171087d8f069b79016d037f4e806df6c2efe12354e3014830450220257a3130f1d47ddf06b6a33882a1f1295cd8506f1ba1383b8b4cb5a40813c7ff022100ccea8cf93c54540f770e805a61585fb0ae82d6b6f68929b65afb0d6a9c0aa4ab014cc9524104b469d4fafd936e8630a5377223c5b7acfa9d2948b96845cc332607ec8528e6018abe46af616567ca44fca2d703a400dfdae73d0e21265c4dbeaf09e6294aa41941048ac7607d833aedb50c7be390955513f40327ff83891b53db2b241af64526ac17b37e7599f5ab2d4c7152779470dbc95c91526217de7bc002197ded7410526bfe4104cad74f0cf89dca7e13f37257e81308772fe3c7280f656ac88367867c54256ed606aa4dd2dc8ce4e73abb3159974f11657d2a365cee6fe86eeec4a8ce529cecd153ae", "outpoint": {"index": 0, "hash": "93feb6881115d03fb7cfe19ff2ad3eb528f0d687cc71b4eff31eebb8028ab925"}, "sequence": 4294967295}]}
> pybtctool deserialize_script `cat script`
[null, "3046022100bcb0e128a7f4f39575f538979ecce4d49142ef6b613b4a98609bc14a7ae5ee0c02210094aca62aeae8301711560171087d8f069b79016d037f4e806df6c2efe12354e301", "30450220257a3130f1d47ddf06b6a33882a1f1295cd8506f1ba1383b8b4cb5a40813c7ff022100ccea8cf93c54540f770e805a61585fb0ae82d6b6f68929b65afb0d6a9c0aa4ab01", "524104b469d4fafd936e8630a5377223c5b7acfa9d2948b96845cc332607ec8528e6018abe46af616567ca44fca2d703a400dfdae73d0e21265c4dbeaf09e6294aa41941048ac7607d833aedb50c7be390955513f40327ff83891b53db2b241af64526ac17b37e7599f5ab2d4c7152779470dbc95c91526217de7bc002197ded7410526bfe4104cad74f0cf89dca7e13f37257e81308772fe3c7280f656ac88367867c54256ed606aa4dd2dc8ce4e73abb3159974f11657d2a365cee6fe86eeec4a8ce529cecd153ae"]

The sigs all validate just fine. Lost the privkeys unfortunately. Any idea what's up?

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: picobit on October 25, 2013, 02:58:00 AM

ETH Zürich has some guys researching Bitcoin.

yes, just like with the node that didnt verify blocks

ed: i did addnode on the 31 i know about about 30m before I posted that, since they were showing up pretty late on the block propagation charts on blockchain.info

Code:

{
"addr" : "129.132.230.70",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 5190397,
"bytesrecv" : 1050137,
"conntime" : 1382655549,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.75",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694502,
"bytessent" : 8231722,
"bytesrecv" : 1047979,
"conntime" : 1382655557,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.73",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694497,
"bytessent" : 3397740,
"bytesrecv" : 1030244,
"conntime" : 1382655559,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.71",
"services" : "00000001",
"lastsend" : 1382694503,
"lastrecv" : 1382694497,
"bytessent" : 5937946,
"bytesrecv" : 1032114,
"conntime" : 1382655572,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.72",
"services" : "00000001",
"lastsend" : 1382694503,
"lastrecv" : 1382694499,
"bytessent" : 5789238,
"bytesrecv" : 1044581,
"conntime" : 1382655580,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.74",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 5528807,
"bytesrecv" : 1024535,
"conntime" : 1382655581,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.76",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694497,
"bytessent" : 7259878,
"bytesrecv" : 1026325,
"conntime" : 1382655583,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265839,
"banscore" : 0
},
{
"addr" : "129.132.230.77",
"services" : "00000001",
"lastsend" : 1382694503,
"lastrecv" : 1382694502,
"bytessent" : 7164951,
"bytesrecv" : 1054956,
"conntime" : 1382655585,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.78",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694500,
"bytessent" : 7033160,
"bytesrecv" : 1057455,
"conntime" : 1382655586,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.79",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 7762812,
"bytesrecv" : 1054750,
"conntime" : 1382655588,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.80",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 5631047,
"bytesrecv" : 1036927,
"conntime" : 1382655591,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.81",
"services" : "00000001",
"lastsend" : 1382694503,
"lastrecv" : 1382694499,
"bytessent" : 6531105,
"bytesrecv" : 1028454,
"conntime" : 1382655788,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.82",
"services" : "00000001",
"lastsend" : 1382694500,
"lastrecv" : 1382694501,
"bytessent" : 7684608,
"bytesrecv" : 1047876,
"conntime" : 1382655788,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.83",
"services" : "00000001",
"lastsend" : 1382694503,
"lastrecv" : 1382694501,
"bytessent" : 633808,
"bytesrecv" : 860529,
"conntime" : 1382655788,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.84",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694498,
"bytessent" : 6493116,
"bytesrecv" : 1019175,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.85",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694496,
"bytessent" : 7309569,
"bytesrecv" : 1035387,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.86",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 6275205,
"bytesrecv" : 1053915,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.87",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694498,
"bytessent" : 6141238,
"bytesrecv" : 1029365,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.88",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 4826677,
"bytesrecv" : 1049668,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.89",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694498,
"bytessent" : 4583074,
"bytesrecv" : 1020827,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.90",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 5577976,
"bytesrecv" : 1002644,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.91",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694500,
"bytessent" : 7511889,
"bytesrecv" : 1058499,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.92",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694498,
"bytessent" : 4798618,
"bytesrecv" : 1027198,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.93",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 6760987,
"bytesrecv" : 1017669,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.94",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 4894180,
"bytesrecv" : 1060215,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.95",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694498,
"bytessent" : 5966016,
"bytesrecv" : 1041092,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.96",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694500,
"bytessent" : 3915213,
"bytesrecv" : 1030510,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.97",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694502,
"bytessent" : 6033589,
"bytesrecv" : 1039128,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.98",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694502,
"bytessent" : 6909276,
"bytesrecv" : 951783,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.99",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694502,
"bytessent" : 7378810,
"bytesrecv" : 1045283,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.100",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 6404674,
"bytesrecv" : 1060138,
"conntime" : 1382655789,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : false,
"startingheight" : 265840,
"banscore" : 0
},
{
"addr" : "129.132.230.72:50373",
"services" : "00000001",
"lastsend" : 1382694502,
"lastrecv" : 1382694499,
"bytessent" : 704308,
"bytesrecv" : 721208,
"conntime" : 1382657820,
"version" : 70001,
"subver" : "/Satoshi:0.8.99/",
"inbound" : true,
"startingheight" : 265844,
"banscore" : 0
}

fun times, a couple may be missing by now & I noticed that one is incoming

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

ETH Zürich has some guys researching Bitcoin.

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

eh, that's a lot of swiss nodes

129.132.230.70   8333   168.27    CH (Zurich)   vbitcoin-01.inf.ethz.ch
129.132.230.74   45606   191.75    CH (Zurich)   vbitcoin-05.inf.ethz.ch
129.132.230.77   55486   51.60    CH (Zurich)   vbitcoin-08.inf.ethz.ch
129.132.230.78   37142   80.95    CH (Zurich)   vbitcoin-09.inf.ethz.ch
129.132.230.79   53164   59.93    CH (Zurich)   vbitcoin-0a.inf.ethz.ch
129.132.230.81   60287   15.05    CH (Zurich)   vbitcoin-0c.inf.ethz.ch
129.132.230.83   55054   43.25    CH (Zurich)   vbitcoin-0e.inf.ethz.ch
129.132.230.84   46816   32.85    CH (Zurich)   vbitcoin-0f.inf.ethz.ch
129.132.230.85   46846   30.87    CH (Zurich)   vbitcoin-10.inf.ethz.ch
129.132.230.86   56112   34.03    CH (Zurich)   vbitcoin-11.inf.ethz.ch
129.132.230.87   52520   26.70    CH (Zurich)   vbitcoin-12.inf.ethz.ch
129.132.230.88   34230   145.58    CH (Zurich)   vbitcoin-13.inf.ethz.ch
129.132.230.89   33692   2.12    CH (Zurich)   vbitcoin-14.inf.ethz.ch
129.132.230.91   50123   64.12    CH (Zurich)   vbitcoin-16.inf.ethz.ch
129.132.230.92   48314   22.68    CH (Zurich)   vbitcoin-17.inf.ethz.ch
129.132.230.93   38011   189.43    CH (Zurich)   vbitcoin-18.inf.ethz.ch
129.132.230.95   35183   69.72    CH (Zurich)   vbitcoin-1a.inf.ethz.ch
129.132.230.97   39092   24.58    CH (Zurich)   vbitcoin-1c.inf.ethz.ch
129.132.230.98   48489   8.93    CH (Zurich)   vbitcoin-1d.inf.ethz.ch
129.132.230.99   57714   13.55    CH (Zurich)   vbitcoin-1e.inf.ethz.ch

piuk

hero member

Activity: 910

Merit: 1005

Quote from: ThePiachu on October 20, 2013, 03:48:08 AM

Feature suggestion - Blockchain Wallet API List Addresses should include an optional field $confirmations

It does take the server significantly more effort to filter by confirmations but I'll look into adding this.

Quote from: malevolent on October 20, 2013, 04:36:15 PM

(Yet Another) Feature Suggestion — would it possible for blockchain.info to include an option in account settings, that when enabled, the user would be asked for 2FA (email, sms, gauth, yubikey, etc.) also upon trying to withdraw BTC (with the ability to set up a daily transaction threshold (in BTC of fiat), above which the user would be asked for 2FA)?

This isn't possible without multisig private keys. Adding restrictions to the user interface would prevent basic attacks, but sophisticated malware could just extract the private key directly out of the browser memory and import it into another bitcoin client.

We've made the decision that we don't want to hold any unencrypted private keys server side which means multisig is especially complicated. The keys not only have to be kept isolated from us but also from each of the user's devices as well. Having said that it would certainly possible to implement with a smartphone app. But for the moment I would prefer to prioritise Hardware wallet support over multisig.

Quote from: dillpicklechips on October 21, 2013, 04:37:22 PM

Can blockchain.info somehow integrate with the Trezor? Have the trezor and web browser interact with it so the private keys aren't even on the computer?

I hope we will be able to add support for trezor soon after its release.

Quote from: dillpicklechips on October 22, 2013, 02:16:44 PM

This will change everything!

If I had a satoshi for everytime I heard a bitcoiner say "This will change everything" I'd be richer than Satoshi himself

Quote from: mb300sd on October 22, 2013, 01:32:35 PM

Is there any way to pull full raw transaction or block data in hex? I'm trying to use http://blockchain.info/rawtx/$tx_index but the scriptsig and scriptpubkey are missing. Being able to pull the information is the same format as sendrawtransaction would be very useful.

This isn't possible at the moment. But you can use /q/outscript to fetch the output scripts e.g.

https://blockchain.info/q/outscript?tx_index=94640319&tx_output_n=0
https://blockchain.info/q/outscript?tx_index=94640319&tx_output_n=1

Quote from: molecular on October 19, 2013, 02:57:28 PM

Cool. Thanks for going forward on this.

Do I understand correctly that the pool server still knows which inputs and outputs were provided by who? So you still trust the server regarding privacy, just not coins, right?

Correct the server has the ability to log the inputs and outputs and de-anonymize you, so it is not trust-less in that regard. There are a number of potential solutions to this some mentioned in the original coinjoin thread. My preferred solution would be to give clients the ability to trade inputs and outputs before submitting them to the server, then proxy back to the client they traded with when asked to sign the inputs.

Quote from: Peter Todd on October 19, 2013, 04:58:52 PM

One issue with the current version is that the blockchain.info wallet app only uses uncompressed keys, especially for sharedcoin change addresses, while internally the pool uses compressed keys.

Good catch, both the client and server will now randomly alternate between compressed and uncompressed keys.

In the following sharedcoin transaction 10 BTC was sent to 19BgLUEFhKAxbcELVMafbvZb4RCzGAkraa:

https://blockchain.info/tx/4602e0c7a0ecb9def7d2f88540a326a4a4bf424622edb2d629c303dc2cb676bb

I'm offering a bounty of 4 BTC to anyone who can successfully predict the senders inputs. The transaction was made using multiple sharedcoin repetitions.

dillpicklechips

hero member

Activity: 994

Merit: 507

Quote from: Blockchain_Helper on October 22, 2013, 09:13:39 AM

Quote from: dillpicklechips on October 21, 2013, 04:37:22 PM

Can blockchain.info somehow integrate with the Trezor? Have the trezor and web browser interact with it so the private keys aren't even on the computer?

Piuk actually posted about this - https://bitcointalksearch.org/topic/m.3308975. I'm sure more details will be released as Trezor starts to be used.

This will change everything! All the convienance of blockchain.info and impossible to steal the private keys! Sweet!

mb300sd

legendary

Activity: 1260

Merit: 1000

Drunk Posts

Is there any way to pull full raw transaction or block data in hex? I'm trying to use http://blockchain.info/rawtx/$tx_index but the scriptsig and scriptpubkey are missing. Being able to pull the information is the same format as sendrawtransaction would be very useful.

Blockchain_Helper

newbie

Activity: 25

Merit: 0

Quote from: dillpicklechips on October 21, 2013, 04:37:22 PM

Can blockchain.info somehow integrate with the Trezor? Have the trezor and web browser interact with it so the private keys aren't even on the computer?

Piuk actually posted about this - https://bitcointalksearch.org/topic/m.3308975. I'm sure more details will be released as Trezor starts to be used.

dillpicklechips

hero member

Activity: 994

Merit: 507

Can blockchain.info somehow integrate with the Trezor? Have the trezor and web browser interact with it so the private keys aren't even on the computer?

VTC

member

Activity: 84

Merit: 14

Quote from: malevolent on October 20, 2013, 04:36:15 PM

(Yet Another) Feature Suggestion — would it possible for blockchain.info to include an option in account settings, that when enabled, the user would be asked for 2FA (email, sms, gauth, yubikey, etc.) also upon trying to withdraw BTC (with the ability to set up a daily transaction threshold (in BTC of fiat), above which the user would be asked for 2FA)?

This would protect people from some more sophisticated malware that waits till the user logs in with his credentials and 2FA, and only then sends funds to the attacker's address.

There is still a possibility that the attacker could wait till the user tries to make a transaction and would replace the user-specified address with his own one. To protect against this, people who have SMS or email as 2FA (hopefully accessing the email account from a different device) could get transaction information about the addresses that are involved along with the code.

This won't help security. One you successfully login, your wallet is fully decrypted locally, and all the private keys become exposed to your computer, unless you are using a secondary password. Make a transaction and use a secondary password and now all your private keys are potentially exposed to malware. I suggested earlier that secondary password should act like a PIN, and only be used to sign the transaction and never saved in memory. So multiple transaction would require re-entering the secondary password. This can potentially help a bit more.

malevolent

legendary

Activity: 3472

Merit: 1727

(Yet Another) Feature Suggestion — would it possible for blockchain.info to include an option in account settings, that when enabled, the user would be asked for 2FA (email, sms, gauth, yubikey, etc.) also upon trying to withdraw BTC (with the ability to set up a daily transaction threshold (in BTC of fiat), above which the user would be asked for 2FA)?

This would protect people from some more sophisticated malware that waits till the user logs in with his credentials and 2FA, and only then sends funds to the attacker's address.

There is still a possibility that the attacker could wait till the user tries to make a transaction and would replace the user-specified address with his own one. To protect against this, people who have SMS or email as 2FA (hopefully accessing the email account from a different device) could get transaction information about the addresses that are involved along with the code.

It would be also nice to be able to set ranges of IP addresses from which the user should be allowed to log in (for those with dynamic IP addresses). Wink

I'll also post this here again in case piuk last time missed it:

Quote from: malevolent on October 16, 2013, 06:11:54 AM

Quote from: Blockchain_Helper on October 14, 2013, 09:50:14 PM

Quote from: truy on October 14, 2013, 08:01:40 PM

Minor feature request: Please print out a text version of the TOTP secret key below the qr code image on the two factor authentication settings page.

I'll pass this suggestion along, but in the meantime you can use a different QR scanner app to get a copy of the secret key. If you ever need to reset two factor authentication, then you can just submit a 2FA reset request. We usually process these within 12-24 hours max (I check them multiple times a day).

Yes, please print a text version of the key, it would be very convenient for users with older phones for which there are alternative Gauth implementations but none of them can scan QR codes. Other QR scanning apps are also problematic to work with.

ThePiachu

sr. member

Activity: 444

Merit: 313

Feature suggestion - Blockchain Wallet API List Addresses should include an optional field $confirmations

Reasoning:
If I am keeping track of multiple accounts looking for full confirmations I first have to make an API call to get 0 confirmation balance for every address and then make individual call for every wallet with balance >0 to check if their balance has 6 or more confirmations. Including $confirmations optional flag in List Addresses API call would cut down on the API calls from potentially many to just 1 API call.

sunnankar

legendary

Activity: 1031

Merit: 1000

Quote from: piuk on October 19, 2013, 01:34:30 PM

Then when you include randomised fees into the mix it makes it almost impossible to determine the inputs used from the value of one output.

How about being able to specify multiple outputs?

Peter Todd

legendary

Activity: 1120

Merit: 1164

Quote from: piuk on October 19, 2013, 01:34:30 PM

Only if you are mixing with other users who want to send different amounts. When mixing with the sharedcoin pool the server doesn't desire any particular output size so can deliberately add input and output combinations which mimic your own. Then when you include randomised fees into the mix it makes it almost impossible to determine the inputs used from the value of one output.

One issue with the current version is that the blockchain.info wallet app only uses uncompressed keys, especially for sharedcoin change addresses, while internally the pool uses compressed keys.

I know iPhone compatibility is a problem, but maybe you could make the pool at least occasionally use uncompressed keys, or add compressed key change as an advanced experts-only option?

Topic: Blockchain.info - Bitcoin Block explorer & Currency Statistics - page 35. (Read 482721 times)