)}
diff --git a/src/app/(public)/layout.tsx b/src/app/(public)/layout.tsx
index ce91718..0bca293 100644
--- a/src/app/(public)/layout.tsx
+++ b/src/app/(public)/layout.tsx
@@ -3,7 +3,7 @@ import { ReactNode } from "react";
export default function LayoutPublic({ children }: { children: ReactNode }) {
return (
);
}
diff --git a/src/app/403/page.tsx b/src/app/403/page.tsx
index cddb41b..9c797e9 100644
--- a/src/app/403/page.tsx
+++ b/src/app/403/page.tsx
@@ -1,6 +1,12 @@
+import type { Metadata } from 'next';
import Link from 'next/link';
import { ShieldOff } from 'lucide-react';
+export const metadata: Metadata = {
+ title: 'Access Forbidden | EthEd',
+ robots: { index: false, follow: false },
+};
+
export default function ForbiddenPage() {
return (
diff --git a/src/app/EIPs101.md b/src/app/EIPs101.md
deleted file mode 100644
index 5d429e6..0000000
--- a/src/app/EIPs101.md
+++ /dev/null
@@ -1,394 +0,0 @@
-# EIP_101: From First Principles to First Proposal
-
-Unders## 4. The lifecycle: how an idea becomes a standard
-
-
-
-Follow one story to make this concrete. Consider a fictional proposal: "Rentable NFTs." The idea is that an NFT owner can grant time-bound usage rights to another account without transferring ownership.d—below is a narrative, professional, text-first course on Ethereum Improvement Proposals (EIPs), written so an undergraduate beginner can follow without pausing to decode jargon.
-
-### Course title
-
-Ethereum Improvement Proposals (EIPs): From First Principles to First Proposal
-
-### Who this is for
-
-Students, early-career developers, product-minded builders, and Web3 enthusiasts who prefer clear explanations, concrete examples, and a guided path from curiosity to contribution.
-
-### Learning outcomes
-
-By the end, learners will be able to explain what an EIP is, trace how an idea becomes a standard, recognize EIP types, read real proposals with confidence, and draft a credible first EIP using EthEd’s Proposal Builder.
-
-***
-
-## 1. Ethereum in plain language
-
-Imagine a global computer that anyone can use and no single company controls. Ethereum is that computer. Programs on this computer are called smart contracts: small pieces of code that do exactly what they say, visible to everyone, and enforced by thousands of machines cooperating to agree on the same state.
-
-
-
-Over time, even the best systems need upgrades. New features, fixes, or standards must be proposed, debated, and agreed to without a CEO pressing a button. That is where EIPs come in. EIPs are the public, transparent “upgrade notes” and “blueprints” that the community reads, critiques, and—when ready—adopts.
-
-A helpful analogy: think of Ethereum as a city. Smart contracts are buildings and services. EIPs are the building codes and city planning rules that keep everything safe, compatible, and evolving. When a new type of bridge is needed, an EIP is the document that proposes its design, explains why it is better, and specifies exactly how to build it.
-
-***
-
-## 2. What is an EIP?
-
-An Ethereum Improvement Proposal (EIP) is a structured document that does three simple things:
-
-- States a problem clearly.
-- Proposes a precise solution.
-- Explains why this solution is the right one now.
-
-Each EIP is public. Anyone can read the exact text, comment, and suggest improvements. Editors maintain format and process quality; developers and researchers examine technical details; application and wallet teams consider user impact; the wider community discusses tradeoffs.
-
-EIPs are not marketing posts or opinion pieces. They are technical specifications with rationale—enough detail that different teams can implement the same behavior without ambiguity.
-
-***
-
-## 3. The kinds of EIPs
-
-There are three main kinds of EIPs, and one of them has subcategories:
-
-
-
-- Standards Track: changes that affect how Ethereum or apps work in practice. These include:
- - Core: changes to the protocol itself, such as fee mechanics or new opcodes.
- - Networking: how Ethereum nodes talk to each other.
- - Interface: client APIs and RPCs that apps and wallets call.
- - ERC (application-level standards): conventions like token interfaces so apps interoperate.
-- Meta: changes to processes outside the protocol, such as how EIPs are managed or reviewed.
-- Informational: best practices or guidance meant to educate, not to enforce.
-
-A simple mental model: if the change affects how software must behave to remain compatible, it is likely Standards Track; if it updates rules about how the community works, it is likely Meta; if it explains a practice or approach, it is likely Informational.
-
-***
-
-## 4. The lifecycle: how an idea becomes a standard
-
-Follow one story to make this concrete. Consider a fictional proposal: “Rentable NFTs.” The idea is that an NFT owner can grant time-bound usage rights to another account without transferring ownership.
-
-- Idea: Someone notices many apps re-implement rentals differently, causing confusion. A forum thread collects examples and pitfalls. The community says, “a standard would help.”
-- Draft: The author writes a proper EIP document: a short abstract, motivation with real app pain points, a specification that defines events and functions with exact semantics, and rationale explaining each design choice. An editor assigns a number and places it in the repository as Draft.
-- Review: Developers of marketplaces and wallets test the interface in small demos. Feedback leads to clearer event names and a safer default for revocation. The spec tightens wording around “rental expiry.”
-- Last Call: For a fixed review window, the community focuses on final objections. Wording is polished, examples are clarified. No breaking changes are introduced at this point.
-- Final: The standard is accepted. Popular marketplaces and several wallets implement it. Apps can rely on consistent behavior, and audits can reuse standard reasoning.
-
-Alternative outcomes also exist. If discussion stalls for months, an editor may mark it Stagnant so attention moves to active work. If the author decides to withdraw the idea, it becomes Withdrawn. Some documents, like process guidelines, live as Living because they evolve continuously.
-
-***
-
-## 5. Anatomy of an EIP (with a guided example)
-
-A well-written EIP reads like a clear engineering spec. Below is a condensed, realistic skeleton for the fictional “ERC-NNNN: Rentable Non-Fungible Tokens.” Each section includes example text to show the tone and level of precision expected.
-
-Title
-“ERC-NNNN: Rentable Non-Fungible Tokens”
-
-Abstract
-“This standard defines a minimal interface for time-bound rental of non-fungible tokens (NFTs). Owners can grant usage rights to a renter until an expiry timestamp without transferring ownership. The standard specifies functions, events, and state requirements that enable consistent integration across wallets and marketplaces.”
-
-Motivation
-“NFT-based applications (games, galleries, memberships) often require temporary access without giving up ownership. Today, projects build custom rental contracts with inconsistent semantics for revocation, renewal, and transfer during active rentals. This fragmentation complicates integrations and audits. A simple, opt‑in interface allows apps to support rentals consistently.”
-
-Specification
-
-- Interface name: IERCXXXXRentable
-- New events:
- - Rented(tokenId, owner, renter, expiresAt)
- - RentalEnded(tokenId, endedAt, reason)
-- Required functions:
- - rentOut(tokenId, renter, expiresAt) external
- - renterOf(tokenId) view returns (address renter, uint64 expiresAt)
- - endRental(tokenId) external
-- Semantics:
- - Only the current owner may call rentOut.
- - During an active rental, transfer of the token by the owner ends the rental.
- - If expiresAt is in the past, calls to endRental must emit RentalEnded with reason “Expired.”
- - renterOf returns zero address and zero expiry if no active rental exists.
-- Error conditions:
- - rentOut must revert if expiresAt ≤ current block time + minimal duration (implementation-defined but recommended ≥ 60 seconds).
- - rentOut must revert if tokenId does not exist.
-
-Rationale
-“Events mirror common wallet needs: one to start, one to end, with machine-parseable reasons for indexing. The owner-only rentOut preserves owner sovereignty. Ending on transfer simplifies asset movement and reduces footguns where a renter persists after sale. The zero-address convention for ‘no renter’ aligns with existing ERC patterns.”
-
-Backwards Compatibility
-“This standard does not modify ERC‑721 core semantics. It adds an interface that contracts may optionally implement. Existing ERC‑721 contracts remain valid. Marketplaces can feature-detect the interface and enable rentals only when present.”
-
-Security Considerations
-“Renter logic must not grant ownership privileges. The renter MUST NOT be treated as ownerOf for transfers or approvals. Care is required around reentrancy on rentOut and endRental; recommended practice is to apply checks-effects-interactions and emit events after state changes. Time-based expiry depends on block timestamps and inherits their small variance.”
-
-Reference Implementation (illustrative)
-“An example wrapper contract implements IERCXXXXRentable for existing ERC‑721 tokens via composition. The wrapper holds tokens and exposes rental controls while preserving original ownership semantics. This pattern enables rentals for collections that cannot be upgraded.”
-
-Test Cases (outline)
-
-- Rent, query renterOf, observe events.
-- Early end by owner; attempt re-rent to a new renter.
-- Transfer during active rental; assert rental ended.
-- Expiry path; endRental after expiry emits expected reason.
-- Non-existent token reverts.
-
-Copyright
-“Public Domain / CC0.”
-
-A complete proposal also includes a short description line and author metadata, and references to discussion threads so reviewers can follow the history.
-
-***
-
-## 6. Reading real EIPs without headaches
-
-A beginner’s reading method that works well:
-
-- Read the Abstract and Motivation together as a single story: “What hurt, and what is the fix.”
-- Skim the Specification once for shape: names of functions, events, and any constants.
-- Jump to Rationale to understand why the odd-looking parts are there.
-- Revisit Specification and underline exact semantics. Where does it revert? What does it guarantee?
-- Scan Backwards Compatibility and Security to understand practical risks for apps and wallets.
-
-This order mirrors how most implementers think: is the problem real, is the solution precise, is the design justified, and what could go wrong.
-
-***
-
-## 7. Case studies that make EIPs intuitive
-
-EIP‑20 (ERC‑20 tokens)
-Problem: early fungible tokens each used different function names and event shapes, breaking wallets and exchanges.
-Core idea: a single minimal interface (balanceOf, transfer, approve/transferFrom, events) so any token “just works.”
-Impact: exchanges, wallets, and protocols could integrate thousands of tokens predictably; the DeFi stack later built on that uniformity.
-
-EIP‑721 (NFTs)
-Problem: unique digital assets needed a first-class identity and ownership model different from fungible tokens.
-Core idea: every token has a unique id; interfaces expose ownership and safe transfers; metadata conveys what the token represents.
-Impact: consistent handling of art, tickets, in-game items, and identity primitives.
-
-EIP‑1559 (fee market change)
-Problem: fee estimation oscillated under congestion, leading to overpayment or stuck transactions.
-Core idea: a predictable base fee per block that adjusts automatically with demand and is burned, plus an optional tip to prioritize inclusion.
-Impact: smoother fee estimation for wallets and more consistent user experience during busy periods.
-
-EIP‑4844 (blob-carrying transactions)
-Problem: rollups needed cheap, temporary data to post proofs without storing all of it forever on chain.
-Core idea: “blobs,” a special, time-limited data space with its own fee market separate from normal gas.
-Impact: major cost reductions for rollups, enabling cheaper L2 transactions and scaling the ecosystem.
-
-EIP‑4337 (account abstraction via contracts)
-Problem: externally owned accounts (EOAs) were too rigid for better UX like social recovery or sponsored gas.
-Core idea: a standardized flow where smart contract wallets validate “user operations,” with bundlers and optional paymasters.
-Impact: gasless experiences, programmable validations, and recovery workflows without changing the base protocol.
-
-EIP‑7702 (EOA delegation, high level)
-Problem: migrating from EOAs to smart accounts without changing familiar addresses is hard.
-Core idea: allow an EOA to temporarily delegate execution to contract logic while remaining compatible with existing tooling.
-Impact: a gentler path toward richer account features with minimal user friction.
-
-Each example follows the same pattern: one clear pain point, one carefully scoped interface or rule, and long-term gains from shared expectations.
-
-
-
-***
-
-## 8. Following the process with EthEd
-
-EthEd is a purpose-built companion for tracking, understanding, and drafting EIPs. A practical way to learn with it:
-
-- Open the dashboard and glance at status distributions. This sets expectations: not every idea becomes Final, and that is healthy.
-- Choose one EIP—say, EIP‑4844—and scroll its status history. Notice how many conversations and iterations precede acceptance.
-- Visit the editors’ activity view to appreciate review load and timelines. This builds empathy for the process and helps authors write clearer drafts.
-- Use advanced filtering to find EIPs similar to a current problem. Reading three related EIPs often reveals a pattern for a better design.
-
-This habit—scan, pick, read, compare—turns a massive repository into a focused weekly practice.
-
-***
-
-## 9. Drafting a first EIP with EthEd’s Proposal Builder
-
-The Proposal Builder transforms a daunting process into a guided writing session. A credible first draft emerges naturally by moving section by section.
-
-- Start with the smallest possible, real problem in an area of familiarity. For instance, a metadata convention that repeatedly causes bugs in one’s own project.
-- In the Builder, fill Title (short and descriptive) and a one‑line Description. Write the Abstract as two or three sentences any developer can read without context.
-- Write the Motivation as a story with concrete failures: “wallet X and marketplace Y interpret Z differently, leading to A and B bugs.” Name specific classes of apps rather than generalities.
-- Draft the Specification last, even though it sits before Rationale. By now the mental model is clear. Specify exact names, argument types, return values, and events. State what must revert and when.
-- Use Rationale to justify every choice that could have been different: naming, event shapes, default behavior, and any guardrails. Link design choices back to the failures mentioned in Motivation.
-- Capture Backwards Compatibility and Security with clear, actionable statements: what implementers must not assume, and where time or reentrancy could bite.
-- Switch to preview mode to catch formatting errors and awkward phrasing. The Builder’s validation hints nudge the draft toward the house style EIP editors expect.
-- Export the Markdown, open a pull request in the EIPs repository, and include links to discussion threads so reviewers can trace context. From here, iteration begins—small edits often matter more than grand rewrites.
-
-A helpful mindset: the Proposal Builder is not just a form; it is a thinking scaffold. When a section feels hard to write, that is a signal the idea needs more sharpening.
-
-***
-
-## 10. Workshop: build a minimal standard in 90 minutes
-
-A guided session that consistently works for beginner cohorts:
-
-Phase 1 — Problem capture (15 minutes)
-Pick one recurring integration pain from a familiar app category: for example, a standard way to express “trial access” for a membership NFT.
-
-Phase 2 — Concrete examples (15 minutes)
-Write down three real failure cases that happened or could plausibly happen. Each example should end in a user-visible bug.
-
-Phase 3 — Interface sketch (20 minutes)
-Define exactly two events and two functions that would prevent those bugs. No more. Name them plainly. Write one paragraph per function describing returns and required reverts.
-
-Phase 4 — Rationale and risks (20 minutes)
-Explain why each choice is safer or simpler than alternatives. List two backwards-compatibility notes and two security pitfalls with mitigations.
-
-Phase 5 — Polish in the Builder (20 minutes)
-Paste each section into the Builder, preview, fix wording, and export. Share drafts for peer review.
-
-The outcome is a compact, credible Draft-ready EIP that demonstrates understanding of purpose, process, and precision.
-
-***
-
-## 11. Contributing beyond authorship
-
-The ecosystem needs more careful readers than authors. High‑quality reviews move proposals faster than any single champion can.
-
-A useful review comment looks like this:
-
-- Quotes the exact sentence in question.
-- States the ambiguity or risk in practical terms.
-- Proposes precise wording that would remove the ambiguity.
-- Mentions a concrete integration scenario affected by the change.
-
-Good etiquette is simple: be specific, be kind, and be ready to change one’s mind when presented with a better argument. Editors and authors remember reviewers who help with clarity.
-
-***
-
-## 12. Glossary in one breath
-
-- Account abstraction: letting account logic be programmable, often via smart contracts, to improve UX like recovery or sponsored fees.
-- Base fee: the protocol‑set fee per block that adjusts with demand and is burned.
-- Blob: special, temporary data space for rollups, priced separately from normal gas.
-- Client: software that runs Ethereum (e.g., execution and consensus clients).
-- Editor: a maintainer who ensures EIPs follow format and process guidelines.
-- ERC: application‑level standard within the EIP framework.
-- Gas: unit measuring computational work on Ethereum.
-- Last Call: fixed, short window for final objections before acceptance.
-- Rationale: section explaining why a specification is designed the way it is.
-- Rollup: L2 system posting proofs and data to Ethereum for security.
-
-***
-
-## 13. Final guidance
-
-A strong EIP feels inevitable when read: the problem was real, the solution was the smallest that could work, and every sharp edge has a guardrail. Starting small, writing precisely, and iterating publicly are the reliable ingredients. With EthEd as the compass—for tracking, comparing, and drafting—beginners become credible contributors far sooner than expected.
-
-
-
-***
-
-# Ethereum Improvement Proposals (EIPs): From First Principles to First Proposal
-
-### Who this is for
-
-Students, early‑career developers, product‑minded builders, and Web3 enthusiasts who prefer clear explanations, concrete examples, and a guided path from curiosity to contribution.
-
-### Learning outcomes
-
-Explain what an EIP is; trace how an idea becomes a standard; recognize EIP types; read real proposals with confidence; and draft a credible first EIP using EthEd’s Proposal Builder.
-
-***
-
-### Ethereum in plain language
-
-Imagine a global computer that anyone can use and no single company controls; Ethereum is that computer, and smart contracts are the programs it runs with transparent rules enforced by many machines working in consensus.
-
-
-
-Ethereum is an open-source blockchain known for its smart contracts and the cryptocurrency ether (ETH).
-
-***
-
-### What is an EIP?
-
-An Ethereum Improvement Proposal is a public, precise, and reviewable specification for changing Ethereum or standardizing how applications interoperate, written so multiple teams can independently implement the same behavior without ambiguity.
-
-***
-
-### The kinds of EIPs
-
-There are three principal kinds: Standards Track (with Core, Networking, Interface, and ERC subcategories), Meta (process changes), and Informational (guidance and best practices).
-
-
-
-Types and Categories of Ethereum Improvement Proposals
-
-***
-
-### The lifecycle: how an idea becomes a standard
-
-An idea graduates from informal discussion to a Draft with an assigned number, moves to Review for community and implementer feedback, enters a short Last Call window for final objections, and becomes Final when stable and adopted; some documents become Living, others can be marked Stagnant or Withdrawn.
-
-
-
-EIP Lifecycle Process Flow
-
-***
-
-### Anatomy of an EIP (guided example)
-
-A strong proposal reads like an engineering spec with minimal surprises: an abstract in two or three sentences, a motivation that names the real integration pain, a specification with exact function names, events, and revert conditions, and a rationale that justifies each tradeoff.
-
-***
-
-### Case studies that make EIPs intuitive
-
-- ERC‑20 standardized fungible tokens so wallets and exchanges could integrate any conforming token consistently.
-- ERC‑721 introduced a first‑class identity for unique assets and safe transfer semantics.
-- EIP‑1559 replaced volatile gas auctions with a predictable base fee that is burned, plus a small tip, improving fee estimation.
-- EIP‑4844 added blob‑carrying transactions with separate pricing to make rollup data cheaper and scale Layer‑2 throughput.
-- EIP‑4337 enabled smart‑account UX like social recovery and sponsored gas via a standardized user‑operation flow without protocol changes.
-- EIP‑7702 proposed temporary delegation from EOAs to contract logic, smoothing the path to richer account capabilities.
-
-
-
-Timeline of Major Ethereum Improvement Proposals
-
-***
-
-### Reading real EIPs without headaches
-
-Read Abstract and Motivation together to confirm the problem and shape of the fix, skim the Specification to map surface area, consult Rationale to understand design choices, then return to Specification to underline exact semantics and check Backwards Compatibility and Security notes.
-
-***
-
-### Following the process with EthEd
-
-A practical habit that works: scan the dashboard to calibrate expectations about status distribution, pick one proposal and read its status history, check editor activity to understand review load, and filter for similar EIPs to compare patterns before drafting.
-
-***
-
-### Drafting a first EIP with EthEd’s Proposal Builder
-
-Start with the smallest real integration problem; write a two‑sentence abstract anyone can parse; tell a specific motivation story with concrete failures; specify exact names, types, events, and revert rules; use rationale to justify each sharp edge; capture backwards‑compatibility and security in actionable terms; preview and validate; export and open a pull request to begin iterative review.
-
-***
-
-### Workshop: build a minimal standard in 90 minutes
-
-- Problem capture: pick a recurring integration pain from a familiar app category and state it in one sentence.
-- Concrete examples: list three realistic failure cases that end in user‑visible bugs.
-- Interface sketch: define exactly two functions and two events to prevent those bugs, with one paragraph per function explaining returns and reverts.
-- Rationale and risks: justify choices against plausible alternatives and list two compatibility notes and two security pitfalls with mitigations.
-- Polish: paste sections into the Builder, preview, refine wording, export, and share drafts for peer review.
-
-***
-
-### Contributing beyond authorship
-
-High‑quality reviewers accelerate good proposals: quote the exact ambiguous sentence, state the risk in practical terms, propose precise wording, and reference a concrete integration scenario that would be affected.
-
-
-
-Key principles of on-chain governance in blockchain, illustrating decentralization, transparency, inclusivity, immutability, and responsiveness.
-
-***
-
-### Glossary in one breath
-
-Account abstraction; base fee; blob; client; editor; ERC; gas; Last Call; rationale; rollup—brief, precise definitions that make specs readable on first pass.
-
-***
\ No newline at end of file
diff --git a/src/app/ENS101.md b/src/app/ENS101.md
deleted file mode 100644
index 0b2fe13..0000000
--- a/src/app/ENS101.md
+++ /dev/null
@@ -1,268 +0,0 @@
-# ENS 101: Names, Profiles, and Safe Display
-
-Welcome to ENS 101. This course explains what a name like “alice.eth” is, why it is useful, and how the site uses it to show a friendly identity next to an account. No prior knowledge needed.
-
-## What will be learned:
-
-- Claim a simple name and set it as the main name that apps can show.
-- Add a picture and a short bio to the name’s public card so apps can read it.
-- See how the site safely shows a name only when checks match.
-
-### Who this is for:
-
-- First‑time learners, students, and teammates building a public profile.
-
-### How long it takes:
-
-- 30–45 minutes total, with short videos per lesson.
-
-## Next steps:
-
-- Open the lessons in order. Each lesson has a quick task at the end.
-
-### Lessons:
-
-- 01-what-is-ens.md
-- 02-get-a-name.md
-- 03-make-it-your-main-name.md
-- 04-add-your-profile.md
-- 05-see-it-work-in-the-site.md
-- 06-badges-with-subnames.md
-- quiz.md
-
-01-what-is-ens.md
-***
-# Lesson 1: What is ENS?
-
-ENS gives a simple name like “alice.eth” that apps can show next to an account. Think of it like saving a contact on a phone—the name is easier to read than the background code.
-
-Why names help:
-
-- Human‑readable: names are simple to recognise and remember.
-- One tiny profile: a name can carry a display picture, a bio, and links.
-- Safer display: good apps check that the name truly belongs to the connected account before showing it.
-
-How it works in simple terms:
-
-- Directory: keeps track of who owns which name.
-- Profile card: stores picture, bio, and links for the name.
-- Lookups go both ways: the name should point to the account, and the account should declare that name as its main name. When both match, the site shows the name confidently.
-
-Watch:
-
-- Short overview video (3–4 min): VIDEO_URL
-
-Task:
-
-- Write down one name idea that is easy to say and spell.
-
-02-get-a-name.md
-***
-# Lesson 2: Get a Name
-
-Goal:
-
-- Search for a name, register it, and remember to renew it later.
-
-Steps:
-
-1) Open the official ENS app (use the link from the course page to avoid look‑alikes).
-2) Search for the chosen name (e.g., learner‑name.eth).
-3) If available, register for at least 1 year. This can be renewed later.
-4) Save a calendar reminder to renew 1–2 weeks before expiry.
-
-Safety tips:
-
-- Double‑check spelling before paying.
-- Use the official link from the course page.
-
-Watch:
-
-- Step‑by‑step registration (4–6 min): VIDEO_URL
-
-Task:
-
-- Register a name on a test network or main network (as preferred).
-- Add a reminder in the calendar to renew.
-
-03-make-it-your-main-name.md
-***
-# Lesson 3: Make It Your Main Name
-
-Goal:
-
-- Set the name as the “Primary name” so apps can show it next to the account.
-
-Steps:
-
-1) In the ENS app, open the name page.
-2) Find “Primary name” (sometimes called “reverse record”).
-3) Select the name and confirm.
-
-Why this matters:
-
-- Apps look up the account’s declared main name. If set, they show it. If not, they fall back to a short code.
-
-Watch:
-
-- Set Primary name (3 min): VIDEO_URL
-
-Task:
-
-- Set the Primary name.
-- Disconnect and reconnect the account in a favorite app to see if the name appears.
-
-04-add-your-profile.md
-***
-# Lesson 4: Add Your Profile
-
-Goal:
-
-- Add a display picture, bio, and website link to the name’s public card.
-
-Steps:
-
-1) Open the name in the ENS app.
-2) Find “Records” or “Profile”.
-3) Add:
- - avatar: link to an image (PNG/JPG; or upload to a host and paste the URL)
- - description: a short bio (1–2 lines)
- - url: personal site or social link
-
-Tips:
-
-- Keep the image square (e.g., 512×512) for clean thumbnails.
-- Keep the bio short and friendly.
-
-Watch:
-
-- Profile records walkthrough (4 min): VIDEO_URL
-
-Task:
-
-- Add an avatar, a bio, and one link.
-
-05-see-it-work-in-the-site.md
-***
-# Lesson 5: See It Work in the Site
-
-Goal:
-
-- Connect the account on the demo page and check that the name appears only when the safety check passes.
-
-What the site does:
-
-- When an account connects, the site:
- - finds the account’s main name,
- - confirms the name points back to the same account,
- - only then shows the name and avatar.
-
-Steps:
-
-1) Open the demo page.
-2) Connect the account.
-3) If both checks match, the site shows the name and avatar. If not, it shows a short account preview.
-
-Watch:
-
-- Live demo (3–4 min): VIDEO_URL
-
-Task:
-
-- Toggle the Primary name off and on to see how the site reacts.
-
-06-badges-with-subnames.md
-***
-# Lesson 6: Badges with Subnames
-
-Goal:
-
-- Understand how the project can issue small child‑names (subnames) as badges.
-
-What a subname is:
-
-- A child under a parent name, for example:
- - cohort2025.alice.eth
-- It acts like a lightweight certificate learners can keep.
-
-How this project uses it:
-
-- After finishing lessons, a “Claim badge” button can create a subname.
-- The badge can include simple text fields like:
- - course: ENS 101
- - cohort: 2025
- - issued_by: EthEd
-
-Steps (demo flow):
-
-1) Click “Claim badge”.
-2) Confirm the action.
-3) View the subname in the profile or supported apps.
-
-Watch:
-
-- Badge claim demo (3–4 min): VIDEO_URL
-
-Task:
-
-- Claim a test badge if available, or view a sample badge on the demo page.
-
-quiz.md
-***
-# ENS 101 — Quick Quiz
-
-1) Why set a Primary name?
-
-- A) It makes the name renew automatically.
-- B) It lets apps know which name to show next to the account.
-- C) It hides the account.
-
-Correct: B
-
-2) What does the site check before showing a name?
-
-- A) Only the name spelling.
-- B) Both directions match: the name points to the account and the account declares that name.
-- C) Nothing—names always display.
-
-Correct: B
-
-3) What can be stored on the name’s public card?
-
-- A) A display picture, a short bio, and a website link.
-- B) Only a password.
-- C) Nothing.
-
-Correct: A
-
-4) What is a subname in this course?
-
-- A) A child‑name under a parent name that can work as a badge.
-- B) A secret backup.
-- C) A coupon.
-
-Correct: A
-
-appendix-dev-note.md
-***
-# Appendix (Dev Note)
-
-This site shows a name only when a simple two‑step check passes.
-
-Pseudocode:
-
-- Get the account’s declared main name.
-- Resolve that name to its account.
-- If both match, show the name and avatar; otherwise, show a short account preview.
-
-Optional code sample (Python):
-
-```python
-from web3 import Web3
-from ens import ENS
-w3 = Web3(Web3.HTTPProvider(RPC))
-ns = ENS.from_web3(w3)
-addr = ns.address("alice.eth")
-name = ns.name(addr)
-verified = (name == "alice.eth")
-```
diff --git a/src/app/about/page.tsx b/src/app/about/page.tsx
index 68d4ec7..eab4ab5 100644
--- a/src/app/about/page.tsx
+++ b/src/app/about/page.tsx
@@ -1,9 +1,18 @@
-
+import type { Metadata } from 'next';
import { Globe, Users, Brain, Target } from 'lucide-react';
import Image from 'next/image';
import Link from 'next/link';
import { Button } from '@/components/ui/button';
+export const metadata: Metadata = {
+ title: 'About | EthEd',
+ description: 'EthEd is a Web3 education platform making blockchain learning accessible, interactive, and rewarding.',
+ openGraph: {
+ title: 'About EthEd',
+ description: 'Making blockchain learning accessible, interactive, and rewarding.',
+ },
+};
+
const AboutPage = () => {
return (
diff --git a/src/app/admin/error.tsx b/src/app/admin/error.tsx
index 03525cf..c08e72e 100644
--- a/src/app/admin/error.tsx
+++ b/src/app/admin/error.tsx
@@ -1,6 +1,7 @@
'use client';
import { useEffect } from 'react';
+import { logger } from '@/lib/monitoring';
import { Button } from '@/components/ui/button';
import { Card, CardContent } from '@/components/ui/card';
import { ShieldX, RefreshCw, Home } from 'lucide-react';
@@ -14,7 +15,7 @@ export default function AdminError({
reset: () => void;
}) {
useEffect(() => {
- console.error('Admin panel error:', error);
+ logger.error('Admin panel error', 'AdminError', undefined, error);
}, [error]);
return (
diff --git a/src/app/api/donate/route.ts b/src/app/api/donate/route.ts
index a8356fa..26f16d3 100644
--- a/src/app/api/donate/route.ts
+++ b/src/app/api/donate/route.ts
@@ -4,6 +4,7 @@ import { authOptions } from "@/lib/auth";
import { prisma } from "@/lib/prisma-client";
import { HttpStatus } from "@/lib/api-response";
import arcjet, { slidingWindow } from "@/lib/arcjet";
+import { logger } from "@/lib/monitoring";
export const dynamic = "force-dynamic";
@@ -81,7 +82,7 @@ export async function POST(request: Request) {
return NextResponse.json({ success: true, donation }, { status: 201 });
} catch (error) {
- console.error("Donate Error:", error);
+ logger.error("Donate Error", "DonateAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
@@ -119,7 +120,7 @@ export async function GET(request: Request) {
totalRaised: totalRaised._sum.amount || 0,
});
} catch (error) {
- console.error("Donate GET Error:", error);
+ logger.error("Donate GET Error", "DonateAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/ens/lookup/route.ts b/src/app/api/ens/lookup/route.ts
index f644065..3de41db 100644
--- a/src/app/api/ens/lookup/route.ts
+++ b/src/app/api/ens/lookup/route.ts
@@ -21,7 +21,6 @@ export async function GET(request: NextRequest) {
select: {
id: true,
name: true,
- email: true,
image: true,
createdAt: true
}
@@ -73,7 +72,6 @@ export async function GET(request: NextRequest) {
select: {
id: true,
name: true,
- email: true,
image: true,
createdAt: true
}
diff --git a/src/app/api/ens/route.ts b/src/app/api/ens/route.ts
index cfeac20..5055696 100644
--- a/src/app/api/ens/route.ts
+++ b/src/app/api/ens/route.ts
@@ -63,8 +63,6 @@ export async function POST(request: NextRequest) {
const suffix = parts.slice(1).join('.');
if (suffix === 'ayushetty.eth' || suffix.endsWith('.ayushetty.eth')) {
rootDomain = 'ayushetty.eth';
- } else if (suffix === 'ayushetty.eth' || suffix.endsWith('.ayushetty.eth')) {
- rootDomain = 'ayushetty.eth';
} else {
// disallow other roots for now
return NextResponse.json({ error: 'Unsupported ENS root domain' }, { status: 400 });
diff --git a/src/app/api/leaderboard/route.ts b/src/app/api/leaderboard/route.ts
index 3f08d7d..e2e8c60 100644
--- a/src/app/api/leaderboard/route.ts
+++ b/src/app/api/leaderboard/route.ts
@@ -1,5 +1,6 @@
import { NextResponse } from "next/server";
import { prisma } from "@/lib/prisma-client";
+import { logger } from "@/lib/monitoring";
export async function GET() {
try {
@@ -40,7 +41,7 @@ export async function GET() {
return NextResponse.json({ success: true, leaderboard: formattedUsers });
} catch (error) {
- console.error("Leaderboard API error:", error);
+ logger.error("Leaderboard API error", "LeaderboardAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Failed to fetch leaderboard" },
{ status: 500 }
diff --git a/src/app/api/og/profile/[id]/route.tsx b/src/app/api/og/profile/[id]/route.tsx
index 8537c6a..48b8665 100644
--- a/src/app/api/og/profile/[id]/route.tsx
+++ b/src/app/api/og/profile/[id]/route.tsx
@@ -1,5 +1,6 @@
import { ImageResponse } from 'next/og';
import { prisma } from '@/lib/prisma-client';
+import { logger } from '@/lib/monitoring';
// Change from 'edge' to 'nodejs' runtime for higher bundle size limits
export const runtime = 'nodejs';
@@ -98,7 +99,7 @@ export async function GET(
}
);
} catch (e: any) {
- console.log(`${e.message}`);
+ logger.error(e.message, "OGProfileImage", undefined, e);
return new Response(`Failed to generate the image`, {
status: 500,
});
diff --git a/src/app/api/projects/[id]/donate/route.ts b/src/app/api/projects/[id]/donate/route.ts
index 5854c64..da95702 100644
--- a/src/app/api/projects/[id]/donate/route.ts
+++ b/src/app/api/projects/[id]/donate/route.ts
@@ -3,6 +3,7 @@ import { getServerSession } from "next-auth";
import { authOptions } from "@/lib/auth";
import { prisma } from "@/lib/prisma-client";
import { HttpStatus } from "@/lib/api-response";
+import { logger } from "@/lib/monitoring";
export const dynamic = "force-dynamic";
@@ -72,7 +73,7 @@ export async function POST(request: Request, { params }: Params) {
return NextResponse.json({ success: true, donation }, { status: 201 });
} catch (error) {
- console.error("Donate Error:", error);
+ logger.error("Donate Error", "ProjectDonateAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/projects/[id]/join/route.ts b/src/app/api/projects/[id]/join/route.ts
index 58680b5..299625d 100644
--- a/src/app/api/projects/[id]/join/route.ts
+++ b/src/app/api/projects/[id]/join/route.ts
@@ -3,6 +3,7 @@ import { getServerSession } from "next-auth";
import { authOptions } from "@/lib/auth";
import { prisma } from "@/lib/prisma-client";
import { HttpStatus } from "@/lib/api-response";
+import { logger } from "@/lib/monitoring";
export const dynamic = "force-dynamic";
@@ -89,7 +90,7 @@ export async function POST(request: Request, { params }: Params) {
return NextResponse.json({ success: true, membership }, { status: 201 });
} catch (error) {
- console.error("Project Join Error:", error);
+ logger.error("Project Join Error", "ProjectJoinAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/projects/[id]/route.ts b/src/app/api/projects/[id]/route.ts
index 8f6bb5c..4a673aa 100644
--- a/src/app/api/projects/[id]/route.ts
+++ b/src/app/api/projects/[id]/route.ts
@@ -3,6 +3,7 @@ import { getServerSession } from "next-auth";
import { authOptions } from "@/lib/auth";
import { prisma } from "@/lib/prisma-client";
import { HttpStatus } from "@/lib/api-response";
+import { logger } from "@/lib/monitoring";
export const dynamic = "force-dynamic";
@@ -45,7 +46,7 @@ export async function GET(_request: Request, { params }: Params) {
return NextResponse.json({ success: true, project });
} catch (error) {
- console.error("Project GET Error:", error);
+ logger.error("Project GET Error", "ProjectAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
@@ -107,7 +108,7 @@ export async function PATCH(request: Request, { params }: Params) {
return NextResponse.json({ success: true, project: updated });
} catch (error) {
- console.error("Project PATCH Error:", error);
+ logger.error("Project PATCH Error", "ProjectAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/projects/route.ts b/src/app/api/projects/route.ts
index 2c7d377..f4f6e12 100644
--- a/src/app/api/projects/route.ts
+++ b/src/app/api/projects/route.ts
@@ -4,6 +4,7 @@ import { authOptions } from "@/lib/auth";
import { prisma } from "@/lib/prisma-client";
import { HttpStatus } from "@/lib/api-response";
import arcjet, { shield, slidingWindow } from "@/lib/arcjet";
+import { logger } from "@/lib/monitoring";
export const dynamic = "force-dynamic";
@@ -54,7 +55,7 @@ export async function GET(request: Request) {
},
});
} catch (error) {
- console.error("Projects GET Error:", error);
+ logger.error("Projects GET Error", "ProjectsAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
@@ -133,7 +134,7 @@ export async function POST(request: Request) {
return NextResponse.json({ success: true, project }, { status: 201 });
} catch (error) {
- console.error("Projects POST Error:", error);
+ logger.error("Projects POST Error", "ProjectsAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/user/[id]/profile/route.ts b/src/app/api/user/[id]/profile/route.ts
index 440852f..f398f7c 100644
--- a/src/app/api/user/[id]/profile/route.ts
+++ b/src/app/api/user/[id]/profile/route.ts
@@ -1,5 +1,6 @@
import { NextRequest, NextResponse } from "next/server";
import { prisma } from "@/lib/prisma-client";
+import { logger } from "@/lib/monitoring";
export async function GET(
request: NextRequest,
@@ -70,7 +71,7 @@ export async function GET(
});
} catch (error) {
- console.error("Public profile fetch error:", error);
+ logger.error("Public profile fetch error", "UserProfileAPI", undefined, error);
return NextResponse.json(
{ error: "Internal server error" },
{ status: 500 }
diff --git a/src/app/api/user/course/complete/route.ts b/src/app/api/user/course/complete/route.ts
index 0854c0e..a68aa5d 100644
--- a/src/app/api/user/course/complete/route.ts
+++ b/src/app/api/user/course/complete/route.ts
@@ -79,7 +79,7 @@ export async function POST(request: NextRequest) {
bonusXp
});
} catch (error) {
- console.error("Course completion Error:", error);
+ logger.error("Course completion Error", "CourseCompleteAPI", undefined, error);
return NextResponse.json({ error: "Internal server error" }, { status: HttpStatus.INTERNAL_ERROR });
}
}
diff --git a/src/app/api/user/nft-sync/route.ts b/src/app/api/user/nft-sync/route.ts
index 6c1c376..8c5dfcb 100644
--- a/src/app/api/user/nft-sync/route.ts
+++ b/src/app/api/user/nft-sync/route.ts
@@ -4,6 +4,7 @@ import { authOptions } from "@/lib/auth";
import { syncUserNFTs } from "@/lib/nft-service";
import arcjet, { shield, slidingWindow } from "@/lib/arcjet";
import { HttpStatus } from "@/lib/api-response";
+import { logger } from "@/lib/monitoring";
export const dynamic = 'force-dynamic';
@@ -39,7 +40,7 @@ export async function POST(request: NextRequest) {
return NextResponse.json(result);
} catch (error) {
- console.error("NFT Sync Error:", error);
+ logger.error("NFT Sync Error", "NFTSyncAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/user/nft/mint/route.ts b/src/app/api/user/nft/mint/route.ts
index b630241..de62504 100644
--- a/src/app/api/user/nft/mint/route.ts
+++ b/src/app/api/user/nft/mint/route.ts
@@ -29,10 +29,8 @@ export async function POST(request: NextRequest) {
});
if (!userCourse) {
- // Optional: you might want to allow minting if they are at 100% even if not flagged yet
- // but for safety we check the flag
logger.warn(`User ${session.user.id} tried to mint NFT for uncompleted course ${courseSlug}`, "api/nft/mint");
- // return NextResponse.json({ error: "Course not completed" }, { status: 400 });
+ return NextResponse.json({ error: "Course not completed" }, { status: 400 });
}
// Check if NFT already exists for this course and user to avoid double minting
diff --git a/src/app/api/user/nft/share/route.ts b/src/app/api/user/nft/share/route.ts
index 0c68507..7c43477 100644
--- a/src/app/api/user/nft/share/route.ts
+++ b/src/app/api/user/nft/share/route.ts
@@ -5,6 +5,7 @@ import { prisma } from "@/lib/prisma-client";
import { pinJSON } from "@/lib/pinata-config";
import { ipfsToGatewayUrl } from "@/lib/ipfs";
import { HttpStatus } from "@/lib/api-response";
+import { logger } from "@/lib/monitoring";
export const dynamic = "force-dynamic";
@@ -65,7 +66,7 @@ export async function POST(request: Request) {
cid = ipfsUri.replace("ipfs://", "");
} catch (pinError) {
// Graceful degradation when Pinata isn't configured
- console.warn("Pinata not configured, returning mock CID", pinError);
+ logger.warn("Pinata not configured, returning mock CID", "NFTShareAPI", { pinError: String(pinError) });
cid = `QmMock${nftId.replace(/-/g, "").slice(0, 32)}`;
}
@@ -76,7 +77,7 @@ export async function POST(request: Request) {
shareUrl: `${process.env.NEXTAUTH_URL || "http://localhost:3000"}/nft/${nftId}`,
});
} catch (error) {
- console.error("NFT Share Error:", error);
+ logger.error("NFT Share Error", "NFTShareAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/user/nfts/route.ts b/src/app/api/user/nfts/route.ts
index f516c81..4b9254f 100644
--- a/src/app/api/user/nfts/route.ts
+++ b/src/app/api/user/nfts/route.ts
@@ -1,4 +1,4 @@
-import { NextRequest, NextResponse } from "next/server";
+import { NextResponse } from "next/server";
import { getServerSession } from "next-auth";
import { authOptions } from "@/lib/auth";
@@ -32,52 +32,3 @@ export async function GET() {
);
}
}
-
-export async function POST(request: NextRequest) {
- try {
- const session = await getServerSession(authOptions);
-
- if (!session?.user?.id) {
- return NextResponse.json(
- { error: "Unauthorized - Please sign in to mint NFTs" },
- { status: 401 }
- );
- }
-
- const body = await request.json();
- const { name, description, image, attributes = [] } = body;
-
- if (!name || !description) {
- return NextResponse.json(
- { error: "Name and description are required" },
- { status: 400 }
- );
- }
-
- // For demo purposes, create a mock NFT
- const nft = {
- id: `nft-${Date.now()}`,
- userId: session.user.id,
- tokenId: `token-${Date.now()}`,
- name,
- description,
- image: image || `https://ethed.app/nfts/default.png`,
- attributes,
- metadata: {
- mintedAt: new Date().toISOString()
- },
- createdAt: new Date()
- };
-
- return NextResponse.json({
- message: "NFT minted successfully",
- nft
- });
-
- } catch {
- return NextResponse.json(
- { error: "Internal server error" },
- { status: 500 }
- );
- }
-}
\ No newline at end of file
diff --git a/src/app/api/user/profile-data/route.ts b/src/app/api/user/profile-data/route.ts
index e18100b..573d8b4 100644
--- a/src/app/api/user/profile-data/route.ts
+++ b/src/app/api/user/profile-data/route.ts
@@ -5,6 +5,7 @@ import { prisma } from "@/lib/prisma-client";
import { getExplorerTxUrl } from "@/lib/contracts";
import arcjet, { shield, slidingWindow } from "@/lib/arcjet";
import { HttpStatus } from "@/lib/api-response";
+import { logger } from "@/lib/monitoring";
export const dynamic = 'force-dynamic';
@@ -50,7 +51,19 @@ export async function GET(request: Request) {
wallets: true,
courses: {
include: {
- course: true
+ course: {
+ select: {
+ id: true,
+ title: true,
+ slug: true,
+ description: true,
+ price: true,
+ level: true,
+ status: true,
+ createdAt: true,
+ updatedAt: true
+ }
+ }
}
},
nfts: {
@@ -170,7 +183,7 @@ export async function GET(request: Request) {
});
} catch (error) {
- console.error("Profile Data Error:", error);
+ logger.error("Profile Data Error", "ProfileDataAPI", undefined, error);
return NextResponse.json(
{ success: false, error: "Internal server error" },
{ status: HttpStatus.INTERNAL_ERROR }
diff --git a/src/app/api/user/wallets/route.ts b/src/app/api/user/wallets/route.ts
index fdc4771..1e58aff 100644
--- a/src/app/api/user/wallets/route.ts
+++ b/src/app/api/user/wallets/route.ts
@@ -3,6 +3,7 @@ import { getServerSession } from "next-auth";
import { authOptions } from "@/lib/auth";
import { prisma } from "@/lib/prisma-client";
import aj, { slidingWindow } from "@/lib/arcjet";
+import { AMOY_CHAIN_ID } from "@/lib/contracts";
// Rate limiting for wallet connections
const walletRateLimit = aj.withRule(
@@ -66,7 +67,7 @@ export async function POST(request: NextRequest) {
}
const body = await request.json();
- const { address: rawAddress, chainId = 1, ensName, ensAvatar } = body;
+ const { address: rawAddress, chainId = AMOY_CHAIN_ID, ensName, ensAvatar } = body;
if (!rawAddress) {
return NextResponse.json(
@@ -130,9 +131,9 @@ export async function POST(request: NextRequest) {
message: "Wallet connected successfully",
wallet
});
- } catch (err: any) {
+ } catch (err: unknown) {
// Handle unique-constraint race: wallet may have been created concurrently
- if (err?.code === 'P2002') {
+ if ((err as { code?: string })?.code === 'P2002') {
const existing = await prisma.walletAddress.findFirst({
where: { address: normalizedAddress, chainId }
});
diff --git a/src/app/community/error.tsx b/src/app/community/error.tsx
new file mode 100644
index 0000000..3af274b
--- /dev/null
+++ b/src/app/community/error.tsx
@@ -0,0 +1,51 @@
+'use client';
+
+import { useEffect } from 'react';
+import { logger } from '@/lib/monitoring';
+import { Button } from '@/components/ui/button';
+import { Card, CardContent } from '@/components/ui/card';
+import { AlertTriangle, RefreshCw, Home } from 'lucide-react';
+import Link from 'next/link';
+
+export default function CommunityError({
+ error,
+ reset,
+}: {
+ error: Error & { digest?: string };
+ reset: () => void;
+}) {
+ useEffect(() => {
+ logger.error('Community page error', 'CommunityError', undefined, error);
+ }, [error]);
+
+ return (
+
+
+
+
+ Couldn't load community
+
+ We had trouble loading the community page. Please try again.
+
+ {error.digest && (
+
+ Error ID: {error.digest}
+
+ )}
+
+
+
+
+
+
+
+ );
+}
diff --git a/src/app/community/layout.tsx b/src/app/community/layout.tsx
new file mode 100644
index 0000000..257f35c
--- /dev/null
+++ b/src/app/community/layout.tsx
@@ -0,0 +1,20 @@
+import type { Metadata } from "next";
+
+export const metadata: Metadata = {
+ title: "Community | EthEd",
+ description:
+ "Join the EthEd community of Web3 learners, builders, and educators. Collaborate, earn rewards, and grow together.",
+ openGraph: {
+ title: "Community | EthEd",
+ description:
+ "Join the EthEd community of Web3 learners, builders, and educators.",
+ },
+};
+
+export default function CommunityLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return children;
+}
diff --git a/src/app/community/page.tsx b/src/app/community/page.tsx
index 277c74d..65cfc48 100644
--- a/src/app/community/page.tsx
+++ b/src/app/community/page.tsx
@@ -25,7 +25,14 @@ import {
CheckCircle,
} from "lucide-react";
import Link from "next/link";
-import { FaDiscord as Discord } from "react-icons/fa";
+// Discord icon - inline SVG to avoid pulling in the entire react-icons package
+function DiscordIcon({ className }: { className?: string }) {
+ return (
+
+ );
+}
import { getFormattedMetrics, formatMetric } from "@/lib/metrics";
interface Milestone {
@@ -651,7 +658,7 @@ export default function CommunityPage() {
diff --git a/src/app/dashboard/error.tsx b/src/app/dashboard/error.tsx
index 20e4aae..b3d3359 100644
--- a/src/app/dashboard/error.tsx
+++ b/src/app/dashboard/error.tsx
@@ -1,6 +1,7 @@
'use client';
import { useEffect } from 'react';
+import { logger } from '@/lib/monitoring';
import { Button } from '@/components/ui/button';
import { Card, CardContent } from '@/components/ui/card';
import { AlertTriangle, RefreshCw, Home } from 'lucide-react';
@@ -15,7 +16,7 @@ export default function DashboardError({
}) {
useEffect(() => {
// Log the error to an error reporting service
- console.error('Dashboard error:', error);
+ logger.error('Dashboard error', 'DashboardError', undefined, error);
}, [error]);
return (
diff --git a/src/app/dashboard/layout.tsx b/src/app/dashboard/layout.tsx
new file mode 100644
index 0000000..6daf847
--- /dev/null
+++ b/src/app/dashboard/layout.tsx
@@ -0,0 +1,16 @@
+import type { Metadata } from "next";
+
+export const metadata: Metadata = {
+ title: "Dashboard | EthEd",
+ description:
+ "Track your learning progress, manage NFT certificates, and view your Web3 education journey.",
+ robots: { index: false, follow: false },
+};
+
+export default function DashboardLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return children;
+}
diff --git a/src/app/donate/layout.tsx b/src/app/donate/layout.tsx
new file mode 100644
index 0000000..134c0e7
--- /dev/null
+++ b/src/app/donate/layout.tsx
@@ -0,0 +1,20 @@
+import type { Metadata } from "next";
+
+export const metadata: Metadata = {
+ title: "Donate | EthEd",
+ description:
+ "Support Web3 education by donating to EthEd. Help make blockchain learning accessible to everyone.",
+ openGraph: {
+ title: "Support Web3 Education | EthEd",
+ description:
+ "Support Web3 education by donating to EthEd.",
+ },
+};
+
+export default function DonateLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return children;
+}
diff --git a/src/app/donate/page.tsx b/src/app/donate/page.tsx
index 749e3a4..2f1ced2 100644
--- a/src/app/donate/page.tsx
+++ b/src/app/donate/page.tsx
@@ -38,7 +38,7 @@ const TOKENS = [
{ symbol: 'WETH', name: 'Wrapped ETH', desc: 'ERC-20 wrapped Ether' },
];
-const DONATION_ADDRESS = '0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18';
+const DONATION_ADDRESS = '0x2A505a987cB41A2e2c235D851e3d74Fa24206229';
/* ─── Animated particles ─── */
function ParticleField() {
diff --git a/src/app/global-error.tsx b/src/app/global-error.tsx
index e9a870c..323384b 100644
--- a/src/app/global-error.tsx
+++ b/src/app/global-error.tsx
@@ -5,7 +5,6 @@ import { Button } from '@/components/ui/button';
import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card';
import { AlertTriangle, RefreshCw, Home } from 'lucide-react';
import Link from 'next/link';
-import { logger } from '@/lib/monitoring';
export default function GlobalError({
error,
@@ -16,7 +15,7 @@ export default function GlobalError({
}) {
useEffect(() => {
// Log the error to an error reporting service
- logger.error('Global error', 'global-error', undefined, error);
+ console.error('Global error:', error);
}, [error]);
return (
diff --git a/src/app/globals.css b/src/app/globals.css
index 73ef5ea..6200cca 100644
--- a/src/app/globals.css
+++ b/src/app/globals.css
@@ -3,6 +3,18 @@
@custom-variant dark (&:is(.dark *));
+/* Respect user motion preferences globally */
+@media (prefers-reduced-motion: reduce) {
+ *,
+ *::before,
+ *::after {
+ animation-duration: 0.01ms !important;
+ animation-iteration-count: 1 !important;
+ transition-duration: 0.01ms !important;
+ scroll-behavior: auto !important;
+ }
+}
+
body {
font-family: var(--font-geist-sans), ui-sans-serif, system-ui, sans-serif;
}
@@ -204,6 +216,9 @@ h1, h2, h3 {
:root:not(.dark) .to-slate-800\/90 { --tw-gradient-to: color-mix(in srgb, var(--muted) 90%, transparent) !important; }
:root:not(.dark) .from-slate-950 { --tw-gradient-from: var(--background) !important; }
:root:not(.dark) .to-slate-950 { --tw-gradient-to: var(--background) !important; }
+:root:not(.dark) .via-slate-950 { --tw-gradient-via: var(--background) !important; }
+:root:not(.dark) .via-slate-900 { --tw-gradient-via: var(--card) !important; }
+:root:not(.dark) .via-slate-800 { --tw-gradient-via: var(--muted) !important; }
/* ── Hover states ── */
:root:not(.dark) .hover\:bg-white\/5:hover { background-color: color-mix(in srgb, var(--muted) 50%, transparent) !important; }
diff --git a/src/app/how-it-works/layout.tsx b/src/app/how-it-works/layout.tsx
new file mode 100644
index 0000000..9aed2a3
--- /dev/null
+++ b/src/app/how-it-works/layout.tsx
@@ -0,0 +1,20 @@
+import type { Metadata } from "next";
+
+export const metadata: Metadata = {
+ title: "How It Works | EthEd",
+ description:
+ "Learn how EthEd works — from signing up to earning NFT certificates for completing Web3 courses.",
+ openGraph: {
+ title: "How It Works | EthEd",
+ description:
+ "Learn how EthEd works — from signing up to earning NFT certificates.",
+ },
+};
+
+export default function HowItWorksLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return children;
+}
diff --git a/src/app/layout.tsx b/src/app/layout.tsx
index ef59ab3..99f2a61 100644
--- a/src/app/layout.tsx
+++ b/src/app/layout.tsx
@@ -85,7 +85,6 @@ export default function RootLayout({
- {/* Dev-only children guard: throws (with stack) if a non-primitive React child is rendered */}
{children}
diff --git a/src/app/leaderboard/error.tsx b/src/app/leaderboard/error.tsx
new file mode 100644
index 0000000..d70e35a
--- /dev/null
+++ b/src/app/leaderboard/error.tsx
@@ -0,0 +1,51 @@
+'use client';
+
+import { useEffect } from 'react';
+import { logger } from '@/lib/monitoring';
+import { Button } from '@/components/ui/button';
+import { Card, CardContent } from '@/components/ui/card';
+import { AlertTriangle, RefreshCw, Home } from 'lucide-react';
+import Link from 'next/link';
+
+export default function LeaderboardError({
+ error,
+ reset,
+}: {
+ error: Error & { digest?: string };
+ reset: () => void;
+}) {
+ useEffect(() => {
+ logger.error('Leaderboard error', 'LeaderboardError', undefined, error);
+ }, [error]);
+
+ return (
+
+
+
+
+ Couldn't load leaderboard
+
+ We had trouble loading the leaderboard. Please try again.
+
+ {error.digest && (
+
+ Error ID: {error.digest}
+
+ )}
+
+
+
+
+
+
+
+ );
+}
diff --git a/src/app/leaderboard/layout.tsx b/src/app/leaderboard/layout.tsx
new file mode 100644
index 0000000..31504cb
--- /dev/null
+++ b/src/app/leaderboard/layout.tsx
@@ -0,0 +1,20 @@
+import type { Metadata } from "next";
+
+export const metadata: Metadata = {
+ title: "Leaderboard | EthEd",
+ description:
+ "See the top Web3 learners on EthEd. Earn XP by completing courses and climb the ranks.",
+ openGraph: {
+ title: "Leaderboard | EthEd",
+ description:
+ "See the top Web3 learners on EthEd. Earn XP and climb the ranks.",
+ },
+};
+
+export default function LeaderboardLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return children;
+}
diff --git a/src/app/leaderboard/loading.tsx b/src/app/leaderboard/loading.tsx
new file mode 100644
index 0000000..7571238
--- /dev/null
+++ b/src/app/leaderboard/loading.tsx
@@ -0,0 +1,30 @@
+import { Card, CardContent } from '@/components/ui/card';
+
+export default function LeaderboardLoading() {
+ return (
+
+
+
+
+
+ {Array.from({ length: 10 }).map((_, i) => (
+
+
+
+
+
+
+
+
+ ))}
+
+
+
+ );
+}
diff --git a/src/app/leaderboard/page.tsx b/src/app/leaderboard/page.tsx
index 58c09fc..67e74b8 100644
--- a/src/app/leaderboard/page.tsx
+++ b/src/app/leaderboard/page.tsx
@@ -1,6 +1,7 @@
'use client';
import { useEffect, useState } from 'react';
+import { logger } from '@/lib/monitoring';
import { motion } from 'motion/react';
import { Trophy, Medal, Crown, Flame, Star, Loader2, ArrowRight, User } from 'lucide-react';
import Footer from '@/app/(public)/_components/footer';
@@ -34,7 +35,7 @@ export default function LeaderboardPage() {
setLeaderboard(data.leaderboard);
}
} catch (err) {
- console.error("Failed to load leaderboard");
+ logger.error("Failed to load leaderboard", "LeaderboardPage");
} finally {
setLoading(false);
}
diff --git a/src/app/learn/error.tsx b/src/app/learn/error.tsx
index 6ab7f96..536f6cf 100644
--- a/src/app/learn/error.tsx
+++ b/src/app/learn/error.tsx
@@ -1,6 +1,7 @@
'use client';
import { useEffect } from 'react';
+import { logger } from '@/lib/monitoring';
import { Button } from '@/components/ui/button';
import { Card, CardContent } from '@/components/ui/card';
import { AlertTriangle, RefreshCw, Home } from 'lucide-react';
@@ -14,7 +15,7 @@ export default function LearnError({
reset: () => void;
}) {
useEffect(() => {
- console.error('Learn page error:', error);
+ logger.error('Learn page error', 'LearnError', undefined, error);
}, [error]);
return (
diff --git a/src/app/learn/layout.tsx b/src/app/learn/layout.tsx
new file mode 100644
index 0000000..633b4c2
--- /dev/null
+++ b/src/app/learn/layout.tsx
@@ -0,0 +1,20 @@
+import type { Metadata } from "next";
+
+export const metadata: Metadata = {
+ title: "Learn | EthEd",
+ description:
+ "Explore Web3 courses on blockchain, Solidity, DeFi, NFTs, and more. Learn at your own pace with hands-on projects.",
+ openGraph: {
+ title: "Learn Web3 & Blockchain | EthEd",
+ description:
+ "Explore Web3 courses on blockchain, Solidity, DeFi, NFTs, and more.",
+ },
+};
+
+export default function LearnLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return children;
+}
diff --git a/src/app/learning-hub/error.tsx b/src/app/learning-hub/error.tsx
index 8e30008..f8d2b04 100644
--- a/src/app/learning-hub/error.tsx
+++ b/src/app/learning-hub/error.tsx
@@ -1,6 +1,7 @@
'use client';
import { useEffect } from 'react';
+import { logger } from '@/lib/monitoring';
import { Button } from '@/components/ui/button';
import { Card, CardContent } from '@/components/ui/card';
import { BookX, RefreshCw, Home } from 'lucide-react';
@@ -14,7 +15,7 @@ export default function LearningHubError({
reset: () => void;
}) {
useEffect(() => {
- console.error('Learning hub error:', error);
+ logger.error('Learning hub error', 'LearningHubError', undefined, error);
}, [error]);
return (
diff --git a/src/app/learning-hub/page.tsx b/src/app/learning-hub/page.tsx
index e9d8e2d..c4d7635 100644
--- a/src/app/learning-hub/page.tsx
+++ b/src/app/learning-hub/page.tsx
@@ -1,15 +1,22 @@
'use client';
import React, { useState } from 'react';
+import dynamic from 'next/dynamic';
import { Tabs, TabsContent, TabsList, TabsTrigger } from '@/components/ui/tabs';
import { Card, CardContent, CardDescription, CardHeader, CardTitle } from '@/components/ui/card';
import { Badge } from '@/components/ui/badge';
import { motion } from 'motion/react';
-import GamificationDashboard from '@/components/GamificationDashboard';
-import DiscussionBoard from '@/components/DiscussionBoard';
import CourseModulePage from '@/components/CourseModulePage';
import { BookOpen, Flame, Trophy, MessageCircle } from 'lucide-react';
+// Lazy-load heavy interactive components
+const GamificationDashboard = dynamic(() => import('@/components/GamificationDashboard'), {
+ loading: () =>
,
+});
+const DiscussionBoard = dynamic(() => import('@/components/DiscussionBoard'), {
+ loading: () =>
,
+});
+
/**
* DEMO: Learning Hub Dashboard
*
diff --git a/src/app/nft/[id]/page.tsx b/src/app/nft/[id]/page.tsx
index b34ebe5..670f0b7 100644
--- a/src/app/nft/[id]/page.tsx
+++ b/src/app/nft/[id]/page.tsx
@@ -52,8 +52,8 @@ export default async function NFTPublicPage({ params }: NFTPageProps) {
const metadata = nft.metadata && typeof nft.metadata === 'object' ? nft.metadata as Record
: {};
const description = (metadata.description as string) || `${nft.name} — earned on EthEd`;
- const txHash = (nft as any).transactionHash as string | null;
- const chainId = (nft as any).chainId as number | null;
+ const txHash = (nft as unknown as { transactionHash?: string | null }).transactionHash ?? null;
+ const chainId = (nft as unknown as { chainId?: number | null }).chainId ?? null;
const explorerUrl = txHash && chainId && !txHash.startsWith('0x' + '0'.repeat(64))
? getExplorerTxUrl(chainId, txHash)
: null;
diff --git a/src/app/not-found.tsx b/src/app/not-found.tsx
index a9ccad6..dbb6a66 100644
--- a/src/app/not-found.tsx
+++ b/src/app/not-found.tsx
@@ -1,14 +1,21 @@
+import type { Metadata } from 'next';
import Link from 'next/link';
import { Button } from '@/components/ui/button';
import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card';
import { Home, ArrowLeft, Search } from 'lucide-react';
+export const metadata: Metadata = {
+ title: 'Page Not Found | EthEd',
+};
+
export default function NotFound() {
return (
- 🔍
+
+
+
Page Not Found
diff --git a/src/app/onboarding/_components/Onboarding.tsx b/src/app/onboarding/_components/Onboarding.tsx
index 906472b..7bd3fe4 100644
--- a/src/app/onboarding/_components/Onboarding.tsx
+++ b/src/app/onboarding/_components/Onboarding.tsx
@@ -1,5 +1,6 @@
"use client";
+import dynamic from "next/dynamic";
import { useState, useEffect } from "react";
import { motion, AnimatePresence } from "motion/react";
import { Button } from "@/components/ui/button";
@@ -7,7 +8,10 @@ import { Card, CardContent, CardHeader, CardTitle } from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Label } from "@/components/ui/label";
import { Badge } from "@/components/ui/badge";
-import Confetti from "react-confetti";
+
+// Lazy-load confetti — only shown on completion
+const Confetti = dynamic(() => import("react-confetti"), { ssr: false });
+
import {
Sparkles,
BadgeCheck,
@@ -19,11 +23,13 @@ import {
Zap,
CheckCircle,
AlertTriangle,
+ Wallet,
} from "lucide-react";
import { toast } from "sonner";
import { useRouter } from "next/navigation";
import { useSession } from "next-auth/react";
import { ENS_ROOT_DOMAIN } from "@/lib/contracts";
+import { SiweLoginButton } from "@/components/siwe-login-button";
export default function Onboarding() {
const { data: session, status, update: updateSession } = useSession();
@@ -151,6 +157,14 @@ export default function Onboarding() {
return;
}
+ // Check if user has a wallet connected (only for email-only users)
+ if (!session?.address) {
+ toast.error("Please connect your wallet to register ENS. If you don't have a wallet, install MetaMask or another Web3 wallet.", {
+ duration: 6000,
+ });
+ return;
+ }
+
try {
setIsLoading(true);
@@ -459,11 +473,37 @@ export default function Onboarding() {
+ {!session?.address && (
+
+
+
+
+
Wallet Required
+
+ ENS registration requires a Web3 wallet. Connect your wallet below to continue.
+
+
+
+
+
+ Don't have a wallet?{' '}
+
+ Install MetaMask
+
+
+
+ )}
+