Let's be clear: Counterparty is not yet anywhere near 100% reliable. The basic protocol, however, is, yes, unambiguous, if for no other reason than that it has a reference implementation.
However, it will get there much sooner than mastercoin. The stress test program can be helpful in finding all the bugs. Any estimate on when counterparty is ready for massive stress testing? I think this will be a critical piece to get in place and then publicize (as soon as XCP passes) When it comes to money, reliability is really the most important thing. Cost savings is probably in second. By passing stress test, intrinsically from not having fees and with automatic scripts that optimize trade outcomes, we can prove that XCP is not only the most reliable platform, but it makes you the most profit. James The thing is that XCP has already been pretty seriously stress tested (in fact, I alone probably broke the network 3-4 times already), and even in alpha state, does work (without anyone's XCP going into a black hole so far). This is undoubtedly due to the massive amount of feedback in this thread. And about the whale; If I burned 50 grand, I'd at least want something back to recoup my costs (which looks to be what's happening here) no matter how I feel about the project. And 7-8 times over the burn price isn't exactly crashing. In reality, I probably burned less BTC than most people in this thread (simply because I don't have much to begin with). A lot of my cold storage went into this project. I think the XCP devs are being super cautious about any reliability claims, for obvious reasons. Also, I think you are severely underestimating the level of stress testing I am thinking of. it needs to be so intense that any competitive system would go back home crying to mommy. Massive amounts of simultaneous transactions, everything, from multiple servers, overflowing blocks, the works. If we want the rest of the world to use XCP for big money transactions, we must make it 100% reliable. Since the XCP protocol is simple and sane, it might take some time, but it is something that will be achievable. Blackbox testing, clearbox testing, graybox testing, flaw analysis, independent source code reviews, everything. Raise the bar so high that any competitor would have to spend months and months and months going in circles trying to fix all their bugs. From what I have heard, it sounds like it is quite possible that mastercoin has too much complexity and when you combine too much complexity with large scale real world volumes and complexity, well, it breaks. James Well obviously more testing will be needed (and is being done every day). But I can't help but notice that even in alpha state, XCP has more complete, working features than many others coins months post-release (I'm not naming names). Decentralized, cheap (~a quarter in fees), attack-proof sports betting powered by the Bitcoin blockchain... |
|
|
|
|
Contract Settled: NotEqual won the pot of 2.0 XCP; 0.0 XCP credited to the feed
address (c1cfe0315493ac2c...3fbd9e4e76bff67d)
Woot, first real XCP bet completed. (This could go into the press release, also).
Broncos lost, but oh well. Congrats Seahawks.
|
|
|
|
Let's be clear: Counterparty is not yet anywhere near 100% reliable. The basic protocol, however, is, yes, unambiguous, if for no other reason than that it has a reference implementation.
However, it will get there much sooner than mastercoin. The stress test program can be helpful in finding all the bugs. Any estimate on when counterparty is ready for massive stress testing? I think this will be a critical piece to get in place and then publicize (as soon as XCP passes) When it comes to money, reliability is really the most important thing. Cost savings is probably in second. By passing stress test, intrinsically from not having fees and with automatic scripts that optimize trade outcomes, we can prove that XCP is not only the most reliable platform, but it makes you the most profit. James The thing is that XCP has already been pretty seriously stress tested (in fact, I alone probably broke the network 3-4 times already), and even in alpha state, does work (without anyone's XCP going into a black hole so far). This is undoubtedly due to the massive amount of feedback in this thread. And about the whale; If I burned 50 grand, I'd at least want something back to recoup my costs (which looks to be what's happening here) no matter how I feel about the project. And 7-8 times over the burn price isn't exactly crashing. In reality, I probably burned less BTC than most people in this thread (simply because I don't have much to begin with). A lot of my cold storage went into this project. |
|
|
|
I think for orders to show up as matched in blockscan, the buyer first has to execute btcpay. Correct me if I'm wrong. Would be helpful to see matched, but unpaid orders though. |
|
|
|
You don't want to do a BTCpay right before the order match is set to expire (especially in the future, when blocks are closer to being full).
Can this be foolproofed somehow before going mainstream? I'd hate to think of all the posts on the forums when people start losing BTC. Maybe the BTCpay operation can accept an order match number as an optional parameter and the escrow time extended if necessary for the amount of that specific order only, provided BTCpay is called before the offer expires. The number of blocks to extend would be based on what the protocol determines is reasonable at the time or could be hardcoded initially. This will come with the GUI/online client. Btcpay right now is not at all user friendly, (neither is order matching), but remember this is alpha quality software. Bitcoin wasn't built in a day (or for that matter, a year). I encourage people to sign up for reddit (if you haven't already) and try to answer outstanding questions in the reddit thread: http://www.reddit.com/r/Bitcoin/comments/1wtz2b/2124_btc_destroyed_in_proofofburn/A lot of people are sold on the idea (unlike, for instance, NXT); they just want to know how to acquire some XCP. |
|
|
|
Hey Blockchain, you have an app for Android an iOS, but can you PLEASE make an app for Windows Phone 8 as well? WP8 is outselling iOS in 24 countries and it has a market share of around 10% nowadays, but there's no way for us to pay for anything with our phones, import paper wallets, etc. Basically we Windows Phone users can't do anything with bitcoin. Can you please help us out by releasing a blockchain.info app? I would be really grateful. P.s., I'm a full-time Windows Phone developer myself, I made the Kraken app ( http://www.windowsphone.com/s?appid=a3857353-599a-434f-8293-398745723de6). If you need help with this, I'm available. +1 million. WP8 has an increasingly dominant international position compared to iOS internationally, which is crucial for global bitcoin adoption. And of course, Microsoft looks to be around for awhile (unlike, for instance, Blackberry). Don't miss out on this market. |
|
|
|
|
Yes please!!! More WP8 apps.
It's inexcusable that WP8 doesn't have a single app (last time I checked) that sweeps private wallets from a QR code. There was one called "Bitcoin", but the private key feature got removed.
|
|
|
|
Seahawks win! (though by 2nd quarter that was kind of obvious). Can you do the broadcast BiggestFish? |
|
|
|
Congrats to the developers and everyone that took the leap and burned their BTCs. We need a Logo design competition as well as some work on marketing, etc.    This looks good. +1, from a designer. The arrow motif is one that I think we should stick to. |
|
|
|
|
Install bitcoin, install the counterparty client, place an order:
C:\counterpartyd>python counterpartyd.py order
usage: counterpartyd order [-h] --from SOURCE --get-quantity GET_QUANTITY
--get-asset GET_ASSET --give-quantity GIVE_QUANTITY
--give-asset GIVE_ASSET --expiration EXPIRATION
[--fee_required FEE_REQUIRED]
[--fee_provided FEE_PROVIDED]
GET_ASSET would be XCP and GIVE_ASSET would be BTC if buying XCP. Expiration is in blocks.
Submit, and wait for an order match. Then use btcpay to pay for the order.
There, completely trustless and decentralized.
|
|
|
|
Is the Dex actually implemented and running bug free?
The Dex is actually implemented and running fine. There have been sample trades made on the exchanges. (There are some minor issues with rounding of numbers, e.g., 1.99999 vs 2.0, however the developers are working on it). Hmm. I'm surprised. From the amount of finagling its taken the mastercoin dev's I had come to the conclusion that it was a rather complicated undertaking. Hi, one of the (early) testers The decentralized exchange is, and has been, working for weeks now. http://www.blockscan.com/order_match.aspx |
|
|
|
These are the magic bytes. They serve a variety of purposes, including indicating the proper network, and serving as a start for explorers such as Abe to parse. Some altcoins that don't change the magic bytes (n00b launches) have problems such as trying to download the litecoin blockchain on start. As for what "pchMessage" means exactly, I don't know. For more info, see http://james.lab6.com/2012/01/12/bitcoin-285-bytes-that-changed-the-world/ |
|
|
|
They have to be confirmed in a block before 283810. Edit it's 283 810 |
|
|
|
I think since you have a change address those are not valid.... what a waste of BTC... Over/under on how many minutes it will take for the owner of that address to realize and come on here screaming about how XCP is a scam? Pretty sure valid. As long as inputs are from same address, and change goes to the original address, should be valid burns. Plus blockscan shows them as valid. Don't really relish dealing with the 0.0099 change though x 50 accounts. Even though I certainly wouldn't mind having them. Totally OT: But block 283807 is pretty funny. When was the last time you saw a block with just a single transaction? Satoshi days? |
|
|
|
I have some press contacts that would be interested in the Counterparty story after the burn period has ended. With Wwat press story should we lead? - Counterparty and the end of Proof of Burn.
- Counterparty and creating your own currency without mining
- Counterparty: Satoshi Nakamoto is back with a new shadowy group
I am curious and seeking new ideas from the community. From a professional standpoint, I like 2. From a "sensationalism sells" standpoint, 3 sells. |
|
|
|
|
I'm assuming Humble Bundle counts to an extent? Paid for god knows how many already.
|
|
|
|
Hi,
Need more guidance on how to actually use the bet/feed system.
What I think I'm trying to do:
Enter a bet from 1Fz5idgemYfsszRMmaQNd2Anvm2JytAoU (my XCP account) to feed 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN (super bowl feed) to bet 1 XCP that Denver (2) will win at or before block 290000 (random estimate in future).
What I entered:
C:\counterpartyd>python counterpartyd.py bet --from 1Fz5idgemYfsszRMmaQNd2Anvm2J
ytAoU --feed-address 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN --bet-type Equal --deadl
ine 290000 --wager 1 --counterwager 1 --target-value 2 --expiration 2
Traceback (most recent call last):
File "counterpartyd.py", line 564, in <module>
deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
AttributeError: type object 'datetime.datetime' has no attribute 'timestamp'
Don't know what to put in expiration because anything is giving me errors.
That error message sure isn't very helpful! The problem is that deadlines are specified in actual times, not block numbers, and moreover in human-readable formats, such as 'Mon Feb 3 10:00:00 UTC 2014'. (I actually haven't figured out myself exactly what datetime will accept, yet... it won't take Unix time, for no reason.) The expiration is the maximum number of blocks that you want your bet to be available to be matched for. What is the correct syntax? C:\counterpartyd>python counterpartyd.py bet --from 1Fz5idgemYfsszRMmaQNd2Anvm2J ytAoU --feed-address 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN --bet-type Equal --deadl ine "Mon Feb 3 10:00:00 UTC 2014" --wager 1 --counterwager 1 --target-value 2 -- expiration 1000 Traceback (most recent call last): File "counterpartyd.py", line 564, in <module> deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline))) AttributeError: type object 'datetime.datetime' has no attribute 'timestamp' Tried ' ' (get counterpartyd: error: unrecognized arguments: Feb 3 10:00:00 UTC 2014'), " ", and "' '". It looks like you may be having the same problem that BiggestFish was seeing: try wrapping the date in another set of single quotes. Bet submitted, have at it (Seahawks fans). Should appear in 10 minutes or so. Implementing xibejian's fix as documented here fixed the problem (quotes or no). Problem also documented here: http://stackoverflow.com/questions/12906402/type-object-datetime-datetime-has-no-attribute-datetime----- Another bug report Quote Traceback (most recent call last): File "./counterpartyd.py", line 465, in <module> deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline))) AttributeError: type object 'datetime.datetime' has no attribute 'timestamp' I have a patch for this Quote 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? |
|
|
|
Did anyone happen to interview Satoshi?  |
|
|
|
Hi,
Need more guidance on how to actually use the bet/feed system.
What I think I'm trying to do:
Enter a bet from 1Fz5idgemYfsszRMmaQNd2Anvm2JytAoU (my XCP account) to feed 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN (super bowl feed) to bet 1 XCP that Denver (2) will win at or before block 290000 (random estimate in future).
What I entered:
C:\counterpartyd>python counterpartyd.py bet --from 1Fz5idgemYfsszRMmaQNd2Anvm2J
ytAoU --feed-address 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN --bet-type Equal --deadl
ine 290000 --wager 1 --counterwager 1 --target-value 2 --expiration 2
Traceback (most recent call last):
File "counterpartyd.py", line 564, in <module>
deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
AttributeError: type object 'datetime.datetime' has no attribute 'timestamp'
Don't know what to put in expiration because anything is giving me errors.
That error message sure isn't very helpful! The problem is that deadlines are specified in actual times, not block numbers, and moreover in human-readable formats, such as 'Mon Feb 3 10:00:00 UTC 2014'. (I actually haven't figured out myself exactly what datetime will accept, yet... it won't take Unix time, for no reason.) The expiration is the maximum number of blocks that you want your bet to be available to be matched for. What is the correct syntax? C:\counterpartyd>python counterpartyd.py bet --from 1Fz5idgemYfsszRMmaQNd2Anvm2J ytAoU --feed-address 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN --bet-type Equal --deadl ine "Mon Feb 3 10:00:00 UTC 2014" --wager 1 --counterwager 1 --target-value 2 -- expiration 1000 Traceback (most recent call last): File "counterpartyd.py", line 564, in <module> deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline))) AttributeError: type object 'datetime.datetime' has no attribute 'timestamp' Tried ' ' (get counterpartyd: error: unrecognized arguments: Feb 3 10:00:00 UTC 2014'), " ", and "' '". |
|
|
|
|
Show Posts
