THELOGICALINDIAN - n-a
I’ve ahead accounting about Quarkchain. What I saw aback again was good. I still accept my anxiety on cross-shard affairs and the association on finality, and I still animosity the accumbent scalability claim.
But in the QuarkChain cipher analysis I absolutely see some things that I like, too.
Testnet is up and running, hitting 10,000 aiguille TPS. Curious what this is per shard, back I accept the amount is cumulative. All-embracing TPS can be a bit of a ambagious metric back anniversary shards TPS should be abstinent individually. And does the all-embracing TPS booty basis alternation certitude into consideration?
All that aside, let’s accept a attending at the code, and see what they accept been up to back aftermost I looked at it.
Python, aforementioned as last. Our absorption is in pyquarkchain, so let’s accept a look.
Good annex management, contempo commits, 9 contributors. Signs of a acceptable repo, let’s dig in.
Quite a lot to go through. Layout is a bit weird. Key classes are in basis it seems, and again we accept directories for testnet, cluster, genesis_data? Might accomplish added faculty back we are added into the code.
Starting with utils, mostly wrappers, acceptable comments, acceptable allegation to libraries used.
Interesting abstraction. Seems a bit needless.
Protocol is the arrangement layer. RPC and affiliation data.
Very analytical to get into EvmState. Will get there soon. Looking at genesis_state currently. For now aloof a accomplish to the EVM state. So at this point balances and addresses alive in the EVM, so a bit of a decoupled architectonics architecture (consensus => EVM). I like the design.
ETH adversity calculations. Starting to feel a bit like Ethereum with sharding.
RocksDB acclimated for key amount brace storage.
Currently ecsda, approaching versions will accept secp256k1 it seems.
Core is mostly affection of activity functions.
Interesting allotment standards for testnet. Where is lambo and micra?
Interesting absence config values. Lots of testing account congenital into the config.
Accounts is as expected. Keystores, creation, etc. Great commenting.
adjust_difficulty is in p2p folder. Weird.
Jumping to array (which is their adaptation of node)
Master / Slave setup, not unpermissioned clusters.
Monitoring kafka blow address? Is transaction abstracts for clusters managed with kafka?
Real meat is in cluster/master.py, it’s good. Clusters are congenital the aforementioned way the shards are. The baton is about the basis alternation for anniversary cluster.
QuarkChain Code Review Conclusion:
It’s acceptable code. Because I authority Quark to a actual aerial accepted I did appetite more, although what I capital added I don’t know. It’s actual good, but I can’t advice but feel there is article added here. For now, it’s shards processing transactions, and affairs actuality committed to the EVM. QKC is active in the EVM. It’s a ascent band-aid for EVM that allows parallelized processing via the shards.
All in all, they body absolutely what they said they were activity to. I don’t anticipate this will see college than 25k TPS though, but it’s alcove allows for circumstantial acute arrangement beheading which is absolutely great. Acceptable code, acceptable progress. Will abide to accumulate an eye on them.
You can babble about QuarkChain in our Telegram group.
Disclaimer: Crypto Briefing code reviews are performed by auditing what is on affectation in the adept annex of the repo’s fabricated available. This was performed as an educational analysis and any comments in the commodity are the assessment of the writer. It is accustomed for cipher to change rapidly, appropriately we timestamp our cipher reviews so that they present a snapshot at a moment in time. Information independent herein should not be acclimated as any animadversion or admonition on the activity as a whole.
QuarkChain Code Review Timestamp: September 24th 2024
