Author

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

sr. member
Activity: 262
Merit: 250
I like what I have read about counterparty and my sixth sense is that it is more legit than competitors. However, I am not technical minded at all.

Could someone please explain the difference between counterparty and some of the other cryptos purporting to do the same thing, like mastercoin, namecoin, ethereum etc?

thank you

Functionality-wise, Counterparty has the most features live and available right now. It is also important to note that Counterparty can trade directly against BTC on the Counterparty decentralized exchange - something others cannot do.

The major difference and in my mind though is that Counterparty is developed under the same principles as Satoshi. The platform was developed for the people to use and *never* was there and will there be some IPO that favours and enrichens the developers. The developers of the platform had to buy in exactly the same way in which everyone else during the proof of burn period.

All other platforms either:

* Have an extremely small number of large holders, or
* Have a 'social contract' to 'richly reward early adopters, or
* Have raised funds in a commercial fashion,

Counterparty is built by the people for the people.
full member
Activity: 216
Merit: 100
Please allow xcp in swarm IPO  Smiley

I think this is a good suggestion. You are using the counterparty infrastructure, why wouldn't you allow the token to be used as well?

I think it's a great suggestion as well. In fact we already set up an XCP -> SWARM vending machine just as we currently have a BTC -> SWARM vending machine.

Problem is we didn't want to turn it on without testing it thoroughly and I haven't had the time.

We also want to integrate it into the feed on www.swarmcorp.com so that you can see both incoming BTC and XCP.

Hopefully I will have time this weekend to make sure everything is working fine and then we will start accepting XCP as well.

Please don't do anything silly like create a fixed exchange rate between BTC and XCP.  Look to the Maidsafecoin debacle to see where that gets you. 

IMO, it's really better to just do one or the other.  It would have been better to go with XCP in the first place, but now that BTC is already announced, better to stick with it.

I do agree with the fixed rate point, was thinking about this as well. As you mention it was a disaster for both maidsafe and mastercoin.

Couldn't you take the coinmarketcap price at the time the XCP is sent? Or is this too difficult to implement?

The peg with Mastercoin in the Maidsafe crowdfund wasn't the problem, in itself. It was, rather, the fact that Mastercoin was pegged to a value well above its market price.
full member
Activity: 155
Merit: 100
I like what I have read about counterparty and my sixth sense is that it is more legit than competitors. However, I am not technical minded at all.

Could someone please explain the difference between counterparty and some of the other cryptos purporting to do the same thing, like mastercoin, namecoin, ethereum etc?

thank you

hero member
Activity: 700
Merit: 500
Please allow xcp in swarm IPO  Smiley

I think this is a good suggestion. You are using the counterparty infrastructure, why wouldn't you allow the token to be used as well?

I think it's a great suggestion as well. In fact we already set up an XCP -> SWARM vending machine just as we currently have a BTC -> SWARM vending machine.

Problem is we didn't want to turn it on without testing it thoroughly and I haven't had the time.

We also want to integrate it into the feed on www.swarmcorp.com so that you can see both incoming BTC and XCP.

Hopefully I will have time this weekend to make sure everything is working fine and then we will start accepting XCP as well.

Please don't do anything silly like create a fixed exchange rate between BTC and XCP.  Look to the Maidsafecoin debacle to see where that gets you. 

IMO, it's really better to just do one or the other.  It would have been better to go with XCP in the first place, but now that BTC is already announced, better to stick with it.
sr. member
Activity: 262
Merit: 250
We'll be at several conferences this summer. Check out the full list here:

https://www.counterparty.co/counterparty-coming-to-a-conference-near-you/

If you're going to any of these, please reach out. We'd love to meet you.

I (Jeremy) will be speaking about crowdfunding with Counterparty and Vennd at Cryptocon Sydney. Cryptocon Sydney runs on the 24th and 25th July. The schedule hasn't been updated yet but it is confirmed with the conference producer.

Both myself and Jonathan will be there. Seek us out and ask all the questions you might have!

http://www.cryptocon.net/
sr. member
Activity: 309
Merit: 250
Swarm
Please allow xcp in swarm IPO  Smiley

I think this is a good suggestion. You are using the counterparty infrastructure, why wouldn't you allow the token to be used as well?

I think it's a great suggestion as well. In fact we already set up an XCP -> SWARM vending machine just as we currently have a BTC -> SWARM vending machine.

Problem is we didn't want to turn it on without testing it thoroughly and I haven't had the time.

We also want to integrate it into the feed on www.swarmcorp.com so that you can see both incoming BTC and XCP.

Hopefully I will have time this weekend to make sure everything is working fine and then we will start accepting XCP as well.
hero member
Activity: 728
Merit: 500
Activity: yes
Please allow xcp in swarm IPO  Smiley

I think this is a good suggestion. You are using the counterparty infrastructure, why wouldn't you allow the token to be used as well?

A company raising an early round of financing probably wants the most liquid currency available so that they can start spending the money. What if swarm took in a high percentage of XCP and then wanted to liquidate 25,000 or so XCP in order to pay for various business expenses?

Fair point and I understand why they would prefer a more liquid token but consider this situation. I have most of my crypto assets in XCP. I want to buy into swarm so I am doing the same thing, moving XCP to the DEX or other exchanges, selling it for BTC and then using that to subscribe for swarm.

I may have missed it in the posts but does swarm benefit XCP other than bringing it some attention via this fundraiser? Please don’t misunderstand me; I like the idea, will be buying in myself and believe it will enhance the overall ecosystem. But will XCP be used within the swarm framework at all? Or just BTC? In order for XCP liquidity to improve, the projects built on top of counterparty should encourage the use of XCP.

+1
hero member
Activity: 647
Merit: 510
Counterpartying
Please allow xcp in swarm IPO  Smiley

I think this is a good suggestion. You are using the counterparty infrastructure, why wouldn't you allow the token to be used as well?

A company raising an early round of financing probably wants the most liquid currency available so that they can start spending the money. What if swarm took in a high percentage of XCP and then wanted to liquidate 25,000 or so XCP in order to pay for various business expenses?
sr. member
Activity: 390
Merit: 254
Counterparty Developer
We'll be at several conferences this summer. Check out the full list here:

https://www.counterparty.co/counterparty-coming-to-a-conference-near-you/

If you're going to any of these, please reach out. We'd love to meet you.
legendary
Activity: 1232
Merit: 1001
Ooo wait... spoke too soon. Sad

I am now getting this...

Quote
> counterpartyd send --source --destination --quantity 123 --asset XCP
Transaction (unsigned): XXXXX
Sign and broadcast? (y/N) y
Transaction (signed): XXXXX
Traceback (most recent call last):
  File "/home/X/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 693, in
    args.unsigned)
  File "/home/X/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 187, in cli
    print('Hash of transaction (broadcasted):', bitcoin.broadcast_tx(signed_tx_hex))
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 547, in broadcast_tx
    return send_raw_transaction(signed_tx_hex)
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 55, in send_raw_transaction
    return rpc('sendrawtransaction', [tx_hex])
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 165, in rpc
    raise exceptions.BitcoindError('{}'.format(response_json['error']))
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}

How can I send XCP?  Maybe I'm doing something wrong?

Check out: https://www.counterparty.co/resources/faqs/i-got-an-error-tx-rejected-code-22-what-is-that/

Thanks.

I confirm

* Enough BTC: Yes
* At least a few confirmations: overs 1 months
* Bitcoind is running and configured properly: no errors in my debug.log
* Waited 10-20 min, 2 week, 2 months: always get this error

Here's my bug report:

counterpartyd --unsigned send --source --destination --quantity 200 --asset XCP
Transaction (unsigned): 0100000002c1eef0f50d2951e0ce71f70dff630291e6de6b1795a0ccc4f20ab944e4cebaa900000 0001976a914cbeefd1b44465e6f30fb50add2d27ec4d64a771888acffffffff084360e4a725dd0c 4c696f2a002ec7522e8235c32bae2d3e01cfa9240dcd80d9020000001976a914cbeefd1b44465e6 f30fb50add2d27ec4d64a771888acffffffff036c2a0000000000001976a914b22854289bda0c16 0cb353a00e2a2fda86b640ef88ac6c2a000000000000475121032bff26e6179750c88ffb4aa1eb6 a8cfc00878d72222ea0bcd768f28de29a6b29211c434e5452505254590000000000000000000000 0100000004a817c8000000000052ae36150000000000001976a914cbeefd1b44465e6f30fb50add 2d27ec4d64a771888ac00000000

hero member
Activity: 728
Merit: 500
Activity: yes
Please allow xcp in swarm IPO  Smiley
newbie
Activity: 48
Merit: 0
just spreading some screenshots of the new features...

looking real good!

xbet.io have made some big additions to their website.

this is their new control panel for users.

really helped me understand what was going on with my bets and it works perfectly with counterwallet.


https://i.imgur.com/5LKllSh.png


and also one for past bets

https://i.imgur.com/xIQ0RJg.png


I am betting on the world cup only with the only truly safe betting application.
sr. member
Activity: 390
Merit: 254
Counterparty Developer
Ooo wait... spoke too soon. Sad

I am now getting this...

Quote
> counterpartyd send --source --destination --quantity 123 --asset XCP
Transaction (unsigned): XXXXX
Sign and broadcast? (y/N) y
Transaction (signed): XXXXX
Traceback (most recent call last):
  File "/home/X/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 693, in
    args.unsigned)
  File "/home/X/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 187, in cli
    print('Hash of transaction (broadcasted):', bitcoin.broadcast_tx(signed_tx_hex))
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 547, in broadcast_tx
    return send_raw_transaction(signed_tx_hex)
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 55, in send_raw_transaction
    return rpc('sendrawtransaction', [tx_hex])
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 165, in rpc
    raise exceptions.BitcoindError('{}'.format(response_json['error']))
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}

How can I send XCP?  Maybe I'm doing something wrong?

Check out: https://www.counterparty.co/resources/faqs/i-got-an-error-tx-rejected-code-22-what-is-that/
legendary
Activity: 1232
Merit: 1001
This has been fixed earlier in the develop branch: https://github.com/CounterpartyXCP/counterpartyd/commit/e64312d064da1a5ed8b6e52744e99fc40f8d12d0

We'll get it ported into master, since it looks like it will be a bit before we merge develop into master again.

For now, feel free to edit the code yourself, directly, to fix the problem.

I've manually patched api.py but I am still getting:

Code:
counterpartyd wallet

Traceback (most recent call last):
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 837, in
    address_data = get_address(db, address=address)
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 29, in get_address
    address_dict['balances'] = util.api('get_balances', {'filters': [('address', '==', address),]})
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/lib/util.py", line 50, in api
    raise exceptions.RPCError('{}'.format(response_json['error']))
lib.exceptions.RPCError: {'data': {'type': 'NameError', 'args': ["global name 'a' is not defined"], 'message': "global name 'a' is not defined"}, 'message': 'Server error', 'code': -32000}

'a' is not very easy to search for references for...





Is there a traceback printing in counterpartyd.log? If so, that would probably have a line number to the error. If it's something we haven't fixed, we'll get it fixed once we know the location (given that you said you already patched the bug we already fixed).


Seems like this has been fixed after I updated this evening.  Thanks.

Ooo wait... spoke too soon. Sad

I am now getting this...

Quote
> counterpartyd send --source --destination --quantity 123 --asset XCP
Transaction (unsigned): XXXXX
Sign and broadcast? (y/N) y
Transaction (signed): XXXXX
Traceback (most recent call last):
  File "/home/X/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 693, in
    args.unsigned)
  File "/home/X/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 187, in cli
    print('Hash of transaction (broadcasted):', bitcoin.broadcast_tx(signed_tx_hex))
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 547, in broadcast_tx
    return send_raw_transaction(signed_tx_hex)
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 55, in send_raw_transaction
    return rpc('sendrawtransaction', [tx_hex])
  File "/home/X/counterpartyd_build/dist/counterpartyd/lib/bitcoin.py", line 165, in rpc
    raise exceptions.BitcoindError('{}'.format(response_json['error']))
lib.exceptions.BitcoindError: {'message': 'TX rejected', 'code': -22}

How can I send XCP?  Maybe I'm doing something wrong?
legendary
Activity: 1232
Merit: 1001
This has been fixed earlier in the develop branch: https://github.com/CounterpartyXCP/counterpartyd/commit/e64312d064da1a5ed8b6e52744e99fc40f8d12d0

We'll get it ported into master, since it looks like it will be a bit before we merge develop into master again.

For now, feel free to edit the code yourself, directly, to fix the problem.

I've manually patched api.py but I am still getting:

Code:
counterpartyd wallet

Traceback (most recent call last):
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 837, in
    address_data = get_address(db, address=address)
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 29, in get_address
    address_dict['balances'] = util.api('get_balances', {'filters': [('address', '==', address),]})
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/lib/util.py", line 50, in api
    raise exceptions.RPCError('{}'.format(response_json['error']))
lib.exceptions.RPCError: {'data': {'type': 'NameError', 'args': ["global name 'a' is not defined"], 'message': "global name 'a' is not defined"}, 'message': 'Server error', 'code': -32000}

'a' is not very easy to search for references for...





Is there a traceback printing in counterpartyd.log? If so, that would probably have a line number to the error. If it's something we haven't fixed, we'll get it fixed once we know the location (given that you said you already patched the bug we already fixed).


Seems like this has been fixed after I updated this evening.  Thanks.
sr. member
Activity: 309
Merit: 250
Swarm
I dont know if this is the correct topic but regarding swarm kind of ipo i think the second phase is ridiculous, 17,000 btcs will not be fulfilled and less chance if they dont reveal technical aspecs, they only say this will be a awesome coin, project, bla bla but dont say why.

17,000 BTC is a very ambitious target, I admit that. We focused at the moment at reaching the 4,000 BTC goal, but if we do actually reach 17,000 BTC we will have a lot of funds to help support projects (e.g. other things that enhance the Counterparty ecosystem), so I hope we do a larger amount.

At the moment we actually need to stay focused on building the platform, like the dashboard we released on launch.

sr. member
Activity: 335
Merit: 255
Counterparty Developer
same problem.

i can't use counterwallet 

show error as below

failoverAPI: Call failed (failed over across all servers). Method: get_normalized_balances; Last error: JSON-RPC Error:
Type: Server error

Code: -32000

Message: Could not contact counterpartyd!

fixed, please retry. Thanks.
full member
Activity: 198
Merit: 100
same problem.

i can't use counterwallet 

show error as below

failoverAPI: Call failed (failed over across all servers). Method: get_normalized_balances; Last error: JSON-RPC Error:
Type: Server error

Code: -32000

Message: Could not contact counterpartyd!
member
Activity: 62
Merit: 14
We have enhanced our user interface.

It is now possible to view all of your betting information, past and future, dirctly from XBet.IO.
newbie
Activity: 41
Merit: 0
Anybody else getting a server error message when trying to login to counterparty?

Looking forward to getting back up and running.

Jump to: