1214
df

@df #1214

Building Larry, FOSS via @frames, @framesfun /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id
122876 Follower 2160 Following
opportunity for another cabal
What are you working on?
Going to any interesting events this week in Berlin?
if you‘ve considered launching a token but aren‘t sure or have questions

my DCs are open
here‘s the order you put the Ps in

product -> platform -> protocol
30,000 Larry bounty - what's the easiest way to pull in every uniswap swap event into my postgres db for events that transact on a growing list of tokens (couple hundred addresses)

@bountybot have tried ponder and index supply, both don't really work nicely for this use case as far as I can devise. Could listen to every uniswap swap event on base and filter, but thats 1 million events a day and feels like it may lead to some perf issues
/dev
agents are going to be hilarious in the future.

they‘re already pretty funny if you tell them to be, and being entertaining is only going to help their distribution.

the most entertaining outcome
would like to see my warpcast seed phrase in settings locked behind a face id check if I enabled that for my login.
same day prediction markets for rainfall in hyperspecific locations + times.

weather forecasts always vague or noisy

locals always seem to know better
what made frames v1 new and interesting was it enabled cross-website actions.

Press a subscribe button in a frame on warpcast, get subscribed on paragraph.

Frames v2 don’t do or even leverage this, and are more similar to an embedded browser.

The proposal below leverages the best parts of frames v1 as a cross-app actions authorization modal, without the performance downsides
bullish communities
bearish novelties
What are you working on?
Gonna re share this because I want to see it happen

The interface between the Frame and the client is currently spec'd to be very limited. I think there is an opportunity to open this interface up to also providing "developer legos" by allowing the Frames in v2 to call an action that opens a limited version of Frames v1 (frames v1 without the "POST" action, so it's only 1 step frames). This allows third party programmability at this permissions layer between Frames and Client, enabling Frames to interact with eachother. As it stands, Frames v2 have no way to interface with each other, or any of the existing developer legos via a trusted context. The trickiest part of implementing Frames v1 for clients was the complexity and performance of state transitions between frames. By limiting Frames v1 to "one step Frames", you get the safe composability without adding much complexity.

https://github.com/farcasterxyz/protocol/discussions/205#discussioncomment-11498632
DEX minting progress percentage is an indicator of nr of NFTs sold, not of capital committed, as it's on the bonding curve and NFTs become more expensive.

Easy to confuse the two - kinda confusing. afaik this is actually less than 5% of DEX minting progress
need a third option tbh
anoncast is interesting, but letting the token rich decide what is shown and what is deleted is already censoring some things and not others
who is building community notes for tokens?
@bankr can you set up a wallet pls
Anybody happen to have sample code to expose the estimated market cap of an ERC20 via ponder.sh by looking at most recent transfer events?
if you delay claiming your Larry tokens, does that also delay any tax burden until you do?
pretty cool
if you're building for the long term, do you really want some people in your community to get a 3x worse entry because they checked their phone 10 mins later?