Dotnix: Milestone Delivery 2

[Ra33it0]

Milestone Delivery Checklist

• The milestone-delivery-template.md has been copied and updated.
• This pull request is being made by the same account as the accepted application.
• 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 AssetHub and/or fiat account provided in the application.
• The delivery is according to the Guidelines for Milestone Deliverables.

Link to the application pull request: w3f/Grants-Program#2259

[PieWol]

Hey @Ra33it0 ,

where is the testing guide and why is it not linked to?

[Ra33it0]

Hey our tests are implemented using Nix tests, to run all test you can call nix flake check --print-build-logs as mentioned in our README.
https://github.com/sporyon/dotnix-core/blob/main/README.md#testing
Let me know if you have further questions, I am here to help.

[PieWol]

Hey @Ra33it0 ,
I've published my evaluation but sadly I'm running into a few issues. Would love to hear your feedback on what might have went wrong. I assume the docker setup didn't work as expected, even though I was strictly following your tutorial. I noticed that the tarball was already existing after running nix build .#docker so I didn't download it again explicitly and instead initiated the docker instance with the existing tarball.

[PieWol]

Sadly while revisiting today and setting up a fresh docker image it didn't work out. I already texted you on element but just for transparency I'll post it here as well.

ubuntu@ip-172-31-20-198:~/dotnix/dotnix-core$ sudo nix build .#docker --extra-experimental-features nix-command --extra-experimental-features flakes
warning: creating lock file '/home/ubuntu/dotnix/dotnix-core/flake.lock'
warning: Git tree '/home/ubuntu/dotnix/dotnix-core' is dirty
trace: evaluation warning: system.stateVersion is not set, defaulting to 24.11. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersion.
[1 copied (148.7 MiB), 75.8 MiB DL]Segmentation fault

[Ra33it0]

The issue you are referencing is a segfrault and likely caused by a bug in nix, maybe a full disk or insufficient free memory or something completely different.
To free up space you can use $ nix-collect-garbage -d or $ docker rm -vf $(docker ps -aq); docker rmi -f $(docker images -aq)

Regarding list-dependencies, we have added it to the docker image and to allow it to working there, the code had to be rewritten slightly as the nix daemon within Docker doesn't support all necessary operations that the old implementation used. It can be tested like this: list-dependencies --all $(nix-build --no-out-link -A nano '<nixpkgs>') (hints for generating auditable paths have been added to the README)

[PieWol]

Congratulations on completing your grant. Your second and final milestone is now accepted! 🎉

[github-actions]

🪙 Please fill out the invoice form in order to initiate the payment process. Thank you!

[github-actions]

We noticed that this is the last milestone of your project. Congratulations on completing your grant! 🎊

So, where to from here? First of all, you should join our Grants Community chat, if you haven't already, so we can stay in touch.
If you are looking for continuative support for your project, there are quite a few options. The main goal of the W3F grants program is to support research as well as early-stage technical projects. If your project still falls under one of those categories, you might want to apply for a follow-up grant. However, depending on your goals and project status, there are other support programs in our ecosystem that might be better suited as the next step. For example, projects with a Business Case/Token should look into the Substrate Builders Program or VC Funding and Common Good projects have a good chance of receiving Treasury Funding. If you are looking for guidance, the team at https://substrate.io/ecosystem/square-one/ has compiled a list of ecosystem support sources and are happy to help you navigate it.

For a more comprehensive list, see our Alternative Funding page. Let us know if you have any questions regarding the above. We are more than happy to point you to additional resources and help you determine the best course of action.
Lastly, we hope your W3F grant was a success and we want to thank you for being part of the journey!

[RouvenP]

hi @Ra33it0 we just sent the DOTs.