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

I don't think your PoB mining reward schedule offers an attractive investment opportunity.

There's only a linear decrease in reward, so early adopters are not rewarded very much at all.  Worse, the reward only decays down to 1000 XCP/BTC, so even in the latest stage a large-scale investor could obtain a huge sum of XCP.  At least it could have been a linear decrease down to zero.

Thus, I'm not sure, XCP makes a lot of sense for anyone to buy.  Seems like only big players can win here.

Here's a plot of the XCP reward for a 1 BTC investment.  The x-axis is the block number.

http://fooplot.com/#W3sidHlwZSI6MCwiZXEiOiIxMDAwKzUwMCooMjgzODEwLXgpLzU1MDAiLCJjb2xvciI6IiMwMDAwMDAifSx7InR5cGUiOjEwMDAsIndpbmRvdyI6WyIyNzcwNjYuMTUzODQ2MTUzOSIsIjI4MjU2Ni4xNTM4NDYxNTM5IiwiLTMzNjcuMjU0MzYwMDYzOTk5NyIsIjM1MDQuNjkzMzEzNTM2Il19XQ--

Not very inspiring... Maybe I got it wrong?

Anyway, that's just my thought on it.  Perhaps someone could explain how I'm wrong?  If not, then it's still not too late to decrease the reward for late-comers to make things more fair for those who have already invested.

from the burning from blockchain.info wallet instruction


To address points to 1CounterpartyXXXXXXXXXXXXXXXUWLpVr , so the change address should be 1CounterpartyXXXXXXXXXXXXXXXUWLpVr, but why the screenshot is using "From" address ?

Yay! Now to just transfer some BTC to the wallet

Yes, it is working. Congrats!! 

If I see this does it mean it's working now:

2014-01-04-T11:34:11Pacific Standard Time Burn: 12ZhgyXFYvWRtpwEAV3t8thgTto2yMM5
R6 burned 1.0 BTC for 1465.54545455 XCP (86f56382\u20268ec50a9d)
2014-01-04-T11:34:11Pacific Standard Time Block: 278690
2014-01-04-T11:34:11Pacific Standard Time Burn: 17LntpaSiQL4pa8moojZGRqe8nLsjibZ
fm burned 0.9999 BTC for 1465.308 XCP (d3cce6dd\u20262f95e3ab)
2014-01-04-T11:34:11Pacific Standard Time Burn: 16nUhvJJZifpdWyqni13AWQwm6GGrAci
bp burned 0.9999 BTC for 1465.308 XCP (a8656bb4\u20268b8c621b)
2014-01-04-T11:34:11Pacific Standard Time Burn: 1CNqtdhXUVBgHdPanpUJZd2osFiYSCYY
cR burned 0.99990499 BTC for 1465.31531262 XCP (26f84ab6\u20261088643a)
2014-01-04-T11:34:11Pacific Standard Time Burn: 1CVEtRWVfx7fovcUK94DJB6Vwz7MdkdY
d1 burned 0.99990499 BTC for 1465.31531262 XCP (49f786b0\u20269c50d383)
2014-01-04-T11:34:11Pacific Standard Time Block: 278691
2014-01-04-T11:34:11Pacific Standard Time Burn: 1AKVdmoAUwcdSjwjTiamcUneDNTF1WvW
CE burned 1.0 BTC for 1465.36363636 XCP (0e0decaf\u2026d53d7d2c)
2014-01-04-T11:34:11Pacific Standard Time Burn: 1h9GvFNK3Ccn2Au8C8BHPeaUamQgArvg
K burned 1.0 BTC for 1465.36363636 XCP (a301bbca\u2026b3f6bb35)
2014-01-04-T11:34:11Pacific Standard Time Block: 278692
2014-01-04-T11:34:11Pacific Standard Time Block: 278693
2014-01-04-T11:34:11Pacific Standard Time Block: 278694
2014-01-04-T11:34:11Pacific Standard Time Block: 278695
2014-01-04-T11:34:11Pacific Standard Time Block: 278696
2014-01-04-T11:34:11Pacific Standard Time Block: 278697
2014-01-04-T11:34:11Pacific Standard Time Burn: 12bsGWBQneVK5M8LqrtonubHeKWRj3gZ
2J burned 0.9999 BTC for 1464.6717 XCP (275b9570\u2026196f8934)
2014-01-04-T11:34:11Pacific Standard Time Block: 278698

With that bitcoin.conf configuration, your bitcoin server listens on port 8332. Worse case, edit bitcoind.conf, and add the following lines:


So given that, that you are not running on testnet, your counterpartyd.conf is configured to listen on the wrong port. With your specified bitcoin.conf file, "rpc-port" in counterpartyd.conf should be "rpc-port=8332", NOT "rpc-port=18832".

Please make those changes, restart both bitcoind/bitcoin-qt and counterpartyd, and let us know if that fixes it.

konfet: Your issue is probably pretty similar to this. Please verify these port numbers, as well as verifying that your bitcoind/bitcoin-qt is actually running, and listening (you can open up a DOS window and run "netstat -an" then search through the list of ports...see if you see those bitcoind ports.

If we shift the launch period, what about the people who have already contributed? What does that say about fairness, as well as the trust that the community has in the Counterparty team to not shift any requirements, unless absolutely necessary (e.g. major security bug, or some other totally blocking issue), AND, if done, do so in a way that preserves existing stakeholders. Shifting the window would be a major fail on both of those fronts.

The fact is, you guys are not losing out, so don't worry. We are barely three days out from launch, and the bonus is still quite close to the 1500 mark. Also, there now exists a way to burn coins without requiring counterpartyd or any extra software, and documentation is available for burning via blockchain.info (which anyone can do). For instructions on that, see: http://counterpartyd-build.readthedocs.org/en/latest/HowToBurn.html#without-using-counterpartyd

If you are uncomfortable doing any of that, we have a well known and trusted member that will be buying and escrowing XCP on others behalf. I'd rather he announce it when he's ready, but it should be in a day or two.

Regarding the Mac wallet, I will try to make that a priority this week, but given that you can burn without a wallet/counterpartyd (or will soon be able to have someone burn for you), it is much less of an issue, IMO.

Leo: I will respond to your issue shortly (I think I know the problem now, it's an easy one). The build system was working, but we had an unexpected backend library dependency release that broke it. I have modified it to be fixed to a specific version so that shouldn't happen again. This was all done within a day of it being discovered. We are doing our best to be responsive to the community and trying to give everyone a fair chance.

Looking through the posts  .. it looks like quite a number of viewers here are only interested in speculating on XCP with little to no inclination as to how the protocol/client actually works. Well I guess seeing that this is the "Alternate currencies" subforum it is to be expected  

At the moment in order to burn XCP you will effectively need to have full control of the address (private key). Yet, many are willing to place this trust with a 3rd party to burn BTC for XCP on behalf of them .....   And without the ability to send the coins to another address this would mean someone else would have control of your coins for an unforeseeable time (seeing that the latest statment from eligius is that they are not going to process the txns)

-imho-

from win64 installer. Bitcoin is started in test network.
also tired of writing about errors and do not receive a feedback

Fixed

Don't you think it's a bit rush to launch the coin ? mac wallet not ready/ most ppl don't have txindex=1 and having to reindex and it may take a few days/ etc, creating the situation to have somebody to burn on behalf of somebody. It sounds like an unfair launch.

How about shifting the launch period for another 7 days, make sure everything is ready, ppl who already burnt the coin will get the reward as if it's burnt in the first day.

+1
Add me to the purchase list as well.

Can you add me to the list for purchasing XCP (I can't do it myself) - or if anyone trusted is willing to walk me through it, I'd be willing to compensate. Thanks!

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?

@PhantomPhreak - Very cool to see you got this project up and running.

I've got the client working on Windows. Although I did have to work around a number of install errors, I don't have logs, but I think they've been aforementioned.

Still couldnt getting run.py to work properly so I am now trying the beta installer, but once again I get an error:


C:\Users\Leo>"C:\Program Files\counterpartyd\counterpartyd.exe"


Could not connect to Bitcoind. Sleeping for five seconds. (Try 0/12)

Bitcoin.conf
rpcuser=rpc
rpcpassword=XXXX
server=1
daemon=1
txindex=1

Counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=18832
rpc-user=rpc
rpc-password=XXXX

Tried port 18832 and 8332, same error. I'm getting really close to just giving up

Ah well, continue burning your coins on this ridiculousness.  I tried.

-wk

DAFUQ ><
I tried:
sudo apt-get install bitcoin-qt
It worked, but it's in German...
Any link to compile bitcoin-qt from source, in English? I haven't found yet.

edit: this do the trick:
Or what is the command line in bitcoind/counterpartyd to list the address in my wallet?
(I guess I have to update counterpartyd for wallet to work)

Sorry to see you've not received any contributions yet.  Your project looks great.  Keep up the great work.  I will be watching it closely.

I'd like to see an example or tutorial on how to setup a feed on the test net, just so I can play around with it and contribute some bug fixes.

May I ask... What specifically/technically is not possible right now, and why?