Proof-of-stake can never scale without blowing up, because PoS isn't trustless

[kiklo]

Here is a Raw Block #10 in ZEIT generated by PoW

{
   "hash": "000005765a95e60ab8dac12d8b6db0279d8c1533d9aa202f47b5f24ae669ab79",
   "confirmations": 2672972,
   "size": 262,
   "height": 10,
   "version": 4,
   "merkleroot": "bfa1212176268c3cd847c2fb12a5de2f9e08697c1e2e8471c12a5e98ca62e015",
   "mint": 749320,
   "time": 1393624519,
   "nonce": 1782841440,
   "bits": "1e0c0527",
   "difficulty": 0.00032497,
   "previousblockhash": "00000159e17922b8eae86014c681ec4534c269079efd57165d24cfd2c224cc7a",
   "nextblockhash": "00000a3cd2b409d928ef399433441d3c237f4be797354c31d25d077164a4b04a",
   "flags": "proof-of-work",
   "proofhash": "000005765a95e60ab8dac12d8b6db0279d8c1533d9aa202f47b5f24ae669ab79",
   "entropybit": 1,
   "modifier": "0000000000000002",
   "modifierchecksum": "4db887a5",
   "tx": [
      "bfa1212176268c3cd847c2fb12a5de2f9e08697c1e2e8471c12a5e98ca62e015"
   ],
   "signature": "30450220159f98d97fc901ade56cbacf7d3f4a6d158e0ed4575c296a14496dceeee335d0022100a 213d6717474c75ec976387b622584dceb04c3fd776c8e117ce1092a2e65d16f"
}

Here is a Recent Raw Block #2672978 Generated by Proof of Stake if that helps

{
   "hash": "cd59b8f77d7f00a2bda0fe2959a0594b73093e5689c08cdba885878fcfa13acc",
   "confirmations": 1,
   "size": 412,
   "height": 2672978,
   "version": 4,
   "merkleroot": "a2a62e347178fe99c962a505f21bc08c14367a4b759e103aae3480dfed8ed63c",
   "mint": 4185.106849,
   "time": 1468489289,
   "nonce": 0,
   "bits": "1d008396",
   "difficulty": 1.94546696,
   "previousblockhash": "984f53eb944df6fc15c054b6b11f661929d80e2f178410f44c953089e3c274a4",
   "flags": "proof-of-stake",
   "proofhash": "0000d41ace1ed7c29775e5045f7b6024eb5be43a4d2499681f52b874a57643b8",
   "entropybit": 0,
   "modifier": "2a15c7ebff376e0d",
   "modifierchecksum": "a24c74db",
   "tx": [
      "f84ed9ac015a391a40af16638b893380dc98eefae5a537abc8f2e7746186891d",
      "64c591dd803bb3ecaf1b9c7060002a88b0c537d63423147e7e3b7dd290e7f217"
   ],
   "signature": "3046022100d18cd3d4836aa1aba7f40ab838371044c88fdd98df6d32cf13654c2a04b2b37a02210 0be325157ac9e5f555d44d0881e1cfeb184162c4256b9d2f28074dfa9e0ffc804"
}

 

[1714857776]

1714857776

[1714857776]

1714857776

[r0ach]

Like I said, PM Presstab or Rat4 and they can probably answer exactly if the algo affects the PoS or was only used in the PoW generation.

Fuserleer is a smarter and better programmer than those guys, and Fuserleer thinks Anonymint is probably better than him, so you're basically asking a pro golfer to ask the audience how to play.  I can keep up with Anonymint and Fuserleer on a conceptual design level, but my programming started in graphics with MEL then going to Python, so going from theory to reality is a lot easier for someone like Anonymint who has been programming for a couple centuries (even though Anonymintcoin is still vaporware).

[kiklo]

Like I said, PM Presstab or Rat4 and they can probably answer exactly if the algo affects the PoS or was only used in the PoW generation.

Fuserleer is a smarter and better programmer than those guys, and Fuserleer thinks Anonymint is probably better than him, so you're basically asking a pro golfer to ask the audience how to play.  I can keep up with Anonymint and Fuserleer on a conceptual design level, but my programming started in graphics with MEL then going to Python, so going from theory to reality is a lot easier for someone like Anonymint who has been programming for a couple centuries (even though Anonymintcoin is still vaporware).

Has he released a Proof of Stake coin?
Never heard of him.

Hmm,
his background lists emunie, which claim to fame is no blockchain, so I don't see how he would have as much experience with Proof of Stake as Presstab or Rat4.


 

[iamnotback]

kiklo, you can't just claim that 'difficulty' field has any relevant meaning in PoS, unless you know what in code is driving the value of that field. Programming isn't like "the UI is always correct". We have to actually understand what the hell "difficulty" means in this PoS algorithm your code is using. Who knows maybe the programmer is setting some value there what is random or just some gibberish hash of some other data. The programmer might have just wanted to use a consistent set of fields between the two UI (PoW and PoS). I really can't determine any thing from that. I'd have to dig into the code, which really isn't fair since I am not being paid to do that.

Every reference I have studied on PoS has never mentioned a difficulty. There is some talk about strategies that an attacker might use which end up using a lot of computation thus being sort of like PoW, except these aren't in the official client and there is no record of the level of that difficulty recorded (since it is an attack, thus not designed into the protocol).

I am sorry but your point about PoS having difficulty doesn't make sense as far as what I know about PoS and the numerous references I have read. The reason your coin hasn't been attacked is it isn't worth doing so. Ethereum wasn't attacked until the marketcap reached $billion and DAO $160m. It has nothing to do with you not needing to use checkpoints. You just got lucky because your coin doesn't have a large enough marketcap to be worth attacking.

That is not intended to be an insult to your coin effort. Everyone should be free to create and market an altcoin. I am not out to destroy all these smaller coins with my words. If you ever manage to reach your larger goals with it, I assume you'll hire a full time programmer then you will start to deal with some of the issues I am pointing out.

Frankly it is pretty rude of you to argue programming issues with me, as I have written perhaps a few 100,000s lines of code in my lifetime ranging from 68000 assembly to C to C++ to PHP to SQL to Android to Java to Javascript to Scala to Haskell, etc, etc, etc


r0ach you are very much correct I haven't launched shit in CC. It is pretty fucking embarrassing. If my health is really like this as I felt past days, then I have no more excuses. Hopefully I won't be posting on the forum. I think it was important to get my thoughts about PoS written down in carefully written post, because someone PM'ed me asking me to evaluate Verticoin's new white paper. So I just wanted to do that PoS vs. PoW thing once and for all  last time.

The Steemit tangent was unexpected today but I think it is important to finish the analysis on that.

[kiklo]

kiklo, you can't just claim that 'difficulty' field has any relevant meaning in PoS, unless you know what in code is driving the value of that field. Programming isn't like "the UI is always correct". We have to actually understand what the hell "difficulty" means in this PoS algorithm your code is using. Who knows maybe the programmer is setting some value there what is random or just some gibberish hash of some other data. The programmer might have just wanted to use a consistent set of fields between the two UI (PoW and PoS). I really can't determine any thing from that. I'd have to dig into the code, which really isn't fair since I am not being paid to do that.

Every reference I have studied on PoS has never mentioned a difficulty. There is some talk about strategies that an attacker might use which end up using a lot of computation thus being sort of like PoW, except these aren't in the official client and there is no record of the level of that difficulty recorded (since it is an attack not designed into the protocol).

I am sorry but your point about PoS having difficulty doesn't make sense as far as what I know about PoS and the numerous references I have read. The reason your coin hasn't been attacked is it isn't worth doing so. Ethereum wasn't attacked until the marketcap reached $billion and DAO $160m. It has nothing to do with you not needing to use checkpoints. You just got lucky because your coin doesn't have a large enough marketcap to be worth attacking.

That is not intended to be an insult to your coin effort. Everyone should be free to create and market an altcoin. I am not out to destroy all these smaller coins with my words. If you ever manage to reach your larger goals with it, I assume you'll hire a full time programmer then you will start to deal with some of the issues I am pointing out.

Hey,
if you don't want to believe it , your choice.
I gave you the name of two guys that could talk code , it is up to you whether it is worth your time.

I think many of those articles on PoS were written by people like G.Maxwell that push BTC.
The difficulty increase is also the reason , maxwell's line about the nothing at stake is a bunch of B.S. .
Because if he stakes online, he increases the difficulty , so that his offline coins will never reach a difficulty as high as his online coins, since they are competing with others so he can never overwrite the chain as long as he is trying to stake in both places.

Here is a Proof of Stake formula for you
hashProofOfStake <= [Coin-age] x [Target]   
[Coin-age] = [amount of coins] x [days in stake]   
Target = Difficulty

Later,
 

[iamnotback]

kiklo, you can't just claim that 'difficulty' field has any relevant meaning in PoS, unless you know what in code is driving the value of that field. Programming isn't like "the UI is always correct". We have to actually understand what the hell "difficulty" means in this PoS algorithm your code is using. Who knows maybe the programmer is setting some value there what is random or just some gibberish hash of some other data. The programmer might have just wanted to use a consistent set of fields between the two UI (PoW and PoS). I really can't determine any thing from that. I'd have to dig into the code, which really isn't fair since I am not being paid to do that.

Every reference I have studied on PoS has never mentioned a difficulty. There is some talk about strategies that an attacker might use which end up using a lot of computation thus being sort of like PoW, except these aren't in the official client and there is no record of the level of that difficulty recorded (since it is an attack not designed into the protocol).

I am sorry but your point about PoS having difficulty doesn't make sense as far as what I know about PoS and the numerous references I have read. The reason your coin hasn't been attacked is it isn't worth doing so. Ethereum wasn't attacked until the marketcap reached $billion and DAO $160m. It has nothing to do with you not needing to use checkpoints. You just got lucky because your coin doesn't have a large enough marketcap to be worth attacking.

That is not intended to be an insult to your coin effort. Everyone should be free to create and market an altcoin. I am not out to destroy all these smaller coins with my words. If you ever manage to reach your larger goals with it, I assume you'll hire a full time programmer then you will start to deal with some of the issues I am pointing out.

Hey,
if you don't want to believe it , your choice.
I gave you the name of two guys that could talk code , it is up to you whether it is worth your time.

I think many of those articles on PoS were written by people like G.Maxwell that push BTC.
The difficulty increase is also the reason , maxwell's line about the nothing at stake is a bunch of B.S. .
Because if he stakes online, he increases the difficulty , so that his offline coins will never reach a difficulty as high as his online coins, since they are competing with others so he can never overwrite the chain as long as he is trying to stake in both places.

Here is a Proof of Stake formula for you
hashProofOfStake <= [Coin-age] x [Target]   
[Coin-age] = [amount of coins] x [days in stake]   
Target = Difficulty

Later,
 

I understand now that by "difficulty" you are referring to the threshold to sign your stake over. And as I told you from this start, this is not computational work that prevents a Long Range attack. One can go back and sign for some state of the chain as far back as the genesis block and pretend that signature was issued back at that time. And rebuild a completely new chain this way, because there is not computational work that has to be done to prevent the attacker from building a very long chain quickly. That is precisely what is meant by the "nothing-at-stake" problem and why checkpoints are required.

So after several pages of you trolling me, now you see I was correct. I warned you.

[kiklo]

I understand now that by "difficulty" you are referring to the threshold to sign your stake over. And as I told you from this start, this is not computational work that prevents a Long Range attack. One can go back and sign for some state of the chain as far back as the genesis block and pretend that signature was issued back at that time. And rebuild a completely new chain this way, because there is not computational work that has to be done to prevent the attacker from building a very long chain quickly. That is precisely what is meant by the "nothing-at-stake" problem and why checkpoints are required.

So after several pages of you trolling me, now you see I was correct. I warned you.

LOL,
Nope you're not, believing G.Maxwell B.S. won't make you right.

You mistake trolling for correcting, and if you are blind to the truth that is your choice.
And if someone thinks G.Maxwell lies are valid or he himself thinks he can prove it.
Tell him to prove it with ZEIT , I'll be waiting for him. (Scary Music Playing) Muu Ha Ha  

 

FYI:
If you reread the earlier posts , I used the term accumulated difficulty.
But declare victory if it makes you feel better, I will settle for the truth.

[iamnotback]

LOL,
Nope you're not, believing G.Maxwell B.S. won't make you right.

You are up against very, very many people who have come to the same conclusion, including the authors of the BitFury white paper I cited, Peter Sztoric, smooth, myself, all of us together have 100+ years of programming experience. Dude you have an enormous ego considering you aren't even a programmer. Do you realize how much a prick you are? Those other guys wouldn't even bother replying to you, because they think you are so stupid.

You mistake trolling for correcting, and if you are blind to the truth that is your choice.

You who is not even a programmer, is going to correct all of us expert programmers.  

If you reread the earlier posts , I used the term accumulated difficulty.

I was also referring to the accumulated sum of the thresholds you call difficulty. That is irrelevant and that you don't understand why, goes directly to the heart of your slobbering Dunning-Kruger ignorance.

I already explained to you there is no computational cost. Adding thresholds which have no computation cost does not prevent the fast construction of a chain from any point in history. The coin age delays are entirely relative to what the attacker constructs on the chain of transactions.

You are making a fool of yourself and you are proudly being a real jerk to me wasting my time and thinking you know more than an expert programmer. And I'm done wasting my time on your ignorance. Just because you listened to some technobabble from your lesser programming friends, doesn't make you qualified to regurgitate their incorrect technical understanding in a debate with me.

You wasted several hours of my time today. This is very expensive. You are making me very angry.

PLEASE FUCKING STOP PRICK.

Why do you think you are important enough to justify putting your text in bright blue when everyone else here is cordial enough to write in black text.

You've been asked several times to be cordial and respectful and stop writing in blue text. You seem to think very highly of your ignorant, slobbering self.

[SmirkinPepe]

I think you are just misdirecting your intellect, which seems above average, on a wild-goose chase.
Power distributions are a fact of nature, whichever system you will build, if it is valuable to humans, power over it will be unfairly distributed. If it isn't, that just means there is a power vacuum waiting to be claimed by someone with the means to.
But I suspect you know this already and you might be on some high level trolling or something.

[greenuser]

looks like proof-of-capacity (PoC) could be the winner here    I do enjoy people getting angry,  thanks, great read. 

[spartacusrex]

There is 1 issue that always seems to be overlooked in the POW vs POS coins debate.

UNLESS you write the client yourself, from scratch, using the white paper, how do you know that your POW client is not malware / hacked ?

There is an element of 'trust' when you download the client for any coin, as even if the website notes the SHA of the executable, source, whatever, that could have been hacked as well. So you need to find the SHA of the 'correct' client.. (Ask a friend, has he been hacked !?)

Although POW does give you the official 'heaviest' chain, it is hard to argue that 99.99% of people will not need to trust the client they have downloaded. Yes - they go to the official page, etc etc.. but they are not 100% unless they wrote / checked / compiled it themselves. (Hackers find a way to infiltrate..)

FOR MOST people - the POS checkpoints have the same trust level requirement. You would still have to trust the client has a correct checkpoint, just as you have to trust the POW client is not hacked.

What I am saying is that the requirement of knowing a single HASH from the POS block chain, does not utterly destroy POS.

..Unless you can think of a way of distributing an executable that I can check is valid without requiring any extra knowledge ? (Like a POW chain.. hmm.. is there such a thing as a POW-executable..)

[CoinHoarder]

All consensus algorithms have cons. PoW, PoS, etc... by focusing on the shortcomings of anything, I can make it look like a pile of crap. Everything and everyone in existence has shortcomings. Nothing is perfect. Anonymity is fooling himself thinking he can come up with a perfect consensus algorithm, and is definitely fooling himself thinking he can come up with a perfect cryptocurrency.

[presstab]

kiklo, you can't just claim that 'difficulty' field has any relevant meaning in PoS, unless you know what in code is driving the value of that field. Programming isn't like "the UI is always correct". We have to actually understand what the hell "difficulty" means in this PoS algorithm your code is using. Who knows maybe the programmer is setting some value there what is random or just some gibberish hash of some other data. The programmer might have just wanted to use a consistent set of fields between the two UI (PoW and PoS). I really can't determine any thing from that. I'd have to dig into the code, which really isn't fair since I am not being paid to do that.

Every reference I have studied on PoS has never mentioned a difficulty. There is some talk about strategies that an attacker might use which end up using a lot of computation thus being sort of like PoW, except these aren't in the official client and there is no record of the level of that difficulty recorded (since it is an attack, thus not designed into the protocol).

I am sorry but your point about PoS having difficulty doesn't make sense as far as what I know about PoS and the numerous references I have read. The reason your coin hasn't been attacked is it isn't worth doing so. Ethereum wasn't attacked until the marketcap reached $billion and DAO $160m. It has nothing to do with you not needing to use checkpoints. You just got lucky because your coin doesn't have a large enough marketcap to be worth attacking.

That is not intended to be an insult to your coin effort. Everyone should be free to create and market an altcoin. I am not out to destroy all these smaller coins with my words. If you ever manage to reach your larger goals with it, I assume you'll hire a full time programmer then you will start to deal with some of the issues I am pointing out.

Frankly it is pretty rude of you to argue programming issues with me, as I have written perhaps a few 100,000s lines of code in my lifetime ranging from 68000 assembly to C to C++ to PHP to SQL to Android to Java to Javascript to Scala to Haskell, etc, etc, etc

Not trying to get in a heated debate or anything, but trying to wrap my head around the claims that difficulty is different from PoW to PoS.

From my understanding, both difficulty adjustment algorithms (although altered from coin to coin) are looking at the time it took to produce a new block. If the time is greater than the targeted block time, then difficulty goes down so that it is easier to produce the next block, if the time it took was less than the target difficulty goes up so that it is harder to produce the next block. I don't see any real conceptional difference in the difficulty adjustment algorithms.

I suppose that maybe its an argument about the valid proof required to create that block rather than the adjustment algorithm itself (sorry the thread has been a bit difficult to follow).

Admittedly, I am not a crazy expert programmer. I am still working on my masters in CS, and learn new things all the time. I have however, what I consider a pretty good fundamental understanding of Bitcoin and Peercoin code bases.

[kiklo]

Not trying to get in a heated debate or anything, but trying to wrap my head around the claims that difficulty is different from PoW to PoS.

From my understanding, both difficulty adjustment algorithms (although altered from coin to coin) are looking at the time it took to produce a new block. If the time is greater than the targeted block time, then difficulty goes down so that it is easier to produce the next block, if the time it took was less than the target difficulty goes up so that it is harder to produce the next block. I don't see any real conceptional difference in the difficulty adjustment algorithms.

I suppose that maybe its an argument about the valid proof required to create that block rather than the adjustment algorithm itself (sorry the thread has been a bit difficult to follow).

Admittedly, I am not a crazy expert programmer. I am still working on my masters in CS, and learn new things all the time. I have however, what I consider a pretty good fundamental understanding of Bitcoin and Peercoin code bases.

IMO and In Reality,
you're a better Proof of Stake programmer than iamnotback.
Which is why I told him he should ask you , since you have more experience in this specific area.

My premise has been Longest Chain with the most difficulty wins in Proof of Stake or Proof of Work and can overwrite a shorter chain of less difficulty.
In his misleading conclusions , he claims this is only valid for Proof of work.
Which makes absolutely no sense and makes this whole topic just seem like a misleading hit piece against PoS.

 

[kiklo]

LOL,
Nope you're not, believing G.Maxwell B.S. won't make you right.

You are up against very, very many people who have come to the same conclusion, including the authors of the BitFury white paper I cited, Peter Sztoric, smooth, myself, all of us together have 100+ years of programming experience. Dude you have an enormous ego considering you aren't even a programmer. Do you realize how much a prick you are? Those other guys wouldn't even bother replying to you, because they think you are so stupid.

You mistake trolling for correcting, and if you are blind to the truth that is your choice.

You who is not even a programmer, is going to correct all of us expert programmers.  

Would not be the 1st Time, I corrected People who thought they knew everything and they were wrong.
Been doing that for ~80 years now.

If you reread the earlier posts , I used the term accumulated difficulty.

I was also referring to the accumulated sum of the thresholds you call difficulty. That is irrelevant and that you don't understand why, goes directly to the heart of your slobbering Dunning-Kruger ignorance.

I already explained to you there is no computational cost. Adding thresholds which have no computation cost does not prevent the fast construction of a chain from any point in history. The coin age delays are entirely relative to what the attacker constructs on the chain of transactions.

You are making a fool of yourself and you are proudly being a real jerk to me wasting my time and thinking you know more than an expert programmer. And I done wasting my time on your ignorance. Just because you listened to some technobabble from your lesser programming friends, doesn't make you qualified to regurgitate their incorrect technical understanding in a debate with me.

You wasted several hours of my time today. This is very expensive. You are making me very angry.

PLEASE FUCKING STOP PRICK.

That is your own Fault ,
No one told you to spread misinformation about a topic, even you admit you do not have a complete understanding of.
Take a pill and calm down or pop a blood vessel , your choice , but don't expect me to let you spread misinformation like it is gospel when it is not.

 

[kiklo]

In regards to Algo discussion from a page ago ,
Why PoS coins mention algo like Scrypt or sha256d or X15

Blackcoin White Paper may offer an explanation
http://blackcoin.co/blackcoin-pos-protocol-v2-whitepaper.pdf

D.  Hash Function
The  original  NovaCoin  protocol  called  for  the  use  of
”Scrypt”  [5]  as  its  Proof-Of-Work;  also  being  used  as  the
block hash. However there are some issues with that previous
implementation.  Using  Scrypt  offers  no  real  advantage  to
Proof-Of-Stake; and is far slower than some alternatives. Since
BlackCoin is no longer in PoW phase, the only major change
would have to occur in the algorithm for determining the block
hash.  Therefore  the  block  hash  has  been  changed  back  to
SHA256d. To reflect this the block version has been increased
to version 7.

 

[presstab]

In regards to Algo discussion from a page ago ,
Why PoS coins mention algo like Scrypt or sha256d or X15

Blackcoin White Paper may offer an explanation
http://blackcoin.co/blackcoin-pos-protocol-v2-whitepaper.pdf

D.  Hash Function
The  original  NovaCoin  protocol  called  for  the  use  of
”Scrypt”  [5]  as  its  Proof-Of-Work;  also  being  used  as  the
block hash. However there are some issues with that previous
implementation.  Using  Scrypt  offers  no  real  advantage  to
Proof-Of-Stake; and is far slower than some alternatives. Since
BlackCoin is no longer in PoW phase, the only major change
would have to occur in the algorithm for determining the block
hash.  Therefore  the  block  hash  has  been  changed  back  to
SHA256d. To reflect this the block version has been increased
to version 7.

The proof hash for PoS coins has always been hashed in SHA, the block hash algorithm really has no direct relevance to the difficulty of producing a PoS block.

[iamnotback]

I think you are just misdirecting your intellect, which seems above average, on a wild-goose chase.
Power distributions are a fact of nature, whichever system you will build, if it is valuable to humans, power over it will be unfairly distributed. If it isn't, that just means there is a power vacuum waiting to be claimed by someone with the means to.
But I suspect you know this already and you might be on some high level trolling or something.

Bottom-up organization is also an aspect of nature, because if it was not then it would require that a top-down omniscience was possible, which is impossible because it would require an innumerable speed-of-light, which would collapse the future and the past into nothingness (read two pages of my posts following the linked one in order to capture my complete reasoning).

There are systems in nature which have successfully resisted top-down organization thus are not power vacuums, e.g. sexual reproduction. Their key trait is that they can't be top-down organized, because they have a local, real-time environment relevance that can't be managed nor captured by the top-down organizer. This was essentially the key fundamental insight of my famous essay about the Rise of Knowledge being that individually empowered (by the Internet) knowledge creation is individually serendipitous and accretive, not capable of being captured by top-down finance:

Economic Devastation

You will probably need a week or two of studying the thread slowly.

I will be the first to admit I needed a week to fully absorb the following works of AnonyMint.

The Rise of Knowledge
Understand Everything Fundamentally

Together these are quite simply the most insightful piece of economic theory I have ever read.

If the author is right and I think he is we are all in the midst of a tragedy of epic proportions.  It is sad unstoppable and will devastate the lives of much of humanity.

Edit:
This thread is now over 100 pages and too long to realistically expect a reader to cover from start to finish. There have been multiple requests for a roadmap or guide. In response to the latest request I wrote the following roadmap.

...

Satoshi's design was an attempt to create such a permissionless, trustless system, that unlike fiat and democracy, would not be captured by any top-down oligarchy. Unfortunately his design is a power vacuum that fails to power distribution of control (e.g. Bitcoin = ChinaCoin) due to economies-of-scale in profitable proof-of-work mining.

I have conceived of a design for unprofitable proof-of-work mining which I believe has the necessary trait to not be a power vacuum.

Note that even phenomena which are not currently a power vacuum, can later become one. CoinCube has been arguing that human reproduction is soon to come under the control of the State or Corporations due to advances in technology for reproduction such as In Vitro Fertilization and other factors. I don't completely recall his reasoning off the top of my head.

[kiklo]

The proof hash for PoS coins has always been hashed in SHA, the block hash algorithm really has no direct relevance to the difficulty of producing a PoS block.

Hmm,

Just to clear it up for everyone myself included.
Aside from PoW generation, when Blackcoin whitepaper say scrypt and moving to sha,
what exactly did Rat4 mean by the block hash was changing from Scrypt to Sha, in your opinion?

 

FYI:
This was a tangent conversation , and has nothing to do with the fact
iamnotback is Wrong in his Slandering of proof of stake.

[kiklo]

Nice fantasy you have asshat.

Unlike you , I have an easier time telling one from the other.  


 

FYI:
Looks like you are developing a stutter.