Frames spec has no example of validating the frame message.

[JoelAlexander]

The frames spec document (https://github.com/farcasterxyz/docs/blob/main/docs/reference/frames/spec.md) states:

The Signed Message can be validated by calling the validateMessage API on Hubs, as shown in the script below.

However there is no example in the document.

Instead the doc should show or link the idiomatic way to validate the frame message from the octet string.

[CryptoExplor]

Still open and very relevant as Frames usage grows. The spec page currently explains what the frame message is but gives no code example of how to verify it server-side.

Here's a minimal example that would greatly help developers — happy to submit a docs PR with something like this:

// pages/api/frame.ts (Next.js example)
import { NeynarAPIClient } from '@neynar/nodejs-sdk';

const client = new NeynarAPIClient(process.env.NEYNAR_API_KEY!);

export default async function handler(req, res) {
  const { trustedData } = req.body;
  
  // Validate the frame message signature via Neynar (or Hubble)
  const result = await client.validateFrameAction(trustedData.messageBytes);
  
  if (!result.valid) {
    return res.status(400).json({ error: 'Invalid frame message' });
  }
  
  const fid = result.action.interactor.fid;
  // ... handle the validated action
}

Alternatively, the docs could show validation using a self-hosted Hubble node via @farcaster/hub-nodejs. Both approaches should be documented.

Happy to open a PR adding this example to the Frames spec page if maintainers confirm the preferred approach.