Content
@
0 reply
0 recast
0 reaction
ncitron.eth
@ncitron.eth
How should we define a light client? Are there particular properties that a light client needs? Lately I've been thinking about lots of different designs with weird tradeoffs and trust assumptions, and it begs the question of what "counts" as a real light client.
3 replies
2 recasts
8 reactions
dylan
@dylsteck.eth
I also wonder what this looks like in the context of a lite client being more user facing Eg. What a lite Farcaster client as an app looks like versus a lite client of an actual Farcaster hub
1 reply
0 recast
1 reaction
ncitron.eth
@ncitron.eth
What is a light client as an app? I'm thinking more about light clients that can verify what's happening on a blockchain on lightweight hardware. I have actually thought a lot about light client hubs and you can sort of build one, but I suspect there is little desire for people to use them as the only property they can provide is "this cast is real" as opposed to ensuring that your feed isn't being censored or manipulated in some way. It seems like the former is potentially just not that interesting for most.
1 reply
0 recast
2 reactions
dylan
@dylsteck.eth
Gotcha, definitely agreed that the proper definition of light client isn’t an app but yet some light blockchain node/verification tool that can run on relatively lightweight hardware I’m separately curious about the latter half but agree that there just might not be much practicality / many use cases behind that
1 reply
0 recast
1 reaction
dylan
@dylsteck.eth
I’d also add that some of my use of “lite client” comes from my work on github.com/dylsteck/litecast in an attempt to make a client that’s as similar to Warpcast as possible while focusing on speed & minimal dependencies
0 reply
0 recast
1 reaction
