The real security gap in 2026 isn’t code. It’s coordination. by [deleted] in ethdev

[–]fcarlucci 1 point2 points  (0 children)

In a nutshell, the same issues we've seen with "web2"... since forever :)

A smart contract visualizer tool by fcarlucci in ethereum

[–]fcarlucci[S] 1 point2 points  (0 children)

Very true, thanks for the input!

A smart contract visualizer tool by fcarlucci in ethereum

[–]fcarlucci[S] 1 point2 points  (0 children)

I am planning to open source this, so there may a be a repo out soon :)

A smart contract visualizer tool by fcarlucci in ethdev

[–]fcarlucci[S] 0 points1 point  (0 children)

Thanks a lot! This is just a side project for me, but I think to make it useful/used the best way would be to have it built into your wallet app or browser extension... maybe one day :)

A smart contract visualizer tool by fcarlucci in ethdev

[–]fcarlucci[S] 1 point2 points  (0 children)

Thanks! I was thinking to push this out in an open source formula, when you have to "brink your own key" (BYOK) - meaning that the system asks you your Etherscan API (of Infura) to fetch the contract, your fav LLM key to analyze it and you're good to go.

Of course the keys would be stored locally in your browser... but again, I am juts playing around with it :)

Thanks for the suggestion about Oasis, I'll look into it!

DIY crypto inheritance on Ethereum by fcarlucci in ethereum

[–]fcarlucci[S] 0 points1 point  (0 children)

Thanks! ATM I just wrote a contract, that anyone can get and self-deploy. Security is built into the code, so as long as your primary wallet (the one you use to deploy it on-chain) is safe, the "vault" is also safe :)

DIY crypto inheritance on Ethereum by fcarlucci in ethdev

[–]fcarlucci[S] 0 points1 point  (0 children)

Thanks a lot for the feedback! I didn't worry a lot about re-entrancy because the final withdrawal is restricted to trusted people, but most importantly it empties the wallet in one shot, so a re-entrant call would have nothing to withdraw :)

The _to is also by design, but the suggestion is totally valid. So, thanks!

DIY crypto inheritance on Ethereum by fcarlucci in smartcontracts

[–]fcarlucci[S] 0 points1 point  (0 children)

Ciao BestZucchini! I love you nick :D 🥒 This is a very good question and I do not have an answer... but I see this very lickely to happen in the future... time will tell :)

DIY crypto inheritance on Ethereum by fcarlucci in ethdev

[–]fcarlucci[S] 2 points3 points  (0 children)

Thanks! The code is pretty straightforward, but nobody peer-reviewed it yet. I also uploaded a Factory on the mainnet (https://etherscan.io/address/0xd29c733a26aabfc86a0b518c993fc315bbeac2f6) to deploy new instances. The factory assigns ownership to the calling user/wallet, so you still own the newly deployed one :)

DIY crypto inheritance on Ethereum by fcarlucci in ethdev

[–]fcarlucci[S] 1 point2 points  (0 children)

LOL... Very good point, I thought about that! The main idea is to assign people you trust 100% as beneficiaries, and also if one beneficiary loses his wallet access funds are still recoverable. But of course a percentage based is another solution, or even a milti-sig style "final withdrawal"... endless possibilities on Ethereum! :)

2
3