Content pfp
Content
@
0 reply
0 recast
2 reactions

Dan Romero pfp
Dan Romero
@dwr.eth
cc @scott @v wdyt https://x.com/smsunarto/status/1692333746907963807?s=46
7 replies
2 recasts
11 reactions

Varun Srinivasan pfp
Varun Srinivasan
@v
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
1 reply
0 recast
10 reactions

Mason Hall pfp
Mason Hall
@mason
Aptos uses REST and I’ve actually quite enjoyed the experience
1 reply
0 recast
1 reaction

Gabriel Ayuso pfp
Gabriel Ayuso
@gabrielayuso.eth
Proper REST APIs are designed around providing CRUD operations on resources and defining a resource hierarchical structure. This doesn't really fit the blockchain node use case. Many people use REST to refer to RPC over HTTP though. 🤷
0 reply
0 recast
6 reactions

Shriphani Palakodety pfp
Shriphani Palakodety
@shriphani
Wire protocols allow a lot more flexibility like say switching from tcp to quic etc. Trivial to write a little shim that exposes a rest api.
0 reply
0 recast
0 reaction

ST pfp
ST
@vercelabloh
ooooooh good question!
0 reply
0 recast
0 reaction

Andrei O. pfp
Andrei O.
@andrei0x309
JSON-RPC(which is what EVM nodes have)and REST don't have significant technical differences. Is more of an ideological thing, so from a naming point it makes sense since a transaction can be described as a Remote Procedure Call.
0 reply
0 recast
0 reaction

Jannik pfp
Jannik
@jannik
Ethereum's consensus node API is REST, so it could be shifting
0 reply
0 recast
0 reaction