Quote from: PhantomPhreak on January 08, 2014, 05:37:51 PM
The values of feeds are, as it were, manually chosen, and bets are made only on feeds.
That still pops red warning trust-issue in my mind...
I have a suggestion to mitigate the feed trust issue. Instead of placing bets on the data from 1 feed, users could be allowed to place bets on the median of data from multiple feeds pointed to identical data, with transaction fees split and distributed among chosen feed providers.
For even more security the bet could be on the median of medians from multiple feeds over a prolonged period of time, say 100 snapshots.
A scammer would have to control 51% of the "feed network" to scam successfully, which would be prohibitively expensive given the transaction fees it costs to maintain a feed.
EDIT: allowing multiple-feed bets also solves the issue of unexpected feed downtime as well as censorship (I'm sure Standard & Poor's would be unhappy to learn that someone is taking their market data for free and piping it into a crypto betting exchange for profit as the underlying for crypto-financial derivative contracts :-))
That won't work---all clients must agree on the exact value of a feed at any given time, and in your scenario, some clients might accept some feeds as valid, and reject others.
I also don't think that we have to worry about censorship of the broadcasts from an address. It's very hard to stop a particular Bitcoin address from being the origin of certain transactions.
Hi
Just as a heads up.. I started working on a XCP CounterParty block explorer shortly after the project was publicly posted, and I would like to announce that I have a live beta version available at
http://www.blockscan.comThere is some basic search functionality to allow you to look up your block balance easily and also to see the transaction history for burned blocks. At the moment this only included confirmed blocks as per the CounterParty client
If you have any suggestions, feedback or bug reports do let me know.
Cheers
That looks great! Thanks!
I'm not sure how easy it is to do anything but burns with Counterparty and unconfirmed blocks, because of the great dependence of the protocol on the order of the transactions within a block. How deterministic is Bitcoind's arrangement of the pool of unconfirmed transactions? (Does anyone know?)
Nitpick: it should be 'Counterparty' in the website header, not 'CounterParty'.
How can I burn a bitcoin for XCP using Electrum? I don't have Bitcoin-qt installed and downloading the fullblockchain will take ages on my internet connection.
Electrum isn't supported (currently). You can use Blockchain.info to burn, however.
Thank you.
Reading the guide to burn via Blockchain.info, I think I understand all of the steps and I am going to try a test amount first but what I don't understand is how to claim my XCP after I have burned my BTC?
Can you please explain this?
Where is this guide?
See
http://counterpartyd-build.readthedocs.org/en/latest/HowToBurn.html.
Another bug report
Traceback (most recent call last):
File "./counterpartyd.py", line 465, in
deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
AttributeError: type object 'datetime.datetime' has no attribute 'timestamp'
I have a patch for this
diff --git a/counterpartyd.py b/counterpartyd.py
index 779ee12..1bbf2bd 100755
--- a/counterpartyd.py
+++ b/counterpartyd.py
@@ -15,7 +15,8 @@ from prettytable import PrettyTable
import time
import dateutil.parser
-from datetime import datetime
+import datetime
+import calendar
from lib import (config, util, exceptions, bitcoin, blocks)
from lib import (send, order, btcpay, issuance, broadcast, bet, dividend, burn, cancel, util)
@@ -462,7 +463,7 @@ if __name__ == '__main__':
json_print(bitcoin.transmit(unsigned_tx_hex))
elif args.action == 'bet':
- deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
+ deadline = calendar.timegm(dateutil.parser.parse(args.deadline).utctimetuple())
Look ok?
Is there any reason to prefer
calendar over
datetime here, generally? That is, will we not have other problems with this new version?
