Hi! My name is Daniel. I am building bountycaster.xyz

Ex Phantom, 0x Project engineer.

From Italy originally, currently live in NYC

How @pirosb3 & I have viewed smart contracts for Bountycaster

- launch quickly w/o smart contracts to validate user behavior on bounties. Huge cost to build contracts no one uses

- proceed cautiously on anything re: user funds

- manual payments are painful but happening, buys us time to experiment with other things

Building @bountycaster (bountycaster.xyz). Co-producer on an Ethereum documentary. Previously co-founder of Scalar Capital and product at Coinbase

Chasing ikigai 💫 Exploring what's next 👨‍💻 Alum: Product @ XMTP, Microsoft, Apple

Reputation - as Farcaster scales it's no longer going to be a tight network where you generally are aware of who others are + more spam

First smart contracts might be around onchain reputation over payments / escrow but TBD on that one since we're first starting with offchain reputation and seeing usage

What's the most impactful feature you're working on?

And what might the first bountycaster smart contract you build do?

Founder ChainVine (Backed by Slow, Multicoin, Hustle Fund, and more) | former COO Setter (20M from Sequoia & NFX, sold Thumbtack) | FID #1277.

Don't want to lose user funds. As we've seen in the space a lot, even contracts with multiple audits have had issues

Number of reasons you could operate cautiously on user funds. Curious what #1 is for you?

Working on building zkTLS infra/products. A ruthless empiricist.

http://opacity.network

Advisor @ EV3 Ventures

Too early to say what's the endgame since we are doing a lot of experiments to see what works and doesn't

Ideally we can support the larger bounties though

What is your vision for bty-caster endgame. Focused on a lot of casual bounties or making it a serious productivity tool? (large bounties).

I feel like you’d want to encourage people to break large bounties up into steps so no one gets rugged after a lot of work. Haven’t thought too deeply about this though.