Publish my existing FLOPPY PEPE game as a React website on IPFS using your normal website publishing flow.

REFERENCE

https://floppy-pepe.bikemcanerkoc.chatgpt.site/

Preserve the existing game rather than designing a replacement. Reuse its source code and original Pepe, RAM and treasure-chest image assets. Preserve the layout, colors, proportions, animations, sounds and arcade buttons. If the reference or source files are inaccessible, explicitly request the source files or repository. Do not silently create an approximate version.

GAME

• Keep the small green Pepe wearing a blue shirt.
• Tap, click or press Space to hop through RAM obstacles.
• Passing a normal obstacle gives 1 point. Gold RAM gives 3 points.
• Colliding with RAM, the ceiling or the ground ends the round.
• Every 10 points increases the level. Speed increases and gaps become narrower.
• Moving RAM gaps begin at level 3.
• Preserve SCORE, BEST, LEVEL, SHARE, RESET, the green IMD link, INFO, STATS and the sound toggle.
• Keep the game immediately playable on desktop and mobile.
• RESET restarts the round without deleting saved player records.

10-DAY COMPETITION

• Replace “3-DAY LEADERBOARD” with “10-DAY LEADERBOARD”.
• The competition lasts exactly 10 days from a configurable launch time. Do not reuse the earlier test competition dates.
• Display the start and end dates clearly.
• Display this exact reward statement: “The competition lasts 10 days. The player ranked #1 at the end will receive 5 IMD. The reward will be sent manually by the organizer after the competition ends.”
• This is one total prize of 5 IMD for the winner.
• Do not create a token, entry fee, automatic payout, prize-distribution contract or daily token payment.
• Freeze competition scores when the competition ends. Allow practice rounds afterward without changing the final ranking.

SHARED LEADERBOARD

• All players must see the same persistent leaderboard.
• Keep Rank, Name, Score and Level columns.
• Rank each player by their highest verified competition score.
• Use a stable player identity; changing a nickname must not create a new player.
• Break equal-score ties by who achieved the score first.
• Refresh immediately after a score is accepted and periodically for other players.
• Verify rounds server-side using game inputs and deterministic replay. Never trust a submitted score number alone.
• Display genuine loading and saving errors; never display fake successful submissions.

DAILY CLAIM

• Preserve the small side panel and the existing cute treasure chest.
• First claim is Day 1. Allow one claim per UTC calendar day.
• Consecutive daily claims increase the streak.
• Missing a day resets the next claim to Day 1.
• Store claim records server-side.
• Claims do not transfer IMD and do not increase game scores.
• Do not restore the old clock or “Local” label.

IPFS AND STORAGE

The IPFS React frontend must connect to a real persistent backend for player records, verified scores and daily claims. Browser storage alone is not sufficient for a shared competition. Keep secret credentials out of frontend code.

If your website publishing environment cannot provision or connect the required backend, explain the missing requirement before presenting the competition as ready. Do not replace shared records with a local-only leaderboard.

DELIVERY

Test hopping, collisions, scoring, difficulty progression, mobile controls, shared ranking, daily claims and the 10-day cutoff.

Return the published IPFS/eth.limo URL, the source repository, and instructions for setting the competition launch time. Keep the original game's appearance.