Quote from: clayop on April 24, 2015, 01:41:15 AM

Quote from: lzr1900 on April 24, 2015, 12:14:13 AM
summer?Means nothing will happen on bitshares this 3-5months.
sell signal.

It's not a sell signal. HODL signal

The difference between an investor and a trader.  Traders chase shiny object while investors sit on gold.

My question:

Can you give any more details about how we are going to generate more fees to become deflationary again? Is it by more of perfecting the product & making it accessible, or is it by strategic partnerships that cant be disclosed?

I have three related questions:

I myself can't see a better system than DPOS for BitAssets but maybe you can. Since you (BM) said on a mumble hangout two weeks ago that the Bitshares team is working on getting the fundamentals right (industrial grade blockchain technology, scaling etc.)...

1) Does the Bitshares team consider any changes to the consensus mechanism (DPOS at the moment)? Bitsaphire has suggested a few very interesting ideas in a mumble session about two weeks ago.
2) Do you see voter apathy as a problem? Voter apathy having two dimensions: a) Quantitative: amount of shares that votes. b) Quantitative: quality of shareholders decisions.
3) How fundamental is the consensus mechanism? How easy / difficult is it to replace it?


If this is better answered on the forum I can open a tread too...

Quote from: lzr1900 on April 24, 2015, 12:14:13 AM
summer?Means nothing will happen on bitshares this 3-5months.
sell signal.

It's not a sell signal. HODL signal

Quote from: yellowecho on April 24, 2015, 12:39:44 AM

Quote from: lzr1900 on April 24, 2015, 12:14:13 AM
summer?Means nothing will happen on bitshares this 3-5months.
sell signal.

you never have anything positive to say.  troll troll troll.
you're not an investor, you're a complainer.

you like it or not.
this is truth.

Quote from: lzr1900 on April 24, 2015, 12:14:13 AM
summer?Means nothing will happen on bitshares this 3-5months.
sell signal.

you never have anything positive to say.  troll troll troll.
you're not an investor, you're a complainer. 

summer?Means nothing will happen on bitshares this 3-5months.
sell signal.

Quote from: bytemaster on April 23, 2015, 05:20:40 PM
BitUSD 3.0 will be different than BitUSD

Combined with the statement that they will exist in parallel  = very very bad idea!

the old bitUSD and (short bitUSD) should have a way to exit...if both systems exist in parallel it should be the same bitUSD to let them do just that.

Quote from: bytemaster on April 23, 2015, 07:51:00 PM
I think hard forks should be few and far between so everyone can rely on a stable platform rather than a moving target.

Agreed, but that is very different than "our LAST hard fork".

Also, as long as the API for Turing complete smart contacts (or DApps, etc.) does not change with the hard fork, I see no problem with having hard forks as frequently as once a year (if there is something worth to update that is). Changes of that nature would not affect any of the work other developers have done to build on top of BitShares but could provide much needed improvements to the protocol.

Quote from: arhag on April 23, 2015, 07:48:12 PM

Quote from: bytemaster on April 23, 2015, 05:20:40 PM
When we announce the roadmap will be included... but it will only have 1 item on it and that is turing complete smart contracts which will be our LAST hard fork.

That's a ridiculous statement. Unless by "our LAST hard fork" you mean the last one done with a hard fork block number decided by the core devs in an update to the client instead of through a decentralized hard fork voting mechanism built into the blockchain protocol.

I can think of so many improvements to the BitShares protocol for the future which simply cannot be replicated with Turing complete smart contracts (and some are more than just improvements to the consensus protocol). The LAST hard fork of BitShares will occur when BitShares is on a steep downward path to insignificance and obsolescence. Until then hard forks are how the protocol improves and stays relevant against the competition (of course not too frequently as it matures). Even protocols critical to the Internet infrastructure need to be updated from time to time (e.g. IPv4 to IPv6).

I think hard forks should be few and far between so everyone can rely on a stable platform rather than a moving target.   There is no point in hard-forking to add new features if the core features are not being utilized.

Quote from: bytemaster on April 23, 2015, 05:20:40 PM
When we announce the roadmap will be included... but it will only have 1 item on it and that is turing complete smart contracts which will be our LAST hard fork.

That's a ridiculous statement. Unless by "our LAST hard fork" you mean the last one done with a hard fork block number decided by the core devs in an update to the client instead of through a decentralized hard fork voting mechanism built into the blockchain protocol.

I can think of so many improvements to the BitShares protocol for the future which simply cannot be replicated with Turing complete smart contracts (and some are more than just improvements to the consensus protocol). The LAST hard fork of BitShares will occur when BitShares is on a steep downward path to insignificance and obsolescence. Until then hard forks are how the protocol improves and stays relevant against the competition (of course not too frequently as it matures). Even protocols critical to the Internet infrastructure need to be updated from time to time (e.g. IPv4 to IPv6).

Quote from: Ander on April 23, 2015, 06:10:13 PM

Quote from: nomoreheroes7 on April 23, 2015, 06:05:44 PM
How concrete is "this summer"? I remember quite a few things were supposed to be coming "last December" that never materialized...also, summer is kind of broad. I like to think of summer as being here as soon as the sun comes out (May - June), but summer can technically be considered active until late September or so.

"This summer" will end up being mid 2016, just like "1.0 by christmas" is Dec 25, 2015. :P

'Oh, you thought we meant Northern Hemisphere summer!?'  :P

Quote from: bytemaster on April 23, 2015, 05:20:40 PM

Quote from: xeroc ¯\_(ツ)_/¯ on April 23, 2015, 09:22:00 AM
- how long are your monday meetings?
- what can possible be more important than non-classified talk? ( :P )
- how is the bitasset3.0 proposal implemented in parallel to bitassets1.0?
- will it be the "same" market/asset just an extra set of features? or will it be a different token?
- will bitassets3.0 be a 1.0 feature?
- when will we have a rough roadmap that can be put on the webpage?

Monday meetings are from 10 am through lunch. 
We will share those plans with you once we get everything ready for public consumption (this summer)
BitUSD 3.0 will be different than BitUSD
1.0 has been postponed due to BitAssets 3.0...
We will have a documented, tested, stable protocol definition this summer that will not need to change that includes the referral system

We are implementing the "implement then announce" rather than the "announce and then implement" approach to avoid missing deadlines and killing buzz or confusing the market.   When we announce the roadmap will be included... but it will only have 1 item on it and that is turing complete smart contracts which will be our LAST hard fork.

BitUSD is like...



BitUSD 3.0 is the one that will actually sell

Quote from: nomoreheroes7 on April 23, 2015, 06:05:44 PM
How concrete is "this summer"? I remember quite a few things were supposed to be coming "last December" that never materialized...also, summer is kind of broad. I like to think of summer as being here as soon as the sun comes out (May - June), but summer can technically be considered active until late September or so.

"This summer" will end up being mid 2016, just like "1.0 by christmas" is Dec 25, 2015. :P

Quote from: bytemaster on April 23, 2015, 05:20:40 PM

Quote from: xeroc ¯\_(ツ)_/¯ on April 23, 2015, 09:22:00 AM
- how long are your monday meetings?
- what can possible be more important than non-classified talk? ( :P )
- how is the bitasset3.0 proposal implemented in parallel to bitassets1.0?
- will it be the "same" market/asset just an extra set of features? or will it be a different token?
- will bitassets3.0 be a 1.0 feature?
- when will we have a rough roadmap that can be put on the webpage?

Monday meetings are from 10 am through lunch. 
We will share those plans with you once we get everything ready for public consumption (this summer)
BitUSD 3.0 will be different than BitUSD
1.0 has been postponed due to BitAssets 3.0...
We will have a documented, tested, stable protocol definition this summer that will not need to change that includes the referral system

We are implementing the "implement then announce" rather than the "announce and then implement" approach to avoid missing deadlines and killing buzz or confusing the market.   When we announce the roadmap will be included... but it will only have 1 item on it and that is turing complete smart contracts which will be our LAST hard fork.

How concrete is "this summer"? I remember quite a few things were supposed to be coming "last December" that never materialized...also, summer is kind of broad. I like to think of summer as being here as soon as the sun comes out (May - June), but summer can technically be considered active until late September or so.

Quote from: btswildpig on April 23, 2015, 05:29:23 PM

Quote from: bytemaster on April 23, 2015, 05:20:40 PM

Quote from: xeroc ¯\_(ツ)_/¯ on April 23, 2015, 09:22:00 AM
- how long are your monday meetings?
- what can possible be more important than non-classified talk? ( :P )
- how is the bitasset3.0 proposal implemented in parallel to bitassets1.0?
- will it be the "same" market/asset just an extra set of features? or will it be a different token?
- will bitassets3.0 be a 1.0 feature?
- when will we have a rough roadmap that can be put on the webpage?

Monday meetings are from 10 am through lunch. 
We will share those plans with you once we get everything ready for public consumption (this summer)
BitUSD 3.0 will be different than BitUSD
1.0 has been postponed due to BitAssets 3.0...
We will have a documented, tested, stable protocol definition this summer that will not need to change that includes the referral system

We are implementing the "implement then announce" rather than the "announce and then implement" approach to avoid missing deadlines and killing buzz or confusing the market.   When we announce the roadmap will be included... but it will only have 1 item on it and that is turing complete smart contracts which will be our LAST hard fork.

will the basic performance still be improved before 1.0 ?

By 1.0 performance problems will be a thing of the past.