Kyle (coffeeslug772)

All the best parts of twitter without psychos and politics running amok. Farcaster 👍 Snappy too!

• 0 replies
• 0 recasts
• 0 reactions

Hello Farcaster!

• 1 reply
• 1 recast
• 2 reactions

Breaking things down into easier bits helps me, I’ll just spend a day with my PM hat on if code isn’t flowing. Personally the struggle is almost always related to something feeling overwhelming. The key is to figure out what that block is for you. Messy desk, no A/C, you’re thirsty; tackle that first 🙂

• 0 replies
• 0 recasts
• 1 reaction

Tried to squeeze this into 1. Essentially eoa key + our key + provider key is what it takes to sign. To validate txn details we can use our incomplete key on our backend to lookup ownership to confirm receiving user XXX actually has said wallet. Return an error + break the flow; no client side involvement ✅

• 0 replies
• 0 recasts
• 1 reaction

Hi Sam! Thanks for posing the question. This stuff is monumentally important to both me and Brian. Our architecture is built around MPC EOAs with AA wallets so anything on chain is SAFE. Since a 3 way approval is involved for signing a server-to-server auth and address ownership check is all we need b4 execution.

• 0 replies
• 0 recasts
• 1 reaction