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

cityglut

full member

Activity: 216

Merit: 100

Quote from: klee on January 03, 2014, 05:55:19 PM

@Developers - Can I send BTC to you and burn them for me?
I want to get in ASAP and it is a bit unfair for me as a mac user - I trust that when you will have a working client you will send the XCP back to me!

klee, I PMed you.

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Up to your thoughts.
Yes you need BTC to start with.

This project is more advance that your common spamnewcoin.
(There is even a cheap industry now... http://coingen.bluematt.me 'hopeless)

Spending time doing research, 'making effort to comprehend and improve your skills:
That's all part of it.

LeoC

full member

Activity: 154

Merit: 100

So I need to own BTC to start burning?
This is highly confusing to me.
Is there a potential to make money here, or will the XCP forever mirror BTC prices?
Seems more like high risk low reward to me.

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Quote from: LeoC on January 03, 2014, 06:25:21 PM

What are the hardware requirements to start burning, would I need an ASIC?

Burning need no specific hardware.
Burning has nothing to do with mining.
Burning is sending coin to an unvalid address, or to an address where it's obvious vanitygen couldn't have succeed to create it (pubkey where nobody own the privkey).

But to obtain XRP, sending BTC somewhere is not sufficent.
Read all the post again, and the doc links.
You have to use counterpartyd to get XCP in exchange of your burning.

LeoC

full member

Activity: 154

Merit: 100

What are the hardware requirements to start burning, would I need an ASIC?

klee

legendary

Activity: 1498

Merit: 1000

@Developers - Can I send BTC to you and burn them for me?
I want to get in ASAP and it is a bit unfair for me as a mac user - I trust that when you will have a working client you will send the XCP back to me!

PhantomPhreak

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Quote from: panonym on January 03, 2014, 05:32:21 PM

Quote from: PhantomPhreak on January 03, 2014, 05:05:57 PM

The fee is the usual BTC fee for a transaction of that size (very small).

So I must have some BTC linked to my key?!
What happen if I try to send XCP from an address which contain 0 bitcoin?
Does the transaction never confirm?
Anyway to cancel it in this case? (That is a major problem with all crypto, to me.)

Yes, you must have some BTC associated with an address from which you would like to send XCP, for example. If you don't have any and you try anyway, counterpartyd will fail gracefully.

Quote from: panonym on January 03, 2014, 05:32:21 PM

Quote from: PhantomPhreak on January 03, 2014, 05:05:57 PM

Use ./counterpartyd.py asset XCP to see how many XCP have been burned in all.

I will have to test. The .py is mandatory? not asset command in the main counterpartyd?

The .py is only mandatory if it doesn't work without it Wink

. I forgot that the build scripts remove that suffix from the command's name. So it should just be counterpartyd asset XCP for you.

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Quote from: PhantomPhreak on January 03, 2014, 05:19:14 PM

Update: The latest version of counterparty allows one also to cancel open orders and bets.

Awesome! That was needed.

Quote from: PhantomPhreak on January 03, 2014, 05:05:57 PM

The fee is the usual BTC fee for a transaction of that size (very small).

So I must have some BTC linked to my key?!
What happen if I try to send XCP from an address which contain 0 bitcoin?
Does the transaction never confirm?
Anyway to cancel it in this case? (That is a major problem with all crypto, to me.)

Quote from: PhantomPhreak on January 03, 2014, 05:05:57 PM

Use ./counterpartyd.py asset XCP to see how many XCP have been burned in all.

I will have to test. The .py is mandatory? not asset command in the main counterpartyd?

Very good job at answering question.
I'm impressed.
Hopefully in 12~24h my bitcoind will be sync and I will be able to start testing.

PhantomPhreak

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Update: The latest version of counterparty allows one also to cancel open orders and bets.

PhantomPhreak

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Quote from: reader31 on January 03, 2014, 04:51:22 PM

Quote

bitcoind -rpcport=8332 getinfo

gave me the following output,

Quote

{
"version" : 80600,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.01100000,
"blocks" : 278479,
"timeoffset" : -10,
"connections" : 8,
"proxy" : "",
"difficulty" : 1418481395.26263547,
"testnet" : false,
"keypoololdest" : 1388704801,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}

so once I updated the port to 8332 in ~/.config/counterpartyd/counterpartyd.conf I was able to connect with biotcoind.

When I run

Quote

counterpartyd --log-file=- -v

I get the following continuous stream of output on the terminal,

Quote

2014-01-03-T01:20:57-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:20:58-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:20:58-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:20:59-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:20:59-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:21:00-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:21:00-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:21:01-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:21:01-0800 "POST / HTTP/1.1" 200 38
.
.
.

Next, In a new terminal, I tried to run the following command,

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

to try to burn 0.01 btc, its asking for a confirmation, when I hit 'y', it crashes with the following message,

Traceback (most recent call last):
File "", line 1, in
ImportError: No module named mechanize
1

I see that the 0.01 btc is still in my address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc and hasnt been deducted.

any insight into why this crash might be happening?

Thx for your help. I really appreciate it

Remove the project directory and re-install. The newest version should both fix the mechanize bug and be more specific about the nature of any other problems you're still having then.

PhantomPhreak

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Quote from: panonym on January 03, 2014, 03:54:11 PM

Could you confirm the command try I wrote is correct?

counterpartyd send --from=mypublickeyholdingXCPinsidewalletdat --quantity=1000 --asset=XCP --to=mynewvanitygenBTCaddress
is that correct to transfer 1000 XCP? (no fee? what about network spam-risk?)

That looks correct. The fee is the usual BTC fee for a transaction of that size (very small).

Quote from: panonym on January 03, 2014, 03:54:11 PM

Is there a command to see the total number of XCP?
If not, could you add it?
It would be a big plus in improving trust to your project.
(Ability to follow number of coin created, to be certain there is no XCP created without burning)

Sure. Use ./counterpartyd.py asset XCP to see how many XCP have been burned in all.

reader31

full member

Activity: 221

Merit: 100

Quote from: PhantomPhreak on January 03, 2014, 10:45:24 AM

Quote from: reader31 on January 03, 2014, 10:13:17 AM

After I get bitcoind sucessfully running(i can see the bitcoind process running),

when I try to run counterpartyd, I get the followiing error,

Quote

Traceback (most recent call last):
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/packages/urllib3/connectionpool.py", line 478, in urlopen
   body=body, headers=headers)
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/packages/urllib3/connectionpool.py", line 285, in _make_request
   conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.3/http/client.py", line 1061, in request
   self._send_request(method, url, body, headers)
  File "/usr/lib/python3.3/http/client.py", line 1099, in _send_request
   self.endheaders(body)
  File "/usr/lib/python3.3/http/client.py", line 1057, in endheaders
   self._send_output(message_body)
  File "/usr/lib/python3.3/http/client.py", line 902, in _send_output
   self.send(msg)
  File "/usr/lib/python3.3/http/client.py", line 840, in send
   self.connect()
  File "/usr/lib/python3.3/http/client.py", line 818, in connect
   self.timeout, self.source_address)
  File "/usr/lib/python3.3/socket.py", line 435, in create_connection
   raise err
  File "/usr/lib/python3.3/socket.py", line 426, in create_connection
   sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/adapters.py", line 324, in send
   timeout=timeout
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/packages/urllib3/connectionpool.py", line 528, in urlopen
   raise MaxRetryError(self, url, e)
requests.packages.urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=18332): Max retries exceeded with url: / (Caused by : [Errno 111] Connection refused)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/coin/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 34, in rpc
   response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/api.py", line 88, in post
   return request('post', url, data=data, **kwargs)
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/api.py", line 44, in request
   return session.request(method=method, url=url, **kwargs)
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/sessions.py", line 382, in request
   resp = self.send(prep, **send_kwargs)
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/sessions.py", line 485, in send
   r = adapter.send(request, **kwargs)
  File "/home/coin/counterpartyd_build/env/lib/python3.3/site-packages/requests/adapters.py", line 372, in send
   raise ConnectionError(e)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=18332): Max retries exceeded with url: / (Caused by : [Errno 111] Connection refused)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/coin/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 401, in
   util.bitcoind_check(db)
  File "/home/coin/counterpartyd_build/dist/counterpartyd/lib/util.py", line 18, in bitcoind_check
   block_count = bitcoin.rpc('getblockcount', [])['result']
  File "/home/coin/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 36, in rpc
   raise exceptions.BitcoindRPCError('Cannot communicate with bitcoind. (Are you on testnet?)')
lib.exceptions.BitcoindRPCError: Cannot communicate with bitcoind. (Are you on testnet?)

theres are my config files,

~/.config/counterpartyd/counterpartyd.conf

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

~/.bitcoin/bitcoin.conf

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

I'm on ubuntu 13.10 and was able to build counterpartd sucessfully from the source....

I'm trying to get counterpartyd running on the mainnet.

any insights would be appreciated. thx.

It looks like counterpartyd is set to run on testnet, as it's looking for Bitcoind on port 18332, though neither of those configuration files has testnet enabled. Did you pass counterpartyd the option --testnet on the command-line? If so, get rid of that and try it again. What was the exact command that you tried to run? Try the following commands, too, to see what port Bitcoind is running on and whether it's working, just in case:
bitcoind -rpcport=8332 getinfo
bitcoind -rpcport=18332 getinfo

running

Quote

bitcoind -rpcport=8332 getinfo

gave me the following output,

Quote

{
   "version" : 80600,
   "protocolversion" : 70001,
   "walletversion" : 60000,
   "balance" : 0.01100000,
   "blocks" : 278479,
   "timeoffset" : -10,
   "connections" : 8,
   "proxy" : "",
   "difficulty" : 1418481395.26263547,
   "testnet" : false,
   "keypoololdest" : 1388704801,
   "keypoolsize" : 101,
   "paytxfee" : 0.00000000,
   "errors" : ""
}

so once I updated the port to 8332 in ~/.config/counterpartyd/counterpartyd.conf I was able to connect with biotcoind.

When I run

Quote

counterpartyd --log-file=- -v

I get the following continuous stream of output on the terminal,

Quote

2014-01-03-T01:20:57-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:20:58-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:20:58-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:20:59-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:20:59-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:21:00-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:21:00-0800 "POST / HTTP/1.1" 200 38
2014-01-03-T01:21:01-0800 Starting new HTTP connection (1): localhost
2014-01-03-T01:21:01-0800 "POST / HTTP/1.1" 200 38
.
.
.

Next, In a new terminal, I tried to run the following command,

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

to try to burn 0.01 btc, its asking for a confirmation, when I hit 'y', it crashes with the following message,

Traceback (most recent call last):
File "", line 1, in
ImportError: No module named mechanize
1

I see that the 0.01 btc is still in my address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc and hasnt been deducted.

any insight into why this crash might be happening?

Thx for your help. I really appreciate it

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Quote from: Wekkel on January 03, 2014, 04:08:51 PM

I must be too far away from serious dev talk, but could someone explain all this in lay man's terms?

- The proof of burn (POB) the dev implemented is a fair, secure and trustless way to generate new coin & split them amongst investor. [first one to such perfected level]

- This is a protocol on top of Bitcoin (no alternative blockchain)

- descentralized exchange feature exist from the lunch. [first one having something else than words]

Wekkel

legendary

Activity: 3108

Merit: 1531

yes

I must be too far away from serious dev talk, but could someone explain all this in lay man's terms?

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Quote from: PhantomPhreak on January 03, 2014, 03:49:26 PM

Actually, send also works for XCP.

I edit a bit too much my post, sorry about that.
Could you confirm the command try I wrote is correct?

counterpartyd send --from=mypublickeyholdingXCPinsidewalletdat --quantity=1000 --asset=XCP --to=mynewvanitygenBTCaddress
is that correct to transfer 1000 XCP? (no fee? what about network spam-risk?)

Is there a command to see the total number of XCP?
If not, could you add it?
It would be a big plus in improving trust to your project.
(Ability to follow number of coin created, to be certain there is no XCP created without burning)

edit: and thanks for the 3 links.
Already saw them, but good that people reading this tread see the 3 link at one place.
Seems to me you have already done a pretty good job with the doc.
Compare to the average newcoin we get, I'm impressed.

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Quote from: NewLiberty on January 03, 2014, 03:38:32 PM

This method is worthy of notice. ++confidence.
One point not mentioned above, PoB, it is also a donation to the larger Bitcoin community in creating slightly more scarce bitcoin.

Yup, NewLiberty is correct.
POB is not a treat to BTC at all.
If it does one thing, it is slightly speeding up it's deflation (or guarantee it).
Theorically. After: it's a pure freemarket.
Where sometime shitty project have huge success & amazing project much less than it should.
Don't think humanity-as-a-whole extremely rational...

PhantomPhreak

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Quote from: panonym on January 03, 2014, 03:21:47 PM

issuance became totaly obscure to me.
I hope we will see centralized info in the coming 1~2 month. FAQ etc. or wiki-style
A gui too, even if limited at the beginning. <== wish wish

Absolutely. For the record, right now there's a README, a protocol spec. and some documentation at Read the Docs.

Quote from: panonym on January 03, 2014, 03:21:47 PM

For counterpartyd to send the XCP to another address: What would the command line looks?

edit: Oh I see on github you have a send command.
Will we finally have descentralized email system where the sender must pay to contact you? 'want that!
edit2: miss read, doesn't seem to be that at all, a pity. [it's for sending assets]

Actually, send also works for XCP.

NewLiberty

legendary

Activity: 1204

Merit: 1002

Gresham's Lawyer

Quote from: panonym on January 03, 2014, 02:28:13 PM

What I really like with proof of burn is that it puts absolutely everyone to the same level of opportunity.
Including the dev.
Congrats for not being one more greedy fast starter.
Your project success, you make money too. 'Good & honest motivation to work!
Thanks for showing exemple. Hope it will have the success it deserves.

It's too easy/unfair to create an IPO coin, sending huge amount of your money to yourself to get coins, that people get by sending you money... scam-smell 99.9%
Just watch Visacoin, Next, Mastercoin, Ripple...
I'm pretty sure for VSC at least 60% of the funds is from the dev to himself.
Almost certain it happened for NXT & MST too.
(uncomfort: your internal assets are thought to be created this way if no XCP-POB)

Proof of burn is the way to go. Almost scam-proof.
Point of a scam: making you lose money, making the scammer take/win your money
With POB, you can still lose your money, but the dev cannot take/win your money.
Therefore there is not real motivation to scam you.
(Obvious security reminder: be careful not having all your BTC in a single wallet.dat...)

The way XCP are created also seem to avoid suddent wish of purposedly bad wealth repartition...
Yeah, 'thinking Next. (announced ~1.5 month invest time, stopped after 2 weeks... BAD)
[DO NOT CHANGE THE TIME ALLOWED TO INVEST, under any pretext, 'trusting you on that]

This method is worthy of notice. ++confidence.
One point not mentioned above, PoB, it is also a donation to the larger Bitcoin community in creating slightly more scarce bitcoin.

panonym

sr. member

Activity: 266

Merit: 250

Help and Love one another ♥

Nice.
order really looks like an awesome function, if it works as pretended.
Have to test.

issuance became totaly obscure to me.
I hope we will see centralized info in the coming 1~2 month. FAQ etc. or wiki-style
A gui too, even if limited at the beginning. <== wish wish

Xibeijan, what do you mean a crap rate?
1BTC = 100XCP or 10000XCP, doesn't change a thing. Have to chose a rate.
Kind of convenient choice. if 1BTC=1000$ 1XCP=min1$
Might very well be 1XCP=0.1BTC in the future. Or 1XCP=1BTC.
Psychologically, it is good that we do not arrive too quickly to 1XCP=10BTC, due to less XCP for 1BTC at start.

For counterpartyd to send the XCP to another address: What would the command line looks?
counterpartyd send --from=mypublickeyholdingXCPinsidewalletdat --quantity=1000 --asset=XCP --to=mynewvanitygenBTCaddress
is that correct to transfer 1000 XCP? (no fee?)

edit: Oh I see on github you have a send command.
Will we finally have descentralized email system where the sender must pay to contact you? 'want that!
edit2: miss read, doesn't seem to be that at all, a pity. [it's for sending assets]

xibeijan

legendary

Activity: 1232

Merit: 1001

Quote from: PhantomPhreak on January 02, 2014, 05:42:27 PM

For an example successful burn on mainnet, see transaction 685623401c3f5e9d2eaaf0657a50454e56a270ee7630d409e98d3bc257560098. (Of course it looks a little funny on blockchain.info.)

0.0005 BTC were burned and 0.74959091 XCP were earned, at a price of 1499.18182 XCP/BTC. The transaction is correctly parsed by counterpartyd.

That's 0.000667 BTC per XCP. A crap rate for such alpha code.

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