Home Platform Transparency

Platform Transparency

Last Updated:

This page documents the platform's economic model, security practices, development status, and risk factors. We believe transparency is the foundation of trust, and we provide this information to help users, researchers, and reviewers understand exactly how Earning by Project-BHV operates.

1. No Deposit, No Investment

Earning by Project-BHV does not accept any form of deposit, investment, or payment from users. This is a fundamental architectural decision, not an omission:

  • No deposit button or page exists anywhere on the platform.
  • No payment gateway is integrated. The platform does not collect credit card, debit card, UPI, PayPal, or any other payment information.
  • No wallet connection is required. There is no MetaMask, Trust Wallet, or Web3 integration of any kind.
  • No token sale has ever been conducted. $EPB is not sold, traded on exchanges, or offered as an investment.
  • No subscription or membership fee is charged. All features are free to access (subject to task gates).

Implication: Because users never deposit money, there is no pool of user funds that could be misappropriated. The platform cannot "rug pull" or "exit scam" because there are no user assets to take. All $EPB in the system was earned through task completion, not purchased.

2. Not a Cryptocurrency

$EPB (Earning Points Balance) is an internal loyalty reward unit, analogous to airline miles, hotel loyalty points, or reward points on platforms like Swagbucks. It is explicitly not a cryptocurrency:

  • No blockchain: $EPB exists only as a numeric value in a MySQL database. There is no distributed ledger, no blockchain, no mining, and no staking in the cryptographic sense.
  • No smart contract: There is no Solidity, Rust, or any smart contract code. All platform logic is implemented in PHP with MySQL transactions.
  • No exchange listing: $EPB is not listed on CoinMarketCap, CoinGecko, or any cryptocurrency exchange. It cannot be traded, swapped, or transferred outside the platform.
  • No DEX or CEX: There is no decentralized or centralized exchange trading $EPB. The only way to obtain $EPB is by earning it on the platform.
  • No wallet address: Users do not have a cryptocurrency wallet or address. There is nothing to connect to MetaMask or any other wallet.
  • No ICO/IDO/IEO: The platform has never conducted any form of token sale or fundraising.

The name "$EPB" stands for "Earning Points Balance." It is a descriptive label for the withdrawable balance on this platform, not a ticker symbol copied from another project. Any similarity to existing tickers is coincidental.

3. Economic Model

The platform's economy is designed to be self-sustaining through a transparent service fee structure:

Revenue sources:

  • Task admin fee (25%): When a user completes a task, 25% of the reward goes to the platform as a service fee. This funds platform operations, development, hosting, and user payouts.
  • Empty generation pool: When a referral slot at a given depth is unoccupied, that generation's commission share returns to the platform.

Withdrawal friction mechanisms:

  • Fuel cost: Withdrawals consume 100 Points per 1 $EPB. Points are earned through daily login, task approvals, and referrals. This ensures users remain engaged to withdraw.
  • Rank cooldown: Withdrawal frequency is governed by the user's highest-ever Points balance. Higher ranks permit more frequent withdrawals.
  • Minimum withdrawal: 100 $EPB minimum ensures administrative overhead per withdrawal is justified.

Inflation control:

  • Points are non-withdrawable and are consumed as fuel, creating natural demand.
  • $EPB supply is controlled because it can only be earned through tasks (which require admin-created tasks with assigned rewards) or through platform activities that consume other resources (staking rewards come from a pool, market buys consume Points).

4. Technical Security

The platform implements multiple layers of technical security to protect user data and ensure fair operation:

Web security:

  • Content Security Policy (CSP): Restrictive headers prevent XSS and data injection attacks. Only whitelisted CDN sources and Cloudflare are permitted.
  • CSRF tokens: Every form submission requires a unique, server-generated token to prevent cross-site request forgery.
  • HttpOnly + SameSite=Strict cookies: Session cookies are inaccessible to JavaScript and restricted to same-site requests.
  • X-Content-Type-Options: nosniff: Prevents MIME-type sniffing attacks.
  • X-Frame-Options: SAMEORIGIN: Prevents clickjacking via iframe embedding.
  • Cloudflare Turnstile: Privacy-preserving bot detection on registration forms.

Transaction integrity:

  • Database transactions: All multi-step financial operations (task commission distribution, staking claims, market trades, withdrawals) use MySQL transactions with commit/rollback to prevent partial updates.
  • Race condition prevention: UPDATE statements include WHERE balance >= amount conditions followed by row-count checks to prevent double-spending.
  • Referral cycle detection: Recursive CTE queries prevent infinite referral loops when transferring referral trees (red packet claims).

User security:

  • Password policy: Minimum 8 characters, must include uppercase letter and digit. Passwords are hashed (bcrypt/argon2).
  • Session heartbeat: Active sessions are tracked with 60-second pings for automatic timeout.
  • Login attempt tracking: Failed login attempts are logged by IP address and timestamp for rate limiting.
  • Device fingerprinting: Browser, platform, and device type are logged for fraud detection.

5. Code & Development

The platform is built on a custom PHP codebase with MySQL database backend. Key development facts:

  • Language: PHP (server-side), JavaScript (client-side)
  • Database: MySQL with InnoDB for transaction support
  • Infrastructure: Cloudflare-protected, StackCP hosting
  • Source code: The platform's source code is privately maintained for security reasons. Public disclosure of the full codebase would expose the system to attackers who could reverse-engineer fraud detection logic. An early-stage version of the platform code is available on GitHub at github.com/GI-STANDARDS/Earning-Website-Template (older version, same core concept).

6. Contact & Support

Users can reach the platform team for support, inquiries, or issues:

7. Risk Disclosure

Important notice: While the platform is designed with user protection and transparency as core principles, users should be aware of the following risk factors:

  • $EPB has no value outside the platform. It is not legal tender, not backed by any government or financial institution, and has no guaranteed redemption value.
  • Reward rates may change. The platform reserves the right to modify earning rates, reward splits, withdrawal minimums, fuel costs, and cooldown periods.
  • Platform availability is not guaranteed. The platform may be temporarily unavailable, modified, or discontinued at any time.
  • Withdrawals are subject to admin review. All withdrawal requests are manually reviewed to prevent fraud and ensure compliance with KYC requirements.
  • Users should not spend money they cannot afford to lose on any platform. While Earning by Project-BHV requires no deposit, users should be aware that no online platform can guarantee permanent operation.
Sitemap
© 2026 Earning by Project-BHV. All rights reserved.