This is off-topic, but required in order to illustrate the illogical trolling of CoinHoarder since he has decided to filibuster my thread and fill it up with off-topic drivel:
1. He condemns pumpers whilst pumping vaporware himself.
I guess you missed where I've been promoting your beloved Bitshares' DEX lately and where I had explained to smooth he was short-sighted when he convinced me that Bitshares was likely a failure or scam:
Why does no one use the BitShares Exchange DEX?
Because we are just fools:
It seems that a corrupted exchange is an essential ingredient for pumping a crypto currency to $billion nosebleed mcaps, so apparently not only is demand being created out-of-thin-air using margined coins the insiders deceptively obtained from the ICO by buying from themselves (taking out a BTC loan and paying it back after the ICO)...
...but likely also that some high volume exchange is also creating tokens literally out-of-thin-air and is another Mt.Gox or Cryptsy waiting to default when there is a run to withdraw.
A likely essential ingredient in BitCON's rise from $10 to $1200 was because Mt.Gox was creating coins out-of-thin-air and handling most of the BTC volume, so this provided more coins for everyone to leverage and create fake demand with.
So this huge pump in ETH likely means another high volume exchange will end up stealing all your coins again soon.
The way this criminal enterprise crypto-currency enterprise works is that the insiders create tokens out-of-thin-air on the exchanges, then when the ponzi scheme implodes, the "hackers" or owners of the exchange are blamed instead of blaming the real manipulators behind the curtain.
We apparently have criminal gangs in the crypto-currency ecosystem. The DAO attacker says the UGGovt + MIT/Cornell universities are complicit. Others say Goldman Sachs is in this. Probably also Russian criminals, etc..
That is likely why there is no enforcement from the SEC. Because the SEC is owned by the criminal gangs.
Nothing has changed! We have not defeated fiat. We have not defeated the same banksters bastards who are always enslaving us.
We're just fools.
And especially after he had basically talked me out of thinking that Bitshares might be a credible team to partner with.
I don't remember ever discussing Bitshares with you or anyone else. It seems unlikely because with one small exception I have always been entirely ignorant about Bitshares, something that even today puts me at a disadvantage in understanding Steem (since it is based closely on Bitshares). The exception is that I was pretty sure their original model of pegged assets was catastrophically unstable and would not work. They later added a price feed, which improved it somewhat.
It may be that I made some general remarks that could be interpreted as arguing against the success of Bitshares model, but I don't know.
Thanks for the explanation.
I'll refresh your memory.
It was after I had announced Zero Knowledge Transactions and it was clear that Monero had a competitive solution RingCT and I was shopping ZKT around to potentially BBR and also I approached Bitshares briefly. Thus that must have been roughly Aug or Sept. There is a post from AnonyMint user name at the Bitshares forum as evidence.
I was discussing with you in private about the merits of ICOs and making money from launching a coin in what ever means. And you were trying to tell me that there is basically no money in it and that is why Monero's plan is the best, because the XMR devs just do it as a hobby or labor of love and don't take it too seriously as a way to generate income. You were always in general coaxing me away from any concept of making money from developing and launching CC, and to the open source hobbyist Monero way.
And I mentioned Bitshares as an example with their significant marketcap which had been as high as $40 million at one point for afair the ProtoShares. And had also mentioned Dash. That is when you instructed me about how all the mcaps are fake and you made me aware that insiders buy from themselves to make it appear that the volume is real.
I said okay maybe for Dash, but Bitshares seems to have legit technology and theirs might be real. And you said that look how Bitshares is trying to sell services (at that time in 2015) because they are basically cash strapped and aren't earning hardly anything from creating CCs.
In short, you were trying to discourage me from pursuing making a CC
if I expected to earn any $ from doing so. That is not to say you were discouraging me from creating a CC if not for expectation of a payday. That is not to say you were wishing for me to fail if I did attempt to. I think you felt you were just giving sound feedback.
To be fair, you were aware of my illness and perhaps you were concerned and felt I might be better off to take employment, get medical insurance, and have a more stable and less risky source of potential income and funding for health care.
But I just know that before that discussion, I never thought about the altcoin market as being one giant scam and being entirely fake. I really bought into your take on that. But now in hindsight, I think you are not entirely correct. Seems people who have produced less technology than I am working on, having reaped some significant paydays.
Waves raised ~$15 million and referred to IOHK's open source without apparently having developed anything at all. It was apparently purely a marketing campaign. Heck I never expected even a $million, so with better tech than they have, why shouldn't I be able to get my $500,000 and also do some good for the CC community.
When I respect someone, it means I listen intently to what they have to say.
CoinHoarder probably gets pissed off when I write about Bitshares' DPOS consensus system (CoinHoarder if you want to refute the following post, please do it in the quoted thread, not here! Damnit!):
1. Since the chosen
single node for each block is deterministic, then in theory it could be very vulnerable to botnet DDoS attack. More generally it lacks fault tolerance, which is critically needed in real world systems. A redesign to have simultaneous disjoint blocks from multiple delegates can't be allowed because there could be double-spends in the presumed disjoint blocks.
2. For DPOS, this is not decentralized control, because the minority has to accept the will of the majority on the election of delegate DPOS nodes, i.e. the permissionless attribute can be lost such as
ChainAnchor being planned for ButtCON. No one can just standup a full node at-will. This also means there isn't really competition in terms of a free market rate for transaction fees.
Btw, Bitcoin-NG accomplishes basically the same deterministic node per block and with decentralized control over the selection of the delegate in real-time employing PoW, yet with chain reorganization issues.
3. The maximum speed (minimum delay) of confirmations is lower bounded by the slowest latency of block propagation to every DPOS node, because otherwise some nodes can't keep up. This can be reasonably fast say several seconds if you've got a very organized set of delegate nodes (but then you really don't have decentralized control), but this is not fast enough for some types of instant microtransactions.
4. Zero-confirmation double-spend transactions (aka Finney Attack) are even more plausible, because a colluding delegate node knows deterministically when it will win the block. Note block periods can be reasonably fast in DPOS, so 0-conf is probably not needed although not fast enough for some types of instant microtransactions, although such probably wouldn't be Finney attacked due to their small values.
5. Proof-of-stake is not a secure consensus algorithm, because for example the nothing-at-stake problem. We compiled
a laundry list of flaws in proof-of-stake. Note I
recently made a suggestion to jl777 and we mutually designed how to record check points for DPoS coins in a PoW block chain.
I am glad you are back youarenotback! Mostly I don't understand all you're saying, but at least your posts challenge me to try to learn new things. Thanx!
Let me try to unpack those points a bit for laymen:
1. Full nodes in DPOS are elected delegates. With Satoshi's PoW, we don't know which node will win the next block. So an attacker wouldn't know which node to jam with a DDoS attack. Any node attacked would simply not participate in competing to produce the next block, but this wouldn't harm the system at all. Whereas, when we designate the node that will decide what goes into the next block, then an attacker knows which node to attack. As well, a node knows when it will control the next block, and thus it can attack the network by withholding (although it would probably get voted out of being a delegate node soon, although it might be difficult to prove when it was a legitimate network hiccup or when it was intentional). I believe Bitcoin-NG may have an analogous weakness.
2. For me, this is the other huge weakness. With DPOS, the set of nodes which process blocks is static until the next voting. And even after voting, standing up a full node is not something an individual can choose to do by himself. There is always politics and centralization involved. The ideologically great thing about Satoshi's design is that anyone at any time can go standup a full node and process his/her transactions on any block he/she wins. The problems of course with Satoshi's design is that it doesn't scale and also that PoW economics of SHA256 means an individual can no longer win a block nor prevent the centralization of mining over time due to it being 100 to 1000X more profitable for the ASIC farms and because scaling can't work without centralization. So DPOS doesn't really gain anything that we can't get by centralizing Satoshi's design other than saving electricity.
I have another solution which I think is a better compromise than both of those. But I won't describe it, because surely others will start to figure out my design if I describe it further. I need to release it asap, so the discussion of its merits can be open sourced.
3. If one full node's block period is say 5 seconds, but the propagation to another of the full nodes is 10 seconds, that latter node will not be able to receive the new block from the former and produce another new block within its 5 second allocation. Thus the block period has a lower bound which is dictated by the slowest propagation on the network of full nodes. And 5 seconds confirmation is too slow for certain types of microtransactions. Imagine you want to start listening to a song, and you have it set to pay a microtransaction automatically, but you have to wait 5+ seconds everytime you want to click to listen to a new song you have not yet paid for. Or similarly when using microtransactions instead of a CAPTCHA. Even 1 second might be too slow! Vcash's Zerotime can't even get close to being fast enough. Probably Lightning Networks won't be fast enough either, not to mention it doesn't scale well.
5. DPOS (delegated proof-of-stake) is still POS with all its flaws. My desire is to attain Satoshi's security model, but with 100% decentralization, massive scaling, 1 second confirmed transactions, and no economic trend towards centralization!
Edit: Steemit is pioneering combining PoW and DPOS in another way, and do take note that this doesn't seem to fix the issues I enumerated above although it mitigates somewhat issue #2 except doesn't solve the economics of centralization of PoW issue:
Consensus in Steem
...
With Steem, block production is done in rounds. Each round 21 witnesses are selected to
create and sign blocks of transactions. Nineteen (19) of these witnesses are selected by
approval voting, one is selected by a computational proof-of-work, and one is timeshared
by every witness that didnt make it into the top 19 proportional to their total votes. The 21
active witnesses are shuffled every round to prevent any one witness from constantly
ignoring blocks produced by the same witness placed before.
This process is designed to provide the best reliability while ensuring that everyone has the
potential to participate in block production regardless of whether they are popular enough
to get voted to the top. People have three options to overcome censorship by the top 19
elected witnesses: patiently wait in line with everyone else not in the top 19, purchase
enough computational power to solve a proof of work faster than others, or purchase more
SP to improve voting power. Generally speaking, applying censorship is a good way for
elected witnesses to lose their job and therefore, it is unlikely to be a real problem on the
Steem network.
Because the active witnesses are known in advance, Steem is able to schedule witnesses to
produce blocks every 3 seconds. Witnesses synchronize their block production via the NTP
protocol. A variation of this algorithm has been in use by the BitShares network for over a
year where it has been proven to be reliable.
Mining in Steem
Traditional proof of work blockchains combine block production with the solving of a proof
of work. Because the process of solving a proof of work takes an unpredictable amount of
time, the result is unpredictable block production times. Steem aims to have consistent and
reliable block production every 3 seconds with almost no potential for forks.
To achieve this Steem separates block production from solving of proof of work. When a
miner solves a proof of work for Steem, they broadcast a transaction containing the work.
The next scheduled witness includes the transaction into the blockchain. When the
transaction is included the miner is added to the queue of miners scheduled to produce
blocks. Each round one miner is popped from the queue and included in the active set of
witnesses. The miner gets paid when they produce a block at the time they are scheduled.
The difficulty of the proof of work doubles every time the queue length grows by 4. Because
one miner is popped from the queue every round, and each round takes 21 * 3 = 63 seconds,
the difficulty automatically halves if no proof of work is found in no more than 21 * 3 * 4 =
252 seconds.