Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 607. (Read 1276933 times)
January 17, 2014, 10:44:31 PM
@Buybitcoinscanada Thank you for your support! I think maybe it was not clear to investors that burned BTC is not usable by the developers. Not sure, but in any case we need to get these guys some more beer !! LOL
January 17, 2014, 10:40:57 PM
Interesting concept - is there any update on approximately when the last day for burning will be?
I get (as of now):
(283810-281072) * 9.66 minutes from now (24-hour block time according to blockchain.info):
6:28:55 am CST | Wednesday, February 5, 2014
January 17, 2014, 10:19:12 PM
Interesting concept - is there any update on approximately when the last day for burning will be?
January 17, 2014, 10:16:45 PM
I'm not quite sure how someone can say that people trying to buy more than 1 BTC worth of XCP are greedy. Someone needs to check the definition of greed. 
January 17, 2014, 09:55:18 PM
Got Python 3.2 and hopefully everything installed, let's see how this goes.
Thanks xnova and all the other devs for their recent work and long hours on this.
Note I think the module is appdirs and not appsdirs. Took an error message to get the right one. (Everything except apsw is available by PIP, btw).
Thanks xnova and all the other devs for their recent work and long hours on this.
Note I think the module is appdirs and not appsdirs. Took an error message to get the right one. (Everything except apsw is available by PIP, btw).
January 17, 2014, 09:51:05 PM
The Counterparty team is pleased to announce the beta availability of the counterpartyd API.
The API will enable applications to be developed around Counterparty and counterpartyd.
Please read the API documentation here: http://counterpartyd-build.readthedocs.org/en/latest/API.html
It's not 100% complete yet, but it covers the various functions and objects returned, as well as giving you an idea of how to get started with coding applications that work against the API.
Please report any bugs with the documentation or API itself via the forums, or via the appropriate github bug tracker. Pull requests for fixes or additional functionality are more than welcome!
The API will enable applications to be developed around Counterparty and counterpartyd.
Please read the API documentation here: http://counterpartyd-build.readthedocs.org/en/latest/API.html
It's not 100% complete yet, but it covers the various functions and objects returned, as well as giving you an idea of how to get started with coding applications that work against the API.
Please report any bugs with the documentation or API itself via the forums, or via the appropriate github bug tracker. Pull requests for fixes or additional functionality are more than welcome!
January 17, 2014, 09:48:03 PM
When blockscan will be fixed? It show just till 280980 block...
Hi
Ok. I've managed to build the latest release and we are back up again.
On a side note, I am also working on some new features not available in other block explorers and should have this up soon
PS: Thank you xnova
Cheers
January 17, 2014, 09:34:39 PM
When blockscan will be fixed? It show just till 280980 block...
mtbitcoin and I are working through these issues currently. Hopefully Soon™.
EDIT: Looks like it's back up.
January 17, 2014, 09:17:53 PM
When blockscan will be fixed? It show just till 280980 block...
January 17, 2014, 09:15:37 PM
Your welcome XNOVA, I'll send more when I can! I hope we can enlist the whole community to keep donations flowing your way!
January 17, 2014, 09:09:40 PM
I want to send an XCP donation to PhantomPhreak, but don't understand how to... sigh.
EDIT: Just sent 0.15 BTC Donation to the project
Come on guys show your love for the project! These guys are working hard on the future of crypto!
EDIT: Just sent 0.15 BTC Donation to the project
Come on guys show your love for the project! These guys are working hard on the future of crypto!
Thank you, much appreciated!!
January 17, 2014, 09:08:02 PM
Ok guys, the build system should work again under Windows and Ubuntu 12.04. Pull the latest from github and let me know if you run into any more issues.
Still no updated installer for Win64 (ran into a new cx_freeze build issue with that that I'll check out tomorrow).
Still no updated installer for Win64 (ran into a new cx_freeze build issue with that that I'll check out tomorrow).
No go under windows for both python 3.2 and 3.3. Has anyone actually got these to work on windows?
--------------------
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\_cprequest.py", line 656, in respond
response.body = self.handler()
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\lib\encoding.py", line 188, in __call__
self.body = self.oldhandler(*args, **kwargs)
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\lib\jsontools.py", line 61, in json_handler
value = cherrypy.serving.request._json_inner_handler(*args, **kwargs)
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\_cpdispatch.py", line 34, in __call__
return self.callable(*self.args, **self.kwargs)
File "C:\counterpartyd_build\dist\counterpartyd\lib\api.py", line 235, in index
data = cherrypy.request.body.read().decode('utf-8')
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\_cpreqbody.py", line 455, in read
return self.fp.read(size, fp_out)
ypeError: read() takes at most 2 positional arguments (3 given)
....
Traceback (most recent call last):
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 625, in
blocks.follow(db)
File "C:\counterpartyd_build\dist\counterpartyd\lib\blocks.py", line 453, in follow
block_count = bitcoin.rpc('getblockcount', [])
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 60, in rpc
response_json = response.json()
File "C:\counterpartyd_build\env\lib\site-packages\requests\models.py", line 733, in json
return json.loads(self.text, **kwargs)
File "C:\Python32\Lib\json\__init__.py", line 319, in loads
return _default_decoder.decode(s)
File "C:\Python32\Lib\json\decoder.py", line 353, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Python32\Lib\json\decoder.py", line 371, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
I just updated the documentation and modified my original post saying the build system was ready to state:
For Windows, please re-follow the build from source Prerequisites instructions here: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#on-windows
(you will need to download Python3.2, and all of those dependencies listed for it)
I am successfully running counterpartyd on Win 7 64 bit, and making API calls to it.
If you are using the API and getting that error, make sure your API destination has an ending slash on it (e.g. "http://localhost:4000/jsonrpc/").
Let me know if after doing all of this you are still having an issue and we can work through it.
January 17, 2014, 08:48:33 PM
I want to send an XCP donation to PhantomPhreak, but don't understand how to... sigh.
EDIT: Just sent 0.15 BTC Donation to the project
Come on guys show your love for the project! These guys are working hard on the future of crypto!
EDIT: Just sent 0.15 BTC Donation to the project
Come on guys show your love for the project! These guys are working hard on the future of crypto!
January 17, 2014, 08:26:47 PM
Ok guys, the build system should work again under Windows and Ubuntu 12.04. Pull the latest from github and let me know if you run into any more issues.
Still no updated installer for Win64 (ran into a new cx_freeze build issue with that that I'll check out tomorrow).
Still no updated installer for Win64 (ran into a new cx_freeze build issue with that that I'll check out tomorrow).
No go under windows for both python 3.2 and 3.3. Has anyone actually got these to work on windows?
--------------------
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\_cprequest.py", line 656, in respond
response.body = self.handler()
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\lib\encoding.py", line 188, in __call__
self.body = self.oldhandler(*args, **kwargs)
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\lib\jsontools.py", line 61, in json_handler
value = cherrypy.serving.request._json_inner_handler(*args, **kwargs)
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\_cpdispatch.py", line 34, in __call__
return self.callable(*self.args, **self.kwargs)
File "C:\counterpartyd_build\dist\counterpartyd\lib\api.py", line 235, in index
data = cherrypy.request.body.read().decode('utf-8')
File "C:\counterpartyd_build\env\lib\site-packages\cherrypy\_cpreqbody.py", line 455, in read
return self.fp.read(size, fp_out)
ypeError: read() takes at most 2 positional arguments (3 given)
....
Traceback (most recent call last):
File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 625, in
blocks.follow(db)
File "C:\counterpartyd_build\dist\counterpartyd\lib\blocks.py", line 453, in follow
block_count = bitcoin.rpc('getblockcount', [])
File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 60, in rpc
response_json = response.json()
File "C:\counterpartyd_build\env\lib\site-packages\requests\models.py", line 733, in json
return json.loads(self.text, **kwargs)
File "C:\Python32\Lib\json\__init__.py", line 319, in loads
return _default_decoder.decode(s)
File "C:\Python32\Lib\json\decoder.py", line 353, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Python32\Lib\json\decoder.py", line 371, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
January 17, 2014, 08:08:19 PM
About the future value of XCP: could you just realize that nobody has a clue, please.
Anybody saying that he know is just trolling. Up or Down, same same.
Indeed an instant x100 is very unlikely.
We may even suffer a relative lost during the first week/month after-burn.
Yet MSC is valued at 60 million.
XCP despite it's alpha-stage and few bug has already more presently working functionality than it's concurrent.
Both may succeed, both may crash, one may succeed better than the other.
But if MSC is valued at 60 millions, theoretically there is nothing preventing XCP to reach 30/60/120 millions.
Just don't expect such valuation too fast.
It could happen in 4~6 month, it could happen in 1 month, or it could never happen.
Just as BTC itself could lose most of it's value if a really amazing innovation appear in 6 month.
I personally plan to hold my XCP a few month, and will not sell them at loses.
If I must way 6 month for that, then 6 month it will be.
Middle term I hope a very nice ROI, but it's gambling.
Are we done?
If a troller come trying to lower XCP credibility without quality argument, just ignore him.
Don't feed the troll.
Everyone can think for him/herself.
If you guys can't resist talking about that, open a dedicated topic for speculation.
Most here are not interested in the "tiny war" between metacoin.
Let's keep focusing on XCP testing and improvement in all field.
Obvious reminder:
Don't invest more than you can afford to lose.
Anybody saying that he know is just trolling. Up or Down, same same.
Indeed an instant x100 is very unlikely.
We may even suffer a relative lost during the first week/month after-burn.
Yet MSC is valued at 60 million.
XCP despite it's alpha-stage and few bug has already more presently working functionality than it's concurrent.
Both may succeed, both may crash, one may succeed better than the other.
But if MSC is valued at 60 millions, theoretically there is nothing preventing XCP to reach 30/60/120 millions.
Just don't expect such valuation too fast.
It could happen in 4~6 month, it could happen in 1 month, or it could never happen.
Just as BTC itself could lose most of it's value if a really amazing innovation appear in 6 month.
I personally plan to hold my XCP a few month, and will not sell them at loses.
If I must way 6 month for that, then 6 month it will be.
Middle term I hope a very nice ROI, but it's gambling.
Are we done?
If a troller come trying to lower XCP credibility without quality argument, just ignore him.
Don't feed the troll.
Everyone can think for him/herself.
If you guys can't resist talking about that, open a dedicated topic for speculation.
Most here are not interested in the "tiny war" between metacoin.
Let's keep focusing on XCP testing and improvement in all field.
Obvious reminder:
Don't invest more than you can afford to lose.
Hope everyone who have invest to making fast money have also remember make small donations for XCP project...
Developers: PhantomPhreak, xnova (Bitcointalk usernames)
BTC and XCP donations: 12J1YFvsWHDCU5HNAWNLNy1Q9nZo8Q4Xgs
If donate to quoted post, remember look address is right from first orginal post
January 17, 2014, 07:33:57 PM
Agree!!!:
More people burn now means less chance to get more than 10x return like Mastercoin in short time.
Those kind of return (10x -> 1000x) requires that people highly suspect it in the beginning and then later found it real and useful. The extreme case is Nxt. Almost no one trusted it in the IPO stage (they got 21 BTC only), and then when the client came out and it worked, the price shot up because the demand suddenly increases but most chips are controlled in the hand of a few people and it's quite easy for they to hold and see the price up to the sky.
For XCP, 1) people are already quite familiar with the idea due to MSC; 2) the 'Prove by Burn' removes the trust issue; 3) the client is working and we can see the source code, so you can see that there're already 1200 BTC burnt in less than half a month. The situation, however, is almost the same after the IPO. Most of people want to buy will burn now anyway. For the demand from those new comers, the supply (from those want quick profit of 30-40%) will be enough to keep the low price.
Therefore, no reason to expect the price could rise significantly without any big news (e.g. a beautiful and user friendly client; a famous asset such as AM moves in; or a lot of bets like those in bitbet are available).
More people burn now means less chance to get more than 10x return like Mastercoin in short time.
Those kind of return (10x -> 1000x) requires that people highly suspect it in the beginning and then later found it real and useful. The extreme case is Nxt. Almost no one trusted it in the IPO stage (they got 21 BTC only), and then when the client came out and it worked, the price shot up because the demand suddenly increases but most chips are controlled in the hand of a few people and it's quite easy for they to hold and see the price up to the sky.
For XCP, 1) people are already quite familiar with the idea due to MSC; 2) the 'Prove by Burn' removes the trust issue; 3) the client is working and we can see the source code, so you can see that there're already 1200 BTC burnt in less than half a month. The situation, however, is almost the same after the IPO. Most of people want to buy will burn now anyway. For the demand from those new comers, the supply (from those want quick profit of 30-40%) will be enough to keep the low price.
Therefore, no reason to expect the price could rise significantly without any big news (e.g. a beautiful and user friendly client; a famous asset such as AM moves in; or a lot of bets like those in bitbet are available).
There is already 60 times more Bitcoins invested in XCP than there was in Nxt. Considering that most people invest to make a quick profit : this is not gonna work !
The profit from the people that invested early in Nxt was about 50 times (like me). We may have 100 times more BTC invested in XCP.
People may loose money
Yes. The risk is becoming more as the burned coin increase. The new burner may have great risk now.
Every burners have lower stakes when new burners coming in. The only solution to keep the your percentage stake is to burn more. Since XCP functionality is very similar to mastercoin and it even has the codes compared to the vaporware in mastercoin, I don't see why XCP should not be valued at least half of Mastercoin market price.
Fair XCP market cap valuation should be at 1/2 mastercoin market cap which is at 60 million$ right now.
BTW: can anyone estimate how many days more until the burning is over ?
Even so, it also need much time (maybe 2-3years)to get the market cap since so many XCP coins have been created. Also donn't forget the possibility of failure of the XCP project.
Just mark the risk.
January 17, 2014, 07:19:19 PM
Ok guys, the build system should work again under Windows and Ubuntu 12.04. Pull the latest from github and let me know if you run into any more issues.
For Windows, please re-follow the build from source Prerequisites instructions here: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#on-windows
(you will need to download Python3.2, and all of those dependencies listed for it)
Still no updated installer for Win64 (ran into a new cx_freeze build issue with that that I'll check out tomorrow).
For Windows, please re-follow the build from source Prerequisites instructions here: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#on-windows
(you will need to download Python3.2, and all of those dependencies listed for it)
Still no updated installer for Win64 (ran into a new cx_freeze build issue with that that I'll check out tomorrow).
January 17, 2014, 05:37:37 PM
Sorry for the noob question - what does the tainted BTC burn means?
Blockchain.info has a nice "Taint analysis" tool. It shows which sending addresses can be traced back to another address:
https://blockchain.info/taint/1CounterpartyXXXXXXXXXXXXXXXUWLpVr
January 17, 2014, 05:13:19 PM
Sorry for the noob question - what does the tainted BTC burn means?
it looks at the correlation of the btc in 2 addresses coming from one address in a previous time period.
the goal of this project was to limit 1 btc per burn, the intention being that this would allow for an even distribution.
but of course some people get greedy and want more, so they split up their btc to different addresses and burn them... using the taint tool on blockchain you can put in an addy and see the taint between that addy and another addy that is in the list of burns.
gotta love greed...
Cheers
Interesting that the 1 BTC limit was imposed to make it more spread out. Burning more is a bit counter productive anyway - the more coins in circulation, the less valuable they are.
January 17, 2014, 05:07:25 PM
Sorry for the noob question - what does the tainted BTC burn means?
it looks at the correlation of the btc in 2 addresses coming from one address in a previous time period.
the goal of this project was to limit 1 btc per burn, the intention being that this would allow for an even distribution.
but of course some people get greedy and want more, so they split up their btc to different addresses and burn them... using the taint tool on blockchain you can put in an addy and see the taint between that addy and another addy that is in the list of burns.
gotta love greed...
Jump to: