[ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread

[reader31]

For the benefit of others trying to burn xcp, here what I did to get my xcp burnt, my os is ubuntu 13.10,

(These steps worked for me, please feel free to correct/modify/update these instructions as needed)

1)
I downloaded and installed the latest bitcoin-qt client and updated the bitcoin.conf( ~/.bitcoin/bitcoin.conf) with this content,

rpcuser=rpc
rpcpassword=rpcpw1234
server=1
daemon=1
txindex=1

and had the bitcon-qt client running.
 

2)
Next, to get counterpartyd installed, from my home directory I ran this command,

sudo apt-get -y update
sudo apt-get -y install git-core python3.3 python3
git clone https://github.com/xnova/counterpartyd_build ~/counterpartyd_build
sudo python3 ~/counterpartyd_build/setup.py

which completed without any errors.


3)
then I updated the counterpartyd.conf file (~/.config/counterpartyd/counterpartyd.conf) with this content,

[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=rpc
rpc-password=rpcpw1234

4)
At this point in a new terminal if I run,

counterpartyd --log-file=- -v


If everything from the above steps worked fine, you should see the following output,

2014-01-04-T12:54:47-0800 Starting new HTTP connection (1): localhost
2014-01-04-T12:54:47-0800 "POST / HTTP/1.1" 200 38
2014-01-04-T12:54:48-0800 Starting new HTTP connection (1): localhost
2014-01-04-T12:54:48-0800 "POST / HTTP/1.1" 200 38
2014-01-04-T12:54:49-0800 Starting new HTTP connection (1): localhost
2014-01-04-T12:54:49-0800 "POST / HTTP/1.1" 200 38
2014-01-04-T12:54:50-0800 Starting new HTTP connection (1): localhost
2014-01-04-T12:54:50-0800 "POST / HTTP/1.1" 200 38
2014-01-04-T12:54:51-0800 Starting new HTTP connection (1): localhost
2014-01-04-T12:54:51-0800 "POST / HTTP/1.1" 200 38

5)
At this point I was ready to burn. I created a new received address in the bitcoin-qt wallet, deposited 0.01 btc into that address.


In a new terminal, I ran,

counterpartyd --rpc-password=rpcpw1234 burn --from=1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc --quantity=0.01

it asked me for a confirmation(hit 'y').

when the burn is sucessful I immediatley got a confirmation string like this,

"8cc4f74ec9b84fc73c0e092c6243253946431448f675b6d2cfd4398438d3b8df"


You should see your transactions show up on this page,

https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr


after you see your transaction confirmed atleast once, you can go back to your terminal and run,

counterpartyd --rpc-password=rpcpw1234 address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc

you should see your balance displayed like this,

Balances
+-------+-------------+
| Asset |    Amount   |
+-------+-------------+
|  XCP  | 14.72636364 |
+-------+-------------+


Burns
+-------------+----------+-----------------+-------------------+
| Block Index |  Burned  |      Earned     |      Tx Hash      |
+-------------+----------+-----------------+-------------------+
|    278611   | 0.01 BTC | 14.72636364 XCP | 8cc4f74e…38d3b8df |
+-------------+----------+-----------------+-------------------+


Sends
+--------+-------+--------+-------------+---------+
| Amount | Asset | Source | Destination | Tx Hash |
+--------+-------+--------+-------------+---------+
+--------+-------+--------+-------------+---------+

Hope this helps someone!

[1713559816]

1713559816

[wizzardTim]

Thank you very much!!!!

Congrats!!

Now we need a similar guide for windows and later for blockchain.info.

[PhantomPhreak]

Is there any way (command) to gauge progress as counterpartyd is processing the blockchain?

$ ./counterpartyd.py  --rpc-password=$BTCPASS market
Traceback (most recent call last):
  File "./counterpartyd.py", line 407, in <module>
    util.database_check(db)
  File "/home/counterpartycoin/counterpartyd/lib/util.py", line 36, in database_check
    raise exceptions.DatabaseError('Countparty database is behind Bitcoind.')
lib.exceptions.DatabaseError: Countparty database is behind Bitcoind.

Sure. The log file (usually in ~/.config/counterpartyd/counterpartyd.log) shows each block as it's being parsed. When the last block parsed is the last block that Bitcoind has seen (check with bitcoind getinfo), the Counterparty database has caught up with Bitcoind.

[xibeijan]

I got another crash...

./counterpartyd.py -v --log-file=yo.log server


Traceback (most recent call last):
  File "./counterpartyd.py", line 532, in <module>
    blocks.follow()
  File "/home/X/counterpartyd/lib/blocks.py", line 390, in follow
    source, destination, btc_amount, fee, data = get_tx_info(tx)
  File "/home/X/counterpartyd/lib/blocks.py", line 319, in get_tx_info
    data = binascii.unhexlify(asm[1])
TypeError: 'str' does not support the buffer interface

I think I've fixed it.  Here's a patch.

diff --git a/lib/blocks.py b/lib/blocks.py
index 7a9985b..827a0d6 100644
--- a/lib/blocks.py
+++ b/lib/blocks.py
@@ -316,7 +316,7 @@ def get_tx_info (tx):
         if not data:
             asm = vout['scriptPubKey']['asm'].split(' ')
             if asm[0] == 'OP_RETURN' and len(asm) == 2:
-                data = binascii.unhexlify(asm[1])
+                data = binascii.unhexlify(bytes(asm[1], 'UTF-8'))
 
     # Only look for source if data were found (or destination is UNSPENDABLE), for speed.
     if not data and destination != config.UNSPENDABLE:

Look OK to you?

[xibeijan]

the bitcoin.conf shouldn't have daemon=1?

Those instructions are for using Bitcoind as the backend for counterpartyd, and then using counterpartyd to burn (entirely safely), not for using Bitcoind to burn BTC directly (which would, at this time, be unsafe).

xnova, when he gets back online soon, should be able to help fix that bug you and a few others are having. I don't think that the daemon=1 option is the problem.

Can I burn more than once from the same BTC address?   For example, burn 0.01 BTC as a test, then burn 0.99 BTC?

What's the min TX fee for bitcoind / counterpartyd?

[xibeijan]

Is there any form of mining with XCP, either in the minting of new CXP (which I doubt) or in the form of harvesting transaction fees?

Thanks.

[LeoC]

Please help, I have bitcoin-qt running just fine and when I try to start Counterpart, I get this:


c:\counterpartyd_build>c:\python33\python.exe run.py -v

Traceback (most recent call last):
  File "c:\counterpartyd_build\env\lib\site-packages\requests\packages\urllib3\c
onnectionpool.py", line 478, in urlopen
    body=body, headers=headers)
  File "c:\counterpartyd_build\env\lib\site-packages\requests\packages\urllib3\c
onnectionpool.py", line 285, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "c:\python33\Lib\http\client.py", line 1065, in request
    self._send_request(method, url, body, headers)
  File "c:\python33\Lib\http\client.py", line 1103, in _send_request
    self.endheaders(body)
  File "c:\python33\Lib\http\client.py", line 1061, in endheaders
    self._send_output(message_body)
  File "c:\python33\Lib\http\client.py", line 906, in _send_output
    self.send(msg)
  File "c:\python33\Lib\http\client.py", line 844, in send
    self.connect()
  File "c:\python33\Lib\http\client.py", line 822, in connect
    self.timeout, self.source_address)
  File "c:\python33\Lib\socket.py", line 435, in create_connection
    raise err
  File "c:\python33\Lib\socket.py", line 426, in create_connection
    sock.connect(sa)
OSError: [WinError 10055] An operation on a socket could not be performed becaus
e the system lacked sufficient buffer space or because a queue was full

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\counterpartyd_build\env\lib\site-packages\requests\adapters.py", line
 324, in send
    timeout=timeout
  File "c:\counterpartyd_build\env\lib\site-packages\requests\packages\urllib3\c
onnectionpool.py", line 528, in urlopen
    raise MaxRetryError(self, url, e)
requests.packages.urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='loc
alhost', port=8332): Max retries exceeded with url: / (Caused by <class 'OSError
'>: [WinError 10055] An operation on a socket could not be performed because the
 system lacked sufficient buffer space or because a queue was full)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 36, in r
pc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=heade
rs)
  File "c:\counterpartyd_build\env\lib\site-packages\requests\api.py", line 88,
in post
    return request('post', url, data=data, **kwargs)
  File "c:\counterpartyd_build\env\lib\site-packages\requests\api.py", line 44,
in request
    return session.request(method=method, url=url, **kwargs)
  File "c:\counterpartyd_build\env\lib\site-packages\requests\sessions.py", line
 382, in request
    resp = self.send(prep, **send_kwargs)
  File "c:\counterpartyd_build\env\lib\site-packages\requests\sessions.py", line
 485, in send
    r = adapter.send(request, **kwargs)
  File "c:\counterpartyd_build\env\lib\site-packages\requests\adapters.py", line
 372, in send
    raise ConnectionError(e)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8
332): Max retries exceeded with url: / (Caused by <class 'OSError'>: [WinError 1
0055] An operation on a socket could not be performed because the system lacked
sufficient buffer space or because a queue was full)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 532, i
n <module>
    blocks.follow()
  File "c:\counterpartyd_build\dist\counterpartyd\lib\blocks.py", line 389, in f
ollow
    tx = bitcoin.rpc('getrawtransaction', [tx_hash, 1])
  File "c:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 40, in r
pc
     raise exceptions.BitcoindRPCError('Cannot communicate with Bitcoind. (counte
rpartyd is set to run on {}, is Bitcoind?)'.format(network))
lib.exceptions.BitcoindRPCError: Cannot communicate with Bitcoind. (counterparty
d is set to run on mainnet, is Bitcoind?)

I have 8GB of ram. This thing keeps spitting out error after error and I followed the instructions to the letter. My profits are decreasing every day!

[PhantomPhreak]

I got another crash...

./counterpartyd.py -v --log-file=yo.log server


Traceback (most recent call last):
  File "./counterpartyd.py", line 532, in <module>
    blocks.follow()
  File "/home/X/counterpartyd/lib/blocks.py", line 390, in follow
    source, destination, btc_amount, fee, data = get_tx_info(tx)
  File "/home/X/counterpartyd/lib/blocks.py", line 319, in get_tx_info
    data = binascii.unhexlify(asm[1])
TypeError: 'str' does not support the buffer interface

I think I've fixed it.  Here's a patch.

diff --git a/lib/blocks.py b/lib/blocks.py
index 7a9985b..827a0d6 100644
--- a/lib/blocks.py
+++ b/lib/blocks.py
@@ -316,7 +316,7 @@ def get_tx_info (tx):
         if not data:
             asm = vout['scriptPubKey']['asm'].split(' ')
             if asm[0] == 'OP_RETURN' and len(asm) == 2:
-                data = binascii.unhexlify(asm[1])
+                data = binascii.unhexlify(bytes(asm[1], 'UTF-8'))
 
     # Only look for source if data were found (or destination is UNSPENDABLE), for speed.
     if not data and destination != config.UNSPENDABLE:

Look OK to you?

Yeah, that looks great. Thanks!

Can I burn more than once from the same BTC address?   For example, burn 0.01 BTC as a test, then burn 0.99 BTC?

What's the min TX fee for bitcoind / counterpartyd?

Yes, you can. counterpartyd will try to warn you if you attempt to burn more than 1 BTC (but if the first burn still isn't confirmed, it might not catch the error!). The fee paid for every Counterparty transaction is 10000 satoshis, as none of them is over a KB.

[xibeijan]

counterpartyd --rpc-password=rpcpw1234 burn --from=1EFU6nkG4y9BmrBTZd4VPu1cF7AwR3qYrN --quantity=0.01

counterpartyd --rpc-password=rpcpw1234 address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc

Why do you use two different addresses?

[PhantomPhreak]

Is there any form of mining with XCP, either in the minting of new CXP (which I doubt) or in the form of harvesting transaction fees?

Thanks.

No, and all of the transaction fees are in BTC, except for those paid in XCP to the operators of 'feeds'.

[btc4ever]

Success, finally!

$ ./counterpartyd.py  --rpc-password=$BTCPASS burn --from=15GzM24gRpNHqPvLJGqWkGMwzQzf8giqJf --quantity=0.00121056
Confirm? (y/N) y
"d9784b362d3a16bfb587a068ca0209b4d7735c24f774d984894e62accd0db2e1"

It required this patch.

$ git diff
diff --git a/lib/bitcoin.py b/lib/bitcoin.py
index c61636b..6d8ed5e 100644
--- a/lib/bitcoin.py
+++ b/lib/bitcoin.py
@@ -111,7 +111,7 @@ def serialise (inputs, destination_output=None, data_output=None, change_output=
     # List of Inputs.
     for i in range(len(inputs)):
         txin = inputs
-        s += binascii.unhexlify(txin['txid'])[::-1]         # TxOutHash
+        s += binascii.unhexlify(bytes(txin['txid'], 'UTF-8'))[::-1]         # TxOutHash
         s += txin['vout'].to_bytes(4, byteorder='little')   # TxOutIndex
 
         # No signature.
diff --git a/lib/blocks.py b/lib/blocks.py
index 7a9985b..827a0d6 100644
--- a/lib/blocks.py
+++ b/lib/blocks.py
@@ -316,7 +316,7 @@ def get_tx_info (tx):
         if not data:
             asm = vout['scriptPubKey']['asm'].split(' ')
             if asm[0] == 'OP_RETURN' and len(asm) == 2:
-                data = binascii.unhexlify(asm[1])
+                data = binascii.unhexlify(bytes(asm[1], 'UTF-8'))
 
     # Only look for source if data were found (or destination is UNSPENDABLE), for speed.
     if not data and destination != config.UNSPENDABLE:

devs, please audit/fix all instances of binascii.unhexlify.  grep finds more of them.

lib/bitcoin.py:    res = binascii.unhexlify(h.encode('utf8'))
lib/bitcoin.py:        s += binascii.unhexlify(bytes(txin['txid'], 'UTF-8'))[::-1]         # TxOutHash
lib/blocks.py:                data = binascii.unhexlify(bytes(asm[1], 'UTF-8'))
lib/cancel.py:    offer_hash_bytes = binascii.unhexlify(offer_hash)
lib/btcpay.py:    tx0_hash_bytes, tx1_hash_bytes = binascii.unhexlify(tx0_hash), binascii.unhexlify(tx1_hash)
test/test_.py:                data = binascii.unhexlify(asm[1])

[PhantomPhreak]

Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in <module>
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

I seem to have fixed the issue.

xibeijan, how did you get around the 'label empty or too long' error?

[xibeijan]

Yes, you can. counterpartyd will try to warn you if you attempt to burn more than 1 BTC (but if the first burn still isn't confirmed, it might not catch the error!). The fee paid for every Counterparty transaction is 10000 satoshis, as none of them is over a KB.

Do the funds have to all come from the same BTC address?

That is, I have a btw address xfoo...

I TX 0.001 BTX to xfoo...

I counterpartyd burn --from=xfoo.. --quantity=0.0099 [paying the 10,000 satoshi (aka 0.0001 BTC) fee]

So far burned 0.0099

I TX 0.9902 BTX to xfoo...

I counterpartyd burn --from=xfoo.. --quantity=0.9901 [paying the 10,000 satoshi (aka 0.0001 BTC) fee]

So far burned 1.0 BTC

Is this find to do?  Does it all add up correctly?

All good?

[reader31]

counterpartyd --rpc-password=rpcpw1234 burn --from=1EFU6nkG4y9BmrBTZd4VPu1cF7AwR3qYrN --quantity=0.01

counterpartyd --rpc-password=rpcpw1234 address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc

Why do you use two different addresses?

Oops...ignore the two different address...you would need to use the same address ofcourse!
Didnt notice i had switched the address. Thx for catching that. Will get that fixed.

[xibeijan]

xibeijan, how did you get around the 'label empty or too long' error?

I had an old version of the requests library.  I think it was 0.12.1

I upgraded to version 2.1.0

[PhantomPhreak]

Success, finally!

$ ./counterpartyd.py  --rpc-password=$BTCPASS burn --from=15GzM24gRpNHqPvLJGqWkGMwzQzf8giqJf --quantity=0.00121056
Confirm? (y/N) y
"d9784b362d3a16bfb587a068ca0209b4d7735c24f774d984894e62accd0db2e1"

It required this patch.

$ git diff
diff --git a/lib/bitcoin.py b/lib/bitcoin.py
index c61636b..6d8ed5e 100644
--- a/lib/bitcoin.py
+++ b/lib/bitcoin.py
@@ -111,7 +111,7 @@ def serialise (inputs, destination_output=None, data_output=None, change_output=
     # List of Inputs.
     for i in range(len(inputs)):
         txin = inputs
-        s += binascii.unhexlify(txin['txid'])[::-1]         # TxOutHash
+        s += binascii.unhexlify(bytes(txin['txid'], 'UTF-8'))[::-1]         # TxOutHash
         s += txin['vout'].to_bytes(4, byteorder='little')   # TxOutIndex
 
         # No signature.
diff --git a/lib/blocks.py b/lib/blocks.py
index 7a9985b..827a0d6 100644
--- a/lib/blocks.py
+++ b/lib/blocks.py
@@ -316,7 +316,7 @@ def get_tx_info (tx):
         if not data:
             asm = vout['scriptPubKey']['asm'].split(' ')
             if asm[0] == 'OP_RETURN' and len(asm) == 2:
-                data = binascii.unhexlify(asm[1])
+                data = binascii.unhexlify(bytes(asm[1], 'UTF-8'))
 
     # Only look for source if data were found (or destination is UNSPENDABLE), for speed.
     if not data and destination != config.UNSPENDABLE:

devs, please audit/fix all instances of binascii.unhexlify.  grep finds more of them.

lib/bitcoin.py:    res = binascii.unhexlify(h.encode('utf8'))
lib/bitcoin.py:        s += binascii.unhexlify(bytes(txin['txid'], 'UTF-8'))[::-1]         # TxOutHash
lib/blocks.py:                data = binascii.unhexlify(bytes(asm[1], 'UTF-8'))
lib/cancel.py:    offer_hash_bytes = binascii.unhexlify(offer_hash)
lib/btcpay.py:    tx0_hash_bytes, tx1_hash_bytes = binascii.unhexlify(tx0_hash), binascii.unhexlify(tx1_hash)
test/test_.py:                data = binascii.unhexlify(asm[1])

Way ahead of you . Thanks for the reminder, though!

[btc4ever]

Question: what if you forget which bitcoin address you used?   I don't see a command equivalent to listtransactions or getinfo in bitcoind.

counterpartyd --rpc-password=rpcpw1234 address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc

[xibeijan]

Yes, you can. counterpartyd will try to warn you if you attempt to burn more than 1 BTC (but if the first burn still isn't confirmed, it might not catch the error!). The fee paid for every Counterparty transaction is 10000 satoshis, as none of them is over a KB.

Do the funds have to all come from the same BTC address?

That is, I have a btw address xfoo...

I TX 0.001 BTX to xfoo...

I counterpartyd burn --from=xfoo.. --quantity=0.0099 [paying the 10,000 satoshi (aka 0.0001 BTC) fee]

So far burned 0.0099

I TX 0.9902 BTX to xfoo...

I counterpartyd burn --from=xfoo.. --quantity=0.9901 [paying the 10,000 satoshi (aka 0.0001 BTC) fee]

So far burned 1.0 BTC

Is this find to do?  Does it all add up correctly?

All good?

Can anyone confirm the above proceedure is fine?

Also, how many confirmations must I want on BTC transfer?

[PhantomPhreak]

Yes, you can. counterpartyd will try to warn you if you attempt to burn more than 1 BTC (but if the first burn still isn't confirmed, it might not catch the error!). The fee paid for every Counterparty transaction is 10000 satoshis, as none of them is over a KB.

Do the funds have to all come from the same BTC address?

That is, I have a btw address xfoo...

I TX 0.001 BTX to xfoo...

I counterpartyd burn --from=xfoo.. --quantity=0.0099 [paying the 10,000 satoshi (aka 0.0001 BTC) fee]

So far burned 0.0099

I TX 0.9902 BTX to xfoo...

I counterpartyd burn --from=xfoo.. --quantity=0.9901 [paying the 10,000 satoshi (aka 0.0001 BTC) fee]

So far burned 1.0 BTC

Is this find to do?  Does it all add up correctly?

All good?

Can anyone confirm the above proceedure is fine?

Also, how many confirmations must I want on BTC transfer?

That looks correct, yes.

One confirmation.

[xibeijan]

Is there any form of mining with XCP, either in the minting of new CXP (which I doubt) or in the form of harvesting transaction fees?

Thanks.

No, and all of the transaction fees are in BTC, except for those paid in XCP to the operators of 'feeds'.

Does that mean we collect fees in BTC by processing XCP transactions or does it go to the normal bitcoin miners?

Also, what about those pain in XCP to the operators of feeds?  Can you please explain a bit more about who that works or provide a link to the documentation about this.

Highly interesting.