A Consensus Protocol Based on the Ability of Network Dispersity.

[yj1190590]

hi:
This is the research paper about the project I posted before.
Thank you for your time.
[disabled]
If there are any questions, please let me know. Thanks.

previous post:[disabled]

[1715001767]

1715001767

[1715001767]

1715001767

[monsterer2]

“Proof of Stake” (PoS) protocol is the most successful one of them because it doesn’t
need any external resources and consumes low energy

I stopped reading the paper at this point. I'm afraid this paper reads like a blog post from someone who just read about cryptocurrencies for the first time.

[yj1190590]

I stopped reading the paper at this point. I'm afraid this paper reads like a blog post from someone who just read about cryptocurrencies for the first time.

I don't quite catch the point of you but if there were any misunderstandings caused by the grammar and syntax, I'm very sorry about that becsuse I'm not a native English speaker.
If you have any point of view that is against mine, would you please tell me in a direct way because I don't want to miss the main idea again. Thanks.

[aleksej996]

I stopped reading the paper at this point. I'm afraid this paper reads like a blog post from someone who just read about cryptocurrencies for the first time.

I don't quite catch the point of you but if there were any misunderstandings caused by the grammar and syntax, I'm very sorry about that becsuse I'm not a native English speaker.
If you have any point of view that is against mine, would you please tell me in a direct way because I don't want to miss the main idea again. Thanks.

Proof of Stake protocol is less secure than Proof of Work. Calling it more successful is naive. It has it's costs and it's benefits.
It trades security for energy consumption, it isn't better, it is just different.

[yj1190590]

Proof of Stake protocol is less secure than Proof of Work. Calling it more successful is naive. It has it's costs and it's benefits.
It trades security for energy consumption, it isn't better, it is just different.

I have never said that PoS is better than PoW.
I said PoS is the most successful one of the other alternative protocols, isn't it ?

All the other protocols are following the same logic, like Proof of Activity, Proof of Burn, Proof of Storage, Proof of Elapsed Time, and so on. "Proof of Stake" (PoS) protocol is the most successful one of them...

[monsterer2]

I stopped reading the paper at this point. I'm afraid this paper reads like a blog post from someone who just read about cryptocurrencies for the first time.

I don't quite catch the point of you but if there were any misunderstandings caused by the grammar and syntax, I'm very sorry about that becsuse I'm not a native English speaker.
If you have any point of view that is against mine, would you please tell me in a direct way because I don't want to miss the main idea again. Thanks.

You cannot objectively verify claimed network latency, so you cannot build a consensus using this concept. I think you have realised this, so you've stake weighted your consensus to compensate.... At best this will leave you with the security model of PoS. At worst you will have all kinds of sybil attack problems related to the nuances of your implementation.

[yj1190590]

You cannot objectively verify claimed network latency, so you cannot build a consensus using this concept. I think you have realised this, so you've stake weighted your consensus to compensate....

You are right, that was one reason that I use stake to measure the power of voting. But it was not a compensation because the "stake" property plays other important roles like “balance the mining power”.
you could see it here: https://github.com/yj1190590/PoND/blob/master/README_eng.md#compete-for-the-voters.

At best this will leave you with the security model of PoS.

You can consider it as a kind of PoS mechanism in this respect, that's OK. But from some other respects it has many differences from PoS. About this question, you could refer to: https://github.com/yj1190590/PoND/blob/master/README_eng.md#faqs if you'd like to.

At worst you will have all kinds of sybil attack problems related to the nuances of your implementation.

Sybil attacks are not so easy just because I use the "stake" property like you said.

[monsterer2]

You can consider it as a kind of PoS mechanism in this respect, that's OK. But from some other respects it has many differences from PoS. About this question, you could refer to: https://github.com/yj1190590/PoND/blob/master/README_eng.md#faqs if you'd like to.

At worst you will have all kinds of sybil attack problems related to the nuances of your implementation.

Sybil attacks are not so easy just because I use the "stake" property like you said.

My point was, if you only achieve the security model of PoS with this technique, why bother at all?

[yj1190590]

My point was, if you only achieve the security model of PoS with this technique, why bother at all?

We assume that you are right that it has the same security level as PoS, which actually not(you will know that if you read the section "51% attack"). At least the new model don't have the common flaws of PoS such as the wealth concentration issue or "nothing at stake" problem.

[yj1190590]

My point was, if you only achieve the security model of PoS with this technique, why bother at all?

We assume that you are right that it has the same security level as PoS, which actually not(you will know that if you read the section "51% attack"). At least the new model don't have the common flaws of PoS such as the wealth concentration issue or "nothing at stake" problem.

And provides incentives to build open development multi-chain systems which may be a progress in the field of cryptocurrency.

Provide an incentive for developers to build extend projects which ensures the sustainability and extendibility of the system.

[monsterer2]

My point was, if you only achieve the security model of PoS with this technique, why bother at all?

We assume that you are right that it has the same security level as PoS, which actually not(you will know that if you read the section "51% attack"). At least the new model don't have the common flaws of PoS such as the wealth concentration issue or "nothing at stake" problem.

All stake based protocols suffer from NaS - yours included.

[yj1190590]

All stake based protocols suffer from NaS - yours included.

I hope this could explaine:

The difference is that when the votes take effect, they are already sealed in the existing blocks. That makes the common problem of PoS such as “nothing at stake” or “stake grinding” resolved.

[monsterer2]

I hope this could explaine:

The difference is that when the votes take effect, they are already sealed in the existing blocks. That makes the common problem of PoS such as “nothing at stake” or “stake grinding” resolved.

Words like 'sealed' have little meaning in any system where block generation has zero cost.

[yj1190590]

Words like 'sealed' have little meaning in any system where block generation has zero cost.

I recommend you to read the article "Transactions as Proof-of-Stake" by Daniel Larimer whose idea was close to mine in this respect.

[monsterer2]

Words like 'sealed' have little meaning in any system where block generation has zero cost.

I recommend you to read the article "Transactions as Proof-of-Stake" by Daniel Larimer whose idea was close to mine in this respect.

That won't help you at all. It doesn't address the problem of historical private keys. I suggest you read this post: https://bitcointalk.org/index.php?topic=1382241.msg14058047#msg14058047

[Realen44]

i

hi:
This is the research paper about the project I posted before.
Thank you for your time.
https://github.com/yj1190590/PoND/blob/master/research_paper.pdf
If there are any questions, please let me know. Thanks.

previous post:https://bitcointalk.org/index.php?topic=3251016.0

[yj1190590]

That won't help you at all. It doesn't address the problem of historical private keys. I suggest you read this post: https://bitcointalk.org/index.php?topic=1382241.msg14058047#msg14058047

Long range attack is an other problem of PoS but we are discussing the NaS problem aren't we?
https://blog.ethereum.org/2014/05/15/long-range-attacks-the-serious-problem-with-adaptive-proof-of-work/

[monsterer2]

That won't help you at all. It doesn't address the problem of historical private keys. I suggest you read this post: https://bitcointalk.org/index.php?topic=1382241.msg14058047#msg14058047

Long range attack is an other problem of PoS but we are discussing the NaS problem aren't we?
https://blog.ethereum.org/2014/05/15/long-range-attacks-the-serious-problem-with-adaptive-proof-of-work/

It's all NaS in the end. Every problem that PoS has is due to NaS.

edit: in any case, what I've posted isn't 'long' range, but instead *any* range.

[yj1190590]

It's all NaS in the end. Every problem that PoS has is due to NaS.

edit: in any case, what I've posted isn't 'long' range, but instead *any* range.

I know what you mean with "NaS" but I used that word with the meaning of the "double voting problem".
If the problem mentioned at that post is still unresolved, I must say that's the problem we haven't resolved yet. But we have at least resolved the first one.

[yj1190590]

That won't help you at all. It doesn't address the problem of historical private keys. I suggest you read this post: https://bitcointalk.org/index.php?topic=1382241.msg14058047#msg14058047

I have thought seriously about the problem you posted and maybe I have found a way to mitigate it. It's useful to any PoS protocols.

First of all the reorganizition is designed to prevent forks. Under normal circumstances,  some stakeholders would be active(trading or mining) in both branches (caused by NaS too) if there appears a fork. According to the probability there will be similar stake proportion of "double-active" users between both branches.

But if the branch is a fake chain built by the attackers, they will be disproportionate —— the proportion mentioned above in the mainchain will be much less than that in the fake one, unless you have bought every account, which is impossible. Under this circumstance, the branch should never be accepted no matter how long it is. This operation is also nessesary to prevent some group of users from getting extra advantage by unfair means when forks come.

By the way, the situation you have mentioned:"any syncing node querying at random will find his fake nodes with fake history" could be resolved by controling the p2p links——

each node only needs to build connection with a certain number of nodes with the fastest response speed.

The attacker needs to try through a lot of past blocks so that the longer range he seeks, the better chance he would success. But the longer range he starts the fork, the more obvious the disproportion will be. I think that might increase the difficulty you launch an attack, after all you gain those private keys by "buying".