Skip to content

Comments

JAM DUNA Milestone 1 Delivery#22

Open
sourabhniyogi wants to merge 5 commits intow3f:mainfrom
jam-duna:jamduna-m1
Open

JAM DUNA Milestone 1 Delivery#22
sourabhniyogi wants to merge 5 commits intow3f:mainfrom
jam-duna:jamduna-m1

Conversation

@sourabhniyogi
Copy link

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
Copy link

github-actions bot commented Dec 18, 2025

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

@sourabhniyogi
Copy link
Author

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

@sourabhniyogi sourabhniyogi marked this pull request as ready for review January 27, 2026 18:26
@sourabhniyogi sourabhniyogi changed the title Colorful Notion Milestone 1 Delivery: JAM DUNA JAM DUNA Milestone 1 Delivery Jan 27, 2026
@PieWol PieWol self-assigned this Feb 3, 2026
@PieWol
Copy link
Member

PieWol commented Feb 3, 2026

Hey @sourabhniyogi , thanks for your submission. I'm going to evaluate it.

The rules of the JAM Prize require your repository of the JAM client to be open source and public. See rule 26. Let me know if you have an questions.

@sourabhniyogi
Copy link
Author

sourabhniyogi commented Feb 5, 2026

Hey @sourabhniyogi , thanks for your submission. I'm going to evaluate it.

The rules of the JAM Prize require your repository of the JAM client to be open source and public. See rule 26. Let me know if you have an questions.

@PieWol Here you go:

https://github.com/jam-duna/jam

I had thought:

  • most teams would be (and are) closed source to support general "clean room" requirements
  • every team would happily invite w3f + fellowship evaluators (who are not part of a JAM team).
  • every team would go "full" open source in M4/M5 timeframe in full accordance with Rule 26

I believe this notion is worth aiming for, and that the "I just sent an invite..." pattern should be dominant. More than a few teams have M2/M3 type code (and more than few do not) I'm sure, and we should continue striving for max clean room compliance, which is best supported by the "I just sent an invite..." pattern, with most all teams continuing "closed source" for most of 2026.

Did this notion disappear?

@sourabhniyogi
Copy link
Author

sourabhniyogi commented Feb 17, 2026

Did this notion disappear?

@PieWol Thank you for adjusting Rule 26 to "The repository must include a clear and permissive open-source license. Members of W3F and the Technical Fellowship must be invited to the repository upon request." -- this will support clean room objectives well. We have invited to https://github.com/jam-duna/jamduna @PieWol and @CrackTheCode016 and @semuelle -- please let us know if there is anyone else needing an invite and what the sharing process is for the fellowship.

Update: We have updated our binary in 0.7.2.15 to address what we believe we have observed (11+ IO errors that we believe are memory issues + 1 real code issue)

@github-actions
Copy link

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.

@sourabhniyogi
Copy link
Author

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

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.

2 participants