Nebojsa Urosevic

42 posts

Nebojsa Urosevic

Nebojsa Urosevic

@neburo

Co-Founder & Blockchain Engineer @TenderlyApp

Katılım Mart 2017
146 Takip Edilen271 Takipçiler
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
The path forward for the ecosystem isn’t about choosing between L1 and L2 scaling. It’s about embracing both while making thoughtful decisions about the underlying tech stack. We’re on the brink of Ethereum reaching global adoption. Here’s what makes it possible. 👇
Tenderly@TenderlyApp

Scaling @ethereum has been the main barrier to global adoption. The dual L1 & L2 scaling strategy finally removes it. Our co-founder @neburo discusses the evolving Ethereum roadmap & why the new strategy is the path forward. Get insights here: 🧵 blog.tenderly.co/why-ethereum-d…

English
1
4
12
1K
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
@apoorveth @TenderlyApp Thanks for reaching out! We had a misconfiguration in our custom EVM module that disabled a specific opcode. Should be all good now 🙌 Regarding extended EIP-7702 support, we have some ideas for the dashboard but would love to hear your opinion on what you'd find most useful.
English
1
0
4
142
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
@gregthegreek @TenderlyApp Yes! Tenderly simulations already display message hash in the execution trace, though not as metadata. We’re adding UI visibility for this soon. Note: A compromised UI could allow malicious payloads to bypass detection. We’re exploring deeper Safe integrations to mitigate this.
English
1
0
3
51
Greg
Greg@gregthegreek·
Do @TenderlyApp simulations have a way to show the message hash you would be signing?
English
1
0
1
253
Nebojsa Urosevic retweetledi
Tenderly
Tenderly@TenderlyApp·
Tenderly engineers have worked on interesting technical endeavors while building our full-stack infra. 🟣 From integration challenges to deciphering unverified contracts, our team shares their insights in Dev Diaries. 📖 Take a look behind the scenes 👇 blog.tenderly.co/developer-diar…
English
1
4
17
711
Nebojsa Urosevic retweetledi
Aayush Gupta 🦇🔊
Aayush Gupta 🦇🔊@Aayush_gupta_ji·
I once telling everyone @TenderlyApp is the most underappreciated development tool, every dev should use.
English
0
3
19
703
Nebojsa Urosevic retweetledi
Kristof Gazso | kristof.eth
Kristof Gazso | kristof.eth@kristofgazso·
new debugging page is live on the @pimlicoHQ dashboard! - paste in user operations to generate a custom tenderly link with a complete tx trace - one-click prefill if you click the new debug button next to eth_sendUserOperation requests you have sent hats off to @TenderlyApp!
English
0
3
35
6K
Nebojsa Urosevic retweetledi
Tenderly
Tenderly@TenderlyApp·
Public testnets were never meant for dapp development. But until now, you had to use them. Not anymore. Replace public testnets with Virtual TestNets, the next-gen Web3 infrastructure designed for dapp development. 🚀 Build with mainnet data now 🧵 blog.tenderly.co/how-virtual-te…
English
38
67
385
105.9K
Nebojsa Urosevic retweetledi
Tenderly
Tenderly@TenderlyApp·
Optimistic rollups are retaining their market-leading positions, with significant growth in on-chain activity. 📈 The Dencun upgrade brought major drops in fees. 💰And many other optimistic trends are taking hold. 💪 Read the full report 🧵 blog.tenderly.co/optimistic-rol…
English
4
17
74
47.9K
Nebojsa Urosevic retweetledi
Tenderly
Tenderly@TenderlyApp·
The Dencun upgrade is live, bringing over a 10x drop in gas fees on L2s. 🎉 With such low fees, you can expect more dapp users to come in. So, the best time to build is now! 🏗️ And with our full-stack infrastructure, you can do it with ease. 🧵 docs.tenderly.co
English
1
5
12
801
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
Maintaining a personal list of ideas often proves to be unproductive. If an idea truly has merit, it will reemerge naturally as you delve into problems
English
0
1
12
454
Serj Korj
Serj Korj@SerjKorj·
@BogdanHabic was right — @neburo is really amazing host! 🔥 Thanks to him now I’m sure that’s Belgrade is the center of discussions about the future of blockchain and banking system 😉 It was very insightful 2 hours 🤯 The most important part is @TenderlyApp office is the only place where founder makes just the best espresso himself ☕️😉 @TarunMangukiya thanks for your intro 🙏 Week is just started and start was amazing! 🚀
Serj Korj tweet media
Belgrade, Republic of Serbia 🇷🇸 English
4
0
13
801
Serj Korj
Serj Korj@SerjKorj·
Next stop is Belgrade 🇷🇸 As a @ycombinator founder @paulg advised to @bchesky — just go where your customers are 😉
Serj Korj tweet media
Dubai, United Arab Emirates 🇦🇪 English
1
0
27
11.2K
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
@msolomon44 @BogdanHabic @fvictorio_nan Yes, the ethresearch post explains how to adjust search in case of internal transaction failures. Regarding O(1) complexity in estimations, the issue lies with internal transactions and their gas availability. The idea is to recalculate minimal gas without any internal failures.
English
0
0
0
33
Matt Solomon
Matt Solomon@msolomon44·
@BogdanHabic @fvictorio_nan Hmm I still don't understand how it's O(1) 😅 Form the ethresearch post it sounds like it's still a binary search but you change the condition for trying again with a lower gas limit?
English
1
0
1
66
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
I'll be at @EthereumZurich from April 14-16 and will be sharing some thoughts on EOF on a panel "Decoding Ethereum Object Format (EOF)" with some awesome speakers. 🚀 Looking forward to meeting the community and old friends. Feel free to DM and meet!
English
1
1
12
827
Nebojsa Urosevic
Nebojsa Urosevic@neburo·
@nnnnicholas This has been becoming a practice for many dApps nowadays, not saying that I fully agree with this approach, but it has some upsides. In cases like this one, @TenderlyApp Simulations can be your best friend, shedding light on reverted internal transactions and output of execution
English
0
0
2
60
nicholas ⛱
nicholas ⛱@nnnnicholas·
idk who needs to hear this but if you're writing a function that calls another contract, and the internal call keeps running Out Of Gas, it might be bc you're not reverting upon failure of the internal call. when wallets simulate the tx to determine gas limit, it succeeds regardless of the outcome of your call to another contract. The gas limit will be set too low and you'll run out of gas. Thanks to @DrGorilla_md for helping me understand this.
English
3
0
14
1.3K