[ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread

[Kyune]

Is there a thread other than this one where the details of Swarm are being discussed?  (Things like...percentage of newly-issued coins that would ultimately trickle back to SWARMCOIN holders...when we can expect to see an alpha client).  I can't find such a thread.  Their website itself is light on details.  Thanks.

[1715510913]

1715510913

[1715510913]

1715510913

[dawie]

Is there a thread other than this one where the details of Swarm are being discussed?  (Things like...percentage of newly-issued coins that would ultimately trickle back to SWARMCOIN holders...when we can expect to see an alpha client).  I can't find such a thread.  Their website itself is light on details.  Thanks.

I'm trying to navigate the info myself.  Maybe the Couterparty Forum site?:
https://forums.counterparty.co/index.php

[baddw]

Ok, thanks. 

Kind of disappointing that it must be a URL and not live entirely within the XCP protocol.  I understand the need/desire for metadata, but there are some bets that are fairly simple and IMO should be able to fit within the constraints of a simple Text Label and Value pair, given that certain metadata (date/timestamp etc.) is embedded by nature of the protocol anyway.  Also, the need to specify an end date or recurring interval is kind of iffy for Bitcoin Difficulty, since each interval could be anywhere from 10 to 16 days, although generally it has been in the 11-13 day range lately.

All of the information actually relevant to bets and their resolution is entirely in the protocol. All of the promises and predictions stored in the extended asset info JSON are entirely unenforcable and independent of the parsing, so counterpartyd completely ignores the 'text' field, (unless it is equal to 'lock'). You can put anything you want in there.

Thanks for the info.  I look forward to a Counterwallet implementation of betting solely on the value in a feed, with user-defined expirations.

Next Bitcoin difficulty change occurs within the next 2 days, I will update the feed when appropriate, for the sake of formality if nothing else.

[PhantomPhreak]

Ok, thanks. 

Kind of disappointing that it must be a URL and not live entirely within the XCP protocol.  I understand the need/desire for metadata, but there are some bets that are fairly simple and IMO should be able to fit within the constraints of a simple Text Label and Value pair, given that certain metadata (date/timestamp etc.) is embedded by nature of the protocol anyway.  Also, the need to specify an end date or recurring interval is kind of iffy for Bitcoin Difficulty, since each interval could be anywhere from 10 to 16 days, although generally it has been in the 11-13 day range lately.

All of the information actually relevant to bets and their resolution is entirely in the protocol. All of the promises and predictions stored in the extended asset info JSON are entirely unenforcable and independent of the parsing, so counterpartyd completely ignores the 'text' field, (unless it is equal to 'lock'). You can put anything you want in there.

Thanks for the info.  I look forward to a Counterwallet implementation of betting solely on the value in a feed, with user-defined expirations.

This exists already.

[baddw]

Ok, thanks. 

Kind of disappointing that it must be a URL and not live entirely within the XCP protocol.  I understand the need/desire for metadata, but there are some bets that are fairly simple and IMO should be able to fit within the constraints of a simple Text Label and Value pair, given that certain metadata (date/timestamp etc.) is embedded by nature of the protocol anyway.  Also, the need to specify an end date or recurring interval is kind of iffy for Bitcoin Difficulty, since each interval could be anywhere from 10 to 16 days, although generally it has been in the 11-13 day range lately.

All of the information actually relevant to bets and their resolution is entirely in the protocol. All of the promises and predictions stored in the extended asset info JSON are entirely unenforcable and independent of the parsing, so counterpartyd completely ignores the 'text' field, (unless it is equal to 'lock'). You can put anything you want in there.

Thanks for the info.  I look forward to a Counterwallet implementation of betting solely on the value in a feed, with user-defined expirations.

This exists already.

Then can you tell me how to bet on the broadcasts from 1ADigCqe5tWXBXcM1V82oWaXRNW2wUpXUS ?  Or alternatively, how to properly format the broadcast to enable betting?  When I put that address into the "Make a Bet" input box in Counterwallet, it says "We can't find a feed at this address".

[PhantomPhreak]

Ok, thanks. 

Kind of disappointing that it must be a URL and not live entirely within the XCP protocol.  I understand the need/desire for metadata, but there are some bets that are fairly simple and IMO should be able to fit within the constraints of a simple Text Label and Value pair, given that certain metadata (date/timestamp etc.) is embedded by nature of the protocol anyway.  Also, the need to specify an end date or recurring interval is kind of iffy for Bitcoin Difficulty, since each interval could be anywhere from 10 to 16 days, although generally it has been in the 11-13 day range lately.

All of the information actually relevant to bets and their resolution is entirely in the protocol. All of the promises and predictions stored in the extended asset info JSON are entirely unenforcable and independent of the parsing, so counterpartyd completely ignores the 'text' field, (unless it is equal to 'lock'). You can put anything you want in there.

Thanks for the info.  I look forward to a Counterwallet implementation of betting solely on the value in a feed, with user-defined expirations.

This exists already.

Then can you tell me how to bet on the broadcasts from 1ADigCqe5tWXBXcM1V82oWaXRNW2wUpXUS ?  Or alternatively, how to properly format the broadcast to enable betting?  When I put that address into the "Make a Bet" input box in Counterwallet, it says "We can't find a feed at this address".

I'm sorry! You're absolutely correct that Counterwallet doesn't yet support choosing the bet parameters for a bare feed (unless Ouziel is working on something that I don't know about). XCP Feeds, on the other hand, does allow you to do this, and it will return a raw transaction which you can sign and broadcast from within Counterwallet. (Though now I'm seeing that there's a bug in XCP Feeds' interface that's not letting me choose the leverage.)

[DistributedBUZZ]

Is there a thread other than this one where the details of Swarm are being discussed?  (Things like...percentage of newly-issued coins that would ultimately trickle back to SWARMCOIN holders...when we can expect to see an alpha client).  I can't find such a thread.  Their website itself is light on details.  Thanks.

I'm trying to navigate the info myself.  Maybe the Couterparty Forum site?:
https://forums.counterparty.co/index.php

Hey check out:
http://www.reddit.com/r/Swarming/

https://bitcointalk.org/index.php?topic=653741.new#new

[baddw]

I'm sorry! You're absolutely correct that Counterwallet doesn't yet support choosing the bet parameters for a bare feed (unless Ouziel is working on something that I don't know about). XCP Feeds, on the other hand, does allow you to do this, and it will return a raw transaction which you can sign and broadcast from within Counterwallet. (Though now I'm seeing that there's a bug in XCP Feeds' interface that's not letting me choose the leverage.)

Awesome, thanks for the link to XCP Feeds, I will give it a shot.

[porqupine]

I'm sorry! You're absolutely correct that Counterwallet doesn't yet support choosing the bet parameters for a bare feed (unless Ouziel is working on something that I don't know about). XCP Feeds, on the other hand, does allow you to do this, and it will return a raw transaction which you can sign and broadcast from within Counterwallet. (Though now I'm seeing that there's a bug in XCP Feeds' interface that's not letting me choose the leverage.)

Awesome, thanks for the link to XCP Feeds, I will give it a shot.

Some backwards non-compatible API changes have left the main-site out of date (but the raw transaction maker should still work). The current development version is at test.xcpfeeds.info - everything except for the wallet should be up on livenet in the next couple days (my internet connection atm is not stable enough for ssh). Also you can expect an enhanced CFD feeds interface sometime this week - but the old one should remain accessible for bets with 'non-json-enhanced' descriptions.

edit: Also leverage is only applicable to CFD's and incompatible with target_value bets

[baddw]

I'm sorry! You're absolutely correct that Counterwallet doesn't yet support choosing the bet parameters for a bare feed (unless Ouziel is working on something that I don't know about). XCP Feeds, on the other hand, does allow you to do this, and it will return a raw transaction which you can sign and broadcast from within Counterwallet. (Though now I'm seeing that there's a bug in XCP Feeds' interface that's not letting me choose the leverage.)

Awesome, thanks for the link to XCP Feeds, I will give it a shot.

Some backwards non-compatible API changes have left the main-site out of date (but the raw transaction maker should still work). The current development version is at test.xcpfeeds.info - everything except for the wallet should be up on livenet in the next couple days (my internet connection atm is not stable enough for ssh). Also you can expect an enhanced CFD feeds interface sometime this week - but the old one should remain accessible for bets with 'non-json-enhanced' descriptions.

edit: Also leverage is only applicable to CFD's and incompatible with target_value bets

Is there any way to have a target_value bet that is not equal or unequal, but greater-than or less-than?  My goal is for somebody to be able to say "I believe that Bitcoin Difficulty will be greater than 18000000000, on or before 21 September 2014 at 12:00:00 UTC".

[porqupine]

I'm sorry! You're absolutely correct that Counterwallet doesn't yet support choosing the bet parameters for a bare feed (unless Ouziel is working on something that I don't know about). XCP Feeds, on the other hand, does allow you to do this, and it will return a raw transaction which you can sign and broadcast from within Counterwallet. (Though now I'm seeing that there's a bug in XCP Feeds' interface that's not letting me choose the leverage.)

Awesome, thanks for the link to XCP Feeds, I will give it a shot.

Some backwards non-compatible API changes have left the main-site out of date (but the raw transaction maker should still work). The current development version is at test.xcpfeeds.info - everything except for the wallet should be up on livenet in the next couple days (my internet connection atm is not stable enough for ssh). Also you can expect an enhanced CFD feeds interface sometime this week - but the old one should remain accessible for bets with 'non-json-enhanced' descriptions.

edit: Also leverage is only applicable to CFD's and incompatible with target_value bets

Is there any way to have a target_value bet that is not equal or unequal, but greater-than or less-than?  My goal is for somebody to be able to say "I believe that Bitcoin Difficulty will be greater than 18000000000, on or before 21 September 2014 at 12:00:00 UTC".

At the moment that can only be done on the feed operator side - i.e. by broadcasting a target_value type feed with Bitcoin Difficulty greater than XXX (target_value: 1, True: Equal, False: Not_Equal)

[BitcoinForumator]

No counterparty servers are currently available. Please try again later. ERROR: JSON-RPC Error:
Type: Server error

Code: -32000

Message: Could not contact insight!

[ontopicplease]

He says he placed two buy orders for two tokens and one of the orders ate his btc

It really sounds like he is trying to scam you. This situation does not seem logical.

Since months I have been buying and following XCP. At the moment my faith in succes is getting lower and lower. Being a technical noob myself, I can only come to the conclusion; XCP is way to technically complicated for the regular human being to become a big succes.

Have you tried Counterwallet? In my opinion it isn't any harder than using a regular Bitcoin wallet whatsoever. Can you please explain what you think is too complicated? What kind of video tutorials would you like to see? I will gladly take the time to explain if need be.

Also, the counterpartyd protocol does not have to be understood by everyone. The point is that it works. More and more higher-level applications and graphical user interfaces will be built, making it super easy for the end user. SWARM will make crowdfunding easier to use, and VENND will make buying tokens as easy as sending BTC to an address.

Instead of concluding something based on no argument provided, it would be beneficial if you pointed out what confuses you, so that we can work on explaining it to the community.

Sorry, I am really bad with computerstuff. Spend a couple of hours on the counterparty wallet etc some months ago, but gave up. I am still holding a decent amount though ( 1600 XCP on poloniex). Thanks for the help your offering, but I don't want to get angry again, I just keep 'm there and wait couple of months.

[BankToTheFuture]

Anybody else getting a server error message when trying to login to counterparty?

Looking forward to getting back up and running.

[xbet.io]

We have enhanced our user interface.

It is now possible to view all of your betting information, past and future, dirctly from XBet.IO.

[coingifts]

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!

[JahPowerBit]

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.

[fractastical]

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.

[xibeijan]

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 <module>
    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.

[xibeijan]

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 <module>
    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.

I am now getting this...

> counterpartyd send --source <sorry> --destination <hidden> --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 <module>
    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?