@Jonbros01@kevinsekniqi A subnet can have more than one blockchain on it though and that idea might get lost with -chain names IMO. I think the -net suffix or something equivalent should be retained e.g. Warpnet. Or maybe something like 'Constellations' sticking with the space/scifi theme of AWM
@kevinsekniqi I thought AWM didn't necessarily rely on an intermediate relayer like IBC does? Or is that diagram just showing how one could implement AWM?
@kevinsekniqi@mrkit2u What specs do you think nodes need to move to atm? It seems to me that it's important to balance hardware reqs such that it doesn't lead to avax being majorly dependent on a handful of CSPs e.g. AWS. Esp given that the liveness threshold is a bit lower than other protocols.
@kevinsekniqi I feel like I see this term also used in the context of bridging where frequently it seems to be shorthand for "no additional trust assumptions" e.g. AWM. Is there a better, more concise term?
@avedarave_ I think people would look very differently on avax if they saw a primary net w/ 10,000+ validators (lower stake reqs) running an EVM++ with vastly improved state bloat, and liquidity flowing freely and quickly btwn a few popular subnets seeing 50+ TPS each.
@avedarave_ Especially since Warp, HyperSDK and Firewood aren't complete and C-chain currently just runs vanilla EVM. Avalabs could articulate explicitly the grand vision and the capabilities other chains are not capable of copying by laying out how these tech puzzle pieces fit together.
@kevinsekniqi@Tederminant Super cool to see this come out finally, I hope you guys make sure @Tederminant is getting his proper credit though!
https://t.co/osIKD8JG5w
Well...not so cool @_patrickogrady. After months of single-person effort of me proposing the architecture and finishing the first MVP alone, you guys mentioned me in 20th tweet in the thread, removed me from the author list in the repo, and redrew the pictures that I drew.
@Tederminant Kind of shameful treatment tbh, I don't get it. Those of us who pay close attention to the protocol know how key you've been along the way though, I hope they rectify things for you.
1/ With the recent AWS announcement I can feel the buzz building around the #Avalanche ecosystem. It seems like a good moment to highlight a few of the reasons that I build on Avalanche.
A. Technology
B. Team
C. Community
@DanielxKilleen@kelxyz_@avalabsofficial Folks can't discover this for themselves though because node reqs are so high and for a permissionless subnet attracting a set of validators is not a seamless process which has been abstracted away from the dApp deployer.
@DanielxKilleen@kelxyz_@avalabsofficial I think that the general conception of Avalanche is that it begins and ends with the C-Chain. The idea that Avalanche is a VM agnostic consensus platform is not really understood by crypto at large and I don't think avalabs' efforts thus far to the contrary have been sufficient.
@webshuuter It's semi-difficult to get the exact rate because staking reward periods fluctuate. On a yearly basis a conservative (read:high) estimate is reward rate x staking ratio x 100. With current #'s it's ~6.2%. Due to delegation fees and differing validation periods it's prolly lower
@nickwh8te@kevinsekniqi@cobie@epolynya@dystopiabreaker Can you really say that a byz actor somehow silently accumulating enough tokens to exceed the 80% safety threshold of avalanche carries a realistic probability of occurring and is therefore a "major flaw"? I kindamaybe get if your safety threshold is <=33%.