Arifanaytulla pfp

Arifanaytulla

@arifanaytulla

363 Following
77 Followers
Arifanaytulla pfp
Why @PlasmaFDN consensus design actually scales scaling blockchains isn't just about tps, it is about coordination getting validators to agree FAST & SECURELY but consensus at scale it is really hard here is how Plasma makes it work= why is consensus hard at scale more validators = more messages = exponential complexity in worst cases, it can degrade to quadratic communication that is a bottleneck for performance & reliability. instead of everyone validating every block plasma picks a small set of validators each round it is faster lighter and avoids message overload. how does plasma pick the committee via a cryptographically secure random process... weighted by proof of stake more stake = more chance of being chosen. slashing= keeping validators honest stake slashing = you misbehave you lose funds reward slashing = misbehave slightly lose your rewards.
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
I spent some time researching how @PlasmaNetwork is approaching Bitcoin interoperability and it's actually a big deal. @PlasmaFDN is making bitcoin more usable across chains their native BTC bridge lets users move bitcoin into plasma without centralized custodians or trusted third parties this means better liquidity cross chain utility and true interoperability. most #BTC bridges today they rely on custodians or small groups of operators @PlasmaFDN flips the script with a decentralized permissionless validator set the same one securing its network. So how does @PlasmaFDN BTC bridge actually work 1. Asset locking, you send BTC to a Plasma controlled address 2. Token minting, validators see it & mint wrapped BTC on Plasma 3. Redemption, you request BTC back validators sign & send it to your wallet Nothing moves without 2/3 of validators signing off this uses threshold Schnorr signatures + Bitcoin's Taproot upgrade making it secure, efficient and hard to censor or compromise.
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
Why didn't @aztecnetwork just use the EVM because EVM wasn't built for privacy let me explain what they built and why Most Layer 2s copy paste the EVM and scale it but @aztecnetwork said nah… we want programmable privacy and the EVM can't handle that so they built their own VM from scratch "the Aztec VM" The EVM is fully public by design every, function call, parameter storage update …is visible on chain if you are building private DeFi, voting or identity that is a dealbreaker. @aztecnetwork solution? build a new architecture with= private state,public state private execution environment 'PXE' a custom zk friendly VM. Public State vs Private State public state = like ethereum anyone can read it private state = encrypted only the user & prover can see it @aztecnetwork lets you work with both in the same app
0 reply
0 recast
0 reaction
Arifanaytulla pfp
Ever wondered how @PlasmaFDN keeps things fast and secure? It is all thanks to their custom built consensus "PlasmaBFT" but first let’s talk about HotStuff. HotStuff is a way for blockchains to agree on what happened fast It avoids unnecessary delays and lets nodes agree in fewer steps, that means quicker transactions. @PlasmaFDN takes HotStuff and makes it even faster with PlasmaBFT It skips an extra step most of the time, so blocks get confirmed quicker in just two rounds instead of three. The result? lower fees, faster confirmations and a smoother user experience, perfect for stablecoin transfers where speed really matters. PlasmaBFT is also super safe as long as less than 1/3 of the validators act badly, everything runs smoothly and securely It even runs multiple steps in parallel to speed things up while one block is being finalized the next is already on the way.
0 reply
0 recast
0 reaction
Arifanaytulla pfp
Been digging into @SeismicSys gitHub lately and here is what I noticed= The repo is active multiple contributors pushing major commits and PRs are flowing in that is always a good sign. Latest PRs are mostly small fixes (like typo corrections) which usually means the core smart contracts are already in place and we’re in the polish phase. Big commits like “845++” and “4406++” tell us there’s been heavy dev work behind the scenes smart contracts like Competition.sol & MockStore.sol are visible. If we go by dev patterns, I’d guess @SeismicSys is just a few steps away from launching its testnet realistically 4_6 weeks is a fair bet. From early code to now it is looking like Seismic’s team (shoutout to @lyronctk @ravi_riley @0xameya rohanpatra and others) is heads down building. Testnet szn is close @noonne_art @xealistt @heathcliff_eth
0 reply
0 recast
0 reaction
Arifanaytulla pfp
Biggest takeaway from yesterday’s @SeismicSys AMA= The real obstacle ahead isn’t building it is the market risk. Here is what I mean🤞🏻 When @SeismicSys first started the big question was "Can we even build base layer encrypted infrastructure"? That is execution risk If you fail at that, nothing else matters. fast forward to today= Seismic has crushed the hard parts devnet is live, testnet is coming soon shielded computation,shielded storage its all happening now the challenge has changed, it is about adoption. this is called market risk, the scary part? even if you build something powerful there’s no guarantee people will use it you have to win hearts, minds and ecosystems. So why do I think @SeismicSys will win? because crypto desperately needs encrypted blockchains without privacy, there is no serious gaming, no serious DeFi, no serious anything forced transparency holds us all back!!!!!! It is just a matter of time @lyronctk @xealistt @noonne_art @heathcliff_eth
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
1 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
1/ Imagine buying a house where every single room has glass wall that’s crypto today transparent yes but would you really want everyone to see your transactions. 2/ Ethereum and other L1s gave us scalability but left us with forced transparency good for decentralization bad for privacy. Businesses and serious users need a fix 3/ Most blockchains encrypt wallet balances cool,that’s like hiding your bank account number but still letting people watch all your transactions. 4/ Enter @SeismicSys not just another L1 but an encrypted blockchain Instead of slapping encryption on top it’s baked into the base layer privacy by design not by patchwork. 5/ Think of @SeismicSys like Incognito mode but for everything onchain. Transactions hidden,smart contract logic hidden,even your app parameters hidden. 6/ @SeismicSys isn’t relying on Zero-Knowledge Proofs (ZKPs) Instead,it’s using a mix of MPC + FHE that’s some next level encryption
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction
Arifanaytulla pfp
0 reply
0 recast
1 reaction
Arifanaytulla pfp
0 reply
0 recast
0 reaction