Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 651. (Read 1276928 times)

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?

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

Success, finally!


It required this patch.


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

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

Why do you use two different addresses?

Yeah, that looks great. Thanks!



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.

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 '>: [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 : [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
    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!

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.

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?

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


Look OK to you?

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.

Thank you very much!!!!

Congrats!!

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

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,


and had the bitcon-qt client running.
 

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


which completed without any errors.


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



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,



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,


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,


you should see your balance displayed like this,



Hope this helps someone!

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

I got another crash...

I seem to have fixed the issue.

I ran ./counterpartyd.py market

and I get

lib.exceptions.DatabaseError: Countparty database is behind Bitcoind.

Is that normal?

Looks like it's synchronising.

How can I check the status?

Thanks.

Sorry, my mistake. I thought that I had seen another person with that same problem.

got the next errors on windows 7 x64 after updating to the newest source
in browser on http://rpc:rpcpw1234@localhost:18332 got
my bitcoin.conf and counterpartyd.conf are next:

Thanks.  Who else if having that bug?  Maybe I could speak with them to see if they got anywhere with it.

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.