FAQ's: Trading
Trading
How do I create a bid?
To create a bid:
- Log in with your API token in the Account View
- Click Create Bid
- Enter your price (BTC/EH/day)
- Enter your budget (total amount to spend)
- Optionally set a speed limit (max EH/s)
- Enter your pool URL and worker identity
- Confirm via Telegram 2FA
Your bid will appear in the order book and begin receiving hashrate when matched.
What is the speed limit option?
The speed limit lets you cap the maximum hashrate delivered to your pool at any given time. Note that the actual average speed will be slightly lower than the limit.
- Set to 0 or leave empty: No limit (unlimited), receive as much hashrate as available
- Set a value (e.g., 10 PH/s): Maximum 10 PH/s delivered at once
This is useful if:
- Your pool has hashrate limits
- You want more consistent hashrate over time rather than bursts
- You're testing with limited capacity
Note: Minimum budget requirements differ based on speed limit — bids with a speed limit require 10,000 sats minimum, while unlimited speed bids require 100,000 sats minimum.
How is price calculated?
Prices on Braiins Hashpower are quoted in BTC/EH/day (default):
- BTC = Bitcoin
- EH = Exahash (1,000 PH), or more precisely it should be EH/s = Exahash per second
- day = 24 hours of hashrate
For example, if the price is 0.45 BTC/EH/day:
- Buying 1 EH/s for 24 hours costs 0.45 BTC (45,000,000 sats)
- Buying 1 PH/s for 24 hours costs 45,000 sats (0.00045 BTC)
The platform also displays equivalent values in sats/PH/day (retail-friendly) and USD/EH/day (fiat reference). You can switch between these formats in the header.
What happens when my bid is matched?
When your bid is matched:
- Hashrate delivery begins automatically
- Hashrate flows to your specified pool
- Your pool receives mining shares
- Your budget is consumed based on hashrate delivered and price (settled hourly)
- You can monitor progress in the bid details
The bid continues until your budget is exhausted or you cancel it. Note that matching is continuous — your bid may lose or regain delivery as market conditions change.
Can I modify an existing bid?
Yes, you can modify active bids using the Edit action:
- Change the price (may affect matching priority)
- Increase the budget
- Modify the speed limit
You can also use Move Bid to quickly update price based on surrounding bids.
Important: Any modification to a bid resets its age in the matching queue, making it younger. This can affect your matching priority among bids at the same price.
All modifications require Telegram 2FA confirmation.
How do I cancel a bid?
To cancel a bid:
- Find the bid in your Current Bids list or the order book
- Click the Cancel action
Note: There is a cooldown period after bid creation before it can be canceled.
After cancellation:
- The bid enters "Pending Cancel" status while delivery ends and financial settlement completes (typically 1-2 minutes)
- Unspent budget is returned to your available balance
- Partially filled bids keep the hashrate already delivered
What is the Overbid feature?
There are two overbid features:
Place Overbid (from order book): Creates a new bid with a price one tick higher than the selected row.
Move Bid (from your bids): Quickly updates your bid price relative to other bids:
- Overbid the next higher price level
- Overbid the next lower price level
- Overbid the bid with the lowest price currently receiving hashrate
Higher prices are matched first, so overbidding can help your bid receive hashrate faster in competitive markets. Note that there is a limit on price decreases (1 change every 10 minutes).
Why was my pool URL rejected?
The platform validates pool URLs before accepting bids. Common rejection reasons:
- Connection failed: Pool URL is incorrect or pool is offline
- Timeout: Pool did not respond in time
- Incompatible pool: extranonce2_size is less than 7
- Invalid worker name: Invalid usernames will be rejected for pools that correctly authorize them. Make sure the username is correct — some pools will consume the hashrate even for invalid usernames without warning.
Verify your pool URL format: stratum+tcp://hostname:port
For more details on pool compatibility, see Pool Compatibility. If your pool is valid but being rejected, contact Braiins support.
What bid statuses exist?
Bids can have the following statuses:
- Created: Bid was created and is waiting for activation
- Active: Bid is ready for matching; may or may not be receiving hashrate depending on market conditions
- Paused: Bid is paused and cannot receive hashrate (usually due to target pool error)
- Pending Cancel: Cancellation requested, waiting for delivery end and settlement
- Fulfilled: Budget fully consumed
- Canceled: Bid was canceled before completion
You can view current bids and bid history separately in the interface.
Why is my bid stuck in a Paused/Active loop?
If your bid keeps switching between Paused and Active status, the most common cause is that your target pool is providing too low mining difficulty.
Braiins Hashpower works optimally with a pool difficulty of 65,536 (65k). While lower difficulties may work, delivery is not guaranteed.
Why the loop happens: The system repeatedly attempts to deliver hashrate to your pool. When the pool provides difficulty below the minimum threshold, delivery fails and the bid is paused. The system then retries, switching the bid back to Active, only to encounter the same issue. In rare cases, delivery may succeed briefly if the pool temporarily assigns higher difficulty.
Solutions:
- Check if your pool allows configuring a minimum difficulty (often via worker name suffix, e.g.,
username.worker+65536) - Contact your pool operator to request higher difficulty for your worker
- If you're running your own pool, reconfigure it to provide higher difficulty (65k recommended)
- Try a different pool that supports higher difficulty settings
If the issue persists, contact Braiins support with your bid ID and pool details.
Do I pay for rejected hashrate?
Yes. The buyer takes responsibility for the quality and configuration of their target pool. If your pool rejects shares due to misconfiguration, stale work, or other issues, you still pay for the hashrate delivered.
There is typically an inherent rejection rate of approximately 0.05% even under optimal conditions, which is normal and expected.