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

I would also like to do the same. I am a windows user - but have not free space for QT (old pc). Is there a way to send bitcoins to you?

The address command doesn't show BTC balances. (Bitcoind won't provide them for arbitrary addresses!)

I'd like to do the same, being a Mac user as well. 
Thx in advance.

I still need help with the error I'm getting when running setup.py

What a success!
Went from 2BTC to 26BTC burned in a few hours. (might be mostly the dev)
I'm betting your project will pass the 100BTC without trouble.
But 'might stay under 1000BTC.
We will see.

So for the very first we finally have the wonder of a descentralized exchange, and you want to stick to centralized one's with all their risk and problem?
As I understood, they dev have API developpement priority in mind to allow this.
I don't see it as necessary as we have the descentralized one.
But more possibilities never hurt, it's true.
(No idea what API is -.-  but I understand what it allow, basically.)

With the addition of incompatible protocols, I would like to add:
Fair & quality lunch matters to me.
The greed or anarcho-communist approach mind too.

Take ripple: over 90% are own by the dev and they wish me to swallow that it is worth 3 billions$? Nice try, but no.

Take Mastercoin:
As they wrote themselve in their doc:
"Mastercoin isn't communism. It is an endevours that rewards early investors, like Bitcoin, or like any startup."
Well, that is not the kind of idea I wish to support. I deal with (anarcho-)capitalism because my choice is low.
If there is a better alternative, I switch directly.
might be very hard to reach, but XCP approach is good enough to me to let me think "anarcho-communist fair-wannabe".
Even if the dev didn't had these words in mind, I wish to support their quality approach.
The way they do it show they are not greedy, I wish to support dev who reflect that.

Also about MSC, the dev were able to create as much as they wanted for themselves, as they just had to send their money to themself in a hidden way to get MSC.
On top of that, they "premined" or "stole 10%" of every investor by creating an additional 1devMSC per 10MSC created.
Make these dev a team of 50 people with a billion $, I still wanna stay away from them.
Kickstarter-not-needed, blablabla. I don't like their style. I'm out.
The individual has power.
Use your power wisely.


PS: nslx, are you a private betatester linked/friend with the 2 main dev?
Or maybe part of their contacts with Eligius pool?
Let us know when the matter is resolved.
I still need a few hours to sync before testing.

If this helps...

Would this have anything to do with an incorrect install of configParser. This was the only module that I was unable to correctly install on windoze box

'----
Traceback (most recent call last):
  File "C:\Install\configparser-3.3.0r2\setup.py", line 12, in
    from setuptools import setup, find_packages
  File "", line 1565, in _find_and_load
  File "", line 1532, in _find_and_load_unlocked
  File "C:\Python33\lib\site-packages\setuptools-1.4.1-py3.3.egg\setuptools\__init__.py", line 5, i
 
  File "C:\Python33\lib\distutils\core.py", line 19, in
    from distutils.config import PyPIRCCommand
  File "C:\Python33\lib\distutils\config.py", line 7, in
    from configparser import ConfigParser
  File "C:\Install\configparser-3.3.0r2\configparser.py", line 397
    _KEYCRE = re.compile(ur"%\(([^)]+)\)s")
                                         ^
SyntaxError: invalid syntax

FLUX built on Link built on any coin is looking to do this as well. Only for abstract trades and barter schemes as well.

We'll be glad to share ideas.

Relevant threads:
LINK:
http://forum.feathercoin.com/index.php/topic,5558.0.html
http://forum.feathercoin.com/index.php/topic,6518.0.html

FLUX:
http://forum.feathercoin.com/index.php/topic,6185.0.html
http://forum.feathercoin.com/index.php/topic,6407.0.html
http://forum.feathercoin.com/index.php/topic,6552.0.html

I am running into the similiar issues on Windows (64bit)

"...Installing setuptools, pip...done.
Traceback (most recent call last):
  File "C:\Python33\Scripts\virtualenv-script.py", line 9, in
    load_entry_point('virtualenv==1.11', 'console_scripts', 'virtualenv')()"


Has anyone actually got this to run correctly on a windows box?

Cheers

Here is the pastebin with my full command prompt. I followed the instructions to the letter from http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html

Windows 7 64 bit
http://pastebin.com/iSTJ1uNk

Cool keep me posted...cant wait to burn some btc


will keep you posted once I successfully complete my first burn...

@Folks who have this running.
I'd like to burn BTC for some XCP, but can't burn the time to rig the environment for this.  If you can escrow for me, I can give you up to the difference in XCP of the early reward for time and the end of month reward.  January is fairly well slotted with other project commitments.
Please PM with your successful burn transactions.


Or that.

reader31: I did try to reproduce your issue and got the same result as you (which is odd because it was working fine earlier in the day, as evidenced by the burn transactions processed and our own testing).

We are taking this up with the Eligius folks and will have this issue resolved ASAP. The good news is that once it is resolved, you should be able to burn BTC successfully, as it appears your setup has been completed.

We are also in talks with some known and trusted 3rd party members of the forums to see if they are willing to perform an XCP escrow/purchase service for folks that don't want to or can't directly use counterpartyd to burn BTC. We will keep you all updated as this develops.

If the burn is successful, counterpartyd will print back something like this:

As it failed, don't worry, no funds will be lost...either the transaction is successfully read and processed by Eligius or it is not.

Please make sure you have the newest version of the source from git (cd into the counterpartyd directory and run "git pull origin master", and you can verify with "git log").

If your code is current, then the problem is most likely on the Eligius side (which from the error message, it appears to be). You may want to try it again a bit later, or, try a higher amount (e.g. 0.05).

1)

I reinstalled/rebuilt counterpartyd from your fresh code. Now when I run


I get the following error message,


2)
Additionally, when I tried to run the following command,

counterpartyd --rpc-password=rpcpw1234 address 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc

to check my address balance, I got this following output,


Is this expected or should I be seeing my btc balance in my account 1CrmTo7Rtk6keeBHbN93B3tAMCm31sG5Tc in the above display(I have 0.011 btc balance in this address)?


Thx.

The following link can be visited to see up to date burn activity for Counterparty: https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr

Note that since the burn blocks are being processed by only one pool at this time (Eligius), investments spanning an hour or two will tend to be "grouped" within single blocks.

I will be releasing a Windows installer for counterpartyd this weekend.

1. Yes, that is correct.

2. All you need to do right now is run Bitcoind/Bitcoin-Qt, have BTC in your wallet, download the Counterparty client, and do a counterpartyd burn.

3. Yep.

4. There's nothing inherent to the 'protocol layer' design of Counterparty (or MSC for that matter) that makes it hard to use on exchanges like those, as far as I know. Rather, all we need is a JSON-API like what Bitcoind has, and it is one of our priorities to develop one. Moreover, after the burn period (or today, if you like) you can buy XCP with BTC on Counterparty's operating decentralised exchange.

5. Well, for one, they'd have a lot of trouble preserving the balances of the addresses of current MSC and Protoshares holders. The protocols are not compatible.

Sorry some really low level questions,

1. If you wait till the end of the month/issuance period will you still get at least 1000 XCP per BTC? (I.e the advantage of burning now is mainly that you will get up to 1500 XCP per BTC?)

2. Will there be a really simple, idiot proof way to purchase XCP before the end of the issuance period? (I.e send BTC to this address from a client... or download this counterparty wallet send BTC to an address there, then from Counterparty wallet BTC address send to burn address. Yes I'm an idiot.)

3. Will the total amount of XCP issued  be 'total amount of BTC sent to burn address in issuance period multiplied by 1000-1500'?

4. As it sits on top of BTC will it be difficult to trade/speculate with it on exchanges like Crypsty/BTC-E before it takes off. 
I.e. people will have to buy XCP on a specialised MSC type decentralised exchange after the issuance period.

5. Can a competitor Mastercoin/Bitshares say "hmm. You guys are geniuses, nice code! Thanks! Saves us some work!"
"Hi Bitshares/MSC here, we're releasing the counterparty code, as smart as those guys are,  we have a full time team/company set up already of 5-10 key people and a few million $ in development funding to support it now, so come on over, the water's warm! "

If you can answer any of those it will be appreciated, thanks!

There are two devs working on the project, myself and xnova. Good night!

Just for more clarity: how many dev is there to this project? 2, 3, more?
I'd like a list of the usernames.
- PhantomPhreak
- xnova
- ?

'have to sleep once in a while
Good night everybody.
Best of luck to this project.

What version of Windows? Also, can you please post the full traceback on pastebin.com and give me the link (or, you can file a bug report at https://github.com/xnova/counterpartyd_build/issues)

Actually, putting all of the output from the run of setup.py on pastebin.com would be most helpful.