Oh SHEESH
Tx Source Buy Sell Price Expiration F_Req F_Prov Remarks
3256 1Mf2abNSv7jzwsjgkrf2k3LTMyEw96Us3H 1000 XCP 1.320 BTC 0.00132 BTC/XCP (4713|5000) 0 0.0001 Invalid: cancelled
Don't tell me my cancellation of this order did not work either, and that lost 1.320 BTC!
PhantomPhreak, can you please have a look? Now I REALLY start to get more than a little worried. We're talking about serious money now. Did the cancellation also send my btc into a black hole? Tell me it isn't so...
Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 541. (Read 1276933 times)
February 06, 2014, 07:29:26 PM
February 06, 2014, 07:21:20 PM
CP Team,
What are the expected next stage milestones for the XCP platform and currency (by concept and appx target dates)? for example: friendly to use client, the next version of the decentralized exchange? what's more after that? can you briefly describe plans? it will also be great for the "spreading the word" aspect. Thanks
What are the expected next stage milestones for the XCP platform and currency (by concept and appx target dates)? for example: friendly to use client, the next version of the decentralized exchange? what's more after that? can you briefly describe plans? it will also be great for the "spreading the word" aspect. Thanks
February 06, 2014, 07:21:07 PM
Can we already make CFD?
I am thinking that the possibility of shorting altcoins would be very interesting!
I think there is huge demand which is not fullfill by the market right know and that could be the killer app of the protocol.
I am thinking that the possibility of shorting altcoins would be very interesting!
I think there is huge demand which is not fullfill by the market right know and that could be the killer app of the protocol.
February 06, 2014, 07:12:35 PM
Your client thought that there was a match where there wasn't one, because it was using a bad rounding algorithm elsewhere. Every client calculates everything itself, so order matching, for instance has to be entirely deterministic.
I was the one whose BTC were lost due to this bug, and since you promised to reimburse, it'd be great if you could attend to that
What was being rounded off wrongly?
February 06, 2014, 06:55:00 PM
Quote
The fee of the bid doesn't satisfy the requirements of the ask.
I think in this case the fees match. Everything checks out: the bid is for .004503 and the ask is for .004519 so they shouldn't cross.
Sure. That, too.
February 06, 2014, 06:53:09 PM
Quote
this is a very rare, irreversible bug in the order matching (normally bugs like this are reversible, but not BTCpay
Can you perhaps explain what exactly the issue is? Or is it buried somewhere a couple of pages back in the forum?
Sure:
https://bitcointalksearch.org/topic/m.4957701
Basically, the rounding code for master and develop was different, so BTCpays for one did not match the other, and went to the wrong accounts (still Counterparty accounts though). As I understand, such a thing will probably almost never happen in the future again, because BTCpay (the only protocol-level irreversible part of Counterparty, besides proof-of-burn) and the rounding issues have been addressed permanently. Note I said almost never.
This event is sort of like Counterparty's version of Bitcoin's infamous blockchain fork. (though since we don't have mining, the analogy is tenuous). [Devs correct me on this]. Fortunately it happened early on, as opposed to when it happened for bitcoin.
I don't get it. When I ran "counterpartyd market" I saw that I had a match for my order along with an order match id. So I did a "counterpartyd btcpay --order-match-id
So "counterpartyd wallet" has been lying about the amount of XCP in my wallet. How could that happen? Even for alpha software, that's a bit unsettling.
And also, a comment to this being a "rounding error". The hashes are just large integer numbers. Rounding does not apply at all, at least not the rounding of the floating-point variety. If the devs say it's a rounding issue, do they really understand the issue at all? I'd really like to know more about this issue, if only to know if it might still be there. Right now I am not confident it's resolved, to be honest.
EDIT: not implying the devs don't know what they're doing. What they did was brilliant - just commenting on this one issue.
Your client thought that there was a match where there wasn't one, because it was using a bad rounding algorithm elsewhere. Every client calculates everything itself, so order matching, for instance has to be entirely deterministic.
February 06, 2014, 06:49:50 PM
| 1.351 | BTC | 0.0045 | BTC/XCP bid | 0.0 | 0.0001 | 293 | 30f5918f95f7a0bb8334838a078fce7f1aec40dda79bf3794c7dccfffe3e3665
| 8.85181818 | XCP | 0.0045 | BTC/XCP ask | 0.0 | 0.0001 | 925 | ff462bdeca74370cf28da51088e7ec95a7c375387e260d8d727f74e61b75b8b4
I did a "counterpartyd market" and see that there seem to be two orders with the same price, but they're not getting matched. I suspect the amounts do not fully match up, however I can't see that in my windows client.
Is there a way to see the price more completely using the windows client? Right now it's impossible to know if the price is 0.00451 or 0.00459...
http://blockscan.com/order_book.aspx
One is 0.004519 and one is 0.004503
Yeah the client should really have the default 8 figures of precision.
The fee of the bid doesn't satisfy the requirements of the ask.
Prices don't have eight figures of precision, but rather twenty-eight.
February 06, 2014, 06:47:35 PM
| 1.351 | BTC | 0.0045 | BTC/XCP bid | 0.0 | 0.0001 | 293 | 30f5918f95f7a0bb8334838a078fce7f1aec40dda79bf3794c7dccfffe3e3665
| 8.85181818 | XCP | 0.0045 | BTC/XCP ask | 0.0 | 0.0001 | 925 | ff462bdeca74370cf28da51088e7ec95a7c375387e260d8d727f74e61b75b8b4
I did a "counterpartyd market" and see that there seem to be two orders with the same price, but they're not getting matched. I suspect the amounts do not fully match up, however I can't see that in my windows client.
Is there a way to see the price more completely using the windows client? Right now it's impossible to know if the price is 0.00451 or 0.00459...
http://blockscan.com/order_book.aspx
One is 0.004519 and one is 0.004503
Yeah the client should really have the default 8 figures of precision.
And perhaps an easier way to match the order. To take this order in full, currently I have to calculate 8.85181818 x 0.004519, a bit of a pain.
February 06, 2014, 06:38:42 PM
Unicode print issues should be fixed in Windows.
Guys, I just pushed out an overhaul of the Unicode handling code in Windows to both develop and master. Especially if you use Windows, please update your git repo to the newest.
Guys, I just pushed out an overhaul of the Unicode handling code in Windows to both develop and master. Especially if you use Windows, please update your git repo to the newest.
Great, it worked. Feeds visible now too, nice. And actually, it worked already in the repo I downloaded 3 hours ago!
February 06, 2014, 06:38:12 PM
Unicode print issues should be fixed in Windows.
Guys, I just pushed out an overhaul of the Unicode handling code in Windows to both develop and master. Especially if you use Windows, please update your git repo to the newest. Note that you shouldn't have to run powershell or anything like that...should work out of the box.
Also, for counterpartyd_build, I updated setup.py to make it more user friendly to do future updates of counterpartyd. All you have to do is run "setup.py update" instead of having to manually issue the git pull commands. Feel free to pull the newest counterpartyd_build commits from github as well. More info about this feature is at: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#id4
Guys, I just pushed out an overhaul of the Unicode handling code in Windows to both develop and master. Especially if you use Windows, please update your git repo to the newest. Note that you shouldn't have to run powershell or anything like that...should work out of the box.
Also, for counterpartyd_build, I updated setup.py to make it more user friendly to do future updates of counterpartyd. All you have to do is run "setup.py update" instead of having to manually issue the git pull commands. Feel free to pull the newest counterpartyd_build commits from github as well. More info about this feature is at: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#id4
Xnova you're the best. Can't wait to try this one !
February 06, 2014, 06:34:59 PM
| 1.351 | BTC | 0.0045 | BTC/XCP bid | 0.0 | 0.0001 | 293 | 30f5918f95f7a0bb8334838a078fce7f1aec40dda79bf3794c7dccfffe3e3665
| 8.85181818 | XCP | 0.0045 | BTC/XCP ask | 0.0 | 0.0001 | 925 | ff462bdeca74370cf28da51088e7ec95a7c375387e260d8d727f74e61b75b8b4
I did a "counterpartyd market" and see that there seem to be two orders with the same price, but they're not getting matched. I suspect the amounts do not fully match up, however I can't see that in my windows client.
Is there a way to see the price more completely using the windows client? Right now it's impossible to know if the price is 0.00451 or 0.00459...
February 06, 2014, 06:26:23 PM
Quote
We thought a lot about whether marketing could be done via bounties, but we concluded that this would quickly become unmanageable, as a real marketing push would require an absurd number of bounties. Since the marketer will essentially be salaried, community contributions are harder to incorporate into our funding plan, as they are impossible to determine beforehand. The Counterparty team, then, will be paying whomever we select regardless, but if community members are interested in donating, they can send BTC and XCP to this address: 1CWq53K95AZVkCPGGW7eEwivBvNzGVGH94
Cmon cough it up already. The man asks for a contribution: give it to him. I put a measly 10% of my burn. Its feeling very alone.
February 06, 2014, 06:21:33 PM
Unicode print issues should be fixed in Windows.
Guys, I just pushed out an overhaul of the Unicode handling code in Windows to both develop and master. Especially if you use Windows, please update your git repo to the newest. Note that you shouldn't have to run powershell or anything like that...should work out of the box.
Also, for counterpartyd_build, I updated setup.py to make it more user friendly to do future updates of counterpartyd. All you have to do is run "setup.py update" instead of having to manually issue the git pull commands. Feel free to pull the newest counterpartyd_build commits from github as well. More info about this feature is at: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#id4
Guys, I just pushed out an overhaul of the Unicode handling code in Windows to both develop and master. Especially if you use Windows, please update your git repo to the newest. Note that you shouldn't have to run powershell or anything like that...should work out of the box.
Also, for counterpartyd_build, I updated setup.py to make it more user friendly to do future updates of counterpartyd. All you have to do is run "setup.py update" instead of having to manually issue the git pull commands. Feel free to pull the newest counterpartyd_build commits from github as well. More info about this feature is at: http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#id4
February 06, 2014, 06:18:05 PM
Quote
this is a very rare, irreversible bug in the order matching (normally bugs like this are reversible, but not BTCpay
Can you perhaps explain what exactly the issue is? Or is it buried somewhere a couple of pages back in the forum?
Sure:
https://bitcointalksearch.org/topic/m.4957701
Basically, the rounding code for master and develop was different, so BTCpays for one did not match the other, and went to the wrong accounts (still Counterparty accounts though). As I understand, such a thing will probably almost never happen in the future again, because BTCpay (the only protocol-level irreversible part of Counterparty, besides proof-of-burn) and the rounding issues have been addressed permanently. Note I said almost never.
This event is sort of like Counterparty's version of Bitcoin's infamous blockchain fork. (though since we don't have mining, the analogy is tenuous). [Devs correct me on this]. Fortunately it happened early on, as opposed to when it happened for bitcoin.
I don't get it. When I ran "counterpartyd market" I saw that I had a match for my order along with an order match id. So I did a "counterpartyd btcpay --order-match-id
So "counterpartyd wallet" has been lying about the amount of XCP in my wallet. How could that happen? Even for alpha software, that's a bit unsettling.
And also, a comment to this being a "rounding error". The hashes are just large integer numbers. Rounding does not apply at all, at least not the rounding of the floating-point variety. If the devs say it's a rounding issue, do they really understand the issue at all? I'd really like to know more about this issue, if only to know if it might still be there. Right now I am not confident it's resolved, to be honest.
EDIT: not implying the devs don't know what they're doing. What they did was brilliant - just commenting on this one issue.
February 06, 2014, 05:54:47 PM
The Counterparty Team is looking to pay someone to do marketing
We have been contacted by several members of the community who are interested in helping out with Counterparty's marketing. It seems to us incongruous with Counterparty's 'project principles' to choose somebody without first telling the entire community that we are looking to pay someone to do PR for Counterparty. For now, we will be paying our marketer month-to-month (in XCP and BTC). We will start considering people now, and will stop considering them within three days (i.e. by to February 9); we will make our decision within seven days (i.e. by February 13), but reserve the right to decide
any time before then.
Here is a summary of what you should provide:
Applicants are expected to have a strong grasp of Counterparty's functionality, and will be asked to demonstrate it, as we believe marketing a protocol you are not familiar with is untenable.
Please PM me, cityglut, if you are interested in applying for the position, and I will provide you with an email address to which you may send your application.
That's great. May I ask which what funds will you pay him?We have been contacted by several members of the community who are interested in helping out with Counterparty's marketing. It seems to us incongruous with Counterparty's 'project principles' to choose somebody without first telling the entire community that we are looking to pay someone to do PR for Counterparty. For now, we will be paying our marketer month-to-month (in XCP and BTC). We will start considering people now, and will stop considering them within three days (i.e. by to February 9); we will make our decision within seven days (i.e. by February 13), but reserve the right to decide
any time before then.
Here is a summary of what you should provide:
- Your CV: What is your experience in marketing (especially in finance), both in- and outside of the crypto community? Have you done marketing work for any other cryptocurrencies? If so, describe in detail what you helped them achieve, and provide a reference who can confirm your
listed contributions. - Your connections: Whom do you know in- and outside of the crypto community who would be valuable in Counterparty's marketing efforts? Please provide enough evidence of your relationship with him or her, so that we can determine whether this relationship may be profitable.
- Your angle: If you had the position of marketing lead for Counterparty, what aspect(s) of Counterparty would you emphasize?
- Your plan: Please provide a very thorough marketing plan for the 30 days after you are hired, including a list of 'milestones' and a 'timeline'. Your timeline should split up the 30 day period into four or five pieces, so that your timeline will essentially consist of an approximately week-by-week plans. We of course understand that there are things which are out of your control, and that consequently your cannot guarantee the precision of your marketing plan up to one week; nevertheless, we would like plans to err on the side of being overly-rigorous.
Applicants are expected to have a strong grasp of Counterparty's functionality, and will be asked to demonstrate it, as we believe marketing a protocol you are not familiar with is untenable.
Please PM me, cityglut, if you are interested in applying for the position, and I will provide you with an email address to which you may send your application.
We thought a lot about whether marketing could be done via bounties, but we concluded that this would quickly become unmanageable, as a real marketing push would require an absurd number of bounties. Since the marketer will essentially be salaried, community contributions are harder to incorporate into our funding plan, as they are impossible to determine beforehand. The Counterparty team, then, will be paying whomever we select regardless, but if community members are interested in donating, they can send BTC and XCP to this address: 1CWq53K95AZVkCPGGW7eEwivBvNzGVGH94
Yes.
You guy rocks.
February 06, 2014, 05:40:49 PM
Price manipulation (troll orders)
Currently it's possible to manipulate the price of any asset easily by entering orders with zero fees.
So suppose the order book has a buy order of A@100 with a required fee of 0.0001. I want to manipulate the last price of A, so I enter a buy order of A@999 with a required fee of zero. Then I sell a tiny amount of A without providing a fee. The order of A@100 will not match because of insufficient fee, but the order of A@999 will match. Now I have artificially created a last price of A@999.
Solution (?):
Same fee for everyone, so you can not cherry-pick your own orders and manipulate the last price by misusing the fee. I think a standard fee is very sensible, why haggle about the fee that is miniscule compared to the value of most orders? It's pointless. Just set a fixed fee for everyone.
Settlement issue
Perhaps I'm seeing it the wrong way, but if an order matches, it's not settled yet. If I'm selling an asset, and I get a match, it's like having a put option which expires when the order expires. If the market moves against me, I can choose not to btcpay my order and it will expire without settling. If the market moves in my advantage, I btcpay and lock in a profit. This seems very problematic to me.
Solution (?):
When someone matches your order, it should go through. Isn't it somehow possible to avoid btcpay? Isn't it possible to structure a transaction on the btc network that is such that if for instance address 1abcde fills my order, that my btc in escrow are sent to 1abcde, automatically settling the transaction without having to do a btcpay? I know, you don't know the address of the one that matches your order in advance, but there has to be a way around that.
Apologies if this has already been addressed!
Currently it's possible to manipulate the price of any asset easily by entering orders with zero fees.
So suppose the order book has a buy order of A@100 with a required fee of 0.0001. I want to manipulate the last price of A, so I enter a buy order of A@999 with a required fee of zero. Then I sell a tiny amount of A without providing a fee. The order of A@100 will not match because of insufficient fee, but the order of A@999 will match. Now I have artificially created a last price of A@999.
Solution (?):
Same fee for everyone, so you can not cherry-pick your own orders and manipulate the last price by misusing the fee. I think a standard fee is very sensible, why haggle about the fee that is miniscule compared to the value of most orders? It's pointless. Just set a fixed fee for everyone.
Settlement issue
Perhaps I'm seeing it the wrong way, but if an order matches, it's not settled yet. If I'm selling an asset, and I get a match, it's like having a put option which expires when the order expires. If the market moves against me, I can choose not to btcpay my order and it will expire without settling. If the market moves in my advantage, I btcpay and lock in a profit. This seems very problematic to me.
Solution (?):
When someone matches your order, it should go through. Isn't it somehow possible to avoid btcpay? Isn't it possible to structure a transaction on the btc network that is such that if for instance address 1abcde fills my order, that my btc in escrow are sent to 1abcde, automatically settling the transaction without having to do a btcpay? I know, you don't know the address of the one that matches your order in advance, but there has to be a way around that.
Apologies if this has already been addressed!
Manipulation by small amounts is not an issue. Also, it's generally a good idea to take volume into account when determining price.
It's not possible to avoid btcpay, and the spread with asset pairs including BTC will indeed be wider than with others.
February 06, 2014, 05:39:58 PM
The Counterparty Team is looking to pay someone to do marketing
We have been contacted by several members of the community who are interested in helping out with Counterparty's marketing. It seems to us incongruous with Counterparty's 'project principles' to choose somebody without first telling the entire community that we are looking to pay someone to do PR for Counterparty. For now, we will be paying our marketer month-to-month (in XCP and BTC). We will start considering people now, and will stop considering them within three days (i.e. by to February 9); we will make our decision within seven days (i.e. by February 13), but reserve the right to decide
any time before then.
Here is a summary of what you should provide:
Applicants are expected to have a strong grasp of Counterparty's functionality, and will be asked to demonstrate it, as we believe marketing a protocol you are not familiar with is untenable.
Please PM me, cityglut, if you are interested in applying for the position, and I will provide you with an email address to which you may send your application.
That's great. May I ask which what funds will you pay him?We have been contacted by several members of the community who are interested in helping out with Counterparty's marketing. It seems to us incongruous with Counterparty's 'project principles' to choose somebody without first telling the entire community that we are looking to pay someone to do PR for Counterparty. For now, we will be paying our marketer month-to-month (in XCP and BTC). We will start considering people now, and will stop considering them within three days (i.e. by to February 9); we will make our decision within seven days (i.e. by February 13), but reserve the right to decide
any time before then.
Here is a summary of what you should provide:
- Your CV: What is your experience in marketing (especially in finance), both in- and outside of the crypto community? Have you done marketing work for any other cryptocurrencies? If so, describe in detail what you helped them achieve, and provide a reference who can confirm your
listed contributions. - Your connections: Whom do you know in- and outside of the crypto community who would be valuable in Counterparty's marketing efforts? Please provide enough evidence of your relationship with him or her, so that we can determine whether this relationship may be profitable.
- Your angle: If you had the position of marketing lead for Counterparty, what aspect(s) of Counterparty would you emphasize?
- Your plan: Please provide a very thorough marketing plan for the 30 days after you are hired, including a list of 'milestones' and a 'timeline'. Your timeline should split up the 30 day period into four or five pieces, so that your timeline will essentially consist of an approximately week-by-week plans. We of course understand that there are things which are out of your control, and that consequently your cannot guarantee the precision of your marketing plan up to one week; nevertheless, we would like plans to err on the side of being overly-rigorous.
Applicants are expected to have a strong grasp of Counterparty's functionality, and will be asked to demonstrate it, as we believe marketing a protocol you are not familiar with is untenable.
Please PM me, cityglut, if you are interested in applying for the position, and I will provide you with an email address to which you may send your application.
We thought a lot about whether marketing could be done via bounties, but we concluded that this would quickly become unmanageable, as a real marketing push would require an absurd number of bounties. Since the marketer will essentially be salaried, community contributions are harder to incorporate into our funding plan, as they are impossible to determine beforehand. The Counterparty team, then, will be paying whomever we select regardless, but if community members are interested in donating, they can send BTC and XCP to this address: 1CWq53K95AZVkCPGGW7eEwivBvNzGVGH94
Yes.
February 06, 2014, 05:39:00 PM
The Counterparty Team is looking to pay someone to do marketing
We have been contacted by several members of the community who are interested in helping out with Counterparty's marketing. It seems to us incongruous with Counterparty's 'project principles' to choose somebody without first telling the entire community that we are looking to pay someone to do PR for Counterparty. For now, we will be paying our marketer month-to-month (in XCP and BTC). We will start considering people now, and will stop considering them within three days (i.e. by to February 9); we will make our decision within seven days (i.e. by February 13), but reserve the right to decide
any time before then.
Here is a summary of what you should provide:
Applicants are expected to have a strong grasp of Counterparty's functionality, and will be asked to demonstrate it, as we believe marketing a protocol you are not familiar with is untenable.
Please PM me, cityglut, if you are interested in applying for the position, and I will provide you with an email address to which you may send your application.
That's great. May I ask which what funds will you pay him?We have been contacted by several members of the community who are interested in helping out with Counterparty's marketing. It seems to us incongruous with Counterparty's 'project principles' to choose somebody without first telling the entire community that we are looking to pay someone to do PR for Counterparty. For now, we will be paying our marketer month-to-month (in XCP and BTC). We will start considering people now, and will stop considering them within three days (i.e. by to February 9); we will make our decision within seven days (i.e. by February 13), but reserve the right to decide
any time before then.
Here is a summary of what you should provide:
- Your CV: What is your experience in marketing (especially in finance), both in- and outside of the crypto community? Have you done marketing work for any other cryptocurrencies? If so, describe in detail what you helped them achieve, and provide a reference who can confirm your
listed contributions. - Your connections: Whom do you know in- and outside of the crypto community who would be valuable in Counterparty's marketing efforts? Please provide enough evidence of your relationship with him or her, so that we can determine whether this relationship may be profitable.
- Your angle: If you had the position of marketing lead for Counterparty, what aspect(s) of Counterparty would you emphasize?
- Your plan: Please provide a very thorough marketing plan for the 30 days after you are hired, including a list of 'milestones' and a 'timeline'. Your timeline should split up the 30 day period into four or five pieces, so that your timeline will essentially consist of an approximately week-by-week plans. We of course understand that there are things which are out of your control, and that consequently your cannot guarantee the precision of your marketing plan up to one week; nevertheless, we would like plans to err on the side of being overly-rigorous.
Applicants are expected to have a strong grasp of Counterparty's functionality, and will be asked to demonstrate it, as we believe marketing a protocol you are not familiar with is untenable.
Please PM me, cityglut, if you are interested in applying for the position, and I will provide you with an email address to which you may send your application.
We thought a lot about whether marketing could be done via bounties, but we concluded that this would quickly become unmanageable, as a real marketing push would require an absurd number of bounties. Since the marketer will essentially be salaried, community contributions are harder to incorporate into our funding plan, as they are impossible to determine beforehand. The Counterparty team, then, will be paying whomever we select regardless, but if community members are interested in donating, they can send BTC and XCP to this address: 1CWq53K95AZVkCPGGW7eEwivBvNzGVGH94
February 06, 2014, 05:36:28 PM
Ok I sent PhantomPhreak a PM. I hope he'll reimburse me like he promised.
Did I someone kinda rob me of my BTC? Because they did arrive, correct? Has someone been exploiting this bug?
So my 0.4 bitcoin went to 1GbkV2QgQ2jqHk8yjgcdwEMfLC1Y6oGSMF? Hey 1GbkV2QgQ2jqHk8yjgcdwEMfLC1Y6oGSMF, how about giving me my XCP?
Would be the right thing to do if it were an honest mistake.
Did I someone kinda rob me of my BTC? Because they did arrive, correct? Has someone been exploiting this bug?
So my 0.4 bitcoin went to 1GbkV2QgQ2jqHk8yjgcdwEMfLC1Y6oGSMF? Hey 1GbkV2QgQ2jqHk8yjgcdwEMfLC1Y6oGSMF, how about giving me my XCP?
Would be the right thing to do if it were an honest mistake.
February 06, 2014, 05:07:09 PM
In my mind, I like to compare XCP and MSC as Linux and M$ (with the broken IE), and http://blog.mastercoin.org/2014/02/06/we-are-hiring-developers-developers-developers/ has just confirmed half of it
How about these to further differentiate XCP and MSC:
- All funds from the exodus address are accessible by the MSC team. This is evidenced by the team being able to refund coins received after the IPO period
- Even after receiving all of the funds, the team still gets further dev coins which amounts to 10% inflation
Mastercoin revokes one of the core tenets of Bitcoin - you can reverse transactions (by specifying that your 'savings' account is compromised). - When buying virtual assets your funds are held in escrow until feedback is sent. The time out for leaving feedback is 60 days. If negative feedback is received, funds are destroyed.
Jump to: