Search content
Sort by

Showing 4 of 4 results by npiguet
Post
Topic
Board Marketplace
Topic OP
Exchanges total client assets?
by
npiguet
on 27/02/2014, 17:03:55 UTC
Hello,

While it is fairly easy to guess how much revenues BTC exchanges get from trading (just take the daily volume and multiply it by double the transaction fee), I can't figure out a way to know how much assets their clients have deposited into the exchange.

Does anyone know where I could find that number for the major exchanges (btc-e, bitstamp, mtgox (before shutdown))?
Has anyone heard any rumors regarding the total deposits in one these exchanges? I haven't been able to find anything.

Thanks for your help!
Post
Topic
Board Development & Technical Discussion
Re: Mt.Gox technical autopsy
by
npiguet
on 26/02/2014, 20:01:18 UTC
Let's say person X (attacker) withdrew e.g. BTC 666.696969 from Gox (or any other exchange). The same person X needed to claim exactly the same amount (BTC 666.696969) from Gox a week or two weeks later, right?

What could be done is to run a query on blockchain data to identify such transaction pairs, initiated from addresses that once had a fairly high value of ''total received'' (indicating they were exchange address) and sent the same amount (BTC 666.696969) twice within a certain period of time.

If someone identifies such pairs, then we might at least get the idea of the maximum possible malleability threshold that went on the Bitcoin network.

You couldn't do that, because only one of the transactions would actually be in the block chain. So you would never actually see the pair of transactions. You can only catch this stuff while neither of the equivalent transactions has entered a valid block.
Post
Topic
Board Development & Technical Discussion
Re: Minimum amount of coins per transaction
by
npiguet
on 25/02/2014, 15:44:48 UTC
Are transactions without outputs considered legal? Because if they are, this could be a workaround to the "no outputs can be smaller than 5430" satoshis rule.
Post
Topic
Board Development & Technical Discussion
Topic OP
Testnet: Why are my transactions not being relayed
by
npiguet
on 25/02/2014, 15:11:51 UTC
Hello,

I've posted a bunch of transactions to the testnet using bitcoind "sendrawtransaction" API call. I've seen different behaviors depending on the transaction.

A bunch of them seem to have been accepted by bitcoind, propagated to the network and were later included in a block. Here's a copy of the filtered debug log for some of these:

Code:
vagrant@precise64:~$ cat /var/log/bitcoin-testnet-debug.log | grep a5ef5716ef3aa493597c69fe2af186f5f56c42cab6e2cf952532fd826be8e250
CTxMemPool::accept() : accepted a5ef5716ef3aa493597c69fe2af186f5f56c42cab6e2cf952532fd826be8e250 (poolsz 7)
received getdata for: tx a5ef5716ef3aa493597c69fe2af186f5f56c42cab6e2cf952532fd826be8e250
received getdata for: tx a5ef5716ef3aa493597c69fe2af186f5f56c42cab6e2cf952532fd826be8e250
received getdata for: tx a5ef5716ef3aa493597c69fe2af186f5f56c42cab6e2cf952532fd826be8e250

vagrant@precise64:~$ cat /var/log/bitcoin-testnet-debug.log | grep e95e89b0eee107320e6925ffc4b8465567d332c0bd41e6c7f6d33464ca6b9739
CTxMemPool::accept() : accepted e95e89b0eee107320e6925ffc4b8465567d332c0bd41e6c7f6d33464ca6b9739 (poolsz 8)
received getdata for: tx e95e89b0eee107320e6925ffc4b8465567d332c0bd41e6c7f6d33464ca6b9739
received getdata for: tx e95e89b0eee107320e6925ffc4b8465567d332c0bd41e6c7f6d33464ca6b9739
received getdata for: tx e95e89b0eee107320e6925ffc4b8465567d332c0bd41e6c7f6d33464ca6b9739
received getdata for: tx e95e89b0eee107320e6925ffc4b8465567d332c0bd41e6c7f6d33464ca6b9739

However some others simply don't seem to actually get out:

Code:
vagrant@precise64:~$ cat /var/log/bitcoin-testnet-debug.log | grep 272da29d0cc728e9b2209e7aa08c26183072e61c7b6e861f9d52086ea9db01ba
CTxMemPool::accept() : accepted 272da29d0cc728e9b2209e7aa08c26183072e61c7b6e861f9d52086ea9db01ba (poolsz 11)

vagrant@precise64:~$ cat /var/log/bitcoin-testnet-debug.log | grep 731f42293930813a68b2cf5db62bde575bdf464576c80c475d1bde6bf29ecb6b
CTxMemPool::accept() : accepted 731f42293930813a68b2cf5db62bde575bdf464576c80c475d1bde6bf29ecb6b (poolsz 12)

vagrant@precise64:~$ cat /var/log/bitcoin-testnet-debug.log | grep 947cffd81b2ab2ec89f1f1404093f2bf5b62898e75555b07e6655ca7a2dddea0
CTxMemPool::accept() : accepted 947cffd81b2ab2ec89f1f1404093f2bf5b62898e75555b07e6655ca7a2dddea0 (poolsz 13)

Here his how the first not-propagating transaction looks like when deserialized:

Code:
{
    "result": {
        "txid": "272da29d0cc728e9b2209e7aa08c26183072e61c7b6e861f9d52086ea9db01ba",
        "version": 1,
        "locktime": 0,
        "vin": [
            {
                "txid": "dc83350010ca3fb10a65b7fe1fa01ed441eebf21c29b37fc529b3283cc17cc3c",
                "vout": 1,
                "scriptSig": {
                    "asm": "304402200b0829716b2a9850be75f98ca3714bb2e6552cdd03e7c5fc3382a133dbb2c84602200357cc2cc7ff57a18b687fb42dd1f00004d7472da6bc3348a7dcd0d8c01f14c701 0392f78df93efd2eabb201b7f8bc969b9f34b9f86d0b02777dea6c6817195972a2",
                    "hex": "47304402200b0829716b2a9850be75f98ca3714bb2e6552cdd03e7c5fc3382a133dbb2c84602200357cc2cc7ff57a18b687fb42dd1f00004d7472da6bc3348a7dcd0d8c01f14c701210392f78df93efd2eabb201b7f8bc969b9f34b9f86d0b02777dea6c6817195972a2"
                },
                "sequence": 4294967295
            },
            {
                "txid": "1d3eb76b11330b01441ce7d5feed2addfeea05dc1f07aa917de142dc408de3b4",
                "vout": 1,
                "scriptSig": {
                    "asm": "30450221008ba16db3879c5eb1e00536c403248046e51205ed9ad744a1cc34265c6eb3a049022058197d6bf773c87a499d5661eaddddc47f59454a8b31a998d633d573d4385c7a01 0248b8bbb3c0e09effcfe1c7c89149a44158ac9c0d35a91b41500a6938aee6a6fd",
                    "hex": "4830450221008ba16db3879c5eb1e00536c403248046e51205ed9ad744a1cc34265c6eb3a049022058197d6bf773c87a499d5661eaddddc47f59454a8b31a998d633d573d4385c7a01210248b8bbb3c0e09effcfe1c7c89149a44158ac9c0d35a91b41500a6938aee6a6fd"
                },
                "sequence": 4294967295
            },
            {
                "txid": "f84ed81090a2ace7731162ba94c8c475a70ad1ed94cc20daffa7d9485b3be5c0",
                "vout": 1,
                "scriptSig": {
                    "asm": "3043022026cc898b343f4a9bd84a773c46e3c77039db974ec128d18a60db624500f68a6c021f20d86520b78b347b6ca24a9cebc53cf765770a750a553ac7187cf3b4c4256e01 02c2e9d98b453b39c91bf75a9a9b9cd5e83917243726395d25c07c4ea0a8fd11f3",
                    "hex": "463043022026cc898b343f4a9bd84a773c46e3c77039db974ec128d18a60db624500f68a6c021f20d86520b78b347b6ca24a9cebc53cf765770a750a553ac7187cf3b4c4256e012102c2e9d98b453b39c91bf75a9a9b9cd5e83917243726395d25c07c4ea0a8fd11f3"
                },
                "sequence": 4294967295
            }
        ],
        "vout": [
            {
                "value": 3.4998,
                "n": 0,
                "scriptPubKey": {
                    "asm": "OP_DUP OP_HASH160 23b7530a00dd7951e11791c529389421c0b8d83b OP_EQUALVERIFY OP_CHECKSIG",
                    "hex": "76a91423b7530a00dd7951e11791c529389421c0b8d83b88ac",
                    "reqSigs": 1,
                    "type": "pubkeyhash",
                    "addresses": [
                        "mimoZNLcP2rrMRgdeX5PSnR7AjCqQveZZ4"
                    ]
                }
            },
            {
                "value": 2.55421689,
                "n": 1,
                "scriptPubKey": {
                    "asm": "OP_DUP OP_HASH160 bf780a65e87768d6dd223435c59a15f57a43318a OP_EQUALVERIFY OP_CHECKSIG",
                    "hex": "76a914bf780a65e87768d6dd223435c59a15f57a43318a88ac",
                    "reqSigs": 1,
                    "type": "pubkeyhash",
                    "addresses": [
                        "mxyMAG9U9ovFV2oEUqQVH88jD8BeQCrD5t"
                    ]
                }
            }
        ]
    },
    "error": null,
    "id": "1"
}

I've included a 0.0001 BTC transaction on all of these transactions, and all of them are below 1 kiB. Am I doing anything wrong?

As I said before, the transactions are sent using bitcoind's "sendrawtransaction", but none of the inputs or the outputs of the transaction have anything to do with the wallet maintained by bitcoind.  In this case, should I periodically call "sendrawtransaction" with my transactions until I finally see them in a block, or will bitcoind do that on its own (even after the client restarts)?