5bb55b Profile
5bb55b

@5bb55b

Followers
1K
Following
484
Statuses
152

KASPlex | https://t.co/ugu8FLDER2 Technical Advisor | HODL

Hong Kong
Joined July 2022
Don't wanna be here? Send us removal request.
@5bb55b
5bb55b
2 months
v2.03 ready for tn10. 4 new OPs, issue/burn/blacklist/chown. The issuance mode will be supported. AMM next. #kaspa #krc20
13
62
264
@5bb55b
5bb55b
5 months
RT @kasplex: 🚀 KRC-20 Mainnet Launch Announcement 🎉 We are thrilled to announce that Kasplex KRC-20 will be launching on the MAINNET on th…
0
834
0
@5bb55b
5bb55b
6 months
@KaspaAlph @kasplex @DesheShai @zerodmsion @kaspa_chinese 一定會開源的,這也是去中心化的一部分。
2
0
19
@5bb55b
5bb55b
6 months
@Krypt0Lurker As a public service, the firewall services will be used
0
0
1
@5bb55b
5bb55b
6 months
@maxibitcat The Light-Indexer of the future can do this
0
0
1
@5bb55b
5bb55b
6 months
RT @KaspaCurrency: The Release Candidate with RBF, Dynamic Fees, Optimized mempool and much more is here! Wallets…
0
210
0
@5bb55b
5bb55b
6 months
@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
@5bb55b
5bb55b
6 months
RT @MichaelSuttonIL: Revealing Kaspa's 10BPS hardfork roadmap — the “Crescendo” Hard-Fork 👇
Tweet media one
0
271
0
@5bb55b
5bb55b
7 months
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
@5bb55b
5bb55b
8 months
RT @kasplex: 🚨 Exciting news, Kaspa enthusiasts! 🚨 Kasplex Open Beta is just around the corner! 🕒 Mark your calendars! On June 30th, expl…
0
475
0
@5bb55b
5bb55b
8 months
RT @kasplex: New update released: 11 June 2024 Version 1.03 1、Preallocation - You can now allocate a certain amount of tokens to a spec…
0
111
0
@5bb55b
5bb55b
8 months
緊接著的是一項非常非常重要的工程實現😁。
13
7
41
@5bb55b
5bb55b
8 months
RT @kasplex: We've just released a new update for Kasplex: 03 June 2024 Version 1.02 1、Change allowed ticker length - Now you can have t…
0
139
0
@5bb55b
5bb55b
9 months
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
@5bb55b
5bb55b
9 months
RT @kasplex: 🎉Kasplex is now live on Kaspa TN11! 🎉 Get ready to test and integrate Kasplex into your applications on the lightning-fast 1…
0
238
0
@5bb55b
5bb55b
9 months
RT @kasplex: 📣Calling all developers! 📣 We're excited to announce that the Kasplex beta launch is just around the corner! This Friday, we'r…
0
226
0
@5bb55b
5bb55b
9 months
Yes the reorganization mechanism of DAG - parallel blocks makes a little complexity, but only a little😎.
@DesheShai
Shai ❤️ Deshe 💜 Wybors𐤊i 💙 (大胡子)
9 months
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.
Tweet media one
0
1
23
@5bb55b
5bb55b
9 months
@auzghosty @hashdawg_ @KaspaCurrency @LiberatedPotato If do this, it will not be accepted by all other indexers that follow the correct protocol.
1
0
2