Bellpair · interactive lab

Inside a Bellpair receipt.

Choose a base. Inspect the two contributions.
Follow the receipt through verification.

Archived C / GMP run
0 of 2 contributions revealed
First contribution
0F
+29centered weight
Prime ending in 0F

Waiting for work

Matching contribution
F1
−29centered weight
Prime ending in F1

Waiting for work

Balance—
Both halves required

The table assigns matching weights before the search.
The work is to find qualifying primes with those endings.

Reveal the pair to inspect
Attempts · recorded
—
Search time
—
Prime tests
—
Workers
—
Recorded verifier result

The independent verifier accepted this receipt. This archived challenge is not issued by your local session.

The verification checks
  1. The issued challenge, number base, message hash, difficulty, expiry and assigned roles.
  2. Both SHA-256 hashes, recomputed from the nonces and canonical message.
  3. The derived prime candidates, primality, endings in the chosen base and table balance.
  4. At redemption: a known, unexpired and unused challenge.

The collision periodic table

Different endings.
Exact counterparts.

Every eligible ending has a reflected partner. The raw fingerprints add to −1. Centering and doubling gives opposite integers.

Base 16 has 64 reflected pairs. The highlighted entries are the roles assigned to this challenge.

Read the protocol
128 eligible endings · base 16Ending · centered weight

The challenge’s selected pair is highlighted.

0F → +29 / F1 → −29

Ten bases · 1,920 native trials

Base choice changes the work.

More eligible endings spread the prime search across more roles. At the same hash threshold, a prescribed pair usually takes more work to find.

Four leading zero hash bits in every base. All rows require two primes.
BasePairsMean attemptsMean search
211,4882.1 ms
334,2235.8 ms
446,2378.5 ms
51015,96719.2 ms
669,59011.3 ms
81624,31128.0 ms
102029,58534.4 ms
122430,89235.7 ms
1664102,956118.0 ms
30120167,341191.1 ms

96 receipts per base per policy · one worker · C/GMP · Intel Core i9-13900H. These experiments use a separate audit hash domain and adjustable thresholds. They establish a cost tradeoff; they do not establish a fastest base or a security advantage. All trials and metadata

Base 10 · retained measurements

The cost of each added constraint.

The same hash difficulty, with one filter added at a time. These are measured costs, not a matched-cost security comparison.

Required workMean attemptsMean time / pair
Hash difficulty only6511.155 ms
Hash + selected endings59,98778.630 ms
Hash + endings + two primes956,5181269.027 ms

12 pairs per method · 6, 8 and 10 hash bits · one worker · mean repeated arithmetic verification 0.031 ms. Timings exclude process and server startup. Complete data

The reference implementation uses C, GMP and OpenMP. Inspect the recorded walkthrough here, or download the MIT-licensed code to run your own searches, check receipts and change the implementation locally.