## Presentation

Hello, I am Guillaume Thiolliere, worked at parity in 2019-2022 and from september 2024. I worked mainly on the runtime part, in FRAME and its pallets.

## Details

- Github: https://github.com/gui1117, formerly https://github.com/thiolliere
- Matrix: @guillaume:parity.io, formerly @gui:parity.io
- Polkadot address: 13psJuWEjBuZGaFqXvFnLMC6ME8RVVfQAhtFhydYjW45oKgZ
- Area(s) of Expertise/Interest:
  - polkadot business-logic (aka the 'runtime')
  - the internals of the frame pallet framework
  - runtime and host APIs

## Some past work: 2019-2022:
* Authored the FRAMEv2 pallet macro. Updating from `decl_module!` to `#[pallet]` macro.
* Designed instantiable pallet concept.
* Implemented the elision of pallet parts in `construct_runtime`.
* Iterable storage (without linked list)

## Recent work:
* FRAME: Fix tasks for instantiable pallets: https://github.com/paritytech/polkadot-sdk/pull/5194
* frame pallet: fix calculation when underestimating refund in storage weight reclaim: https://github.com/paritytech/polkadot-sdk/pull/5273
* various comments and contribution in the transaction extension PR: https://github.com/paritytech/polkadot-sdk/pull/3685
  * The PR was missing the pipeline for bare extrinsics, so weight wasn't checked nor registered for bare extrinsics
  * Subtle comments like `CheckNonce` prepare was overriding the whole storage item with value coming from validate, potentially erasing other change in the account storage.
  * The pipeline was made to allow multiple version of transaction extension but there was no plan to make the version part of any signed payload.
  * Currently implementing the next step of the transaction extension horizon: https://github.com/paritytech/polkadot-sdk/pull/6324
* improve the precision of benchmarks for system chains, potentially resulting in better resource usage of the system chains. https://github.com/polkadot-fellows/runtimes/pull/525
* Many PR review in polkadot-sdk.

## Presentation

I am Guillaume Thiolliere, worked at parity in 2019-2022 and from september 2024. I worked mainly on the runtime part, in FRAME and its pallets.

## Details

- Github: https://github.com/gui1117, formerly https://github.com/thiolliere
- Matrix: @guillaume:parity.io, formerly @gui:parity.io
- Polkadot address: 13psJuWEjBuZGaFqXvFnLMC6ME8RVVfQAhtFhydYjW45oKgZ
- Area(s) of Expertise/Interest:
  - polkadot business-logic (aka the 'runtime')
  - the internals of the frame pallet framework
  - runtime and host APIs

## Some past work: 2019-2022:
* Authored the FRAMEv2 pallet macro. Updating from `decl_module!` to `#[pallet]` macro.
* Designed instantiable pallet concept.
* Implemented the elision of pallet parts in `construct_runtime`.
* Iterable storage (without linked list)

## Recent work:
* FRAME: Fix tasks for instantiable pallets: https://github.com/paritytech/polkadot-sdk/pull/5194
* frame pallet: fix calculation when underestimating refund in storage weight reclaim: https://github.com/paritytech/polkadot-sdk/pull/5273
* various comments and contribution in the transaction extension PR: https://github.com/paritytech/polkadot-sdk/pull/3685
  * The PR was missing the pipeline for bare extrinsics, so weight wasn't checked nor registered for bare extrinsics
  * Subtle comments like `CheckNonce` prepare was overriding the whole storage item with value coming from validate, potentially erasing other change in the account storage.
  * The pipeline was made to allow multiple version of transaction extension but there was no plan to make the version part of any signed payload.
  * Currently implementing the next step of the transaction extension horizon: https://github.com/paritytech/polkadot-sdk/pull/6324
* improve the precision of benchmarks for system chains, potentially resulting in better resource usage of the system chains. https://github.com/polkadot-fellows/runtimes/pull/525
* Many PR review in polkadot-sdk.


Request to join the fellowship

- **Problem Statement:** Identifying Guillaume Thiolliere's expertise and contributions in the Polkadot ecosystem.
- **Significance:** Understanding the technical contributions and areas of expertise of Guillaume Thiolliere in Polkadot development.
- **Proposed Solution:** Highlighting Guillaume Thiolliere's past and recent work in the Polkadot ecosystem, including specific contributions and projects.
- **Expected Outcomes:** Increased awareness of Guillaume Thiolliere's valuable contributions to the Polkadot community and ecosystem.

#37 Request to join the fellowship