PyJAMaz M1 Delivery by JAMdot Technologies by emielsebastiaan · Pull Request #20 · w3f/jam-milestone-delivery

emielsebastiaan · 2025-12-17T15:58:48Z

This document outlines the Milestone 1 delivery for PyJAMaz, detailing the team, deliverables, and development timeline for the JAM protocol implementation.

Milestone Delivery Checklist

The milestone-delivery-template.md has been copied and updated.
I have disclosed any and all sources of reused code in the submitted repositories and have done my due diligence to meet its license requirements.
In case of acceptance, invoices must be submitted and payments will be transferred to the Polkadot account provided in the invoice.
The delivery is according to the rules of the JAM Prize.

This document outlines the Milestone 1 delivery for PyJAMaz, detailing the team, deliverables, and development timeline for the JAM protocol implementation.

github-actions · 2025-12-17T15:59:02Z

T&C Assistant Lite bot All Contributors have signed the latest T&Cs.
_{Posted by the CLA Assistant Lite bot.}

emielsebastiaan · 2025-12-17T16:00:17Z

I have read and hereby sign the JAM Prize Terms and Conditions.

emielsebastiaan · 2025-12-17T16:04:22Z

recheck

Bump PyJAMaz to v0.1.44-gp0.7.2

Update docker tag to `v0.1.45-gp0.7.2`

emielsebastiaan · 2026-02-02T16:42:46Z

Hello @CrackTheCode016 ,
We spotted some preliminary results of the W3F-led audit (unfinished) eval of PyJAMaz here: https://github.com/w3f/jam-conformance/tree/pyjamaz_m1/fuzz-reports/0.7.2

Thank you for this preliminary feedback. We have pushed a new Docker image with tag v0.1.45-gp0.7.2 (or latest) for your further evaluation which fixes one identified issue related to gas accounting. This fix allows the following reports to match the desired post-state: 1769559762_3064, 1769559762_3187, 1769559762_3607, 1769559762_6159 and 1769559762_6633.

Report 1769559762_4234 however seems to have done something unexpected on the side of the fuzzer. This has been discussed in a discussion and our assessment is the same: davxy/jam-conformance#164

We look forward to the audit results. Thank you for your attention.

CrackTheCode016 · 2026-02-04T12:49:32Z

Hey @emielsebastiaan, thank you for posting those, they also surprised me a little. I hope to share updated/finished results by EOW. Thank you for your patience and vigilance throughout this process!

CrackTheCode016 · 2026-02-06T04:02:39Z

Hello @emielsebastiaan, I hope you and the team are well.

I have just pushed the updated results to the directory. Unfortunately, it did not pass 1 million blocks; there seems to be a consistent error preventing some runs. The traces are present in most implementations (as you can see in the summaries).

You may also see a summary of the runs below:

TRACE ID                  | IMPORTED   | SOURCE             | STATUS/ERROR
-------------------------------------------------------------------------------------
1770149026                | 1,103      | Report             | {'communication': 'IO error...
1770149261                | 97,951     | Report             | ✅ Success
1770172732                | 26,437     | Report             | {'communication': 'IO error...
1770178141                | 98,206     | Report             | ✅ Success
1770201469                | 98,081     | Report             | ✅ Success
1770225241                | 71,259     | Report             | {'communication': 'IO error...
1770241019                | 97,978     | Report             | ✅ Success
1770264632                | 63,451     | Report             | {'communication': 'IO error...
1770278983                | 98,224     | Report             | ✅ Success
1770301662                | 97,864     | Report             | ✅ Success
-------------------------------------------------------------------------------------

📊 --- FINAL SUMMARY ---
Total Runs Analyzed:   10
Total Blocks Imported: 750,554 / 1,000,000
Progress:              75.06%
------------------------------
Average per Run:       75,055.40
Min Blocks (Worst):    1,103
Max Blocks (Best):     98,224
------------------------------
⚠️  FAILED: Missing 249,446 blocks to reach goal.

emielsebastiaan · 2026-02-06T10:52:32Z

Hello @CrackTheCode016 ,
Thank you for the audit results.
It seems we are almost there (emphasis on almost).
We found a single 'unhandled exception' in our logging system that explains the fuzzer-target crash.

We have pushed a new Docker image with tag v0.1.46-gp0.7.2 (or latest) for your further evaluation.
We look forward to your (hopefully) final evaluation.

Thank you again.
Emiel

CrackTheCode016 · 2026-02-10T14:23:01Z

Hey @emielsebastiaan, looks like that did the trick - PyJAMaz passed the 1 mil benchmark, congrats! 🎉 You may find the results on the same fork/branch.

We'll reach out with next steps soon, thank you for your patience and prompt fixes!

emielsebastiaan · 2026-02-10T14:57:40Z

Thank you @CrackTheCode016 this really made our day (week, month, year and past 20 months).

emielsebastiaan · 2026-02-10T16:05:29Z

recheck

emielsebastiaan · 2026-02-10T16:09:28Z

I have read and hereby sign the latest JAM Prize Terms and Conditions.

emielsebastiaan · 2026-02-10T16:13:28Z

recheck

danicuki · 2026-02-11T18:51:09Z

Congrats @emielsebastiaan and PyJAMaz team for this incredible accomplishment

boymaas · 2026-02-16T19:17:19Z

Better late than never! Congrats to @emielsebastiaan and the whole PyJAMaz team—M1 is really "de kers op de taart" (the cherry on the cake, old Dutch saying) for the hard work!

prasad-kumkar · 2026-02-17T09:49:56Z

Congrats @emielsebastiaan 🚀

emielsebastiaan · 2026-02-18T15:02:14Z

Hello @CrackTheCode016 @PieWol ,
I have granted access to the repository (https://github.com/JAMdotTech/pyjamaz) for your further evaluation.
Let me know if we need to grant access to others.

Update Docker Hub tag for v0.7.2 M1 Fuzzer Target

github-actions · 2026-03-19T15:49:18Z