SpaceJam Milestone 1 delivery

[clearloop]

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.

Conformance

Once meeting conformance problems while reviewing the spacejam binary, feel free to discuss:

• in this PR
• at spacejamapp/specjam/issues
• ping me in matrix channels (if need to review the source code of our implementation)

[github-actions]

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

[clearloop]

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

[midegdugarova]

hi @clearloop, thank you for your submission. We will now start evaluating your submission.

[clearloop]

hi @midegdugarova , happy new year! May I ask if there is any updates from the review? seeing other teams under reviewing have their branches in the conformance fork and got updates recently

[midegdugarova]

hi @clearloop ! Please find the reports to the fuzzing session. Unfortunately your implementation currently fails to move beyond 2000 steps, at some point there is a state root mismatch.

https://github.com/midegdugarova/jam-conformance/tree/spacejam/fuzz-reports/0.7.2/reports/spacejam/1770234404
https://github.com/midegdugarova/jam-conformance/tree/spacejam/fuzz-reports/0.7.2/reports/spacejam/1770234623
https://github.com/midegdugarova/jam-conformance/tree/spacejam/fuzz-reports/0.7.2/reports/spacejam/1770234843

[clearloop]

hi @midegdugarova , thanks for the updates! just updated spacejam to 0.0.26, which resolved 1770234623, however I didn't manage to reproduce the problems in the other two reports, they work locally in my env, I did two patches for them incase they'll block our process:

1. on non-linux platform, fallback to interpreter (the panic could be caused by the compiler on macOS/windows)
2. capture the unexpected panics on the spacejam target and returns them as error message

[midegdugarova]

Hi @clearloop, thanks! I'll continue with the evaluation

[midegdugarova]

hi @clearloop the target keeps crashing. i run it on linux.
im sharing the logs here, looks like there is an out of range access error. https://github.com/midegdugarova/jam-conformance/blob/spacejam/scripts/sessions/1770387078/logs/fuzzer_spacejam.log

[clearloop]

hi @midegdugarova , thanks for the logs! I have identified that we have memory leak issues on processing large sequence of blocks! All problems are resolved in 0.0.27!

[midegdugarova]

hi @clearloop ! i fuzzed it again, this time the state root mismatch occured after the 560000 step. here is the report: https://github.com/midegdugarova/jam-conformance/blob/spacejam/fuzz-reports/0.7.2/reports/spacejam/1770628119/report.json

[clearloop]

hi @midegdugarova , thanks for the updates! I can confirm we have problem at 1770628119 and made a fix for it at 0.0.28! however, I can not reproduce the diff in the report, could you please introduce the logs like before in the branch next time we meet problems, that would be really helpful for my debugging!

[midegdugarova]

hi @clearloop ! thanks for the quick action. Some news to share:

We’ve updated the Terms & Conditions to better support the competition's progress and allow for milestone 1 payment prior to the Graypaper version 1.0 release, amongst other changes. 🎉

You can review the full announcement in this Polkadot Forum post. Please review the changes carefully.

To stay eligible for the prize: Please agree to accept the new terms by replying to the bot's comment below. We are excited to continue working together!

[midegdugarova]

recheck

[github-actions]

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.

[clearloop]

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

[clearloop]

recheck

[midegdugarova]

hi @clearloop ! Unfortunately, the implementation ran into State root mismatch error on after abou 860k steps. Please find the traces here.

and the report.

The log file for this run is way too large - i could provide you with logs on specific steps on request.

As per the T&C, the 2-week grace period starts now. You may now push fixes, and we will re-fuzz accordingly within this time period.

[clearloop]

hi @midegdugarova , I just made the fix at 0.0.29! also I have fixed the problem that we can not reproduce the diff in the reports, for the logs, I actually just need */target_spacejam.log for cases ^ ^

I currently have the following concerns about the submission:

1. we are currently at 860k step, if it means we just need to run the rest 140k steps to complete the fuzz?
2. for the 2-weeks period, I could not find references but the appeals, will the 2-weeks period get updates each time we update fixes or we have to complete the fuzz within it otherwise we will be re-queued?

[midegdugarova]

hi @clearloop thank you for fast response!

1. Okay, i will include the spacejam logs next time!

2. Each time we verify the traces with your patch as well as start the fuzzing from the beginning with a different seed. Right now I will start the process from the beginning and wait until it reaches 1000000 steps. Then your implementation will be considered valid. Good news is, your implementation is very fast, and will need less than a day to process a million steps.

3. Within the next 2 weeks you can make as many fixes as you can, and I will try to fuzz as soon as possible, but if after 2 weeks your implementation still hasn't passed, you will have to re-submit. (section 8.1.4. )

[clearloop]

Hi @midegdugarova , happy Chinese new year! any updates from the fuzz process? I'm ready to make another fix today > <

As the 14-days period triggers, hope we can make the progress more aggressive, from my side, I have already processed reports from all other teams' results to make sure that spacejam won't be blocked by duplicated bugs

[midegdugarova]

hi @clearloop !

Congratulations, I just shared the report that shows Spacejam passed one million steps!

I will now make sure your submission meets all other criteria for the fellowship review and mark it as such.

You will then hear from the fellowship.

[clearloop]

hi @midegdugarova ! really nice to hear this good news at Chinese New Years' Eve!

I just invited you to spacejamapp/spacejam for the pre-check, ready to invite teams from w3f & the fellowship!

[boymaas]

Congratulations @clearloop! 🎉

[emielsebastiaan]

Congrats 🍾🎉🎈

[0xjunha]

Congrats @clearloop !

[prasad-kumkar]

Congratulations @clearloop 🎊