From a6631635520aa10d89876bb7757042d4fbdfd8b4 Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Thu, 28 Nov 2024 12:11:31 +0200 Subject: [PATCH 1/7] add evidence #3 Signed-off-by: Andrei Sandu --- .../sandreim/0003-sandreim-evidence-2024.md | 93 +++++++++++++++++++ 1 file changed, 93 insertions(+) create mode 100644 evidence/sandreim/0003-sandreim-evidence-2024.md diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md new file mode 100644 index 0000000..5ff475c --- /dev/null +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -0,0 +1,93 @@ +# Evidence-0003: Promotion to Rank III + +| | | +| --------------- | ------------------------------------------------------------------------------------------- | +| **Report Date** | 2024/11/26 | +| **Submitted by**| Andrei Sandu | + +## Member details + +- Matrix username: @sandreim:parity.io +- Polkadot address: 13QdJvnJgfoitjrxESwrCWTaLMN8KvXxufDUucXM6EWGuxqh +- Current rank: 2 +- Date of initial induction: 2023/07/18 +- Date of last report: N/A +- Area(s) of Expertise/Interest: Parachain Consensus, Elastic Scaling, Node performance engineering, observability and resilience, Stress and integration testing + +## Reporting period + +- Start date: 2023/07/18 +- End date: 2024/11/26 + +## Evidence + +During the reporting period I have played an important role in the design, development and deployment of a few major contributions to Polkadot which had signficant impact: + +- better decentralization and security by increasing parachain validators from 200 to 500 +- more blockspace by increasing the number of usable cores to 100 +- lowering the latency and increasing maximum throughput of parachains with Elastic Scaling +- faster and lower cost parachain consensus protocol performance engineering with Subsystem Benchmarks + +I've been an active paritcipant in OpenDev calls and in the [Polkadot forum](https://forum.polkadot.network/u/sandreim/activity), constantly giving updates on the progress of the implementation, testing and deployment. + +I consider that this evidence, detailed in next section, is aligned both in quality and quantity with the Fellowship for a rank 3 promotion. + +### Increasing number of validators and cores + +This is a multi year project which is still on going. I have started this project by searching for bottlnecks +in the node protocols implementation, network stack and runtime. At the time Polkadot had 200 validators +and 40 cores. I lead the [project planning](https://github.com/paritytech/roadmap/issues/26), +development, testing and deployment of protocol changes to scale up to 500 validators and 100. + +Major design and code contributions: + +- **Assignment certificates v2**: Introduces a new kind of assignment certificate that batches multiple tranche0 in a single certificate/message: https://github.com/paritytech/polkadot-sdk/pull/1178 + +- **Approval voting re-design**: + [new design](https://github.com/paritytech/polkadot-sdk/issues/1617) that would allow the + approval voting subsystems to process messages in parallel. This design was further + refined and has been fully implemented and proven by benchmark tests that approval voting is no + longer a bottleneck at a scale of 1000 validators and 200 cores. + +I've communicated with the ecosystem about scaling up plans in forum posts and Element chats: +[Kusama](https://forum.polkadot.network/t/update-parachain-validator-set-size-increase-on-kusama/8218), +[Polkadot](https://forum.polkadot.network/t/update-polkadot-validator-set-size-increase/8682) + +### Parachain consensus performance benchmarks + +I designed and implemented multiple modular components that are used to emulate the network +traffic and load found in large scale networks on local development machine. It performs stress +test of one ore more parachain consensus subsystems without the need to run the network of that +size. It collects granular CPU usage and network metrics and is an integral part of ongoing +scalability and performance optimization development and CI performance regression testing. + +**Availability read benchmarks PR** https://github.com/paritytech/polkadot-sdk/pull/2528 +**Availability write benchmarks PR** https://github.com/paritytech/polkadot-sdk/pull/2970 + +### Elastic scaling (MVP) + +I played a major role in the design, development and testing of the first iteration(MVP) of +Elastic Scaling which is was deployed to Kusama and currently allows parachains to +use up to 3 cores per relay chain block. I had several signficant contributions to bootstrap +the node side and runtime implementation: + +- [Introduce an assumed core index](https://github.com/paritytech/polkadot-sdk/pull/3229) +- [Runtime changes for backing multiple candidates ](https://github.com/paritytech/polkadot-sdk/pull/3231) +- [Benchbuilder improvements for elastic scaling](https://github.com/paritytech/polkadot-sdk/pull/3573) +- [Collator protocol support](https://github.com/paritytech/polkadot-sdk/pull/3795) +- [Statement distribution support](https://github.com/paritytech/polkadot-sdk/pull/3879) + +### Elastic scaling (RFC103) + +Initial design work: [Github](https://github.com/polkadot-fellows/RFCs/issues/92) + +Authored [RFC 103](https://github.com/polkadot-fellows/RFCs/blob/main/text/0103-introduce-core-index-commitment.md) and lead it's [planning](https://github.com/orgs/paritytech/projects/119/views/25) and development. + +Significant code contributions in both runtime and node side: + +- [Introduce the new Polkadot primitives](https://github.com/paritytech/polkadot-sdk/issues/5044) +- [Node feature sanity checks](https://github.com/paritytech/polkadot-sdk/pull/5362) +- [Full Runtime implementation](https://github.com/paritytech/polkadot-sdk/pull/5423) +- [Bootstrap node implementation](https://github.com/paritytech/polkadot-sdk/pull/5679). +- [Candidate Validation](https://github.com/paritytech/polkadot-sdk/pull/5847) +- [Statement Distribution](https://github.com/paritytech/polkadot-sdk/pull/5883) From e55cc018bee4bfd5930b5381824ce995466e85a6 Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Thu, 28 Nov 2024 14:47:34 +0200 Subject: [PATCH 2/7] voting rec Signed-off-by: Andrei Sandu --- evidence/sandreim/0003-sandreim-evidence-2024.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md index 5ff475c..7e38d87 100644 --- a/evidence/sandreim/0003-sandreim-evidence-2024.md +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -91,3 +91,14 @@ Significant code contributions in both runtime and node side: - [Bootstrap node implementation](https://github.com/paritytech/polkadot-sdk/pull/5679). - [Candidate Validation](https://github.com/paritytech/polkadot-sdk/pull/5847) - [Statement Distribution](https://github.com/paritytech/polkadot-sdk/pull/5883) + +## Voting record + +| Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments | +|---|---|---|---|---| +|I |90% |N/A | | | +|II |80% |N/A | I have voted on 4 out of 21 referenda in which I was eligible to vote (19% voting activity) | I target to raise it to 80% at least for the next reporting period | +|III|70% |100% | | | +|IV |60% |90% | | | +|V |50% |80% | | | +|VI |40% |70% | | | From 300f830df5d91b226c5169abb78cc0b9833af995 Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Thu, 28 Nov 2024 14:50:14 +0200 Subject: [PATCH 3/7] spellcheck Signed-off-by: Andrei Sandu --- .../sandreim/0003-sandreim-evidence-2024.md | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md index 7e38d87..e7d5f2d 100644 --- a/evidence/sandreim/0003-sandreim-evidence-2024.md +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -1,9 +1,9 @@ # Evidence-0003: Promotion to Rank III -| | | -| --------------- | ------------------------------------------------------------------------------------------- | -| **Report Date** | 2024/11/26 | -| **Submitted by**| Andrei Sandu | +| | | +| --------------- | ------------------------------------------------------------------------------------------ | +| **Report Date** | 2024/11/26 | +| **Submitted by**| Andrei Sandu | ## Member details @@ -12,7 +12,7 @@ - Current rank: 2 - Date of initial induction: 2023/07/18 - Date of last report: N/A -- Area(s) of Expertise/Interest: Parachain Consensus, Elastic Scaling, Node performance engineering, observability and resilience, Stress and integration testing +- Area(s) of Expertise/Interest: Parachain Consensus, Node Performance Engineering, Observability, Stress and integration testing ## Reporting period @@ -21,33 +21,33 @@ ## Evidence -During the reporting period I have played an important role in the design, development and deployment of a few major contributions to Polkadot which had signficant impact: +During the reporting period I have played an important role in the design, development and deployment of a few major contributions to Polkadot that had significant impact: - better decentralization and security by increasing parachain validators from 200 to 500 - more blockspace by increasing the number of usable cores to 100 - lowering the latency and increasing maximum throughput of parachains with Elastic Scaling - faster and lower cost parachain consensus protocol performance engineering with Subsystem Benchmarks -I've been an active paritcipant in OpenDev calls and in the [Polkadot forum](https://forum.polkadot.network/u/sandreim/activity), constantly giving updates on the progress of the implementation, testing and deployment. +I've been an active participant in OpenDev calls and in the [Polkadot forum](https://forum.polkadot.network/u/sandreim/activity), constantly giving updates on the progress of the implementation, testing, and deployment. -I consider that this evidence, detailed in next section, is aligned both in quality and quantity with the Fellowship for a rank 3 promotion. +I consider that this evidence, detailed in the next section, is aligned both in quality and quantity with the Fellowship for a rank 3 promotion. ### Increasing number of validators and cores -This is a multi year project which is still on going. I have started this project by searching for bottlnecks -in the node protocols implementation, network stack and runtime. At the time Polkadot had 200 validators +This is a multiyear project that is still on going. I have started this project by searching for bottlenecks. +in the node protocols implementation, network stack and runtime. At the time Polkadot had 200 validators. and 40 cores. I lead the [project planning](https://github.com/paritytech/roadmap/issues/26), -development, testing and deployment of protocol changes to scale up to 500 validators and 100. +development, testing, and deployment of protocol changes to scale up to 500 validators and 100. Major design and code contributions: - **Assignment certificates v2**: Introduces a new kind of assignment certificate that batches multiple tranche0 in a single certificate/message: https://github.com/paritytech/polkadot-sdk/pull/1178 - **Approval voting re-design**: - [new design](https://github.com/paritytech/polkadot-sdk/issues/1617) that would allow the - approval voting subsystems to process messages in parallel. This design was further - refined and has been fully implemented and proven by benchmark tests that approval voting is no - longer a bottleneck at a scale of 1000 validators and 200 cores. +[new design](https://github.com/paritytech/polkadot-sdk/issues/1617) that would allow the +approval voting subsystems to process messages in parallel. This design was further +refined and has been fully implemented and proven by benchmark tests that approval voting is no +longer a bottleneck at a scale of 1000 validators and 200 cores. I've communicated with the ecosystem about scaling up plans in forum posts and Element chats: [Kusama](https://forum.polkadot.network/t/update-parachain-validator-set-size-increase-on-kusama/8218), @@ -56,8 +56,8 @@ I've communicated with the ecosystem about scaling up plans in forum posts and E ### Parachain consensus performance benchmarks I designed and implemented multiple modular components that are used to emulate the network -traffic and load found in large scale networks on local development machine. It performs stress -test of one ore more parachain consensus subsystems without the need to run the network of that +traffic and load found in large-scale networks on local development machines. It performs stress +test of one or more parachain consensus subsystems without the need to run the network of that size. It collects granular CPU usage and network metrics and is an integral part of ongoing scalability and performance optimization development and CI performance regression testing. @@ -66,9 +66,9 @@ scalability and performance optimization development and CI performance regressi ### Elastic scaling (MVP) -I played a major role in the design, development and testing of the first iteration(MVP) of -Elastic Scaling which is was deployed to Kusama and currently allows parachains to -use up to 3 cores per relay chain block. I had several signficant contributions to bootstrap +I played a major role in the design, development, and testing of the first iteration (MVP) of +Elastic Scaling, which was deployed to Kusama and currently allows parachains to +use up to 3 cores per relay chain block. I had several significant contributions to bootstrap the node side and runtime implementation: - [Introduce an assumed core index](https://github.com/paritytech/polkadot-sdk/pull/3229) @@ -81,7 +81,7 @@ the node side and runtime implementation: Initial design work: [Github](https://github.com/polkadot-fellows/RFCs/issues/92) -Authored [RFC 103](https://github.com/polkadot-fellows/RFCs/blob/main/text/0103-introduce-core-index-commitment.md) and lead it's [planning](https://github.com/orgs/paritytech/projects/119/views/25) and development. +Authored [RFC 103](https://github.com/polkadot-fellows/RFCs/blob/main/text/0103-introduce-core-index-commitment.md) and led it's [planning](https://github.com/orgs/paritytech/projects/119/views/25) and development. Significant code contributions in both runtime and node side: From c6e4cc0be23219d5752e1948a38c9f5f06a27ccb Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Fri, 29 Nov 2024 12:46:19 +0200 Subject: [PATCH 4/7] update Signed-off-by: Andrei Sandu --- .../sandreim/0003-sandreim-evidence-2024.md | 55 ++++++++++++------- 1 file changed, 35 insertions(+), 20 deletions(-) diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md index e7d5f2d..06c2dbb 100644 --- a/evidence/sandreim/0003-sandreim-evidence-2024.md +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -2,7 +2,7 @@ | | | | --------------- | ------------------------------------------------------------------------------------------ | -| **Report Date** | 2024/11/26 | +| **Report Date** | 2024/11/29 | | **Submitted by**| Andrei Sandu | ## Member details @@ -17,37 +17,44 @@ ## Reporting period - Start date: 2023/07/18 -- End date: 2024/11/26 +- End date: 2024/11/29 ## Evidence -During the reporting period I have played an important role in the design, development and deployment of a few major contributions to Polkadot that had significant impact: +During the reporting period I have played an important role in the design, development and deployment of a few major changes to Polkadot that had significant impact: - better decentralization and security by increasing parachain validators from 200 to 500 - more blockspace by increasing the number of usable cores to 100 - lowering the latency and increasing maximum throughput of parachains with Elastic Scaling - faster and lower cost parachain consensus protocol performance engineering with Subsystem Benchmarks -I've been an active participant in OpenDev calls and in the [Polkadot forum](https://forum.polkadot.network/u/sandreim/activity), constantly giving updates on the progress of the implementation, testing, and deployment. +I've been an active participant in OpenDev calls and in the +[Polkadot forum](https://forum.polkadot.network/u/sandreim/activity), consistently giving updates +on the progress of the implementation, testing, and deployment of Elastic Scaling. I consider that this evidence, detailed in the next section, is aligned both in quality and quantity with the Fellowship for a rank 3 promotion. ### Increasing number of validators and cores -This is a multiyear project that is still on going. I have started this project by searching for bottlenecks. -in the node protocols implementation, network stack and runtime. At the time Polkadot had 200 validators. -and 40 cores. I lead the [project planning](https://github.com/paritytech/roadmap/issues/26), -development, testing, and deployment of protocol changes to scale up to 500 validators and 100. +I have started working on this project before being inducted in the fellowship. +That work consisted of load testing, benchmarking and research to find parachain consensus +protocol and implementation bottlenecks on the node and runtime implementation. At the time +Polkadot had 200 validators and 40 cores. I created the +[scalability roadmap](https://github.com/paritytech/roadmap/issues/26) which includes +multiple changes and ideas I contributed as improvements in major parachain consensus protocols: +availability, approval voting and the overall node side subsystem architecture. Major design and code contributions: -- **Assignment certificates v2**: Introduces a new kind of assignment certificate that batches multiple tranche0 in a single certificate/message: https://github.com/paritytech/polkadot-sdk/pull/1178 +- **[Assignment certificates v2](https://github.com/paritytech/polkadot-sdk/pull/1178)**: +This is an enhancement of the approval voting protocol aimed at reducing the usage +of netwoprk/CPU resources by a factor of up to 6 in perfect network conditions. -- **Approval voting re-design**: -[new design](https://github.com/paritytech/polkadot-sdk/issues/1617) that would allow the -approval voting subsystems to process messages in parallel. This design was further -refined and has been fully implemented and proven by benchmark tests that approval voting is no -longer a bottleneck at a scale of 1000 validators and 200 cores. +- **[Approval voting subsystem re-write](https://github.com/paritytech/polkadot-sdk/issues/1617)**: +Proposal of a simpler and scalable subsystem architecture. The two existing approval voting +subsytems are merged into a single one. The new subsystem introduces message processing parallelism +to make use of more CPU resources in order to handle the load at a scale of 1000 validators and +500 cores. I've communicated with the ecosystem about scaling up plans in forum posts and Element chats: [Kusama](https://forum.polkadot.network/t/update-parachain-validator-set-size-increase-on-kusama/8218), @@ -55,14 +62,20 @@ I've communicated with the ecosystem about scaling up plans in forum posts and E ### Parachain consensus performance benchmarks -I designed and implemented multiple modular components that are used to emulate the network +My main motivation to build this was to replace the old ways of doing load testing by +running very large networks. It was expensive, slow and produced huge amounts of data +that was very hard to analyze and reason about. The output of my work is a +[new tool](https://github.com/paritytech/polkadot-sdk/tree/master/polkadot/node/subsystem-bench) +which is required for continous improvement of the scalability and resilience of the parachain +consensus protocols and Polkadot. + +I designed and implemented [multiple modular components](https://github.com/paritytech/polkadot-sdk/tree/master/polkadot/node/subsystem-bench#reusable-test-components) that are used to emulate the network traffic and load found in large-scale networks on local development machines. It performs stress -test of one or more parachain consensus subsystems without the need to run the network of that +tests of one or more parachain consensus subsystems without the need to run the network of that size. It collects granular CPU usage and network metrics and is an integral part of ongoing scalability and performance optimization development and CI performance regression testing. -**Availability read benchmarks PR** https://github.com/paritytech/polkadot-sdk/pull/2528 -**Availability write benchmarks PR** https://github.com/paritytech/polkadot-sdk/pull/2970 +**Subsytem benchmarks PRs**: [1](https://github.com/paritytech/polkadot-sdk/pull/2528), [2](https://github.com/paritytech/polkadot-sdk/pull/2970) ### Elastic scaling (MVP) @@ -79,9 +92,11 @@ the node side and runtime implementation: ### Elastic scaling (RFC103) -Initial design work: [Github](https://github.com/polkadot-fellows/RFCs/issues/92) +Played a primary role in initial design work: [Github](https://github.com/polkadot-fellows/RFCs/issues/92) -Authored [RFC 103](https://github.com/polkadot-fellows/RFCs/blob/main/text/0103-introduce-core-index-commitment.md) and led it's [planning](https://github.com/orgs/paritytech/projects/119/views/25) and development. +Authored [RFC 103](https://github.com/polkadot-fellows/RFCs/blob/main/text/0103-introduce-core-index-commitment.md) +and led the [planning](https://github.com/orgs/paritytech/projects/119/views/25) and +it's full implementation in multiple parachain consensus protocol components. Significant code contributions in both runtime and node side: From 357e5e9801a2b0ca8af79e2d523a5e42b3ac15cc Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Fri, 29 Nov 2024 12:53:35 +0200 Subject: [PATCH 5/7] updates Signed-off-by: Andrei Sandu --- .../sandreim/0003-sandreim-evidence-2024.md | 39 ++++++++++--------- 1 file changed, 21 insertions(+), 18 deletions(-) diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md index 06c2dbb..55dacff 100644 --- a/evidence/sandreim/0003-sandreim-evidence-2024.md +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -12,7 +12,8 @@ - Current rank: 2 - Date of initial induction: 2023/07/18 - Date of last report: N/A -- Area(s) of Expertise/Interest: Parachain Consensus, Node Performance Engineering, Observability, Stress and integration testing +- Area(s) of Expertise/Interest: Parachain Consensus, Node Performance Engineering, Observability, +Stress and integration testing ## Reporting period @@ -21,39 +22,41 @@ ## Evidence -During the reporting period I have played an important role in the design, development and deployment of a few major changes to Polkadot that had significant impact: +During the reporting period, I have played an important role in the design, development, and +deployment of a few major changes to Polkadot that had a significant impact: - better decentralization and security by increasing parachain validators from 200 to 500 - more blockspace by increasing the number of usable cores to 100 -- lowering the latency and increasing maximum throughput of parachains with Elastic Scaling +- lowering the latency and increasing the maximum throughput of parachains with Elastic Scaling - faster and lower cost parachain consensus protocol performance engineering with Subsystem Benchmarks I've been an active participant in OpenDev calls and in the [Polkadot forum](https://forum.polkadot.network/u/sandreim/activity), consistently giving updates on the progress of the implementation, testing, and deployment of Elastic Scaling. -I consider that this evidence, detailed in the next section, is aligned both in quality and quantity with the Fellowship for a rank 3 promotion. +I consider that this evidence, detailed in the next section, is aligned both in quality and +quantity with the Fellowship for a rank 3 promotion. ### Increasing number of validators and cores -I have started working on this project before being inducted in the fellowship. -That work consisted of load testing, benchmarking and research to find parachain consensus +I started working on this project before being inducted into the fellowship. +That work consisted of load testing, benchmarking, and research to find parachain consensus protocol and implementation bottlenecks on the node and runtime implementation. At the time Polkadot had 200 validators and 40 cores. I created the [scalability roadmap](https://github.com/paritytech/roadmap/issues/26) which includes multiple changes and ideas I contributed as improvements in major parachain consensus protocols: -availability, approval voting and the overall node side subsystem architecture. +availability, approval voting, and the overall node-side subsystem architecture. Major design and code contributions: - **[Assignment certificates v2](https://github.com/paritytech/polkadot-sdk/pull/1178)**: This is an enhancement of the approval voting protocol aimed at reducing the usage -of netwoprk/CPU resources by a factor of up to 6 in perfect network conditions. +of network/CPU resources by a factor of up to 6 in perfect network conditions. - **[Approval voting subsystem re-write](https://github.com/paritytech/polkadot-sdk/issues/1617)**: Proposal of a simpler and scalable subsystem architecture. The two existing approval voting -subsytems are merged into a single one. The new subsystem introduces message processing parallelism -to make use of more CPU resources in order to handle the load at a scale of 1000 validators and +subsystems are merged into a single one. The new subsystem introduces message processing parallelism +to make use of more CPU resources to handle the load at a scale of 1000 validators and 500 cores. I've communicated with the ecosystem about scaling up plans in forum posts and Element chats: @@ -62,18 +65,18 @@ I've communicated with the ecosystem about scaling up plans in forum posts and E ### Parachain consensus performance benchmarks -My main motivation to build this was to replace the old ways of doing load testing by -running very large networks. It was expensive, slow and produced huge amounts of data -that was very hard to analyze and reason about. The output of my work is a +My main motivation for building this was to replace the old ways of doing load testing by +running large networks. It was expensive and slow, producing huge amounts of data +that were very hard to analyze and reason about. The output of my work is a [new tool](https://github.com/paritytech/polkadot-sdk/tree/master/polkadot/node/subsystem-bench) -which is required for continous improvement of the scalability and resilience of the parachain +which is required for the continuous improvement of the scalability and resilience of the parachain consensus protocols and Polkadot. I designed and implemented [multiple modular components](https://github.com/paritytech/polkadot-sdk/tree/master/polkadot/node/subsystem-bench#reusable-test-components) that are used to emulate the network traffic and load found in large-scale networks on local development machines. It performs stress -tests of one or more parachain consensus subsystems without the need to run the network of that -size. It collects granular CPU usage and network metrics and is an integral part of ongoing -scalability and performance optimization development and CI performance regression testing. +tests of one or more parachain consensus subsystems without running a network. It collects granular +CPU usage and network metrics and is an integral part of ongoing scalability and performance +optimization development and CI performance regression testing. **Subsytem benchmarks PRs**: [1](https://github.com/paritytech/polkadot-sdk/pull/2528), [2](https://github.com/paritytech/polkadot-sdk/pull/2970) @@ -96,7 +99,7 @@ Played a primary role in initial design work: [Github](https://github.com/polkad Authored [RFC 103](https://github.com/polkadot-fellows/RFCs/blob/main/text/0103-introduce-core-index-commitment.md) and led the [planning](https://github.com/orgs/paritytech/projects/119/views/25) and -it's full implementation in multiple parachain consensus protocol components. +implementation in multiple parachain consensus protocol components. Significant code contributions in both runtime and node side: From 9e441de26d8b66fd6c2518eef38228133ed61ec6 Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Fri, 29 Nov 2024 13:06:57 +0200 Subject: [PATCH 6/7] reword Signed-off-by: Andrei Sandu --- evidence/sandreim/0003-sandreim-evidence-2024.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md index 55dacff..acd312e 100644 --- a/evidence/sandreim/0003-sandreim-evidence-2024.md +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -22,8 +22,8 @@ Stress and integration testing ## Evidence -During the reporting period, I have played an important role in the design, development, and -deployment of a few major changes to Polkadot that had a significant impact: +During the reporting period, I have played an important role in the design, development, and +deployment of a few major projects to Polkadot that had a significant impact: - better decentralization and security by increasing parachain validators from 200 to 500 - more blockspace by increasing the number of usable cores to 100 From 54dd6b30f10e555c6d0c5dac7076e4be86909dda Mon Sep 17 00:00:00 2001 From: Andrei Sandu Date: Fri, 29 Nov 2024 19:12:16 +0200 Subject: [PATCH 7/7] update voting Signed-off-by: Andrei Sandu --- evidence/sandreim/0003-sandreim-evidence-2024.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/evidence/sandreim/0003-sandreim-evidence-2024.md b/evidence/sandreim/0003-sandreim-evidence-2024.md index acd312e..568220b 100644 --- a/evidence/sandreim/0003-sandreim-evidence-2024.md +++ b/evidence/sandreim/0003-sandreim-evidence-2024.md @@ -115,7 +115,7 @@ Significant code contributions in both runtime and node side: | Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments | |---|---|---|---|---| |I |90% |N/A | | | -|II |80% |N/A | I have voted on 4 out of 21 referenda in which I was eligible to vote (19% voting activity) | I target to raise it to 80% at least for the next reporting period | +|II |80% |N/A | I have voted on 4 out of 20 referenda in which I was eligible to vote (20% voting activity) || |III|70% |100% | | | |IV |60% |90% | | | |V |50% |80% | | |