Content pfp
Content
@
0 reply
0 recast
2 reactions

timbeiko.eth pfp
timbeiko.eth
@tim
please farcaster, halp
6 replies
3 recasts
40 reactions

Danno Ferrin pfp
Danno Ferrin
@shemnon.eth
I think Martin is wrong if it's what I'm thinking it is, which is the synthetic tx trick used during the dao and used to deploy the beacon root contract. It's still an EOA, it's just that no one knows the private key to the address, since you can extract a public key from almost any random r and v.
1 reply
0 recast
3 reactions

Danno Ferrin pfp
Danno Ferrin
@shemnon.eth
Also, any funds sent to the synthetic address (the contract deployer) should be considered lost as no one knows the private key. And if someone figures out how to get the private key we are in so much more trouble than wondering if it's an EOA.
1 reply
0 recast
0 reaction

Martin  pfp
Martin
@koeppelmann.eth
I would say an address that no one owns is not an eOa - or would you call 0x0000… an EOA?
2 replies
0 recast
0 reaction

Dan Finlay 🦊 pfp
Dan Finlay 🦊
@danfinlay
Philosophically it’s not owned, but at the protocol level it has spent gas and sent a tx, so it resembles an eoa in every other meaningful functional sense.
0 reply
0 recast
1 reaction

Danno Ferrin pfp
Danno Ferrin
@shemnon.eth
I call those accounts "hollow" - they could be either an EOA or a contract but we won't know until filled with a transaction from it or code is deployed there. Real vanity addresses are likely hollow forever since finding a hash or key to it is computationally near impossible.
0 reply
0 recast
1 reaction