Skip to content

Conversation

@soheimam
Copy link
Collaborator

What changed? Why?
-- added call out to using neynar for notification verification

@cb-heimdall
Copy link
Collaborator

cb-heimdall commented Oct 28, 2025

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1


Always use both `fid` and `appFid` together to identify a unique user-client combination.
</Info>
<Info>
Copy link
Contributor

@hughescoin hughescoin Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add a warning under the <Info> to say this. Since the info above is helpful and not setting the neynar API key will result in an error.

<Warning>
Set the `NEYNAR_API_KEY` environment variable in your project to complete webhook verification. You can request a free API key [here](https://dev.neynar.com/).
</Warning>

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hughescoin resolved now

Prerequisites

Before implementing notifications, make sure you have a Neynar API key (free tier available) to verify webhook events from the Base app.

Set the NEYNAR_API_KEY environment variable in your project:

NEYNAR_API_KEY=your_api_key_here

it has to be a pre req because the code cant run without this

<Step title="Create a webhook server">
Create a webhook server to handle webhook events.

<Info>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we removing this?

</Warning>
</Panel>

## Prerequisites
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants