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

baddw

hero member

Activity: 700

Merit: 500

Quote from: porqupine on June 17, 2014, 12:32:51 AM

Quote from: baddw on June 17, 2014, 12:09:31 AM

Quote from: PhantomPhreak on June 16, 2014, 07:05:59 PM

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

full member

Activity: 214

Merit: 101

Quote from: baddw on June 17, 2014, 12:09:31 AM

Quote from: PhantomPhreak on June 16, 2014, 07:05:59 PM

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

hero member

Activity: 700

Merit: 500

Quote from: PhantomPhreak on June 16, 2014, 07:05:59 PM

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.

DistributedBUZZ

newbie

Activity: 37

Merit: 0

Quote from: dawie on June 16, 2014, 02:52:38 PM

Quote from: Kyune on June 16, 2014, 02:32:08 PM

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

PhantomPhreak

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Quote from: baddw on June 16, 2014, 05:25:47 PM

Quote from: PhantomPhreak on June 16, 2014, 04:58:31 PM

Quote from: baddw on June 16, 2014, 03:48:14 PM

Quote from: PhantomPhreak on June 14, 2014, 01:50:06 PM

Quote from: baddw on June 12, 2014, 05:04:47 PM

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

baddw

hero member

Activity: 700

Merit: 500

Quote from: PhantomPhreak on June 16, 2014, 04:58:31 PM

Quote from: baddw on June 16, 2014, 03:48:14 PM

Quote from: PhantomPhreak on June 14, 2014, 01:50:06 PM

Quote from: baddw on June 12, 2014, 05:04:47 PM

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

sr. member

Activity: 476

Merit: 300

Counterparty Chief Scientist and Co-Founder

Quote from: baddw on June 16, 2014, 03:48:14 PM

Quote from: PhantomPhreak on June 14, 2014, 01:50:06 PM

Quote from: baddw on June 12, 2014, 05:04:47 PM

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

hero member

Activity: 700

Merit: 500

Quote from: PhantomPhreak on June 14, 2014, 01:50:06 PM

Quote from: baddw on June 12, 2014, 05:04:47 PM

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.

dawie

member

Activity: 115

Merit: 10

BTC for a better world

Quote from: Kyune on June 16, 2014, 02:32:08 PM

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

Kyune

sr. member

Activity: 287

Merit: 250

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.

cityglut

full member

Activity: 216

Merit: 100

Quote from: porqupine on June 16, 2014, 03:25:50 AM

Quote from: Kalkuuuta on June 16, 2014, 03:01:06 AM

Quote from: Matt Y on June 15, 2014, 03:01:01 PM

Quote from: Bitcoin++ on June 15, 2014, 12:33:04 PM

I just realized that XCP is perfect for issuing digital currencies backed by real assets.
(Others may have written about this before, so forgive me if I "steal" these thoughts ... )

Unlike altcoins, you don't need to fear the network collapsing any more than you need for bitcoin.

Therefore XCP is the perfect platform for issuing an asset/coin, right?

Now say you own a shop and want customers to pay in a crytpo-currency because it's convenient and has low fees. The problem with bitcoin is volatility. Therefore you issue CRYPTODOLLAR which you back by USD. How you do it is simply that you put your asset for sale at the price of one dollar measured in bitcoins. Your asking price always adjusts up and down according to BTC's price. You also promise always to buy back at 99 cents, so that customers only faces a tiny spread (kinda like ETFs on the stock exchange are priced).

As long as your customers trust that you'll always buy back their CRYPTODOLLARS they have a cryptocurruency with zero volatility. To gain this trust you may have an audited bank account with the same amount of dollars as you've issued of these assets. The same can be done backed by gold, silver, or anything else.

In terms of betting this could work just as well. Xbet.io is an excellent service, but it's difficult to get the XCPs needed to bet. The spread is large and the volume is low. If someone trustworthy issues a CASIONDOLLAR or similar based on the description above, it becomes more user friendly. At the moment, though, this may be impossible (If I understood correct) since only XCPs are possible to use for betting. But in a future update of Counterparty any asset can be used, am I right?

Yes.

Couple page ago here was speculating about price and betting option one big reason for get price higher. If all assets are coming possible for use betting what you think for XCP price happen when that no need still?

You wouldn't enable more than one asset for betting - because that would decrease contract liquidity, and hence hurt protocol utility as a whole.

Edit: Also trust based issuance of tokens like dollars or euros is only useful in special cases - in most cases it's much preferable to make a CFD and not have to trust an issuer...

There are some much more interesting and much more obvious use-cases for Counterparty assets in derivatives than CFDs; futures, for example.

EDIT: Original post was redundant with porqupine.

porqupine

full member

Activity: 214

Merit: 101

Quote from: Kalkuuuta on June 16, 2014, 03:01:06 AM

Quote from: Matt Y on June 15, 2014, 03:01:01 PM

Quote from: Bitcoin++ on June 15, 2014, 12:33:04 PM

I just realized that XCP is perfect for issuing digital currencies backed by real assets.
(Others may have written about this before, so forgive me if I "steal" these thoughts ... )

Unlike altcoins, you don't need to fear the network collapsing any more than you need for bitcoin.

Therefore XCP is the perfect platform for issuing an asset/coin, right?

Now say you own a shop and want customers to pay in a crytpo-currency because it's convenient and has low fees. The problem with bitcoin is volatility. Therefore you issue CRYPTODOLLAR which you back by USD. How you do it is simply that you put your asset for sale at the price of one dollar measured in bitcoins. Your asking price always adjusts up and down according to BTC's price. You also promise always to buy back at 99 cents, so that customers only faces a tiny spread (kinda like ETFs on the stock exchange are priced).

As long as your customers trust that you'll always buy back their CRYPTODOLLARS they have a cryptocurruency with zero volatility. To gain this trust you may have an audited bank account with the same amount of dollars as you've issued of these assets. The same can be done backed by gold, silver, or anything else.

In terms of betting this could work just as well. Xbet.io is an excellent service, but it's difficult to get the XCPs needed to bet. The spread is large and the volume is low. If someone trustworthy issues a CASIONDOLLAR or similar based on the description above, it becomes more user friendly. At the moment, though, this may be impossible (If I understood correct) since only XCPs are possible to use for betting. But in a future update of Counterparty any asset can be used, am I right?

Yes.

Couple page ago here was speculating about price and betting option one big reason for get price higher. If all assets are coming possible for use betting what you think for XCP price happen when that no need still?

You wouldn't enable more than one asset for betting - because that would decrease contract liquidity, and hence hurt protocol utility as a whole.

Edit: Also trust based issuance of tokens like dollars or euros is only useful in special cases - in most cases it's much preferable to make a CFD and not have to trust an issuer...

Kalkuuuta

member

Activity: 64

Merit: 10

Quote from: Matt Y on June 15, 2014, 03:01:01 PM

Quote from: Bitcoin++ on June 15, 2014, 12:33:04 PM

I just realized that XCP is perfect for issuing digital currencies backed by real assets.
(Others may have written about this before, so forgive me if I "steal" these thoughts ... )

Unlike altcoins, you don't need to fear the network collapsing any more than you need for bitcoin.

Therefore XCP is the perfect platform for issuing an asset/coin, right?

Now say you own a shop and want customers to pay in a crytpo-currency because it's convenient and has low fees. The problem with bitcoin is volatility. Therefore you issue CRYPTODOLLAR which you back by USD. How you do it is simply that you put your asset for sale at the price of one dollar measured in bitcoins. Your asking price always adjusts up and down according to BTC's price. You also promise always to buy back at 99 cents, so that customers only faces a tiny spread (kinda like ETFs on the stock exchange are priced).

As long as your customers trust that you'll always buy back their CRYPTODOLLARS they have a cryptocurruency with zero volatility. To gain this trust you may have an audited bank account with the same amount of dollars as you've issued of these assets. The same can be done backed by gold, silver, or anything else.

In terms of betting this could work just as well. Xbet.io is an excellent service, but it's difficult to get the XCPs needed to bet. The spread is large and the volume is low. If someone trustworthy issues a CASIONDOLLAR or similar based on the description above, it becomes more user friendly. At the moment, though, this may be impossible (If I understood correct) since only XCPs are possible to use for betting. But in a future update of Counterparty any asset can be used, am I right?

Yes.

Couple page ago here was speculating about price and betting option one big reason for get price higher. If all assets are coming possible for use betting what you think for XCP price happen when that no need still?

xibeijan

legendary

Activity: 1232

Merit: 1001

Quote from: xnova on June 15, 2014, 07:38:40 PM

Quote from: led_lcd on June 15, 2014, 07:17:19 PM

Quote from: xnova on June 15, 2014, 06:57:06 PM

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

This is in the api.error.log:

Code:

[14/Apr/2014:10:20:11] HTTP Traceback (most recent call last):
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/cherrypy/_cprequest.py", line 656, in respond
   response.body = self.handler()
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/cherrypy/lib/encoding.py", line 188, in __call__
   self.body = self.oldhandler(*args, **kwargs)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/cherrypy/_cpdispatch.py", line 34, in __call__
   return self.callable(*self.args, **self.kwargs)
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/lib/api.py", line 445, in index
   response = JSONRPCResponseManager.handle(data, dispatcher)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/manager.py", line 47, in handle
   request = JSONRPCRequest.from_json(request_str)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/jsonrpc.py", line 22, in from_json
   return JSONRPC10Request.from_json(json_str)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/jsonrpc1.py", line 93, in from_json
   method=data["method"], params=data["params"], _id=data["id"]
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/base.py", line 12, in __init__
   self.params = params
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/jsonrpc1.py", line 57, in params
   raise ValueError("Incorrect params {}".format(value))
ValueError: Incorrect params {'filters': [{'field': 'address', 'value': 'addressRedacted', 'op': '=='}]}

Eh...unfortunately not very helpful, due to the nature of that error. We'll have ouziel find and fix this 'a' bug in master tomorrow morning first thing (as well as a counterwallet mobile bug Swarm was having problems with).

Yeah, this is pretty bad and needs fixed.

porqupine

full member

Activity: 214

Merit: 101

Cross Post from Counterparty Forums:

Quote

Development version of the new site is UP at test.xcpfeeds.info.

* General *
The Front-page is still being redone.

* Web Wallet *

Web Wallet is BIP32 deterministic - your Counterwallet testnet login should work.

Wallet does not currently display any unconfirmed transactions (including your own)
- this will be implemented soon.

Wallet is not Security tested - you may loose your Testnet BTC.

* Betting *
All Times are in UTC / GM.

Addresses must have been used at least once to send a Bitcoin Transaction in order
for XCPfeeds to find the Pubkey_hex, betting is not currently 'wallet address book'
conscious, so even using xcpfeeds wallet the address must have been used at least once
prior for a valid tx to be created.

Selecting a team will auto select the best odds if there are open bets available for the team.

* Known Issues *
Display Glitch for the Odds Slider Using Chrome (or Chromium) when loading a Binary Bet view for the first time.
Pixelated loading wheel on Firefox.

*******

I will lack a stable internet connection until Thursday or Friday of this week, so advanced apologies if I am not able to respond to bug reports promptly.

Bug reports and comments: https://forums.counterparty.co/index.php/topic,329

toffoo

sr. member

Activity: 408

Merit: 261

Quote from: xnova on June 15, 2014, 07:37:47 PM

* Added a Team page at: https://www.counterparty.co/team/

Nice, but FYI this page isn't rendering for me good on Safari/OSX:

led_lcd

sr. member

Activity: 262

Merit: 250

Quote from: xnova on June 15, 2014, 07:38:40 PM

Eh...unfortunately not very helpful, due to the nature of that error. We'll have ouziel find and fix this 'a' bug in master tomorrow morning first thing (as well as a counterwallet mobile bug Swarm was having problems with).

Thanks. Unfortunately, there wasn't anything in counterpartyd.log

xnova

sr. member

Activity: 390

Merit: 254

Counterparty Developer

Quote from: led_lcd on June 15, 2014, 07:17:19 PM

Quote from: xnova on June 15, 2014, 06:57:06 PM

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

This is in the api.error.log:

Code:

[14/Apr/2014:10:20:11] HTTP Traceback (most recent call last):
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/cherrypy/_cprequest.py", line 656, in respond
   response.body = self.handler()
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/cherrypy/lib/encoding.py", line 188, in __call__
   self.body = self.oldhandler(*args, **kwargs)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/cherrypy/_cpdispatch.py", line 34, in __call__
   return self.callable(*self.args, **self.kwargs)
  File "/home/jeremy/counterpartyd_build/dist/counterpartyd/lib/api.py", line 445, in index
   response = JSONRPCResponseManager.handle(data, dispatcher)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/manager.py", line 47, in handle
   request = JSONRPCRequest.from_json(request_str)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/jsonrpc.py", line 22, in from_json
   return JSONRPC10Request.from_json(json_str)
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/jsonrpc1.py", line 93, in from_json
   method=data["method"], params=data["params"], _id=data["id"]
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/base.py", line 12, in __init__
   self.params = params
  File "/home/jeremy/counterpartyd_build/env/lib/python3.3/site-packages/jsonrpc/jsonrpc1.py", line 57, in params
   raise ValueError("Incorrect params {}".format(value))
ValueError: Incorrect params {'filters': [{'field': 'address', 'value': 'addressRedacted', 'op': '=='}]}

Eh...unfortunately not very helpful, due to the nature of that error. We'll have ouziel find and fix this 'a' bug in master tomorrow morning first thing (as well as a counterwallet mobile bug Swarm was having problems with).

xnova

sr. member

Activity: 390

Merit: 254

Counterparty Developer

Website updates

Hey guys...knocked out numerous website updates today to www.counterparty.co:

* Tagline added to home page...this may be tweaked over the next week
* Added a Team page at: https://www.counterparty.co/team/
* Added a projects portfolio at https://www.counterparty.co/projects/ ...please email us if your launched project is not listed
* Countertalk ep1 is up and properly listed: https://www.counterparty.co/category/countertalk/

led_lcd

sr. member

Activity: 262

Merit: 250

Quote from: voldemort628 on June 15, 2014, 07:14:13 PM

Is there any particular reason why you chose Australia?

It's the country where we are living. We have engaged legal counsel here in Australia too in case people were wondering.

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