Petar Maksimović | Nethermind
@PetarMax
Followers
99
Following
22
Statuses
28
Formal Verification Engineer and BD Lead (@NethermindEth). Web3, program analysis, photography, singing, tennis, mental health. All views are my own.
London, UK
Joined October 2012
RT @NethermindSec: Who verifies the (zk) verifier? Nethermind! The Formal Verification team at @NethermindSec, led by @JulekSU, just made…
0
19
0
RT @intmaxIO: In collaboration with the Formal Verification team at @NethermindSec, we’ve prioritized security by rigorously validating our…
0
6
0
RT @JulekSU: Excited to be releasing details of this work! Applying @leanprover to verifying the security properties of @intmaxIO's INTMAX2…
0
4
0
RT @NethermindSec: In collaboration with @intmaxIO, the Formal Verification team at Nethermind Security has formalized the INTMAX2 protocol…
0
7
0
@Ismael_H_R @ant_sabado @zksync Actually, it was their zk verifier that was verified and this was a first-of-its-kind effort, done in collaboration with the Nethermind Formal Verification team led by @JulekSU. We will be publishing a comprehensive blog post soon!
0
2
4
RT @JulekSU: Was really a pleasure working with @intmaxIO, particularly @HiokiLeona, Erik and @missbitcoin_mai! Also, appreciate my team's…
0
16
0
RT @NethermindSec: It's been a pleasure collaborating with @intmaxIO on formally verifying key security properties of the INTMAX2 protocol…
0
14
0
This off-the-cuff comment Magnus made can't be an attempt to influence FIDE because it was said privately to Ian and FIDE separately agreed for the title to be shared. It was, however, extremely unfortunate, leaving one thinking: "What would have happened had FIDE not agreed?" People seem to think that in that case Magnus and Ian would have actually gone through with the quick-draw festival, but that is not likely. Doing so would only have damaged their fair-play reputation in front of the entire chess world and given FIDE the best possible ammunition against Magnus, much unlike the dress code PR disaster of which they were rightfully on the receiving end. Having said this, the rules are such that the tie is broken by the first win, and the format clearly favours winning if the players play fairly. Out of the 14 games Magnus played yesterday, 10 were decisive, including the first four against Ian. Citing "lacking decisive tie-break rules" doesn't really hold water.
2
0
8
RT @NethermindSec: @vanishree_rao We've worked with @zksync to verify the functional correctness of their on-chain verifier, @RiscZero to p…
0
5
0
RT @NethermindSec: @drakefjustin Amazing initiative, @drakefjustin — we have no doubt that it will result in many successful projects that…
0
7
0
RT @FormalLand: With formal verification, you avoid the need to do successive code audits, as the reasoning of why the code is correct is w…
0
4
0
2/2 The money we raise together will help Shelter be there for more children and families facing homelessness this winter and beyond. Thank you :)
0
0
2
1/2 On the 3rd of December I will be taking part in the Walk for Home initiative organised by the Shelter charity, the goal of which is to help 151,000+ children living in unsafe and unfit housing in the UK right now. Any donations would be hugely appreciated.
0
0
2
RT @tkstanczak: In the recently published 6-part Ethereum roadmap discussion, @VitalikButerin highlighted that "our task is to bring the ro…
0
91
0
RT @NethermindEth: ⚡️Supercharging @ethereum while keeping it decentralized, secure & stable. Introducing Surge Rollup, an ULTRABASED roll…
0
122
0
I am thrilled to annouce that I have joined the Lamport team at @NethermindEth as a Formal Verification Engineer and Business Development Lead. Looking forward to contributing to the vision of Nethermind and the overall web3 ecosystem!
0
1
11
Here's a little something I had the pleasure of working on at @rv_inc, a very fruitful collaboration with @term_labs!
1/ Today, we bring a new blog post written in conjunction with @term_labs on how audits can optimize the code base 🛠️🔎. In this case, how a 2-week audit resulted in a new simplified algorithm to improve code efficiency
0
2
7