Author

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

full member
Activity: 216
Merit: 100
Only Mastercoin funding is centralized, protocol itself isn't centralized.

This isn't the place to discuss Mastercoin, but it may be worth pointing out an important difference here between Mastercoin's protocol and Counterparty's: every Mastercoin transaction has to have a small output to the Exodus Address (to which at least J.R. holds the private key). Counterparty has no such limitation.

EDIT: typo

Q1. I know you said this isn't the place to discuss MSC, but is the above true? Do you mean every future MSC transaction, (even once it's up & running) will have a small output to the Exodus address? That sucks.

Yes, it is true.

Q2. As much as I like your POB decentralisation and I really do. Maintaining & further developing something like this will require serious funding? No? We can't expect you guys to do all the work when you're getting the same risk/reward incentive as us. Even Protoshares are now issuing Angel shares as they need more direct funding. (Or maybe they're just scamming, we'll have to see if they actually release their delayed Keyhotee soon.)

While we do appreciate donations, it may be worth pointing out that Bitcoin's development was not predicated on outside funding, and Counterparty is: 1) much simpler and smaller project than Bitcoin, and 2) relatively full-featured.

Most open-source projects are community-driven, with software developers contributing not primarily for the financial incentives, but because they really believe in the project they are developing (Gavin Andresen, for example, worked on Bitcoin a long time before being hired full-time). I will certainly be investing in Counterparty, but this is because I think it is a great project with lots of potential, not because there is a lot of money in alt-coins at the moment.
sr. member
Activity: 476
Merit: 300
Counterparty Chief Scientist and Co-Founder
Have the instructions for how to burn on blockchain.info been posted yet?

No, not yet.
legendary
Activity: 1232
Merit: 1001
Can anyone help with this error I'm getting?

./counterpartyd.py server

I get.

Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long
legendary
Activity: 1138
Merit: 1001
Only Mastercoin funding is centralized, protocol itself isn't centralized.

This isn't the place to discuss Mastercoin, but it may be worth pointing out an important difference here between Mastercoin's protocol and Counterparty's: every Mastercoin transaction has to have a small output to the Exodus Address (to which at least J.R. holds the private key). Counterparty has no such limitation.

EDIT: typo

Q1. I know you said this isn't the place to discuss MSC, but is the above true? Do you mean every future MSC transaction, (even once it's up & running) will have a small output to the Exodus address? That sucks.

Q2. As much as I like your POB decentralisation and I really do. Maintaining & further developing something like this will require serious funding? No? We can't expect you guys to do all the work when you're getting the same risk/reward incentive as us. Even Protoshares are now issuing Angel shares as they need more direct funding. (Or maybe they're just scamming, we'll have to see if they actually release their delayed Keyhotee soon.)
sr. member
Activity: 462
Merit: 250
Very interested, after the success of NXT, this is the only 2nd gen crypto that doesn't scream scam to me.  But yeah, please come up with a simplified (ie. idiot proof) way to invest because I am scared I am going to screw something up and lose my BTC.
legendary
Activity: 1232
Merit: 1001
Have the instructions for how to burn on blockchain.info been posted yet?
legendary
Activity: 1138
Merit: 1001
Announcement: We made some changes to the protocol and the client: now burns don’t require the use of OP_RETURN, and we’re no longer pushing transactions through Eligius, which seems to now be rejecting anything with such an output. This means that 1) a bunch of bugs have been fixed, 2) the only Counterparty transaction that will work on mainnet until Bitcoind 0.9 comes out is a burn, 3) burns are much faster, and 4) it is theoretically possible for burns to be made with a regular Bitcoin client.

We’re not currently recommending that anyone use anything other than counterpartyd to burn. The format of a Counterparty transaction
is very specific, and we can’t guarantee that a transaction constructed by any other software will work (and if it doesn’t, you’ll lose your BTC).

For those interested, the protocol will recognise as a valid burn any transaction with the following characteristics:
  • All of the input addresses are identical.
  • The address of the first output is the unspendable address '1CounterpartyXXXXXXXXXXXXXXXUWLpVr' (mainnet) or 'mvCounterpartyXXXXXXXXXXXXXXW24Hef' (testnet).
  • The total number of BTC burned by the source address is less than or equal to 1.

Instructions on how to use a Blockchain.info wallet to construct a burn should be forthcoming. The burn functionality of counterpartyd will continue to work as it has been doing, and of course previous burns remain valid.

+1. That would be great if you could send BTC from a blockchain.info wallet and receive XCP.

& thanks for answering my previous questions.
legendary
Activity: 876
Merit: 1000
Etherscan.io
Actual problem is that you will not be able to send those XCP anywhere.
Because for this to work on the mainnet, Eligius need to process your transaction.
Which it stopped.

counterpartyd address ADDRESS
So that at least is still working, with burn.
(I have to test by myself instead of asking the question...
But I'm curious and soft/hardware troube prevent me to test right now.)
Can I check the amount of XCP in any address with this command? Including not mine.

Yes, you can  Smiley

Since everything is on the blockchain

Example output:


Balances
+-------+---------------+
| Asset |     Amount    |
+-------+---------------+
|  XCP  | 1479.70063636 |
+-------+---------------+
sr. member
Activity: 266
Merit: 250
Help and Love one another ♥
Actual problem is that you will not be able to send those XCP anywhere.
Because for this to work on the mainnet, Eligius need to process your transaction.
Which it stopped.

counterpartyd address ADDRESS
So that at least is still working, with burn.
(I have to test by myself instead of asking the question...
But I'm curious and soft/hardware troube prevent me to test right now.)
Can I check the amount of XCP in any address with this command? Including not mine.
full member
Activity: 221
Merit: 100
cool thx Smiley will wait for the first confirmation.
sr. member
Activity: 476
Merit: 300
Counterparty Chief Scientist and Co-Founder
I was able to burn btc sucessfully...The transactions are on the blockchain.

1)
How many confirmations should I wait for before the xcp shows up in my balance?

2)
whats the command to check the total number of xcp I have?


I'm invested. So very excited to support this project Smiley

Congratulations!

1) One confirmation. (That is, it just has to be in the blockchain.)

2) counterpartyd address ADDRESS
full member
Activity: 221
Merit: 100
I was able to burn btc sucessfully...The transactions are on the blockchain.

1)
How many confirmations should I wait for before the xcp shows up in my balance?

2)
whats the command to check the total number of xcp I have?


I'm invested. So very excited to support this project Smiley
legendary
Activity: 876
Merit: 1000
Etherscan.io
Luckily not.
Otherwise you could burn the coin of everyone you wish  Roll Eyes

Yeah. Makes sense now.. Wasn't thinking straight just now  Smiley

So to a burn for a 3rd party one would need to burn the coins for Xcp and transfer the Xcp over to the btc address?
sr. member
Activity: 266
Merit: 250
Help and Love one another ♥
Luckily not.
Otherwise you could burn the coin of everyone you wish  Roll Eyes
legendary
Activity: 876
Merit: 1000
Etherscan.io
Any ideas as to what would this imply?


----
C:\counterpartyd_build\dist\counterpartyd>counterpartyd.py --rpc-user=rpc --rpc-password=XXXXXX  -
v market
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 407, in
    util.database_check(db)
  File "C:\counterpartyd_build\dist\counterpartyd\lib\util.py", line 36, in database_check
    raise exceptions.DatabaseError('Countparty database is behind Bitcoind.')
lib.exceptions.DatabaseError: Countparty database is behind Bitcoind.

Are you running counterpartyd server in the background? (I just changed the error message to ask that question itself.)  What block is it on?

Yup. Fixed this. Thanks. I can confirm that the windows installation is indeed working


Regarding the burn process. Can we burn on behalf of another address not within our control (which we don't own the private keys). Lets say I want to burn BTC for XCP on behalf of a friend, can I just use his BTC address as the source in the "from" command line?


sr. member
Activity: 476
Merit: 300
Counterparty Chief Scientist and Co-Founder
'losing money today, and having problem with my laptop *laugh
Yesterday was better.

Joke appart, how is it that it works on testnet?
Everyone testing with pre-v0.9?
(I never used a testnet, is there a whole blockchain-to-DL-again only for it?)

testnet just accepts non-standard transactions. (Any transaction with an OP_RETURN output is, before 0.9, non-standard.) There's a separate blockchain, but it's only about 500 MB.
sr. member
Activity: 476
Merit: 300
Counterparty Chief Scientist and Co-Founder
Any ideas as to what would this imply?


----
C:\counterpartyd_build\dist\counterpartyd>counterpartyd.py --rpc-user=rpc --rpc-password=XXXXXX  -
v market
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 407, in
    util.database_check(db)
  File "C:\counterpartyd_build\dist\counterpartyd\lib\util.py", line 36, in database_check
    raise exceptions.DatabaseError('Countparty database is behind Bitcoind.')
lib.exceptions.DatabaseError: Countparty database is behind Bitcoind.

Are you running counterpartyd server in the background? (I just changed the error message to ask that question itself.)  What block is it on?
sr. member
Activity: 266
Merit: 250
Help and Love one another ♥
'losing money today, and having problem with my laptop *laugh
Yesterday was better.

Joke appart, how is it that it works on testnet?
Everyone testing with pre-v0.9?
(I never used a testnet, is there a whole blockchain-to-DL-again only for it?)
sr. member
Activity: 476
Merit: 300
Counterparty Chief Scientist and Co-Founder
Okay
A little of turbulence.

I'm not convince I like this last change announcement.
When things are say to be done like that-way from tx to ty, I like it to stay that way.

Main problem I see is that before: a fully working counterpartyd was available for testing.
Now only the burning...
Meaning I have to trust you for the working of the descentralized exchange.
Also might mean that I cannot transfer my XCP, does send still work?
Very bad if ONLY burn work...

How comes that Eligius was the only pool to treat OP_RETURN?
Do you have any influence there? contact?
This suddent change make me uncomfortable with your project.
Also, is it 100% sure OP_RETURN will be in the v0.9?
For my research it appear to be likely, but 100% sure?

Please try to solve the situation with Eligius.
Need the ability to test.

You can still use all of Counterparty's functions on testnet. It's just that right now no one is mining transactions with OP_RETURN on mainnet.

We are trying to talk to the operator of Eligius and find out what changed. It's possible that he just updated the version of Bitcoind that he was running and hasn't yet patched it again. His PHP form, which was working for me for a whole month, just suddenly started rejecting our transactions. Eligius does a few things that other pools don't do, for example rate-limiting address reuse.

We are as sure as we could possibly be that OP_RETURN will be in 0.9. See Gavin's announcement. Furthermore, I recently contacted Gavin myself, mentioned that we were going to be using OP_RETURN and asked when he thought that 0.9 would be released: there should be a release candidate out in only a couple of weeks (TM).
sr. member
Activity: 266
Merit: 250
Help and Love one another ♥
Okay
A little of turbulence.

I'm not convince I like this last change announcement.
When things are say to be done like that-way from tx to ty, I like it to stay that way.

Main problem I see is that before: a fully working counterpartyd was available for testing.
Now only the burning...
Meaning I have to trust you for the working of the descentralized exchange.
Also might mean that I cannot transfer my XCP, does send still work?
Very bad if ONLY burn work...

How comes that Eligius was the only pool to treat OP_RETURN?
Do you have any influence there? contact?
This suddent change make me uncomfortable with your project.
Also, is it 100% sure OP_RETURN will be in the v0.9?
For my research it appear to be likely, but 100% sure?

Please try to solve the situation with Eligius.
Need the ability to test.


edit: WORST: if this problem with Eligius happen globally after v0.9 is out, your project is dead, burned coin lost... Knowing what went/is going wrong with Eligius is very important.
Jump to: