![5bb55b Profile](https://pbs.twimg.com/profile_images/1773228443284738048/w7-HBIey_x96.png)
5bb55b
@5bb55b
Followers
1K
Following
484
Statuses
152
KASPlex | https://t.co/ugu8FLDER2 Technical Advisor | HODL
Hong Kong
Joined July 2022
RT @KaspaCurrency: The Release Candidate with RBF, Dynamic Fees, Optimized mempool and much more is here! Wallets…
0
210
0
@DesheShai Yes, we can have a smaller archive database, which is easier to maintain, but we may still keep at least one complete copy of the original data.
2
4
56
RT @DesheShai: Had a nice morning meeting with the @kasplex team where they updated me on their progress on several fronts and we had some…
0
178
0
RT @MichaelSuttonIL: #Kaspa 10-BPS testnet #TN11 is looking quite a beauty now I think this DAG structure is a better reflection of how 1…
0
305
0
Yes the reorganization mechanism of DAG - parallel blocks makes a little complexity, but only a little😎.
So I was sent this video by @QuaiNetwork (a project I know nothing about) that alleges to compare Quai with $kas. I don't have time to watch a 45 minutes "comparison" video, so I decided I would just watch it up to the first major mistake which arrived (surprisingly?) about 5 minutes in. The guy who calls himself "Dr K" claims that GHOSTDAG reorgs are easy "because Kaspa is a UTXO chain" and that it would be much more difficult for "smart contracts or an account system", he then assesses that for that reason "Kaspa will never have programmability". We've heard this kind rubbish since Kaspa launched. Any layer that works above the consensus level (be it UTXO, AAM, EVM, etc.) is agnostic to how the chain is obtained. Any computations that are made, are made with respect to the chain returned by GHOSTDAG. If there is some reorg that changes say the last 10 blocks in the chain, the complexity of recomputing is exactly the same as it would have been in a depth 10 reorg in a regular chain. The (proven and peer reviewed) security of GHOSTDAG assures that only a small suffix of the chain (that is, the ordering of the entire DAG output by the consensus layer) is ever changed. This is exactly the same as the security properties of say Bitcoin or pre-merge Eth. assuring only shallow reorgs. Beyond that point, the complexity of recomputing is exactly the same. Arguing that recomputing is more difficult than DAGs is, essentially, not understanding the blockDAG paradigm at all. I didn't watch the rest of the video, so if a point that's actually salient is made feel free to bring it to my attention. But always remember that the "DAGs can't support smart-contracts" attack vector is futile, and people who use it are either misleading or just haven't properly done their research. When it comes to Kaspa its the same story every time: 1. people tell us what we are aiming for can't be done (often not as an honest observation but in attempt to step over us to promote their own project), 2. we do it anyway. Smart contracts and other forms of programmability will be no different.
0
1
23
@auzghosty @hashdawg_ @KaspaCurrency @LiberatedPotato If do this, it will not be accepted by all other indexers that follow the correct protocol.
1
0
2