| Report Date | Date of submission (2024/07/02) |
| Submitted by | clangenb |
@clang:matrix.org16YCL3UVpVWQLGW3p3Zx4k5WAEp9W1DwdDnxAbyAaPxVxnp312024/03/27NAParachain Builder, Runtime, Clients| Areas of Contribution | Tasks | Links | Notes |
|---|---|---|---|
| Polkadot SDK | Case Study: Split polkadot parachains service file into multiple modules | SDK #4369 | |
| Fellows/runtimes | Encointer Pallets: Polkadot SDK Updates v1.10.0/v1.12.0/v1.13.0 | Encointer Pallets #387, #395, #398 | |
| Fellows/runtimes | Encointer System Chain: Upgrade to v1.13.0 | Runtimes #351 | |
| Fellows/runtimes | Encointer Pallets: Improve code-quality and documentation | Encointer Pallets #389 |
I am partially employed by Integritee, Encointer and Ajuna. I did not receive salary by them for the evidences that I stated above unless I state that explicitly. However, my polkadot/substrate expertise is also growing by implementing tasks paid by ecosystem projects. Good examples are:
Threshold
Hi Kian!
Just to be sure, do you also mean the PRs on the runtime repository for encointer? Here, I would disagree, as long as encointer is a system chain.
I totally agree that all things that are not in evidences are not part of the core-fellowship per see, but I do think that other ecosystem efforts should be at least kept in mind to give the reader a better understanding of what my work consisted, and how I am otherwise active in the blockchain world. Or do you think this is misplaced, and the curious reader should just dive into my GitHub account?
Your work on #4369 was a valuable experiment! for the record though, the rest of the contributions are in my opinion outside the scope of the core fellowship.