OPTIONAL BLOCK REPORTING
Share the blocks you find
Already contributing work? Use your existing provider token to report individual block finds. Your work collector can keep running unchanged.
Reports appear on your approved public profile as operator-reported finds. We compare the hash and height with our collected XBT chain data. A match establishes chain inclusion, not who found the block. Reported finds do not change attributed block totals, scores or work-only outcomes.
Report a block
Use a block from your own mining records. You need an active provider token and a linked, approved profile with publication consent. New operator? Register here.
The token is used only for this request and is not saved by this page. Retrying the same report does not create another entry. Withdrawals remove it from the public list.
Connect your own block feed
When your software records a block find, save its real height and hash, then send one report. No public stats URL, worker identities, addresses or private mining configuration are needed.
POST https://xbtpulse.tech/api/block-reportsAuthorization: Bearer YOUR_EXISTING_PROVIDER_TOKENContent-Type: application/json
{
"height": YOUR_BLOCK_HEIGHT,
"hash": "YOUR_64_CHARACTER_BLOCK_HASH"
}The placeholders are deliberately invalid. Fill them from real mining records. A successful response means the report was stored; the profile shows the separate chain check as collection catches up.
Optional Python sender
Download the block-report sender and save each real event as a JSON file. It uses Python 3.9+ with no extra packages.
python3 xbtpulse-block-reporter.py block.json
python3 xbtpulse-block-reporter.py block.json --submit --token-file /path/to/token.txtThe first command checks locally. The second sends the saved report. Keep your JSON file until the sender confirms acceptance; on a temporary failure, retry that same file. A hook or scheduler can invoke this command for each event in your own queue.
Keep the token file private (chmod 600 /path/to/token.txt on Linux). The existing Prime token.txt can be used. This sender does not read DATUM logs or discover blocks for you.
Retries and corrections
The provider and block hash identify a report. Identical retries return HTTP 200; new reports return 201. Wait at least a minute after a network or server error. HTTP 429 requires a one-hour wait. Other errors need correction before retrying.
To retract an incorrect report, send its original height and hash with "action": "withdraw". You can then submit corrected details. An old retry cannot restore an unchanged withdrawn report; contact XBT Pulse if you withdrew it by mistake. Reports are retained for 90 days; up to 50 appear on the profile. Each provider can make 60 changes per hour.