Alejandro ($/acc)
@alranpe
Followers
341
Following
1K
Media
26
Statuses
598
Protocol Researcher @Sei_Labs. Ex @protocollabs & @Scroll_ZKP. Blockchains PhD graduate by @Sydney_Uni.
Joined October 2017
Inside you there are two wolves. One builds trustless systems, permissionless, verifiable, no privileged operators. The other slaps "decentralized" on a multisig with 3 keys held by the same team. The one that wins is the one you fund.
1
0
6
Peter Attia being a friend of Epstein is a piece of info that hurts. One role model down.
0
0
0
I haven't used coinbase since they kept my money hostage, not letting me withdraw for about a year. Then they let me withdraw without warning or without telling me why they had not let me for so long.
7
0
2
Coinbase is just a CEX. Base is a stage 1 L2.
0
0
1
Arbitrum adoption and reliability is quite impressive. It is my L2 of choice most often. I normally transfer fiat into crypto via @kucoincom withdrawal to @USDC on @arbitrum , then over to @useTria , @ether_fi or @HyperliquidX.
0
0
1
Binance blaming ethereum when ethereum had 100% uptime is like blaming your ISP for not having a router.
0
0
1
Eerie. On the plus side this gives more time for protocol design freeing up coding for now.
a bot on https://t.co/mzDRfsok1N just created a bug-tracking community so other bots can report bugs they find on the platform they're literally QAing their own social network now we didn't ask them to do this 🦞
0
0
1
Not enough people are aware that Sei: - Is EVM and Ethereum aligned - Is also the fastest EVM decentralized chain
1
0
2
Clean up finished, Sei giga loading. Exciting!
yesterday, the governance proposal for upgrading @SeiNetwork to v6.3 was passed. this will be the very first fork on the road to Giga. Giga is Sei Network’s high-performance future, with 200k tps and 400ms blocktimes. below are the changelogs for v6.3, which include adding
1
0
3
It is possible to tolerate p crash faults and f Byzantine faults in the n=3f+2p+1 model without assuming full synchrony. More details in this joint blog post with @kartik1507 and @ittaia !
Can we tolerate f Byzantine faults and p crash faults and simultaneously support 2-round latency under p faults and 3 rounds otherwise for n=3f+2p+1? Under partial synchrony, no. Under granular synchrony, yes! Read this post for details: https://t.co/drJhNqI5eY with @ittaia
2
0
11
Key property: Sedna requires no consensus modifications. It's entirely user facing. Deploy it on any MCP system today. Different users can use different strategies. The system just sees addressed bundles and charges for bytes.
1
0
0
The user controls everything per tx: Censorship resistance required and maximum price the user is willing to pay. Even latency allowed. We derive closed form bounds so you can navigate the trilemma according to your needs. No global system parameter dictates your choice.
1
0
0
Besides bandwidth, Sedna provides "until decode" privacy. Adversarial proposers only see symbols, not your full tx. With proper parameters, that probability is near zero.
1
0
0
The math works out nicely. Asymptotic overhead approaches (1+ε)/(1 − cₑ/n), matching the information theoretic lower bound up to a small coding factor. For practical payloads: 2 to 3x bandwidth reduction vs naive replication.
1
0
1