Remix

Make your own version of XMINERS ORC

Get an exact, working copy in your account, then change anything with chat.

Original by exepratik

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# BUILD XMINERS ORC — PREMIUM TELEGRAM-STYLE MINING WEB APP

Act as a senior full-stack engineer, UI/UX designer, database architect and security engineer.

Build or upgrade a complete, mobile-first web application called XMINERS ORC. The application should be strongly inspired by the overall layout, navigation, mining flow and engagement mechanics of Nautilus Mine, while using original branding, original graphics and independently implemented components.

IMPORTANT: This is a real, functional web application project, not just a static mockup or UI prototype.

## 1. BRAND IDENTITY

Product name: XMINERS ORC
Creator credit: Made by exe.pratik
Support and queries: Instagram @ofc_atlas

Visual style:
- Premium black background.
- Emerald-green highlights.
- Subtle metallic silver details.
- Futuristic mining terminal aesthetic.
- Original XMINERS X logo and original ORC-themed mining core.
- Smooth transitions, subtle glow, animated progress rings and lightweight particle effects.
- Professional charts, compact cards and clear typography.
- Fully responsive on Android, iPhone, tablet and desktop.

Do not use Bitcoin/BTC branding, BTC logos or unrelated cryptocurrency names. Do not copy Nautilus Mine's exact proprietary assets, logo, code or pixel-perfect screens.

## 2. MANDATORY LOGIN

Users must sign in before entering the main application.

Implement Google Login using the builder's supported authentication integration. If Google OAuth credentials or configuration are required, explain the setup instead of pretending authentication is working.

Requirements:
- Unauthenticated users see only the login screen.
- Protect all private pages and account-specific backend operations.
- Show the user's Google profile picture, email and account settings after login.
- Persist authenticated sessions securely.
- Add a working sign-out button.
- Ensure one user's balance, wallet and mining history are never visible to another user.
- Enforce authorization on the server and in database access policies, not only in the UI.

## 3. MINING DASHBOARD

Create a polished mining dashboard with:
- Available ORC balance.
- Pending and confirmed in-app rewards.
- Current mining status.
- Animated ORC mining core.
- Three-hour countdown timer.
- Circular mining progress indicator.
- Configured reward per session.
- Mining rate and miner level.
- Total completed sessions.
- Recent mining activity.
- Provider connection status based on actual integration health.
- Compact activity and reward charts.

The dashboard must feel like a polished Telegram mini mining game while remaining easy to navigate on a mobile phone.

## 4. THREE-HOUR MINING ENGINE

Configure each eligible mining session as follows:

Session duration: 3 hours.
Target reward: 0.1999 ORC per successfully completed session.

Required workflow:
READY → RUNNING → COMPLETED → CLAIMED → READY.

Rules:
- The server controls session start and end timestamps.
- Users can have only one active session at a time.
- Refreshing the page must not reset the timer or create another session.
- Rewards become eligible only after the configured session completes.
- Claiming a reward must be idempotent and must never credit the same session twice.
- Prevent duplicate requests, race conditions, negative balances and client-side reward manipulation.
- Record every reward credit in a transaction ledger.
- Allow a new session only when the previous session meets the configured completion and claim rules.
- Display clear error messages and retry options.
- Do not disable security controls to work around rate-limit errors.

IMPORTANT: If no funded blockchain reward system exists, implement the 0.1999 ORC value as a clearly labelled in-app reward or simulation. Never falsely claim that actual ORC tokens were mined or transferred.

## 5. NAVIGATION AND FEATURES

Use a mobile-first fixed bottom navigation bar.

Include:
1. Home — balance, session timer and mining core.
2. Mine — session controls and mining history.
3. Upgrades — miner levels and progression.
4. Rewards — daily check-in, missions and achievements.
5. Settings — profile, wallet, security and support.

Also include:
- Referral links and referral history.
- Leaderboard using legitimate recorded application data.
- Notifications for session completion and reward status.
- Empty, loading, offline and error states.

All buttons must perform their intended actions. Do not create decorative buttons that do nothing.

## 6. MINER UPGRADES

Create upgrade cards for:
- 10 ORC
- 20 ORC
- 50 ORC
- 100 ORC

These are proposed in-app upgrade tiers, not guaranteed investment returns.

Display the cost, level, effect and applicable mining rate before confirmation.

Validate balances and purchases on the server. Record transactions safely and prevent duplicate purchases or overspending.

If the purchase system is not configured, show a clear unavailable state rather than pretending the purchase succeeded.

## 7. WALLET AND WITHDRAWAL

Create a wallet page supporting an appropriately validated ORC address on the configured blockchain.

Include:
- Network identification.
- Wallet address management.
- Available and pending rewards.
- Withdrawal request form.
- Minimum withdrawal and fee information only when actually configured.
- Withdrawal history and statuses.
- Authorized admin review.

Never ask for seed phrases or private keys.

Do not claim a withdrawal is completed without verified payment or blockchain transaction evidence. Keep real withdrawals disabled until a genuine funded payout mechanism is configured.

## 8. PROVIDER AND REWARD INTEGRATIONS

Show the provider as Connected only when an actual integration health check confirms connectivity.

If no provider exists, show Not Configured.

Prepare a clean integration structure for verified rewarded ads, referral rewards and future blockchain payouts. Rewarded ads must be verified server-side; clicking a frontend button alone must not generate rewards.

Never fabricate mining hashpower, network statistics, provider connectivity, advertising revenue or blockchain transactions.

## 9. SETTINGS, SUPPORT AND CREATOR CREDIT

Create a Settings page containing:
- Google profile and email.
- Wallet settings.
- Account security.
- Notification preferences.
- About XMINERS ORC.
- Support and queries.

Display the creator credit exactly as:

Made by exe.pratik

Display the support contact exactly as:

For any queries, contact us on Instagram: @ofc_atlas

Make @ofc_atlas a clickable Instagram link:
https://www.instagram.com/ofc_atlas/

Show the creator credit discreetly in Settings → About and the app footer. Keep the Instagram contact accessible without making it intrusive.

## 10. FIX EXISTING BUGS

Audit and fix:
- Repeated content when scrolling.
- Duplicate page sections and navigation.
- Mining session rate-limit errors.
- Multiple active countdown timers.
- Repeated API requests.
- Duplicate reward claims.
- Incorrect currency symbols.
- Mobile overflow and broken layouts.
- Missing error handling.
- Authentication and database access vulnerabilities.

Use reusable components, stable list keys, controlled polling and server-side validation. Do not solve rate-limit errors by removing appropriate rate limits.

## 11. TECHNICAL QUALITY

Use the builder's supported backend, database and authentication features.

- Preserve existing working Google Login and user data when upgrading an existing project.
- Use server-side authorization and database security policies.
- Keep API keys and privileged credentials out of frontend code.
- Add concurrency-safe session and reward operations.
- Use accessible buttons, readable text and reduced-motion support.
- Optimize for low-end Android devices and slow connections.
- Do not invent unsupported SDK functions.
- Do not claim tests passed unless they were actually executed.

## 12. ACCEPTANCE TESTS

Verify the following before completion:

1. Login is required to access the dashboard.
2. Google sign-in and sign-out work.
3. Users cannot access other users' private records.
4. Each user can have at most one active session.
5. The three-hour countdown persists after refresh.
6. The configured reward is 0.1999 ORC per eligible completed session.
7. Duplicate claims cannot create extra rewards.
8. Starting a subsequent session does not trigger uncontrolled requests or rate-limit errors.
9. All page sections appear once.
10. Mobile navigation and scrolling work properly.
11. Currency uses ₹ for INR and ORC for token quantities.
12. Withdrawal and provider statuses reflect verified reality.
13. Instagram support links open correctly.
14. “Made by exe.pratik” appears in Settings → About and the footer.
15. The app has no fake live mining, fake provider connection or fabricated payouts.

First inspect the project and its available integrations. Then implement the app, run available tests and report what is functional, what was tested, and which external integrations still require setup.

Deliver a polished, production-oriented XMINERS ORC application, not merely a visual demo.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.