Just came to clarify that I have NOT been hired by Gavin. We are just talking  :)

If I could spend all the time in the world working on cryptocurrency...well I would be a happy camper. As it stands there is only a limited amount of time in the day...and I have a wife and child to go and take care of and spend time with. Hopefully I could work on both projects in the future. But first thing's first, I gotta get this down.

Just now read the article and wanted to make a comment. Particularly in regards to what you'd do differently. Doing all of this in memory kind of defeats the purpose of having stored data. It adds speed, that is true, but there are problems in regards to having truly decentralized applications and to have them be verifiable. On the other hand, the way Bitshares operates it would likely not be an issue mainly due to the way that the consensus algo operates. As for the merkle tri-graph, I would like to hear why it is redundant. It is very much expensive, that is true, but if you want a truly decentralized and trustless application, it is somewhat necessary. But again, I can see why you'd do it this way due to the Bitshares algo as the goal in the algo is not to be trustless, just to be decentralized. There are tradeoffs to everything. In any case. Hope all is well.

Quote from: toast on December 25, 2015, 08:24:13 PM

QuoteEthereum is attempting to pivot to making a completely flexible and completely interchangeable consensus mechanism in each shard

That's not what he's saying. Ethereum plans to use Casper for all shards (it doesn't even make sense to formulate it this way IMO). What he's saying is if you wanted to fork ethereum and make a *new* network, it will be easier to use your own consensus mechanism.

Are you saying that it doesn't make sense to use Casper for all shards? Or what I was suggesting? In any case, thanks for the clarification.

I was reading through Vitalik's newer article https://blog.ethereum.org/2015/12/24/understanding-serenity-part-i-abstraction/ and it occured to me while reading it that it appears that Ethereum is attempting to pivot to making a completely flexible and completely interchangeable consensus mechanism in each shard, enabling small levels of centralization for economies of scale when changing state while still being all around decentralized in the grand scheme of their chain.

This struck me as the perfect use case for a DPOS style consensus algorithm to be the consensus basis for these shards and then to push into the massive scheme overall. Particularly in the case of graphene this allows for the benefits of centralization while also keeping things relatively decentralized for those who care enough.  I hope this doesn't get moved...I would like to hear your thoughts on the matter.

I am holding onto BTS because I believe that along with Ethereum, it is going to be the only other cryptocurrency 2.0 project to make a difference...and I actually see the model of DPOS melding quite well into the new Ethereum Serenity model if I understand it correctly.

I wonder why it's more of a China thing...adoption numbers would say otherwise :/

Essentially what Bitshares is doing is selling derivatives of different cryptocurrencies in their attempt to be a decentralized exchange. Would not this ruling legally harm the protocol and those working for it? Please discuss and alleviate my concerns.


http://www.seattletimes.com/business/markets/bitcoin-community-has-its-say-on-us-commodity-ruling/

You're missing a third. Jaak.

Quote from: sittingduck on August 27, 2015, 02:50:24 AM
Your post in a no sequitur.  This has nothing to do with the number of witnesses. 


Sent from my iPhone using Tapatalk

I hope you were not referring to my post because I don't recall discussing the number of witnesses.

Needs Ethereum.

Yeah I have to say I don't think this is a good idea. For one, I'm beginning to think there won't be enough volume (most definitely at first) to make it worth the overhead that 1 second blocks will produce. While it is quite the technical achievement, remember, this is far more than mastercard or visa can handle combined on any given day...that's a lot of transactions going on. By all means keep the 1 second blocks. It's allowing BTS to develop an incredible niche market for high speed trading. However, with that bloat comes security issues...there are far less people running full nodes as I have expressed many times as a security flaw and that there should be a brainstormed way to incentivize non witness/delegate nodes to run full chains. Even then! I can still accept that because of the light wallet web querying. But this is really pushing the envelope here. I know you're very big on low latency environments (which I think is awesome) however I think this is really compromising security especially in a realm where not everyone is on to vote as it is, and the voting time periods have been extended, so there's even the chance that the attacker wouldn't be kicked out. I truly think that this is a flawed approach to the issue of latency as it is expecting unrealistic expectations from shareholders and from your average participant. I hope you will consider this opinion and choose not to move forward with this and find another way to reach your low latency expectations. I should also add that while it may not be your intention, it does make the witnesses look a tad greedy when it comes to their payment schedule as they're sacrificing what really makes this unique...decentralization...for more pay (I can't really blame them for wanting more pay, but I also have stake in the product, so I must make my voice heard on the issue). Thanks again.

The reason I suggested gitter is that it keeps up to date with the PRs and commits on the github page and its got a direct upload link to the page. Is there a reason folks are opposed to the idea of Gitter? I like IRC, but I just think Gitter is superior.

Quote from: luckybit on August 18, 2015, 02:06:57 AM

Quote from: Ben Mason on August 17, 2015, 02:55:23 PM
I agree! I'm all for patience and strategy but if the important stuff is ready, let's get more eyes on 2.0.! Thousands of devs  could suddenly be incentivised to start building interfaces.

Bitshares 2.0 needs volume more than anything else, it needs to find ways to take advantage of it's 100,000 transactions per second, and we need to fully take advantage of the innovation momentum.

We might have 6 months lead time before everyone else catches up to Bitshares 2.0, so in that time you would want to do everything you can to boost volume, bring in new users, and show the world what you can do with these specs. It's kind of like video card or GPU developers don't sell the cards just on specs, they show some demos.

We need some demo products to prove to people that Bitshares 2.0 can do what other platforms can't. Once people realize you can't do it on Bitcoin no matter how much Bitcoin developers try to claim otherwise, then Bitshares 2.0 will find it's niche.

I think Bitshares 2.0 has plenty of opportunities in the ATM market, the exchange sites, which will now be easy to set up and wont require regulations, the majority of exchanges host other people's money, are money transmitters, probably aren't even profitable, and they could all be convinced to switch over to Bitshares 2.0 or else lose competitive advantage.

Perhaps Shapeshift could use Bitshares 2.0 on the backend or something like Shapeshift, and then expand out from there. My opinion is Minebitshares can be leveraged.

Better yet, you could run a clone of shapeshift on Ethereum for decentralized access and then have Bitshares be the backend trading for it. Hardware integrated with BTS...liking the sound of that.

Any news on the programmability of smart contracts on the Graphene platform? Any docs on how to develop a smart contract in Graphene? If not, where could I learn more and create documentation?

The community has its good sides and it has its downsides. I haven't been contributing to the code like I promised I would because something came up for a project I've been working on for a long time. You may very well see me eventually and I intend to contribute some of the UI designs I intended to once this first step of the project is done. If only there were 48 hours in a day, right?