Frequently Asked Questions

You do not need to buy tokens to join the community. Buying PLOV does not give you an ownership stake in a company or a promise of income.

This cultural idea explains the project’s name and voice. It does not determine the token’s value.

Use published rules, reports and Proof-hub records to assess what has been delivered. A project name or a set of documents does not remove the risks of buying a token.

Membership of a chat or community does not by itself entitle you to an airdrop, payment or loyalty rewards. Distribution programmes have separate rules.

The official X account is @PlovTeam. Links to the channels, chat and Telegram folder are listed below. Check the exact address: a similar name or logo does not prove authenticity.

Send partnership proposals to hello@plovcoin.com. Voluntary participation does not imply payment, an airdrop or a future reward.

The launch will be postponed if critical requirements remain unmet. A quarterly target is not a confirmed date; check the latest official announcement.

A planned venue does not mean trading is already available. After launch, use confirmed pool links and check the token address; Jupiter route availability must be verified separately.

Before the pool is publicly activated, the starting configuration will be disclosed in a dated participant guide. It is not a guaranteed price, a price floor or a promise of value.

Supported wallets for claims will be listed in the claim instructions. Network fees require SOL. Check the website address and the signing request; never share your recovery phrase.

The initial fee is part of the measures against bots and does not make trading bot-proof. Exact parameters are published in the launch guide and confirmed by the pool configuration in Proof-hub. Review the total cost before confirming a swap; no token fee does not mean a free trade.

Slippage is the difference between the expected and executed price; the trade’s own price impact is a separate factor. The metric is p90 slippage for $1,000 trades. The provisional planning reference for the first 30 days after TGE is under 1.0%; this is not a measured result or guarantee. Measurement methodology will be published with the first monitoring report. See the Whitepaper for monitored liquidity metrics.

The plan is gradual expansion with a Tier-2 first approach, based on organic demand, liquidity depth and community metrics. Discussions and plans are not confirmed listings.

Check the official Solana mint: mint authority is unset. Burns reduce the remaining supply; disabled minting does not mean every token is already circulating.

These are designated allocations, not proof that tokens have been distributed or unlocked. Actual transfers, balances and restrictions are verified separately in Proof-hub.

This applies to the official token on Solana. It does not guarantee wallet operation, exchange availability or the safety of other assets; third-party services have their own restrictions.

Completed burns are documented by transactions in the Proof-hub log. Burning reduces supply but does not guarantee a price increase.

Each wave has its own published rules covering participants, checks, claim windows and token availability. A planned programme does not mean participation or claims are already open.

Access may open by participant groups, or cohorts. Another group receiving access does not by itself mean there is an error with your application. Grouping rules and windows are published for the wave. T+24h is the earliest start of a readiness review, not an automatic claim opening.

Check the published Wave Policy. There is no universal minimum SOL balance, wallet age or transaction count for all waves.

An eligibility rejection and a portal error are different cases. Use the official contact in the Wave Policy and never share your recovery phrase. Reviewing a request does not guarantee inclusion or payment. Publishing a full wallet CSV is not a universal requirement.

Availability schedules and restrictions are published in the Wave Policy before participation. Check your own wave and cohort; there is no universal schedule established here.

Check the revised deadline and resumption announcement. A problem with your connection or device does not by itself mean a general pause. After the deadline, the Wave Policy’s unclaimed-token rule applies; reinstatement is not automatic.

The plan uses on-chain balance snapshots at specified times. Eligibility, observation periods and reward calculations must be approved and published in the Loyalty Policy before the programme opens.

PlovDrop is funded from its own 45% allocation. Airdropped tokens may count towards holding tenure, while eligible reward balances will be defined by the Loyalty Policy. Previously displayed percentages should not be treated as active reward terms or a promised return. Tier conditions, caps and distribution procedures are published before the programme opens.

Risks include limited liquidity, software errors, fraudulent websites, loss of wallet access and service outages. Security reviews, revoked token authorities and public documents do not eliminate these risks.

B4LhtMwbKh8D1nfj7dE6FefKpg7U2qkbYC371DBcJq9x. Tokens with this name on Ethereum, BSC or TON, including purported bridged versions, are not official $PLOV.

Check the domain, Solana network and full token address. Claims take place only through claim.plovcoin.com. Never share your recovery phrase, and inspect every signing request. An authentic link does not mean the project is risk-free.

A plan or rule is not proof of execution. A missing public record also does not prove that an event never happened. Without supporting evidence or a current timestamp, that claim cannot be treated as verified by this page.

All 12 findings are marked Fixed (2 Medium, 2 Low, 8 Info; no Critical or High). The public report was published on hacken.io on 17 September 2026 — the link and scope are on Proof-hub. Future wallet-connect, registration and claim functionality is outside this review’s scope.

A multisig address alone does not prove that liquidity is locked. Proof-hub should identify the position, owner, withdrawal permissions, delays and supporting operations. Planned controls should not be treated as already active.

Conditional liquidity operations under the policy are not a promise to support the price. No fast automatic backstop is planned for the first hours; a readiness review after T+24h does not mean an operation happens automatically.

Include the page address, time and safe reproduction steps; for a suspicious transaction, include its public identifier. Avoid publishing exploit details that could harm users. No reward is promised without separately published terms.

Financial operations must follow treasury permissions and procedures. Check current rules, roles and execution evidence; future governance plans do not describe present rights.

Multisig controls, independent review within its scope, Proof-hub and planned team vesting help assess accountability. Each measure and its actual implementation must be verified separately; a pseudonym does not remove that need.

Check the current signature threshold, execution delay and permissions, not just the wallet label. Treasury balance and total supply are different metrics. Multiple approvals reduce dependence on one key but do not guarantee that funds are safe.

Check the actual start date, programme address, amount and restrictions in Proof-hub. Until that evidence is published, these are approved terms rather than proof of an active restriction.

If governance changes, voting rules, powers and execution procedures will be published separately. Discussing a future DAO does not create those rights today.

The registry will identify the placement, platform, type and amount of compensation, and available payment evidence. Influencer compensation is not counted as PlovDrop. An empty registry is not proof that no paid placements have occurred.