Asch will shine by its own values. Let's have some patience.
Posts made by corpuscrypto
RE: Why ASCH making a foundation is a BIG DEAL, and what that means to crypto community.
@standerup Sadly I don't know chinese yet! Maybe it's a good time to start learning?
Why ASCH making a foundation is a BIG DEAL, and what that means to crypto community.
Like I said in a previous post, I'm writing variate stuff about ASCH in order to get us more known! This one is titled "Why ASCH making a foundation is a BIG DEAL, and what that means to crypto community". You can find it here https://medium.com/@corpuscrypto/why-asch-making-a-foundation-is-a-big-deal-and-what-that-means-to-crypto-community-104ca8ae10c9
I'm looking forward to your comments and suggestions for more short articles like this!
ASCH value comes from the heart.
Hello everybody! With the intention of making ASCH better and more known in the western community, I have started to write some stuff related to our most beloved cryptocurrency.
I share with you this post, titled "ASCH value comes from the heart", you can check it at https://medium.com/@corpuscrypto/asch-value-comes-from-the-heart-ac367dd0fa5 !
I hope you guys like it!
RE: Delegates/Masternodes broken and unfair???
@littlewhale @feng First of all, thank you for making ASCH better. I don't have the time nor the skills to do that background jobs you mention, and if ASCH is growing, is due to its community, and actually I'm trying to do my part in that. But I still believe, from a perspective of a new user, who just got their first XAS and wants to vote for someone, that we should facilitate the task of knowing better what are the delegates doing. Sure, people could visit the forums, use google translate (if the user doesn't know chinese, like me) to check the chinese part of it (wich cointains the majority of the information), or maybe check the github. But, shouldn't be useful that in the web wallet there were actually information about the delegates? Let them write something about theirselves, and let me check that while browsing the delegate list. I believe that would improve transparency, as @mannanj wants. That way, at least a piece of information will be added, and I don't believe that would hurt anybody, on the contrary, it will help making ASCH a better community.
However @mannanj , it is a HUGE step to say that maybe they're corrupted, just because we're lacking some info. Using kind of words isn't very wise. I believe the proof of there is actually a good work going on is that the community is getting bigger, there are people working on DApps using ASCH's tech, and many people are volunteers here. That is a very good sign of that something good is happening here.
RE: Asch do you have a face? Humans do......
Well right now they showed their most human face https://twitter.com/AschPlatform/status/927753330398347264
RE: Delegates/Masternodes broken and unfair???
I'm glad you posted this like I suggested on Reddit, a healthy debate contributes to community.
Personally I believe it would help if the online wallet showed more information about delegates: what are they doing, their proposals, their work , etc.
RE: One of the most important things about Asch
Check out the white paper, under "Bizantine Fault Tolerance" and you will understand why Asch is so different. The team introduced PBFT (Practical Byzantine Fault Tolerance)
Byzantine Fault Tolerance
The major difference between Asch system and DPOS is reflected in the second part of the
What the DPOS applied is, first, randomly sorting the delegate list of current round (to make
sure the delegate of next round cannot be predicted since the order of delegate of each
round will be different), then let delegates create block in turn through a round-robin way.
The main issue of this algorithm is that, if a delegate attempt to attack, he may broadcast
many different blocks, which may contact double payment trades, to “fork” the whole
network. It is no doubt that if only one delegate betrays, the fork will be solved by syncing
with the next longest chain. However, it will take a much longer time to eliminate betrayed
nodes as their amount is increasing. A few betrayed nodes are enough to have a serious
impact on system security, which means even we can gain 6 confirmations, it still may not be
sure that the network is safe.
To deal with this problem, we introduced an algorithm known as PBFT (Practical Byzantine
Fault Tolerance). Same as DPOS, PBFT also chooses delegates in the way of round-robin. The
different part is there will not be a block generated after delegates are voted. In fact, there
will be a piece of propose issued to determine the hash code of next block. Only when more
than 2/3 of all nodes agree with this propose, next block will be generated. The hash of next
block must be the same as that agreed with all delegates of current round. Essentially, the
introduction of PBFT solved the issue of abusing the delegates’ right, and improved the
control capability of ledgers.