Nishant Das
@n1shantd
Followers
842
Following
2K
Media
3
Statuses
293
Previously @OffchainLabs @prylabs
Singapore
Joined November 2018
After seven and a half years, I've made the bittersweet decision to step down from my role at @prylabs . I want to thank my amazing colleagues at @OffchainLabs for everything over the past few years. I am deeply proud of what we have accomplished over the years.
23
6
143
Amazing job by the partnerships team at @OffchainLabs on getting this deal done ! Big moves for arbitrum.
Working with the @RobinhoodApp team has been an incredible journey. We believe the launch of their tokenized stocks on @Arbitrum today is just the beginning of what will be the rails that powers finance all around the world with their soon to be Robinhood Layer 2 blockchain. 🧵.
0
0
3
RT @arbitrum: Robinhood is now onchain with Arbitrum!. Arbitrum will serve as @RobinhoodApp's rails to merge DeFi and TradFi in what is a 0….
0
942
0
RT @OffchainLabs: Eight years of shaping Ethereum. From powering the Beacon Chain to shipping the Merge, Dencun, and now Pectra — Prysm has….
0
84
0
Building Prysm and Ethereum has been a great privilege and I am very grateful for being able to be a part of it over the years. To the ethereum community, both the coredevs and larger ecosystem, thank you for everything over the years and making ethereum an awesome place to be.
1
0
31
RT @prylabs: 🚀 Prysm v6.0.1 is out.- Includes bug fixes to payload_attributes endpoint. - Reminder: To be compatible with Pectra, you must….
github.com
v6.0.1 This release fixes two bugs related to the payload_attributes event stream. If you are using or planning to use this endpoint, upgrading to version 6.0.1 is mandatory. (H/t IBribe2Much for f...
0
21
0
RT @leonardoalt: looking forward to eth RISCV being proposed [check], implemented [started], discussed for years, and then abandoned.
0
4
0
This position would be basically ossifying the evm in its current form. I don't see how we could make any significant changes without EOF.
I was one of EOF's biggest supporters. I now think we might be making a mistake. Speaking for Reth:.1. Nix it altogether. Replace with EIP7912. 2. If we cannot rally core dev teams on (1), do EOF w/ code & gas introspection restored. Screenshot w/ full context.
3
1
7
If you want to significantly increase the transaction payload size on mainnet, bandwidth will be the biggest bottleneck. You would need to have both ePBS and RLNC to allow bigger payloads to be propagated to the network in time.
EPIC ACTUAL DATA on how much the gas limit can be raised. initial results suggest that all 5 node clients can already support a substantially higher gas limit. mainnet is currently 1.25MGas/s. the 5 node clients are supporting 80x - 280x times that. still need to comb through
0
2
5
RT @beaconcha_in: We are now ready for Pectra! 🥳. 👉Validator deposits with invalid signatures are now handled correctly. 👉Pectra deposit qu….
0
17
0
I dont understand points like this at all. You cant increase the gas limit safely before fixing the dos vectors. The gas limit is always specified to handle the worst case blocks for clients.
@notnotstorm @GiulioRebuffo removing dos vectors is not scaling but these fixes are needed. i’m not against them obviously. i think my criticism is pretty simple and clear: we’re doing many things in parallel and most don’t really provide much to the end user. at the end the market will solve things.
0
1
2
RT @OffchainLabs: Our Chief Scientist, @EdFelten, appeared on @CNBC yesterday to discuss tariffs and their impact on crypto. “We don’t th….
0
33
0
Simulations carried out have shown that we would be able to double pectra's current target blob count with no loss in latency. This could be applied to peerDAS to support even higher blob counts.
1
1
7
The rest of the peers receive announcements instead. What does this achieve ? It greatly reduces the amount of duplicates in the network. With a reduced number of message duplicates you can correspondingly bump up the blob count.
1
0
6
This introduces 2 new control messages along with a new announcement degree parameter. Gossipsub currently eagerly pushes messages, we add to it with a new lazy pull mechansim. Instead of broadcasting messages to your whole mesh, you only send to a subset of them.
1
0
4
Gossipsub v2 , a way to double the blob count without peerDAS.
ethresear.ch
Authors: Pop, Nishant, Chirag tldr; with gossipsub v2.0, we can double the blob count from whatever is specified in Pectra Gossipsub v2.0 spec: here Introduction Gossipsub is a pubsub protocol over...
7
19
106
RT @OffchainLabs: Episode 3 of Core Notes from Core Devs is now out!. Catch the Ethereum core developers at @offchainlabs discuss the lates….
0
73
0
There is no reason a current client can't be modified to be a beam client in the future. 95% of what a client does exists outside its state transition process. Reimplemening components in new clients which are already battle tested in mainnet currently is insanity.
1
0
21