Add Sentry to Next.js Client

[meshackyaro]

Description

This issue aims to address the implementation of Add Sentry to Next.js Client.

The core objective is to: Configure error tracking wrappers exclusively for the Next.js React client.

By completing this feature, we will ensure that the TrustFlow protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the Frontend architecture and adherence to the existing project conventions.

When picking up this issue, please ensure you document any new dependencies or architectural decisions made during development.

Component

Frontend

Difficulty

🔴 Hard

Tasks

• Review Next.js App Router structure
• Implement the UI components for: Add Sentry to Next.js Client
• Ensure responsive design using Tailwind CSS or standard modules
• Add caching for npm dependencies in CI
• Run npm run lint and npm run typecheck
• Run npm run build to verify production bundling

Acceptance Criteria

• Feature accurately implements the objective: Configure error tracking wrappers exclusively for the Next.js React client.
• Any PR that introduces TypeScript errors is automatically blocked
• CI pipeline runs in under 3 minutes per PR
• Code is properly reviewed and approved by codeowners

Estimated Time

1-3 days

[Biokes]

Hi maintainer,
I will like to work on this issue.

[grantfox-oss]

🦊 GrantFox — @Biokes has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #6)
2. Your PR will be reviewed by the trustflow-protocol maintainers

Good luck! Track your progress on GrantFox.

[rupesh-kumar-sah]

Hello @maintainers,

I can tackle Add Sentry to Next.js Client. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in trustflow-protocol/trustflow-frontend
• Core Implementation: Implement Add Sentry to Next.js Client with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Quality Assurance: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.

I am ready to start immediately—please assign this to me!