The takeaway should be that Symbiont has a lot more resources than Counterparty has alone, so we'll be working on products that are orthogonal to Counterparty *as well*. (We'll also have more resources than ever dedicated to Counterparty itself.)
Are you speaking from the perspective of Counterparty or Symbiont? If the former, you're saying that the Counterparty dev group will be working (in part) on products orthogonal to Counterparty? If the latter, is Symbiont currently working on any product that incorporates Counterparty? When I wrote 'we', I meant 'Symbiont'; Symbiont is doing a lot with Counterparty.
|
|
|
Sounds to me not too different with the overstock situation. I feel this statement is trying to decouple counterparty and Symbiont. yep. sounds to me they want to abandon it. it's a very polite way to say "we're done with counterparty and not interested in it anymore, we're making something cooler". That's not what the post said at all. The technology that Symbiont has developed outside of Counterparty does not overlap or compete with Counterparty at all. They're different things for different uses, one being private network/private blockchain/permissioned access, and the other (Counterparty) being public blockchain, public ledger, open access. It's kind of like a computer manufacturer who only made desktops now releasing their first laptop model. Sure, they're both computers, but they have different uses, and there are certain cases where one is clearly more appropriate than the other. To reiterate, Counterparty is still being actively supported and developed (by symbiont staff members, nonetheless). You can see that just by looking at the github. That's correct, except laptops vs. desktops isn't a great metaphor, because laptops *are* competing with desktops to some degree. A better comparison would be laptops and phones, where neither competes with the other at all. The takeaway should be that Symbiont has a lot more resources than Counterparty has alone, so we'll be working on products that are orthogonal to Counterparty *as well*. (We'll also have more resources than ever dedicated to Counterparty itself.)
|
|
|
For those that don't already know, Symbiont is currently hiring developers in the New York area. We're looking in particular for a front-end/full-stack web dev.; but we're also interested in other applicants with experience developing cryptocurrency and distributed systems software. Shoot me an e-mail or a PM if you think you'd be a good fit! See Stack Overflow Careers for a detailed job description for the front-end spot.
|
|
|
1)https://github.com/bitcoin/bitcoin/commit/41076aad0cbdfa4c4cf376e345114a5c29086f81 seems OP_ CHECKLOCKTIMEVERIFY merging into mainline Although serial Counterparty disparager Flavien "coinprism" charlon suggests counterparty cannot benefit from this, I think he may be mistaken. Can anyone chime in to suggest otherwise? Sounds very interesting. I'd like to know too. Counterparty doesn't benefit from the introduction of `OP_CHECKLOCKTIMEVERIFY`, but you can easily code identical (or much greater) functionality into Counterparty smart contracts. Counterparty already has infinitely more features than Colored Coins could ever have, because Colored Coins is just Bitcoin + tokens. To add a feature to Colored Coins, you have to fork Bitcoin itself; to add a feature to Counterparty, you just have to write it up and send it out.
|
|
|
how far are smart contracts away from being implemented into mainnet?
There's still a lot of development and testing to be done, but we're making very good progress. (See, e.g., this upstream PR made this morning: https://github.com/ethereum/pyethereum/pull/238#issuecomment-87641778). It's very important to get the launch right the first time (for security reasons, if nothing else).
|
|
|
The GUI comes with a standalone installer for Windows and a MacOS installer coming soon, and will be configured to run in ‘light’ mode by default, meaning that users will no longer have to run a local instance of bitcoin/counterparty clients or download the blockchain to get started. Global consensus is fragile, so I'm wondering: what is the security model behind this? How could I know whether the data provider for the light mode is honest? You can parse cilent-side the transaction that the server (with access to the Bitcoin UTXO pool) tells you to sign. Make 100% certain that it sends the right funds to the right place, e.g.
|
|
|
How's status on smart contracts? Rumors on Reddit that Ethereum scraps Serpent. CounterParty fares any better? Serpent has lost funding. Some projects have been written in Serpent, but according to Vitalik: I personally will not have time to continue Serpent development at anything more than the current glacial pace [...] Unless someone from the Counterparty community wanted to maintain Serpent, it's dead. It should be possible to fork cpp-ethereum and make Solidity compatible with Counterparty, but the severe limitations in Solidity make me question Ethereum's programmable contract concept. On the one hand the core concept itself is quite vulnerable to language ecosystem takeovers, because these are miniscule, poorly maintained designer languages based on experimental compilers and VMs. OTOH is the concept of Turing complete code really that much better than a semi-restricted DSL, or even hard coding features into the protocol? If your idea of Turing complete is Python, well Serpent is downright bad. It lacks basic programming features and is in general the opposite of confidence inspiring. Solidity is not much better. They still don't have arrays. I'm not sure it's even worth copying, because it would be trivial for a better approach to crush whatever sliver of a network effect Ethereum has with something better written or written with a better architecture. [...] Crafting beautiful UX is infinitely more valuable than offering a Turing Complete™ platform. Isn't it more viable for anyone with an interesting "contract" idea to just visit https://github.com/CounterpartyXCP/counterpartyd and create a damn pull request? What is so hard or bad about that? It works plenty well for Bitcoin. Who are the industry leaders who don't think that's good enough? http://www.reddit.com/r/counterparty_xcp/comments/2y0apx/contract_news/Our compatibility with Ethereum smart contracts is at the virtual machine level, so it doesn't matter what language (Serpent, Solidity, LLL, etc.), you write the contracts in---they'll run on both Counterparty and Ethereum the same. Between the Counterparty and the Ethereum communities, we'll figure out what languages we want to write contracts in and develop those.
|
|
|
Looks like counterparty has a problem getting normalized balances of compressed addresses. Uncompressed address: { "jsonrpc":"2.0", "id":0, "method":"get_normalized_balances", "params":{ "addresses":[ "16P8vY1gVspGG8JeeWK8MSYzX4B9yqcJbF" ] } } Gives response: { "jsonrpc": "2.0", "result": [], "id": 0 } Compressed: { "jsonrpc":"2.0", "id":0, "method":"get_normalized_balances", "params":{ "addresses":[ "12ze3N3Qeet6ji82rw8JqaepTL9uUxihFX" ] } } Gives response: { "jsonrpc": "2.0", "id": 0, "error": { "message": "Invalid params", "code": -32602 } } Looking into it. See https://github.com/CounterpartyXCP/counterpartyd/issues/720
|
|
|
When this issue will be fixed cause Poloniex has no ETA for fixing FLDC deposits ? They said it's on Counterparty side.
I'm working with him now to resolve the technical issues.
|
|
|
As with its original BitLicense proposal, DFS will accept comments, but only for thirty days in this round. At the expiration of those thirty days, DFS will likely prepare a final version and then publish it in the state Register. DFS extended the last comment period in response to industry outcries for more time. I doubt that there will be an extension granted, so if you plan to file a comment, it should be done quickly.
Who should file a comment? Altcoin developers might want the final rule to more clearly define what it means to “administer” a digital currency. Multisig developers might ask for a clearer definition of custody, “controlling” or “holding”. They might even argue for a specific exemption. http://www.coindesk.com/bitlicense-2-0-latest-revisions-mean-bitcoin-businesses/Would the Counterparty team want to clarify things here? I don't know what kind of clarification you're looking for. I don't have any comment to make on that article or BitLicense. (Obviously, we don't administer XCP or any other currency.)
|
|
|
There is a bit of confusion in the air with regards to some of the recent quotes by the Overstock CEO and the various interpretations of them. It's arguable that they do seem to be getting progressively vague and I can see why some might get the idea this is Byrne distancing himself, while others adopt the mindset it's business as usual in the background and recent price action is just an excuse to take advantage of a price dip based on skewed info. I'd expect the developers to be under some sort of NDA preventing them from saying too much beyond what's already said so I don't think you will be able to rely on full clarifications right now.
It's a shame to see hot/cold snippets trickle down into the news then waves of buying or selling based simply on said snippets, although it's not as if you would expect market participants to not react to them. A binary yes or no, or no news at all would be preferable. However Let's not forget CounterParty has great value potential since far before Medici was ever announced, has continued to show great promise more than a year later with incredible unexpected additions like turing complete scripting language, multisig, to name just two. Hope that we don't stay in a cycle of ups and downs with everything revolving around the currently non-existant Medici
Yes, the situation is unclear---sorry, we just can't say much at the moment. There'll be some relevant (positive) announcements very soon, though! Suffice it to say that Evan, Robby and I will all be working on Counterparty for the forseeable future. Please explain to me how this announcement is positive. Obviously I wasn't talking about Evan and Robby leaving Overstock. And Overstock is still using Counterparty for Medici. (This has been reaffirmed publicly very recently.) I'm advising them personally on their technical design.
|
|
|
well, without knowing further it is an unethical business strategy by overstock.
No its not. Its called a "business decision." Still stings though. There wasn't any unethical business strategy. Evan and Robby left voluntarily.
|
|
|
Doesn't the fact that OP_RETURN is prunable could have nasty effects on the mid/long term ?
i think this was covered a while back, it seem to be no issue I am honestly curious about that. Can anyone point me to somewhere where this has been discussed before ? Nope, no nasty effects. It really is ideal that that Counterparty data be prunable (as our multisig-encoded data are now).
|
|
|
Can someone explain medici?
Medici is to stocks and shares what bitcoin is to money. edit: bitcoin with a lower case b, as both use the Bitcoin network. So it's like asset exchange on Next? Forgive my ignorance Counterparty has its own asset exchange. Medici brings regulatory compliance, user interfaces, professional services, off-chain stuff, etc., so that users can trade shares of public companies, e.g., (on Counterparty) legally and easily. Counterparty is the primary technological platform; Medici is an application and service. (Think Bitcoin/Coinbase.)
|
|
|
hopefully someone can go today and we can see what the real deal is. http://www.meetup.com/BitcoinCenterNYC/events/213645872/Satoshi Monday ft. Overstock's Medici PlatformThis Monday, January 19th, Satoshi Square will be having a presentation from Overstock.com about their upcoming Medici crypto-equity platform.
Good news??? Haha, I was there. Was anyone else? only got the snippets from here, don't know if they recorded it https://twitter.com/BitcoinCenterNYif this guy rephrases correctly it will be build on top of counterparty They did record it, and yes, [he said] it will be built on top of Counterparty.
|
|
|
hopefully someone can go today and we can see what the real deal is. http://www.meetup.com/BitcoinCenterNYC/events/213645872/Satoshi Monday ft. Overstock's Medici PlatformThis Monday, January 19th, Satoshi Square will be having a presentation from Overstock.com about their upcoming Medici crypto-equity platform.
Good news??? Haha, I was there. Was anyone else?
|
|
|
There is a bit of confusion in the air with regards to some of the recent quotes by the Overstock CEO and the various interpretations of them. It's arguable that they do seem to be getting progressively vague and I can see why some might get the idea this is Byrne distancing himself, while others adopt the mindset it's business as usual in the background and recent price action is just an excuse to take advantage of a price dip based on skewed info. I'd expect the developers to be under some sort of NDA preventing them from saying too much beyond what's already said so I don't think you will be able to rely on full clarifications right now.
It's a shame to see hot/cold snippets trickle down into the news then waves of buying or selling based simply on said snippets, although it's not as if you would expect market participants to not react to them. A binary yes or no, or no news at all would be preferable. However Let's not forget CounterParty has great value potential since far before Medici was ever announced, has continued to show great promise more than a year later with incredible unexpected additions like turing complete scripting language, multisig, to name just two. Hope that we don't stay in a cycle of ups and downs with everything revolving around the currently non-existant Medici
Yes, the situation is unclear---sorry, we just can't say much at the moment. There'll be some relevant (positive) announcements very soon, though! Suffice it to say that Evan, Robby and I will all be working on Counterparty for the forseeable future.
|
|
|
Have any additional devs been hired now that Robby and Evan are working full time on Medici?
Robby and Evan are still contributing to Counterparty. But yes, we recently hired another full-time developer.
|
|
|
|