Skip to content

JavaJAM Milestone 1 - #21

Open
jaymansfield wants to merge 6 commits into
w3f:mainfrom
javajamio:main
Open

JavaJAM Milestone 1#21
jaymansfield wants to merge 6 commits into
w3f:mainfrom
javajamio:main

Conversation

@jaymansfield

Copy link
Copy Markdown

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.

@github-actions

github-actions Bot commented Dec 17, 2025

Copy link
Copy Markdown

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

@jaymansfield

Copy link
Copy Markdown
Author

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

@jaymansfield

Copy link
Copy Markdown
Author

recheck

@CrackTheCode016 CrackTheCode016 self-assigned this Jan 9, 2026
@jaymansfield

Copy link
Copy Markdown
Author

@CrackTheCode016

Hello, a new JavaJAM build has been released resolving a bug that caused 1768865617, 1768843098, 1768931417, 1768918455 from https://github.com/w3f/jam-conformance/blob/javajam_m1/fuzz-reports/0.7.2/summaries/summary_javajam.txt.

@CrackTheCode016

Copy link
Copy Markdown

Hello @jaymansfield, thank you! I was going to write you today informing you of the results.

Thank you for the new release; we will get back to you with the results / new feedback soon. Thank you for your patience!

@jaymansfield

Copy link
Copy Markdown
Author

Just tagging the discussion for the traces 1768864701 and 1768945074 here for visibility.

davxy/jam-conformance#160

@jaymansfield

jaymansfield commented Feb 3, 2026

Copy link
Copy Markdown
Author

Hey @CrackTheCode016, any updates on this?

Thanks!

@CrackTheCode016

Copy link
Copy Markdown

Hello @jaymansfield, we should have results by EOW, we had to take some time formalizing some processes. The fuzzing will continue meanwhile :)

We will post the results once ready. Thank you so much for your patience, apologies for the wait.

@CrackTheCode016

Copy link
Copy Markdown

Hey @jaymansfield, just sharing that your target managed to complete 1 million steps successfully! 🎉

See here for the fuzzing results.

We'll reach out with the next steps soon, now that the technical aspect has been evaluated.

Thank you for your patience.

@jaymansfield

Copy link
Copy Markdown
Author

Thank you @CrackTheCode016 for the update!

@jaymansfield

Copy link
Copy Markdown
Author

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

@jaymansfield

Copy link
Copy Markdown
Author

recheck

@danicuki

Copy link
Copy Markdown

congrats @jaymansfield 🎉

@CrackTheCode016 CrackTheCode016 added the fellowship review This submission is in review by the Fellowship label Feb 13, 2026
@jaymansfield

Copy link
Copy Markdown
Author

As per the updated rule 26 the repository has been set back to private. Please let me know who should be invited to view it

@github-actions

Copy link
Copy Markdown

Thank you for your submission. Please note that you need to accept our latest Terms and Conditions before your submission can be considered for the JAM Prize. Please submit the following text as a separate comment:

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

@jaymansfield

Copy link
Copy Markdown
Author

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

@github-actions

Copy link
Copy Markdown

Thank you for your submission. Please note that you need to accept our latest Terms and Conditions before your submission can be considered for the JAM Prize. Please submit the following text as a separate comment:

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

@anaelleltd anaelleltd removed the fellowship review This submission is in review by the Fellowship label Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants