Please fix

medium

bug: rarity guidance contradicts the displayed block cards

src/pages/index.astro:86

Now: Home says every 1,000th block is Milestone and every 100th is Notable; About repeats these overlapping rules, but the displayed #100 card is Epic and #1,000 is Rare.

Change to: Replace the Home paragraph with 'After block #1,000, every 1,000th block is Milestone; other multiples of 100 are Notable. Earlier blocks use the Legendary, Epic, or Rare tiers.' In About, label Milestone 'Multiples of 1,000 after #1,000' and Notable 'Multiples of 100 after #1,000, excluding Milestones'. Keep the existing artwork and rarity implementation.

Why: Collection guidance should accurately describe the cards people choose; the existing precedence in src/components/BlockCard.astro:4 assigns Legendary, Epic and Rare before testing divisibility.

At 390×844 (also 1440×900), open /preview/index.html.

Read the sample captions '#100 · Epic' and '#1000 · Rare', then scroll to Why collect? > Milestone Blocks: it says 'Every 1,000th block is a Milestone.

Every 100th is Notable.'

Open /preview/about.html and inspect Rarity Tiers: #100 falls under both Epic and Notable, and #1,000 under Rare, Milestone and Notable.

Expected: one unambiguous tier per block matching the rendered cards.

Actual: two concrete sample cards contradict the prose; About has the same overlap at src/pages/about/index.astro:25–29.

less

medium

bug: changing the block during preview displays the previous block

src/scripts/mint.ts:181

Now: The block input remains editable while Preview card awaits blockMinted(). Editing the input invalidates previewRequest, but showToken() subsequently increments that counter again, allowing the old request to display a card and a success message for the previous block.

Change to: Capture the preview request ID before the first RPC await, pass it through to showToken(), and check that same ID before displaying either a card or any result/error message. The existing input handler must invalidate the whole pending preview, including the initial blockMinted() read.

Why: The visible preview must belong to the selected block. A late response must not restore an obsolete card after the visitor changes the field.

At 390×844 in Chromium and WebKit, open /preview/mint.html without a wallet.

Delay the eth_call response for blockMinted(1) by 2,000ms (network interception or throttling), leave Block number at 1 and click Preview card.

While the read is pending, change Block number to 2, then release the unchanged RPC response.

Reproduced in both engines using unchanged captured public Sepolia responses and a measured 2,000ms delay: input value = '2', #tokenSection is visible, #tokenCaption = 'Block #1 · Legendary · Sepolia', and #mintStatus = 'Showing the on-chain card for block #1.'.

Expected: after the edit, the old request cannot reveal a preview or report success for #1; the user can request a new preview for #2.

The input handler at src/scripts/mint.ts:220 invalidates the counter before showToken() creates its new ID at line 170.