Integration readiness check

A short, fixed-scope second opinion on your plan or prototype for connecting to users’ BRC-100 wallets. You get a written punch list of what to fix now and what can wait.

Who it’s for: Teams planning a BRC-100 integration, or with an early prototype, who want a second opinion before building more.

What you send: A short description of your app and what it needs from the wallet (sign-in, payments, micropayments, or some mix), plus access to your prototype, repo or architecture notes.

What I do (about 5 hours): Review how the app connects to the wallet and what permissions it asks for. Check the signing and payment flows for common mistakes, including anywhere the app could end up able to spend more than the user intended. Look at the approval and error experience. Flag anything that will be expensive to fix later.

What you get: A written punch list ordered by priority (what’s fine, what to fix now, what to fix before launch), a 30-minute call to walk through it, and a recommendation on whether you need a deeper review or hands-on help. The fee is credited toward either.

What it isn’t: This is not a full security audit. The punch list reports what I noticed at this depth. It is not a statement that your app is safe.