Dhruba Basu Profile Banner
Dhruba Basu Profile
Dhruba Basu

@dhrubabasu_

1,364
Followers
256
Following
25
Media
232
Statuses

engineer @AvaLabs โ€ข vibes @NuveauxTrading

nyc
Joined January 2020
Don't wanna be here? Send us removal request.
@dhrubabasu_
Dhruba Basu
2 years
0/ @DefiKingdoms 's DFK Chain has cleared 2B API requests since their launch last week. @avalancheavax 's primary network cleared 15B API requests in the same time. A short thread on how @avalabsofficial came to operate one of the largest public blockchain APIs ๐Ÿงต
24
105
431
@dhrubabasu_
Dhruba Basu
2 years
# of Validators that control 33% of stake: Fantom - 3 Solana - 19 Avalanche - 27
18
38
228
@dhrubabasu_
Dhruba Basu
2 years
0/ ๐Ÿ“ŠInterested in graphs? @avalabsofficial just launched three new dashboards on #Avalanche Stats. For your consideration: - Reward Distribution - Network Status - Staking
17
48
201
@dhrubabasu_
Dhruba Basu
2 months
0/ Since ACP-77 was published ~1 month ago, there has been 100+ comments left on the discussion thread. This level of (almost ๐Ÿ˜…) overwhelming community engagement is amazing to see! Here's the updates that were made from this first round of feedback ๐Ÿงต
9
66
191
@dhrubabasu_
Dhruba Basu
1 month
Tell me you're incapable of building a performant chain with a large validator set without telling me. @avax is at 1782 validators and finalizes transactions within seconds.
@jayendra_jog
Jay
1 month
The entire industry is moving towards smaller validator sets. Every major L1 that has launched in the past 2 years has had a validator set of <200. Every major modular chain that has launched has had a sequencer set of 1. Huge validator sets will become a thing of the past.
84
20
241
16
37
150
@dhrubabasu_
Dhruba Basu
2 months
0/ ACP-77 calls for the removal of the 2000 $AVAX staking requirement for Subnet validators. In its place, a continuous P-Chain dynamic fee mechanism is introduced. Let's take a closer look ๐Ÿงต
4
44
121
@dhrubabasu_
Dhruba Basu
27 days
0/ Proposing ACP-103 w/ @Abenegia and @stephenbuttolph : Add Dynamic Fees to the X-Chain and P-Chain Read the full details on GitHub below! ๐Ÿ‘€
3
44
89
@dhrubabasu_
Dhruba Basu
8 months
ACP-20: Ed25519 p2p ๐Ÿš€ AvalancheGo, the primary @avax node client, uses TLS certificates to facilitate p2p messaging. By default, a 4096 bit RSA key is used to sign the certificate. ACP-20 proposes the adoption of Ed25519 instead.
6
38
84
@dhrubabasu_
Dhruba Basu
6 months
# of Validators that control 33% of stake: Sei - 7 / 39 Aptos - 18 / 125 Solana - 21 / 1829 Avalanche - 27 / 1717
@dhrubabasu_
Dhruba Basu
2 years
# of Validators that control 33% of stake: Fantom - 3 Solana - 19 Avalanche - 27
18
38
228
3
42
86
@dhrubabasu_
Dhruba Basu
5 months
AvalancheJS version 4 was released publicly today ๐Ÿค˜๐Ÿพ The @AvaLabs engineering team took this opportunity to completely rewrite the library from scratch. The result is a highly performant and lightweight JS library as fast as the @avax network ๐Ÿš€
3
18
84
@dhrubabasu_
Dhruba Basu
1 month
Sei's consensus protocol has quadratic communication complexity. If their validator set expands, they lose fast finality. It's convenient they claim this is where the industry is heading. Sounds more like a skill issue to me.
Tweet media one
@jayendra_jog
Jay
1 month
@0xCygaar disagree - this is a great thing it results in much more sustainable networks, greater upper bound network performance, and still allows for trustlessness/verifiability through approaches such as light clients that consume zk proofs
6
0
14
11
29
83
@dhrubabasu_
Dhruba Basu
2 months
0/ ACP-77 replaces the 2000 AVAX minimum cost to be a Subnet validator with a market-driven P-Chain continuous fee mechanism. What implications does this have for the Avalanche Network? ๐Ÿงต
9
25
75
@dhrubabasu_
Dhruba Basu
2 months
Loving the community engagement so far on the biggest proposal for @avax . Make sure to voice your opinion on ACP-77 below! I will be responding to every comment as ACP-77 makes its way from "Proposed" to "Implementable" ๐Ÿซก
3
23
72
@dhrubabasu_
Dhruba Basu
21 days
Join me in discussing ACP-103: Add Dynamic Fees to the X-Chain and P-Chain on June 20th at 14:30 UTC (07:30 PT/10:30 ET)! Following a brief presentation of the latest spec, @AvaLabs engineers will answer any questions The per Subnet Validator fee will be using this algorithm ๐Ÿ‘€
2
36
62
@dhrubabasu_
Dhruba Basu
7 days
RPCs provide a seamless way to interact with blockchains, but added latency can degrade the user experience At @AvaLabs , we are committed to delivering a high-performance public API. Proud to see that effort pay off, ranking #2 in median latency and #3 in p95 among all providers
@1kxnetwork
1kx
7 days
Today we announce Atlas. Atlas is a dashboard we built in-house to compare Web3 data providers. It is intended to inform developer decision-making around RPC provider use and to help researchers gain valuable data insights. โ†“
28
38
285
3
15
55
@dhrubabasu_
Dhruba Basu
1 month
The @AvaLabs engineering team is committed to large validator sets. Check out the latest consensus research from @_patrickogrady and co ๐Ÿ‘‡๐Ÿพ
@_patrickogrady
patrickogrady.xyz
1 month
Vena: Optimistically Responsive Consensus Over Large Validator Sets
14
115
247
4
9
54
@dhrubabasu_
Dhruba Basu
6 months
0/ Maximal Extractable Value (MEV) in crypto is often compared to or equated with Payment for Order Flow (PFOF) in TradFi. However, each impacts the unsuspecting trader in very different ways. Why? Regulations (I know, I know) ๐Ÿงต
3
32
52
@dhrubabasu_
Dhruba Basu
3 months
2/ ACP-77 will bring @avax to a world where Subnets: - Are not required to stake 2000 $AVAX per validator - Only sync the P-Chain (not X/C-Chain) - Have arbitrary validator requirements (e.g. ERC-20 or ERC-721 staking) - Have full control over staking rewards
5
4
49
@dhrubabasu_
Dhruba Basu
2 years
7/ In total, our public API clears 2.5B requests per day at an average latency of 108ms. As more and more subnets come online, we expect this number to balloon very quickly.
4
2
42
@dhrubabasu_
Dhruba Basu
11 months
ICYMI: The P-chain is height indexed as of Cortina 8. As part of this release, a new RPC method (platform.getBlockByHeight) was added to AvalancheGo. Check out the documentation here: Try it out on the public RPC!
Tweet media one
Tweet media two
@_patrickogrady
patrickogrady.xyz
11 months
4/ P-Chain Height Pruning/Indexing Cortina 8 deletes rejected blocks from disk (we stopped writing them a few releases ago) and reformats the disk format of accepted blocks to be more minimal. Additionally, this release indexes blockIDs by height.
1
0
15
4
11
35
@dhrubabasu_
Dhruba Basu
3 months
77 is the new 13 see you tmrw ๐Ÿซก
12
4
35
@dhrubabasu_
Dhruba Basu
3 months
8/ The requirements also do not have to be restricted to Avalanche. Subnets could require a lock-up of ERC-20s on Ethereum or SPLs on Solana. The possibilities are endless. Subnets now have full control over their validator set.
2
1
34
@dhrubabasu_
Dhruba Basu
3 months
1/ ACP-13 (authored by @_patrickogrady ) outlined a vision for how Subnets can evolve to give increased flexibility to Subnet creators. ACP-77 expands on those ideas, providing a technical specification that brings that vision to life.
2
0
35
@dhrubabasu_
Dhruba Basu
3 months
There is no ACP-77 without the one and only @AaronBuchwald
@_patrickogrady
patrickogrady.xyz
3 months
Wanted to give a big shoutout to @AaronBuchwald for his research over the last few months on different directions ACP-13 should take (its initial form left much to be desired) that informed many of the ideas in ACP-77. Recommend checking out the following write-ups to get a
3
10
79
2
3
35
@dhrubabasu_
Dhruba Basu
2 years
6/ The immensely popular Crystalvale launch for @DefiKingdoms could not have been a more perfect proof-of-concept. For DFK Chain, we clear 500M API requests per day at an average latency of 200ms.
1
2
34
@dhrubabasu_
Dhruba Basu
1 month
New ACP-77 research coming out of the @blockworksres showing it will be as cost-effective as Celestia-based rollups. If you want a teaser for how much a Subnet Validator will cost, read the full report :) s/o @EffortCapital for the in-depth analysis โค๏ธ
@blockworksres
Blockworks Research
1 month
Reinventing @AVAX Subnets. With the competition of dedicated blockchain solutions heating up, the Avalanche community is proposing a structural change in how Subnets launch. Potentially making them as cost-effective as operating a Celestia-based rollup. What is ACP-77? ๐Ÿงต
27
157
423
3
6
33
@dhrubabasu_
Dhruba Basu
3 months
5/ Requiring 2000 $AVAX per validator made Subnets prohibitively expensive. Regulated entities who cannot validate permissionless, smart contract-enabled blockchains (like the C-Chain) could not consider a Subnet. Evidently, Subnets were not as sovereign as creators expected.
2
1
30
@dhrubabasu_
Dhruba Basu
8 months
One use-case that I'm particularly excited about is ECVRFs. As specified in RFC9381 (), elliptic curves can be used to construct a VRF. This enables Subnets to utilize their validator sets in order to generate on-chain randomness secured by stake ๐Ÿคฏ
2
3
30
@dhrubabasu_
Dhruba Basu
6 months
Been a pleasure seeing @_patrickogrady (the crypto Mr. Beast) develop this idea Read the deep dive below๐Ÿ‘‡๐Ÿพ
@_patrickogrady
patrickogrady.xyz
6 months
1/ Introducing Vryx: Fortifying Decoupled State Machine Replication (How the #Avalanche HyperSDK Will Reach HyperTPS)
28
124
345
0
3
28
@dhrubabasu_
Dhruba Basu
3 months
4/ However, no Elastic Subnets are live on Mainnet. It was clear that Permissionless Subnets as they stand today could be more desirable. The hurdles for creating Subnets was too high, preventing Subnets from reaching widespread adoption.
1
0
28
@dhrubabasu_
Dhruba Basu
3 months
11/ With Subnets receiving far more sovereignty, an open question has been posed in the ACP: Should they still be called Subnets? The @avax community can take advantage of this opportunity to re-brand Subnets.
3
1
27
@dhrubabasu_
Dhruba Basu
3 months
7/ As the P-Chain only verifies the BLS multi-signature, Subnets can enforce any arbitrary requirement for joining the Subnet's validator set. A Subnet, for example, can require that validators lock up some set of tokens ($AVAX or others) on the C-Chain or the Subnet itself.
1
0
27
@dhrubabasu_
Dhruba Basu
3 months
6/ ACP-77 redefines the P-Chain <> Subnet relationship to provide increased flexibility for Subnet creators. By leveraging the BLS multi-signatures that secures Avalanche Warp Messaging, the P-Chain can authenticate adding/removing validators from the Subnet.
1
2
26
@dhrubabasu_
Dhruba Basu
2 years
4/ Since then, we've worked tirelessly to build the public API that exists today. For @avalancheavax 's primary network, we regularly clear 2B API requests per day at an average latency of 85ms. We are incredibly proud of this to say the least! But we're not done.
1
1
25
@dhrubabasu_
Dhruba Basu
3 months
3/ From day one, @avax envisioned interoperable chains natively communicating with each other by leveraging a single common layer (the P-Chain). Through Avalanche Warp Messaging, interoperability was delivered to the masses.
2
0
25
@dhrubabasu_
Dhruba Basu
3 months
9/ This new relationship between the P-Chain and Subnets also provides a dynamic where Subnets can use the P-Chain as an impartial judge to modify parameters (in addition to its existing role of helping to validate incoming Avalanche Warp Messages).
1
0
22
@dhrubabasu_
Dhruba Basu
3 months
10/ If a Validator is misbehaving, the Subnet validators can collectively generate a BLS multi-signature to reduce the weight of the misbehaving validator. This operation, and any other validator eviction, is fully secured by the Avalanche Primary Network.
1
0
21
@dhrubabasu_
Dhruba Basu
2 months
Tweet media one
@dankrad
Dankrad Feist
2 months
Together with Justin Drake, I have recently decided to become an advisor to Eigenlayer, on the same conditions -- I am taking this position personally, not representing the Ethereum Foundation, and with a focus on risks and decentralization. I am therefore fully expected to take
79
43
460
0
3
22
@dhrubabasu_
Dhruba Basu
2 years
5/ 2022 was dubbed the year of subnets. APIs are critical for subnets, after all it's the primary way users interact with them. We wanted to make sure subnet creators did not need to deal with the complexity of operating a public API and could instead leverage our API platform.
1
1
22
@dhrubabasu_
Dhruba Basu
2 months
7/ Thank you to everybody participating in the ACP-77 discussion thread. Many of these changes came directly from the thread โค๏ธ Make sure to voice your opinion on ACP-77 if you haven't already! I will continue engaging with everybody who comments ๐Ÿซก
1
4
22
@dhrubabasu_
Dhruba Basu
2 years
1/ When @avalancheavax launched in September of 2020, we launched a public API. At the time, the UX for this API was not great. We had to put in aggressive rate-limiting to ensure abusive users don't impact the experience of others.
1
1
21
@dhrubabasu_
Dhruba Basu
2 years
2/ When the first dapps came online in early 2021, normal users ran into these rate limits as dapps performed numerous API requests to get all the data needed for their frontends. Our discord support channel back then:
1
1
20
@dhrubabasu_
Dhruba Basu
6 months
Shoutout NodeID-64Zz8dh68ypXYWaUcfkXDm9UuG9VNXrk8 for being the first to support every ACP ๐Ÿซก Vote with your validator today!
@_patrickogrady
patrickogrady.xyz
6 months
Thanks to @dhrubabasu_ for helping to support this on the Public API ๐Ÿ™
Tweet media one
0
1
19
0
3
19
@dhrubabasu_
Dhruba Basu
5 months
The focus on minimal dependencies paid off tremendously. The bundle size of v4 is 10x smaller than the bundle size of v3: Minified: 1.1MB -> 129.7 kB Minified + Gzipped: 337 kB -> 38.3 kB
Tweet media one
Tweet media two
2
1
19
@dhrubabasu_
Dhruba Basu
2 years
3/ To export recent rewards in CSV, JSON or XLSX format, you can click the download button in the bottom right of your screen: Tis' the season after all๐Ÿ˜‰
1
3
18
@dhrubabasu_
Dhruba Basu
2 months
@puntium The maintenance burden and cost of running your own chain will go down over time making the Appchain thesis inevitable With ACP-77, Avalanche will enable chain creators to capture all value from their chainโ€™s activity since you are only paying for the size of your validator set
0
2
17
@dhrubabasu_
Dhruba Basu
5 months
> everyone will just blame RPCs Users do not care about the intricacies of blockchains. If you're lucky, they'll only blame the RPCs if they have a bad experience. When @avax had RPC issues early on, many users wrote us off and believed there was a problem with the chain itself
@0xMert_
mert | helius | hSOL
5 months
JUP airdrop is coming what will happen: - lots of bots will spam + compete - blocks will fill up - chance of user txns landing will go down - users will experience delays using the chain - some ecosystem teams won't be ready to handle this - everyone will just blame RPCs
86
131
1K
1
1
15
@dhrubabasu_
Dhruba Basu
8 months
Since ACP-20 also proposes signing the Snowman++ blocks with the same Ed25519 key, the validation criteria must be clearly defined. ACP-20 suggests ZIP-215 for the validation criteria. @hdevalence has a excellent article on this topic:
1
0
16
@dhrubabasu_
Dhruba Basu
1 month
A service to deploy L2s on a L1 is a *checks notes* L0?? 1) What
@tokenterminal
Token Terminal
1 month
Tweet media one
10
12
78
2
4
16
@dhrubabasu_
Dhruba Basu
5 months
We're very proud of how minimal the dependency list is. Big thank you to @paulmillr for creating all the dependencies we rely on! Truly a powerhouse in the crypto JS space โค๏ธ ๐Ÿซก
Tweet media one
2
0
16
@dhrubabasu_
Dhruba Basu
2 years
3/ It was clear that our API architecture needed to be reworked to service all these requests while maintaining a reliable service. We publicly announced the rework in April 2021 when we were clearing 3B API requests per month.
1
2
16
@dhrubabasu_
Dhruba Basu
2 months
3/ A minimum $AVAX balance commitment has been added to the Ed25519 signature. This prevents Subnet Validators from being registered with a lower than expected initial $AVAX balance.
1
0
16
@dhrubabasu_
Dhruba Basu
2 months
1/ To continue enabling Subnet Validators/Nodes to bootstrap securely without a dedicated set of bootstrappers, the Primary Network will track and gossip Subnet Validator IPs.
Tweet media one
1
0
15
@dhrubabasu_
Dhruba Basu
2 years
1/ Ever wondered how much AVAX was minted since genesis? Introducing the Reward Distribution dashboard:
Tweet media one
1
0
15
@dhrubabasu_
Dhruba Basu
2 months
โ€œfirstโ€=๐Ÿงข congrats on sub-second latency but no need to lie
@AptosLabs
Aptos Labs
2 months
1/ Aptos is setting a new standard as the first blockchain to achieve sub-second end-to-end (E2E) latency ๐Ÿ’ฅ Thanks to a series of performance and latency improvements by the Aptos Labs team, Aptos is the fastest blockchain on the market with truly instant transactions.
Tweet media one
56
134
393
1
4
14
@dhrubabasu_
Dhruba Basu
2 months
8/ For Subnet creators, this means that the cost of deploying a Subnet is reduced by hundreds of thousands of dollars. A production-grade Subnet is recommended to deploy with 8 validators which would require 16k $AVAX or $560k. After ACP-77, this upfront cost is removed entirely.
2
4
15
@dhrubabasu_
Dhruba Basu
8 months
If all Avalanche validators have a corresponding Ed25519 key, it opens up possibilities for future experimentation. For instance, this key could be used for to swap out TLS for alternative communication protocols like QUIC or NOISE.
1
0
14
@dhrubabasu_
Dhruba Basu
2 months
2/ However, a critical side-effect of the 2000 $AVAX requirement is an implicit cap on the total number of validators that can exist on the P-Chain. Dividing the maximum supply of 720M $AVAX by 2000 $AVAX per validator yields a maximum number of 360k validators.
1
1
13
@dhrubabasu_
Dhruba Basu
2 months
4/ SetSubnetValidatorWeightTx has replaced EvictSubnetValidatorTx. Subnets can modify the weight of an existing validator using this transaction. The validator will be removed if this transaction is issued with a Weight of 0.
Tweet media one
1
0
13
@dhrubabasu_
Dhruba Basu
2 years
2/ By default, it displays rewards for all validators/delegators. You can also filter by any number of NodeIDs and/or addresses.
Tweet media one
1
0
13
@dhrubabasu_
Dhruba Basu
2 months
6/ The Backwards Compatibility section has been updated with the migration path for existing Subnets to migrate to the new Subnet validation flow.
1
0
13
@dhrubabasu_
Dhruba Basu
2 months
2/ In the Warp payload specifications, "timestamp" has been replaced with "expiry" to avoid confusion with the transaction timestamp.
Tweet media one
1
0
12
@dhrubabasu_
Dhruba Basu
2 months
6/ ACP-77 proposes introducing a continuous P-Chain dynamic fee mechanism to replace the upfront fixed cost of 2000 $AVAX. Instead of staking 2000 $AVAX, Subnet validators will be charged a continuous dynamic fee in $AVAX throughout their validation period.
1
1
13
@dhrubabasu_
Dhruba Basu
2 years
5/ What happened to the old Staking dashboard? It underwent a full revamp to include historical data all the way back to genesis:
Tweet media one
1
0
12
@dhrubabasu_
Dhruba Basu
2 months
1/ Before ACP-77, all Subnet validators were required to be Primary Network validators. To be a Primary Network validator, 2000 staked $AVAX is required.
1
0
12
@dhrubabasu_
Dhruba Basu
27 days
1/ As resource-constrained environments, blockchains must carefully design a fee mechanism to fluctuate based on the supply of and demand for said resources to serve as a deterrent against spam and denial-of-service attacks.
1
0
11
@dhrubabasu_
Dhruba Basu
2 months
Impressiveโ€ฆ now letโ€™s see the e2e latency
Tweet media one
@AveryChing
avery.apt ๐ŸŒ
2 months
Breaking: New L1 record for daily transactions - all with no change in gas fees or success rate. This is @Aptos .
18
23
122
1
2
10
@dhrubabasu_
Dhruba Basu
2 months
5/ SetSubnetValidatorManagerTx has been added for Subnets to set the (blockchainID, address) pair managing the Subnet's validators. Subnets will be able to use a smart contract on their own Subnet, C-Chain, or any other Subnet to manage their validators.
1
0
11
@dhrubabasu_
Dhruba Basu
8 months
2/ With the growing number of subnets slated for launch on @avax , simple transfers will be demanded more by users. Supporting it natively on the network level will provide a cheaper option for both validators and users.
1
0
11
@dhrubabasu_
Dhruba Basu
2 months
10/ As the total number of Subnet validators approaches the target number, the Subnet validator fee will climb higher until the network stabilizes at the target number. While the total number of Subnet validators is below the target number, the fee will be very low.
2
0
11
@dhrubabasu_
Dhruba Basu
2 months
11/ Like all other P-Chain fees, all Subnet validator fees are burned.
2
1
11
@dhrubabasu_
Dhruba Basu
8 months
1/ To transfer between @avax P-Chain addresses, users must export their funds out of the P-Chain. Adopting this ACP solves this UX problem by unlocking native transfers on the P-Chain ๐Ÿ”“
1
0
10
@dhrubabasu_
Dhruba Basu
27 days
7/ Because block production is asynchronous in Snowman, many blocks could be produced in a short window to game the fee mechanism. ACP-103's fee mechanism has two key properties to account for the asynchronous block production.
1
0
10
@dhrubabasu_
Dhruba Basu
26 days
Solana doesnโ€™t have *automatic* slashing but does have the ability to slash after a network halt when they can attribute the safety violation: Avalanche doesnโ€™t have slashing either. Hard to slash all malicious validators without burning any honest ones
@0xvanbeethoven
Ludwig
26 days
til solana doesn't have slashing
1
0
20
0
1
10
@dhrubabasu_
Dhruba Basu
2 months
14/ Note that ACP-77 does not modify any Primary Network validation mechanics. The continuous fee mechanism only applies to Subnet validators.
2
0
10
@dhrubabasu_
Dhruba Basu
27 days
6/ ACP-103's fee mechanism defines a target gas/s T and adjusts based on excess gas consumption, defined as the difference between the current gas consumption and T.
1
0
10
@dhrubabasu_
Dhruba Basu
27 days
8/ First, block height cannot be used to determine if utilization is above or below target utilization. To account for this, the time between the current block timestamp and the parent block timestamp is multiplied by the target gas/s when updating the excess gas consumption.
Tweet media one
1
0
10
@dhrubabasu_
Dhruba Basu
27 days
2/ The current fixed fee mechanism on the X-Chain and P-Chain does not robustly handle spikes in load. Switching these chains to a dynamic fee mechanism will ensure that load is properly priced given allotted processing capacity.
1
0
10
@dhrubabasu_
Dhruba Basu
2 months
5/ Luckily, there is a battle-tested solution that enables drastic reduction in cost to become a Subnet validator while simultaneously metering the number of validators: dynamic fee mechanisms.
1
0
10
@dhrubabasu_
Dhruba Basu
2 months
9/ Regardless of the throughput on the Subnet itself, the sum of the Subnet validator fees for a Subnet is proportionate only to the number of Subnet validators. A Subnet with 8 validators and 0 TPS is charged the same amount in $AVAX as a Subnet with 8 validators and 100k TPS.
2
0
10
@dhrubabasu_
Dhruba Basu
2 months
4/ As ACP-77 outlines, it was clear that 2000 $AVAX per validator made Subnets prohibitively expensive. By reducing the amount required to become a Subnet validator, the maximum number of validators increases. This can cause memory pressure issues if implemented improperly.
2
0
10
@dhrubabasu_
Dhruba Basu
27 days
9/ Second, a block gas limit cannot meter the maximum rate of gas consumption on Snowman chains as multiple blocks can be issued at the same timestamp. Instead, a leaky bucket is employed to meter the maximum rate of gas consumption:
Tweet media one
1
0
10
@dhrubabasu_
Dhruba Basu
5 months
I'd like to give a special shoutout to @ohleevar for teaming up with me to create the initial MVP ๐Ÿซถ๐Ÿพ Huge props to the @coreapp engineering team for embracing it from day one. They tirelessly developed the MVP to achieve the results you see today!
1
0
10
@dhrubabasu_
Dhruba Basu
2 months
7/ After ACP-77 is activated, Subnet validators: - no longer have to hold a considerable amount of a volatile asset ($AVAX) - no longer receive $AVAX staking rewards since they are not Primary Network validators - no longer pay a large upfront cost before validating a Subnet
1
1
10
@dhrubabasu_
Dhruba Basu
27 days
11/ ACP-77 will re-use the same fee mechanism defined in ACP-103 for the continuous Subnet validator fee. I will be updating ACP-77 now that ACP-103 has the mechanism specified, stay tuned!
1
0
10
@dhrubabasu_
Dhruba Basu
2 months
13/ Since the memory footprint of a single Subnet validator is low, the target number of Subnet validators can be set very high (in the order of tens of thousands, if not hundreds of thousands or higher). For comparison, @avax currently has 267 Subnet validators on Mainnet.
1
1
10
@dhrubabasu_
Dhruba Basu
2 months
3/ Why is this important? Each additional validator on the P-Chain adds load to the P-Chain in the form of increased consistent RAM usage. With the fixed fee of 2000 $AVAX to add a validator, there was no concern that the P-Chain could face memory pressure issues.
1
0
10
@dhrubabasu_
Dhruba Basu
2 months
@puntium Running your own chain is hard. From managing bootnodes, defining a robust tokenomics curve to incentivize validation, integrating with tooling etc I donโ€™t consider L2s as your own chain since youโ€™re paying the L1 more for DA and security as activity on your chain goes up
1
1
9
@dhrubabasu_
Dhruba Basu
27 days
5/ Instead of deploying multidimensional fees now, ACP-103 sets up for a transition to multidimensional fees by measuring each transaction's consumption of the resources: - Bandwidth - Reads - Writes - Compute and merging them into a single "gas" dimension.
1
0
9
@dhrubabasu_
Dhruba Basu
27 days
4/ When determining the block packing algorithm that should be used, there were concerns of fairness/gameability that were not clear how to resolve. Further analysis/work needs to be done before deploying multidimensional fees on the @avax Primary Network.
1
0
9