> For the complete documentation index, see [llms.txt](https://block9.gitbook.io/bidhub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://block9.gitbook.io/bidhub/bidhub-the-platform/bidhub-bidder-benefits.md). # BidHub 'Bidder' Benefits Bidders using BidHub will benefit from its sales mechanism. Anyone can participate in BidHub auctions. Additionally, Block9 pfp holders will have exclusive benefits (see the Holder Benefits tab). ### Benefits for ALL bidders: * Allows buyers to pay what they want to mint an NFT or partake in an auction. * Anti-botting measures prevent bots minting all the NFTs & stops bots dumping on the market when secondary opens. * Increased information for whitelisted wallets to make decisions if WL phase goes after public. * Buyers can run a bidding strategy that suits them. * Auction 'highest price wins' reduces time zone disadvantages for buyers. * Automatic refunds for all unsuccessful bids. ### Buyer valuation - Pay what you want As a buyer, you choose the price you are willing to pay. If you bid enough then you will win. If you don't win then you are refunded and you know that the purchase was more than you were willing to pay. ### Bidding Strategy You can submit multiple bids, this means you have the opportunity to run a minting strategy that suits you. \ \ Example for a NFT mint - you may choose to bid for 5 NFTs at a low price of 1 $Sol as hopeful bids, but also place bids for 2 NFTs at a higher price of 4 $Sol as a *more likely to win* option. ### Time Zones BidHub eliminates the need for you to act quickly and hit the mint button as soon as the mint opens. \ \ The primary filter for successful bids is bid price, as long as you have an 'active bid' at the end of the auction then you will be successful. Timestamp is only considered for bids with the exact same bid value. ### **Reduced Botting - Platform Fee Deters Bots** BidHub implements a small fee which deters bots from submitting excessive bids, ensuring that regular collectors have a better opportunity to win. ### Reduced Botting - Bidding Window, not First Come First Serve (FCFS) BidHub operates over a defined period of time, rather than being first-come-first-serve (FCFS). This mitigates the advantage that custom RPC bots have, giving equal opportunity to all users to place bids without being beat by bots. ### Whitelist (WL) Mechanism With the new 'WL last' whitelisting mechanism offered by BidHub, **whitelisted collectors have more control and flexibility in deciding whether to purchase based on the outcome of public bidding**. This eliminates the risk of upfront commitments to projects that may not sell out when they go public. The shift to the last phase of minting in **BidHub also offers the opportunity for whitelisted collectors to mint at a lower price compared to other non-whitelisted bids.** ### **Audio - Bidder Benefits** {% embed url="" %}

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://block9.gitbook.io/bidhub/bidhub-the-platform/bidhub-bidder-benefits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.