Member Request

[athei]

I am Alexander Theißen and joined Substrate development in early 2020. My contributions are mainly around pallet-contracts. I took it from a proof and concept, made substantial design changes, added a benchmark suite and got it into a production ready state. It is now deployed on Shiden and more networks are ready to deploy once the code saw a 3rd party audit. I also ventured deeper into the stack to create infrastructure needed for pallet-contracts. Currently, I am the maintainer for the pallet-contracts and wasm-instrument crates.

Working on Substrate is my main occupation and I am available to fix issues quickly in parts of the code base I am responsible for. I gave a lecture on pallet-contracts during the first wave of the Polkadot Academy in Cambridge. I will be contributing to the second wave, too. Additionally I am active on the Substrate stack exchange where I am in the top 10 users when sorted by karma.

Earliest non trival contribution

• Allow to distinguish out of gas from other traps paritytech/substrate#4883 Not a massive PR but non trivial in my book.

Most notable contribution

• Implement nested storage transactions paritytech/substrate#6269 Massively simplifies runtime development and is now the default in FRAME.

More notable contributions

• Introduce weight refund paritytech/substrate#5584
• Integrate pallet_contracts gas with the weight system paritytech/substrate#5712
• Allow fee calculation to happen off-chain paritytech/substrate#6076
• seal: Rework contracts API paritytech/substrate#6573
• seal: Add automated weights for contract API calls paritytech/substrate#7017
• contracts: Add automated weights for wasm instructions paritytech/substrate#7361
• contracts: Allow runtime authors to define a chain extension paritytech/substrate#7548
• contracts: Lazy storage removal paritytech/substrate#7740
• contracts: Remove state rent paritytech/substrate#9669
• contracts: Add storage deposits paritytech/substrate#10082
• Add production profile to substrate-wasm-builder paritytech/substrate#10747
• Add dev_getBlockStats RPC paritytech/substrate#10939
• contracts: Prevent PoV attack vector with minimal viable solution paritytech/substrate#11372
• contracts: Composable ChainExtension paritytech/substrate#11816
• Make automatic storage deposits resistant against changing deposit prices paritytech/substrate#12083

I would like to apply for Rank 4 (Architect).

[rphmeier]

I support @athei for IV Dan in effect but the time requirements may limit to III Dan

[gavofyork]

I think we need to be fairly strict on time requirements since it's about the only thing which we can measure non-controversially. In time terms IV Dan would still be a few months off at the earliest.

In terms of contributions, I think III Dan is largely defensible, though I'd note that there's only one PR which would be considered "substantial" according to the Manifesto (a 2,000-10,000 line crate), and much of it is not logic. I'd also point to Manifesto section 6.4.1: There's the "played a primary role in implementing a major component from start to finish" point. Furthermore, we are apparently missing missing the three long-form semi-technical articles on Polkadot.

[athei]

I support @athei for IV Dan in effect but the time requirements may limit to III Dan

In time terms IV Dan would still be a few months off at the earliest.

Fair enough. Changed to 3.

In terms of contributions, I think III Dan is largely defensible, though I'd note that there's only one PR which would be considered "substantial" according to the Manifesto (a 2,000-10,000 line crate), and much of it is not logic. I'd also point to Manifesto section 6.4.1: There's the "played a primary role in implementing a major component from start to finish" point.

There is not much left of the original pallet-contracts code. It was transformed in many small PRs rather than a few large ones. I'd argue that this should satisfy "played a primary role in implementing a major component from start to finish".

Furthermore, we are apparently missing missing the three long-form semi-technical articles on Polkadot.

This is correct. Can my contributions on the stack exchange make up for it?: https://substrate.stackexchange.com/users?tab=Reputation&filter=all