Sabnock pfp

Sabnock

@sabnock.eth

154 Following
532 Followers


Sabnock pfp
Sabnock
@sabnock.eth
Which projects have / are integrating with Coinbase Smart Wallet?
1 reply
2 recasts
15 reactions

Sabnock pfp
Sabnock
@sabnock.eth
cc @wilsoncusack
0 reply
0 recast
0 reaction

Sabnock pfp
Sabnock
@sabnock.eth
Which projects have / are integrating with Coinbase Smart Wallet?
1 reply
2 recasts
15 reactions

Sabnock pfp
Sabnock
@sabnock.eth
Anyone out there?
16 replies
5 recasts
170 reactions

Sabnock pfp
Sabnock
@sabnock.eth
Rm
0 reply
0 recast
1 reaction

Sabnock pfp
Sabnock
@sabnock.eth
Seems like that shouldn't work since Shanghai is a version before that upgrade?
0 reply
0 recast
0 reaction

Sabnock pfp
Sabnock
@sabnock.eth
Usually you use the name of the execution upgrade (eg Shanghai and not shapella)
1 reply
0 recast
0 reaction

Sabnock pfp
Sabnock
@sabnock.eth
That's Cancun. Dencun is an informal portmanteau of the CL upgrade, Deneb, and EL upgrade, Cancun. https://github.com/ethereum/execution-specs/blob/master/network-upgrades%2Fmainnet-upgrades%2Fcancun.md
1 reply
0 recast
1 reaction

Sabnock pfp
Sabnock
@sabnock.eth
Shouldn't you be using "cancun"?
1 reply
0 recast
0 reaction

Sabnock pfp
Sabnock
@sabnock.eth
I don't *think* anyone has built multicall in Huff yet but I would double check huffmate
1 reply
0 recast
2 reactions

Sabnock pfp
Sabnock
@sabnock.eth
🔵
0 reply
0 recast
3 reactions

Sabnock pfp
Sabnock
@sabnock.eth
Having met him, I'd say a vampire
0 reply
0 recast
2 reactions

Sabnock pfp
Sabnock
@sabnock.eth
I think that's fine. I just dislike the all too common practice of writing them for every contract in your project and inheriting. I think you should he inheriting as few interfaces as possible.
1 reply
0 recast
0 reaction

Sabnock pfp
Sabnock
@sabnock.eth
If you've used foundry-huff in the past to build your Huff projects, you may prefer the more minimal huff-runner from @jtriley Give it a try https://github.com/whitenois3/huff-runner
0 reply
0 recast
27 reactions

Sabnock pfp
Sabnock
@sabnock.eth
As in if you have all you structs and errors defined at file-level in one file, do you think named imports should be preferred regardless of length? import { Struct1, Struct2, Struct3, ... StructN, Error1, Error2, Error3, ... ErrorN } from "lib.sol" as opposed to import "lib.sol"
1 reply
0 recast
0 reaction

Sabnock pfp
Sabnock
@sabnock.eth
Think you should add a comment clarifying imports declared at file level which you don't address. As in is it permissible to have an unnamed import if what you're importing is at file-level or don't declare anything at file-level and import it at all?
1 reply
0 recast
2 reactions

Sabnock pfp
Sabnock
@sabnock.eth
I love it so much
1 reply
0 recast
4 reactions

Sabnock pfp
Sabnock
@sabnock.eth
Yes
0 reply
0 recast
1 reaction

Sabnock pfp
Sabnock
@sabnock.eth
https://vitalik.eth.limo/general/2021/06/18/verkle.html
0 reply
0 recast
1 reaction

/ / / / . KNNY® pfp
/ / / / . KNNY®
@knny
SONY FH-100W https://gallery.so/post/2e6zZSFdhm7jVgjy50acfvBQrQj
1 reply
1 recast
3 reactions