A place for talking about the Ethereum Virtual Machine on Farcaster.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

founder & ceo @argus @worldengine // prev: Dark Forest,  Trail of Bits, Uniswap

cc @scott

@v wdyt

https://x.com/smsunarto/status/1692333746907963807?s=46

We want to add REST APIs to Farcaster Hubs

Originally did RPC because it was what hubs used to sync with each other and we just exposed them to clients, but increasingly convinced that REST is the right API for hubs <> clients 

cc @adityapk

In general in blockchain development this kind of decision making is quite common; using a certain wire format or API because it's what <popular project> used without much further thought.

cofounder /ethglobal, team /op-stack, /canada native 

liamhorne.com

* sponsored by Merkle, 5 USDC at a time
* higher rank in Tae Kwon Do than Vladimir Putin
* hobbies include emailing customer support at crypto companies

Strongly agree, that's why Optimism coined the phrase "EVM Equivalence". But, it's also easy to copy interfaces because YOU are familiar with some other interface, and overestimate how many potential developers really care all that much.

There's an argument for that, in that a consistent developer experience reduces friction when you're hopping between projects. Going your own way can be justifiable, but the value in not requiring a context switch just to use your API - especially if you're trying to attract developers - can't be ignored

Ideally, you'd research every decision perfectly but if I had to err, I'd rather it be on the side of popular thing that everyone uses instead of writing the custom thing that no one else uses :)