All work

HackenBlockchain testing · QAN

I found 400+ spots where a blockchain engine gives different results.

01 · The problem

A blockchain engine must give the same answer on every run.

I had to find every place where it might not.

02 · What I built

Agents guess where it might give a different answer on a re-run.

  • Then they write and run many tests for each guess.
  • A test runs the same program again and again.
  • A run that differs is confirmed and reported.

03 · How it looks

One guess, checked run by run.

Guess 17: items read in a different order

The same program, run four times.

Result fingerprint

Run 18f3a…c21

Run 28f3a…c21Same

Run 341c9…7e0Differs

Run 48f3a…c21Same

Run 3 gives a different answer.Confirmed and reported.

Example values.

04 · The result

400+ spots found and confirmed.

Hacken open-sourced it.

Check it yourself

See it on GitHub

Next story

ResearchTechVC matchmaking

Startups stop pitching investors who were never a fit.

Before
Startups pitched investors who were never a fit.
I built
I built a pipeline that researches every VC fund.
Result
5,000 VC funds, ranked for each startup, every time.
Read the story: VC matchmaking

Bring one research question.