Paul Cowgill

@paulcowgill

770 Following

3069 Followers

Paul Cowgill pfp

excited for /farcasterfridays today in /chicago!

0 reply

1 recast

7 reactions

Paul Cowgill pfp

building a group payments protocol for multiplayer games this week we: * came up with the idea * shipped a first draft of the contracts, UI, and API

2 replies

2 recasts

21 reactions

Paul Cowgill pfp

building /static this week we shipped: * a new layout in the app * simpler payouts in the protocol * the name ⚡ static

6 replies

2 recasts

35 reactions

Paul Cowgill pfp

building something 🆕 with the /onceupon team this week we built out the protocol and app for betting on onchain outcomes (see video) excuse the rough edges design-wise - this week was all about functionality aiming to launch this for a real onchain outcome on /base 🔜

2 replies

1 recast

37 reactions

Paul Cowgill pfp

here's the end result for the uniswap example, where we were able to directly use the build artifacts from node_modules

0 reply

0 recast

2 reactions

Paul Cowgill pfp

a nice easter egg feature for builders on warpcast would be backtick code highlighting like in slack and notion `myFunction`

2 replies

0 recast

11 reactions

Paul Cowgill pfp

to test a new contract under development and an old contract with a solidity version older than forge supports (without using fork tests): deploy the bytecode of the old contract using assembly in the test file. uniswap v2 makes forge test and forge script sad, but this fixes it.

1 reply

1 recast

4 reactions

Paul Cowgill pfp

if you’re trying to use vm.readFile and it isn’t working, you need this in your foundry.toml: fs_permissions = [{ access = "read", path = "./"}] h/t @jomessin for figuring this out

0 reply

0 recast

10 reactions

Paul Cowgill pfp

very basic but useful learning from this week: if you're trying out a new smart contract write function you just built, and it doesn't work, try it again with more gas

5 replies

0 recast

8 reactions

Paul Cowgill pfp

building something 🆕 with the /onceupon core team this week we: * got set up with the latest smart contract protocol + app tech stack * came up with the idea for our first experiment: a protocol that makes markets for onchain events * deployed and wired up a prototype - contracts, FE, and BE

4 replies

6 recasts

56 reactions

Paul Cowgill pfp

building /onceupon this week we made a hard choice, and we shut down products we've shipped in the past: the block explorer and the api. i think this counts as a form of shipping. https://warpcast.com/jomessin/0x1499f992

6 replies

3 recasts

38 reactions

Paul Cowgill pfp

building /onceupon this week we shipped: * updated the context repo to support the default RPC log format and shipped this in our ETL pipeline * set up self-serve stripe payments for the api * started consuming new trending api endpoints in our demo apps * optimized the transactions endpoint for code readability

0 reply

0 recast

17 reactions

Paul Cowgill pfp

building /onceupon this week we shipped: * new, faster transactions API endpoint w/ docs * trending contracts API endpoints w/ docs * helped @skyoneer use our API to build a dashboard for their product * new landing page for the API * updated user auth implementation under the hood for onceupon.xyz

1 reply

1 recast

15 reactions

Paul Cowgill pfp

building /onceupon this week we shipped: * the once upon ui kit, something @cdt and @guscost cooked up for our internal hackathon. here's an early look! planning to clean it up, add more components, and open-source it soon. https://ui.onceupon.xyz * updated nouns contextualizations to support the new contract versions (thanks to @datadanne.eth)

2 replies

2 recasts

16 reactions

Paul Cowgill pfp

building /onceupon this week we shipped: * a beta version of our new dev dashboard and api docs * sent early access to the first team using our self-serve dashboard to build w/ the once upon API * onchaintrends.dev w/ @openrank * updated our demo apps to make once upon API requests using prod api keys

2 replies

1 recast

22 reactions

Paul Cowgill pfp

building /onceupon this week we shipped: * contextualizations for @skyoneer https://www.onceupon.xyz/0xb45805566a842efb6329c11e092158f3e0eddaa2:4653 * a flow to generate api keys and use them for api auth * persisted login state for contract.cool * a to-be-announced demo app with /openrank

0 reply

2 recasts

15 reactions

Paul Cowgill pfp

building /onceupon this week we shipped something we haven't announced yet, but here's some early alpha for this channel. we shipped https://contract.cool, an app for finding trending contracts in your farcaster network. under the hood, it uses our new trending api for the past seven days of data.

9 replies

4 recasts

43 reactions

Paul Cowgill pfp

building /onceupon, the modern API for onchain data. built for consumer crypto devs. this week, we 👇

3 replies

3 recasts

21 reactions

Paul Cowgill pfp

SIWE, SIWF, SIWSW (Coinbase Smart Wallet) to support logging into apps as a contract: can we get more adoption of ERC-1271 this time around? or find a simpler standard? or is sending a tx to auth with every app sufficiently realistic on L2s and L3s? (probably not) or does CB SW already have this solved somehow?

7 replies

11 recasts

73 reactions

Paul Cowgill pfp

@jomessin and I wrote about /onceupon's next chapter. take a look 👀

2 replies

1 recast

14 reactions