İtibar tabanlı hisse kanıtı

The Proof-of-Stake(PoS) has several issues like "Nothing at Stake Attack", "Long Range Attack", "DDoS Attacks", "Rich get Richer", and "Byzantine Failures". Therefore, we created the Reputation-Based Proof-of-Stake(RBPoS) to fix the weaknesses of the PoS. RBPoS requires single fork responsibility to any validator since "Nothing at Stake Attack" occurs due to no penalty for simultaneous block signing on two different same-sized fork. Also, RBPoS uses checkpoints in our approach because when the PoS approach has no time challenge and no concern about the result, it can face a "Long Range Attack." On the other hand, RBPoS needs delay between two consecutive blocks. If any user disobeys the delay rule, the user immediately faces slashing. This is because "DDoS Attacks" occurs due to simultaneous request as overloaded. On the other side, RBPoS uses a particular coin age calculation, the reputation coin age, to decrease the rich people's majority power. We solved the "Rich get Richer" issue with the reputation coin age because "Rich get Richer" means that the significant actors can get more chances for validation according to their capital. We created a new role for the network as a compliance officer. The compliance officer is responsible for data synchronization and health of information. "Byzantine Failures" are about distributed system asynchronous data problem failures. Namely, we reduce the "Byzantine Failures" scenarios with compliance officers. We simulated a blockchain network with our approach. According to the experimental results, we reached a more robust system than Pure PoS.