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

[PhantomPhreak]

Okay, my rescan is finish.

Before burning I will update XCPsoft.
Just wanna make sure the following is correct (no more, no less):

Code:

cd ~/counterpartyd_build
git pull origin master
cd ~/counterpartyd_build/dist/counterpartyd
git pull origin master

Sure nothing else to do?

edit: info for those trying:
on counterparty.conf rpc-port=8332 (have to modify the original 18332)
'currently listing tons of "Starting new HTTP connection (1): localhost". Your "parsing" I guess.
That's kind of long, for a change..
(with old version, I haven't updated yet, 'wait confirmation)

EDIT: 'was too long, I aborded with ctrl+c
Did the upper 4 command
Then xcp --log-file=- -v
The start is exactly the same, a endless list of this kind

Code:

2014-01-05-T10:12:01+0100 Starting new HTTP connection (1): localhost
2014-01-05-T10:12:01+0100 "POST / HTTP/1.1" 200 2734

For now /home/user/.config/counterpartyd/counterpartyd.log is empty.
/home/user/.config/counterpartyd/ = 46.8 kB
/home/user/counterpartyd_build = 13.2Mb

Get rid of the -v, and those annoying messages will disappear.

[1715390115]

1715390115

[1715390115]

1715390115

[1715390115]

1715390115

[1715390115]

1715390115

[wizzardTim]

I felt the same

This slug is sooo painful!!!

So I went in the bitcoin-qt dir and ran "bitcoin-qt.exe -reindex"


aaaaaaaaaaaaaaaaaaaaaaaand the same story again

EDIT: tommorrow it will have synched again!

[wizzardTim]

BTW did you leave the deamon=1 in the .conf or not?

[panonym]

BTW did you leave the deamon=1 in the .conf or not?

Yes.
This is my bitcoin.conf

Code:

rpcuser=goodusername
rpcpassword=goodpassword
rpcport=8332
rpcallowip=127.0.0.1
server=1
daemon=1
txindex=1
gen=0

And my counterpartyd.conf

Code:

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

Get rid of the -v, and those annoying messages will disappear.

I don't mind the messages.
At least I can watch the progress, more or less.
edit: improvement idea = you could add the block number on all output.
I guess I have to wait it finish.  << ?
I tried this in another terminal

Code:

xcp address 12FWiDgNr2ubaWBTbwX9vwoGzhvpwN5wtd

It failed (DB behind or something)

505 more blocks to go.
Way more slow than the rescan of bitcoind.
   >> 25 minutes for 15 blocks... WTF that mean 13.61hours again??

Q: Is this data saved anywhere? I see no change of size in any file.
A real pain if that's needed at every start...  (edit a major problem if 13h each time...)

Code:

Counterparty database is behind Bitcoind. Is the counterpartyd server running?

xcp --log-file=- -v
This command make the server running, right?

[PhantomPhreak]

BTW did you leave the deamon=1 in the .conf or not?

Yes.
This is my bitcoin.conf

Code:

rpcuser=goodusername
rpcpassword=goodpassword
rpcport=8332
rpcallowip=127.0.0.1
server=1
daemon=1
txindex=1
gen=0

And my counterpartyd.conf

Code:

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

Get rid of the -v, and those annoying messages will disappear.

I don't mind the messages.
At least I can watch the progress, more or less.
edit: improvement idea = you could add the block number on all output.
I guess I have to wait it finish.  << ?
I tried this in another terminal

Code:

xcp address 12FWiDgNr2ubaWBTbwX9vwoGzhvpwN5wtd

It failed (DB behind or something)

505 more blocks to go.
Way more slow than the rescan of bitcoind.
   >> 25 minutes for 15 blocks... WTF that mean 13.61hours again??

Q: Is this data saved anywhere? I see no change of size in any file.
A real pain if that's needed at every start...  (edit a major problem if 13h each time...)

I don't understand what's going on. You should turn off logging with -v.

[panonym]

Done

Code:

xcp --log-file=-
2014-01-05-T11:04:53+0100 RESTART
2014-01-05-T11:05:48+0100 Block: 278330
2014-01-05-T11:06:27+0100 Block: 278331

485 block to go, I'm up 5 blocks.
Really seem to take 25min for 15 blocks... Keep you posted.

edit: going slightly faster. 3min for 6 blocks.
Making 4h instead of 13h.
Something else to speed up? (in a month it's gonna take days)

About the log,
no need to specify I wish it recorded in counterpartyd.log ?
something like counterprotocold --log-file='/home/user/.config/counterpartyd/counterpartyd.log'

edit: at least the data is saved somewhere.
I killed it and restart, no problem, no loss.

Finally a tiny change:

Code:

xcp --log-file=-
2014-01-05-T11:14:40+0100 RESTART
2014-01-05-T11:15:49+0100 Block: 278342
2014-01-05-T11:18:10+0100 Block: 278343
2014-01-05-T11:19:03+0100 Burn: 1Pcpxw6wJwXABhjCspe3CNf3gqSeh6eien burned 0.2 BTC for 299.38181818 XCP (7c2b1ca0…556d1cd7)
2014-01-05-T11:19:03+0100 Block: 278344

Not faster though, 2min20 between block 278342 and 278343.

In another terminal:

Code:

xcp address 1Pcpxw6wJwXABhjCspe3CNf3gqSeh6eien

Still asking me

Code:

Is the counterpartyd server running?

(I have a symlink xcp for counterpartyd, 'convenient)

That's long and difficult.
But I feel I become more confortable, 'learning.
That's rewarding. Good feeling.


edit: my screen went buggy & totally black for a few sec. Suddent Internal error.
/usr/bin/compiz ?
The log doesn't show anything about xcp. My guess is the bug was related to firefox.
Weird. Terminal is frozen. Can't use it.
I'm gonna restart.
For reader: I doubt this is linked with XCP.
(Restarted: weird keyboard, now everything seem normal again)

After restart I do 4sec~2min per block.

[BldSwtTrs]

Why I have that?

Code:

C:\>cd counterpartyd_build

C:\counterpartyd_build>C:\Python33\python.exe run.py --log-file=-
Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 1/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 2/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 3/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 4/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 5/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 6/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 7/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 8/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 9/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 10/12)
Could not connect to Bitcoind. Sleeping for five seconds. (Try 11/12)
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 413, i
n <module>
    util.bitcoind_check(db)
  File "C:\counterpartyd_build\dist\counterpartyd\lib\util.py", line 19, in bitc
oind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 51, 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?)

C:\counterpartyd_build>

My bitcoin.conf is :

Code:

rpcuser=rpc
rpcpassword=password
rpcport=188332
rpcallowip=127.0.0.1
server=1
daemon=1
txindex=1
gen=0

My counterpartyd.conf is :

Code:

[Default]
rpc-connect=localhost
rpc-port=188332
rpc-user=rpc
rpc-password=password

[panonym]

Wrong port.
It's 8332 on both.

[podizzle]

so investing in xcp right now gives me a chance to make 10-20% profit? and after next month there is no chance at the value of xcp going up. i guess i just dont see the upside.

[panonym]

During the 7 coming hour, you still make 40% bonus.
Soon 10% of the time will have pass.
(humm tired, math seem wrong, 'lazy to check again)

After the burning period: it's freemarket.
I doubt that anyone will sell under 1000XCP/1BTC.
Personnality I highly doubt to sell under 100XCP/BTC.
Wanna 1BTC for 20XCP lolz.
Will see~

[xibeijan]

Let's say I want to put out a broadcast with a fee of .01 (or 1% of the bets made on the broadcast) - it would look like this:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01

The text of a broadcast is a string. If you want to publish a value later on, then the syntax is:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01 --value=VALUE

Does that help?

I don't understand why there are two commands nor what they do.

For the first command, is the fee of 0.01 something I have to pay?

For the second command, do I need to pay for each update I make?  If so, do I pay in BTC or XCP?   Finally, where is this information stored?  In the bitcoin block chain OR does counterpart have its own block chain?

Thanks.

[jayso043]

I tested sending XCP burn via blockchain.info see aca58858a3266ca911e83769b00959349869966ad3910432100c20dc01df32b9 Could someone check if the XCP that worked. thanks

[BldSwtTrs]

Wrong port.
It's 8332 on both.

Cool. Thanks.

Now I have another problem though :

Code:

C:\>C:\Python33\python.exe run.py --log-file=-
C:\Python33\python.exe: can't open file 'run.py': [Errno 2] No such file or dire
ctory
C:\>

[panonym]

Don't know.
My guess is counterpartyd is not properly installed, if at all.

[kdrop22]

I tested sending XCP burn via blockchain.info see aca58858a3266ca911e83769b00959349869966ad3910432100c20dc01df32b9 Could someone check if the XCP that worked. thanks

Seems alright to me.
Both criteria are met.
a) The transaction amount < 1 BTC
b) The change address is same as sending address.

[panonym]

I tested sending XCP burn via blockchain.info see aca58858a3266ca911e83769b00959349869966ad3910432100c20dc01df32b9 Could someone check if the XCP that worked. thanks

Seems alright to me.

I'd wait a real confirmation before sending more, if I was you.
& 2 transactions after yours after 1 confirmation, your none yet.

[subSTRATA]

XCP added to fire that was already started by MSC and will make Bitcoin devs and miners ban all those protocols sooner.
For you morons not seeing that coming and obviously not thinking much I just wanna say thanks for burning your bitcoins.
Burn even more bitcoins so my stash goes up in value even more.

[panonym]

Go troll elsewhere, little-ripple-fan, will you.

Can't stop people from using Bitcoin to store data.
OP_RETURN will just make it cleaner.

Even in the unlikely event of v0.9 renouncing about OP_RETURN, the transaction record can serve as proof of investment.
We would rely by trust on dev to make it right, but that's still a security.

[subSTRATA]

Can't stop people from using Bitcoin to store data.

[cityglut]

Let's say I want to put out a broadcast with a fee of .01 (or 1% of the bets made on the broadcast) - it would look like this:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01

The text of a broadcast is a string. If you want to publish a value later on, then the syntax is:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01 --value=VALUE

Does that help?

I don't understand why there are two commands nor what they do.

For the first command, is the fee of 0.01 something I have to pay?

For the second command, do I need to pay for each update I make?  If so, do I pay in BTC or XCP?   Finally, where is this information stored?  In the bitcoin block chain OR does counterpart have its own block chain?

Thanks.

No, the fee is something those who are betting on your feed have to pay. The fee is basically meant to incentivize the issuer of the feed to maintain the integrity of the feed (both updating it regularly and not tampering with it). In my opinion, feed-issuers have the added incentive of developing a reputation: the more often they maintain their feeds to the satisfaction of those who are betting, the more trusted they will become, and hence the more often betters will bet on feeds issued by them.

You have to pay the standard Bitcoin fee for making a transaction each time you update your feed, yes.

The information is stored in the Blockchain. Counterparty does not have its own blockchain; Counterparty transactions are made on the Bitcoin blockchain.