| Report Date | 2025-12-07 |
| Submitted by | Clara van Staden |
In the last 3 months, my work has spanned technical contributions, application support on Snowbridge, as well as an expanded focus on Polkadot initiatives outside of Snowbridge.
Snowbridge V2, which brings major cost savings to bridge users, was released on-chain around middle October. I worked on off-chain support for Snowbridge V2, including the Snowbridge TypeScript SDK, and supporting Snowbridge V2 in the Snowbridge app. Snowbridge V2 will be enabled for Ethereum <> AssetHub routes in the next week, realizing significant cost savings for users: ~50% reduction for Ethereum to Polkadot transfers and a ~75% reduction for Polkadot to Ethereum transfers. I also added developer documentation for Snowbridge V2, wrote the Snowbridge V2 release announcement on the Polkadot Forum and gave an overview of Snowbridge V2 at the Polkadot Builders Party.
I was responsible for Ethereum Fusaka support on Snowbridge. This covered on-chain version support, off-chain relayer support, coordinating a runtime release and the Polkadot system chain runtime upgrade referendums. The Snowbridge Ethereum client switched over seamless on 3 Dec 2025.
In an effort to expand my contributions in the ecosystem outside of Snowbridge, I have collaborated with Oliver Tale-Yazdi to work on social account recovery on Polkadot. I have created a basic UI to demonstrate the functionality (backend to be completed).
For the first time in Snowbridge's history on Polkadot mainnet, we had our first incident. A member of our team noticed failing transactions on BridgeHub and alerted our team. I immediately realized what happened (that BridgeHub was not upgraded, while AssetHub was). I uploaded the BridgeHub runtime wasm 5 minutes after we discovered the outage, minimizing affected transactions. While the incident was regrettable, I believe it demonstrated my commitment and knowledge to maintain a high availability service. I was also responsible for the root cause incident report and the referendum to correct the affected transactions.
The Snowbridge and bridges team were both under the impression that Snowbridge would not be affected by the AssetHub migration. A day before the migration, I realized that this might not be the case. After further investigation from our team, we saw that Snowbridge would be affected by the migration, enabling us to make the necessary provisions to ensure no user transactions are affected (notifying our users, putting the Snowbridge UI under maintenance mode, and notifying all our partners to do the same). This again shows a proactive response from my side to ensure user funds are protected.
I believe my contributions these last 3 months are worthy of Rank II retention, and hope you will favourably view my application.
Provide your voting record in relation to required thresholds for your rank.
| Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
|---|---|---|---|---|
| I | 90% | N/A | ||
| II | 80% | N/A | There were no valid referenda I was eligible to vote on. | |
| III | 70% | 100% | ||
| IV | 60% | 90% | ||
| V | 50% | 80% | ||
| VI | 40% | 70% |
No referendum was created