Skip to content

TSJAM M1 Delivery#19

Open
vekexasia wants to merge 3 commits into
w3f:mainfrom
vekexasia:main
Open

TSJAM M1 Delivery#19
vekexasia wants to merge 3 commits into
w3f:mainfrom
vekexasia:main

Conversation

@vekexasia

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 T&Cs.
Posted by the CLA Assistant Lite bot.

@vekexasia

Copy link
Copy Markdown
Author

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

@PieWol PieWol self-assigned this Jan 19, 2026
@PieWol

PieWol commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

Hey @vekexasia ,

I'm happy to let you know that your target managed to complete 1 million steps successfully! 🎉
See here for the fuzzing results.

I split it into ten consecutive runs, as the time to process worsens over time. Until 100k steps it seems to be running as fast as expected. To give you a better understanding, I have gathered the following logs from an instance that's fuzzing your target for a few days straight at this point.

2026-01-29 10:25:06 [s=486802]
2026-01-29 12:46:40 [s=492310]
2026-01-29 13:22:18 [s=493600]
2026-01-29 14:04:10 [s=495164]

This means by now your target is able to process only about 40 steps per minute. Are you aware of this? Any ideas why this is the case? Anyway for M1 conformance this decrease in performance shall not be an issue.

I'll follow up soon with more details on how we will proceed with your submission. Let me know if you have any other questions.

Best,
Piet

@vekexasia

Copy link
Copy Markdown
Author

Hello @PieWol Thanks for the great news. 🎉

I will be trying to figure it out why that performance degradation happens even if replicating that scenario is going to be a bit problematic considering my internal fuzzer is nowhere as complete as yours.

@boymaas

boymaas commented Jan 29, 2026

Copy link
Copy Markdown

Congratulations! 🚀

@emielsebastiaan

Copy link
Copy Markdown

🤩 congrats 🎉

@PieWol PieWol added fellowship review This submission is in review by the Fellowship changes requested Please resolve all open issues, comments and questions to proceed with the review and removed fellowship review This submission is in review by the Fellowship labels Feb 3, 2026
@PieWol

PieWol commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

Hey @vekexasia, the rules of the JAM Prize require your repository of the JAM client to be open source. See rule 26. Let me know if you have an questions.

@vekexasia

vekexasia commented Feb 3, 2026

Copy link
Copy Markdown
Author

Hey @PieWol Ofcourse. let me know if I should share to someone else. I just sent an invite in github for you to be acollaborator of the sourcecode.

Branch of 0.7.2 is v0.7.2-wip

Edit: I changed the visibility of the repo to public https://github.com/vekexasia/tsjam

@PieWol PieWol added fellowship review This submission is in review by the Fellowship and removed changes requested Please resolve all open issues, comments and questions to proceed with the review labels Feb 4, 2026
@PieWol

PieWol commented Feb 4, 2026

Copy link
Copy Markdown
Contributor

Hey @vekexasia , please include a Polkadot and Kusama address in the README of your repository. See rule 22. Thanks.

@vekexasia

Copy link
Copy Markdown
Author

Hey @PieWol done.

@vekexasia

Copy link
Copy Markdown
Author

As per the amended rule 26 i restored repository visibility to private. Please let me know the github handles to invite.

@PieWol PieWol removed their assignment Mar 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fellowship review This submission is in review by the Fellowship

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants