# Fellowship application for Vincent Geddes

# Details

Matrix username: [@vgeddes](https://collectives.polkassembly.io/user/vgeddes):matrix.org

Github: [https://github.com/vgeddes](https://github.com/vgeddes)

Mail: vincent.geddes@gmail.com

Polkadot address: 16YdterMH6axUsZP52fF3M7JJePfNB3yCd8dXwniEofpTSiP

# Motivation

I have been part of the Polkadot community since 2020, leading the effort to build and deliver Snowbridge, a trustless and decentralized bridge between Polkadot and Ethereum. This is a major system compromising many different subcomponents spread over multiple chains, including AssetHub, BridgeHub, and Ethereum.

Snowbridge is active and is currently holds over $80 million in bridged assets. In terms of user traction, It is a key component allowing the Mythos and KILT chains to deliver their products. Integrations with other parachain systems are in development.

Joining the fellowship will allow me to more effectively participate in fellowship governance topics related to trustless bridges.

I would like to apply for the *Dan II* level as I believe I have fulfilled the necessary requirements:

* I am the primary individual responsible for the technical development and delivery of Snowbridge. Many teams of course contributed to its delivery.
* I am deeply familiar with:
    * Trustless bridging protocols, design, and implementation
    * BEEFY consensus protocol
    * XCM, XCM Executor, and ongoing XCMv5 development
* I have published a long-form technical article about Snowbridge:
    * [https://docs.snowbridge.network/architecture/overview](https://docs.snowbridge.network/architecture/overview)
* I developed the reference implementation for a system that is described in a [paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf) by W3F and is currently pending submission to academic journals.

# Contributions

## Random-sampling BEEFY client

In collaboration with W3F (Alistair Stewart, Bhargav Bhatt), we designed a novel random-sampling light-client for the BEEFY consensus gadget.

I implemented the specification, which today is powering verification of Polkadot→Ethereum messages for Snowbridge.

* Code: [BeefyClient.sol](https://github.com/Snowfork/snowbridge/blob/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol) [[Blame](https://github.com/Snowfork/snowbridge/blame/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol)]
* [Implementation Article](https://docs.snowbridge.network/architecture/verification/polkadot)
* [Research Paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf)

## Snowbridge BridgeHub Pallets

Snowbridge includes several pallets that are currently operational on the BridgeHub system chain.

Primary author:

* [snowbridge-pallet-system](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/system)
* [snowbridge-pallet-inbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/inbound-queue)
* [snowbridge-pallet-outbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/outbound-queue)

Major contributor:

* [snowbridge-pallet-ethereum-client](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/ethereum-client)
* [Primitive crates](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/primitives)

Note that these pallets originated in our separate team [repository](https://github.com/Snowfork/snowbridge), and were later [duplicated](https://github.com/paritytech/polkadot-sdk/pull/2522) into the Polkadot-SDK. As such, historical commit history was lost, and I won’t appear as a committer to the relevant files.

Refer to this [snapshot](https://github.com/Snowfork/snowbridge/tree/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets) to view the original pallets. For example, here is a [blame](https://github.com/Snowfork/snowbridge/blame/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets/outbound-queue/src/lib.rs) showing my commits to the original inbound-queue pallet.

## Snowbridge Ethereum Contracts

I designed and authored all the contracts on the Ethereum side of the bridge:

[https://github.com/Snowfork/snowbridge/tree/main/contracts](https://github.com/Snowfork/snowbridge/tree/main/contracts)

## Snowbridge Off-chain relayers

I am a major contributor to our off-chain relayers, which synchronize state between the BridgeHub and Ethereum:

* BEEFY consensus relay
* Beacon consensus relay
* Polkadot user message relay
* Ethereum user message relay

[https://github.com/Snowfork/snowbridge/tree/main/relayer](https://github.com/Snowfork/snowbridge/tree/main/relayer)

## Snowbridge V2

More recently, a new version Snowbridge is under development, which makes use of XCMv5 to provide better UX and more features.

As part of this effort, I am responsible specifically for:

* The design [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) (along with major contributions from Alistair Singh, Adrian Catangiu, and Francisco Aguirre)
* The ethereum contracts: [https://github.com/Snowfork/snowbridge/pull/1300](https://github.com/Snowfork/snowbridge/pull/1300)

## XCMv5

Along with my team, I helped review the ongoing XCMv5 development effort. The Parity XCM/Bridges and Snowbridge team met up in September 2024 in Berlin to finalize XCMv5 requirements, among other things.

As one of the outputs of this retreat, I wrote up a semi-formal [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) for Snowbridge V2, which relies heavily on XCMv5, and helps validate its design with an actual user-facing project. Other contributors to this document included Alistair Singh, Adrian Catangiu, and Francisco Aguirre.

## Miscellanous

* Minor contribution to pallet-assets: [https://github.com/paritytech/substrate/pull/9742](https://github.com/paritytech/substrate/pull/9742)
* Minor contribution to XCMv4: [https://github.com/paritytech/polkadot/pull/6286](https://github.com/paritytech/polkadot/pull/6286)
* Utility pallets:
    * Snowbridge governance CLI: [https://github.com/Snowfork/snowbridge/tree/main/control](https://github.com/Snowfork/snowbridge/tree/main/control)

## Governance

I created a successful OpenGov [proposal](https://polkadot.polkassembly.io/referenda/680) to activate Snowbridge. This was a complex proposal that orchestrated changes on multiple chains, including AssetHub, BridgeHub, and Ethereum.

# Fellowship application for Vincent Geddes

# Details

Matrix username: @vgeddes:matrix.org

Github: [https://github.com/vgeddes](https://github.com/vgeddes)

Mail: vincent.geddes@gmail.com

Polkadot address: 16YdterMH6axUsZP52fF3M7JJePfNB3yCd8dXwniEofpTSiP

# Motivation

I have been part of the Polkadot community since 2020, leading the effort to build and deliver Snowbridge, a trustless and decentralized bridge between Polkadot and Ethereum. This is a major system compromising many different subcomponents spread over multiple chains, including AssetHub, BridgeHub, and Ethereum.

Snowbridge is active and is currently holds over $80 million in bridged assets. In terms of user traction, It is a key component allowing the Mythos and KILT chains to deliver their products. Integrations with other parachain systems are in development.

Joining the fellowship will allow me to more effectively participate in fellowship governance topics related to trustless bridges.

I would like to apply for the *Dan II* level as I have fulfilled the following requirements:

* I am the primary individual responsible for the technical development and delivery of Snowbridge.
* I am deeply familiar with:
    * Trustless bridging protocols, design, and implementation
    * BEEFY consensus protocol
    * XCM, XCM Executor, and ongoing XCMv5 development
    * AssetHub and BridgeHub system parachains
* I have published a long-form technical article about Snowbridge:
    * [https://docs.snowbridge.network/architecture/overview](https://docs.snowbridge.network/architecture/overview)
* I developed the reference implementation for a system that is described in a [paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf) by W3F and is currently pending submission to academic journals.

# Contributions

## Random-sampling BEEFY client

In collaboration with W3F (Alistair Stewart, Bhargav Bhatt), we designed a novel random-sampling light-client for the BEEFY consensus gadget.

I implemented the specification, which today is powering verification of Polkadot→Ethereum messages for Snowbridge.

* Code: [BeefyClient.sol](https://github.com/Snowfork/snowbridge/blob/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol) [[Blame](https://github.com/Snowfork/snowbridge/blame/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol)]
* [Implementation Article](https://docs.snowbridge.network/architecture/verification/polkadot)
* [Research Paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf)

## Snowbridge BridgeHub Pallets

Snowbridge includes several pallets that are currently operational on the BridgeHub system chain.

Primary author:

* [snowbridge-pallet-system](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/system)
* [snowbridge-pallet-inbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/inbound-queue)
* [snowbridge-pallet-outbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/outbound-queue)

Major contributor:

* [snowbridge-pallet-ethereum-client](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/ethereum-client)
* [Primitive crates](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/primitives)

Note that these pallets originated in our separate team [repository](https://github.com/Snowfork/snowbridge), and were later [duplicated](https://github.com/paritytech/polkadot-sdk/pull/2522) into the Polkadot-SDK. As such, historical commit history was lost, and I won’t appear as a committer to the relevant files.

Refer to this [snapshot](https://github.com/Snowfork/snowbridge/tree/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets) to view the original pallets. For example, here is a [blame](https://github.com/Snowfork/snowbridge/blame/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets/outbound-queue/src/lib.rs) showing my commits to the original inbound-queue pallet.

## Snowbridge Ethereum Contracts

I designed and authored all the contracts on the Ethereum side of the bridge:

[https://github.com/Snowfork/snowbridge/tree/main/contracts](https://github.com/Snowfork/snowbridge/tree/main/contracts)

## Snowbridge Off-chain relayers

I am a major contributor to our off-chain relayers, which synchronize state between the BridgeHub and Ethereum:

* BEEFY consensus relay
* Beacon consensus relay
* Polkadot user message relay
* Ethereum user message relay

[https://github.com/Snowfork/snowbridge/tree/main/relayer](https://github.com/Snowfork/snowbridge/tree/main/relayer)

## Snowbridge V2

More recently, a new version Snowbridge is under development, which makes use of XCMv5 to provide better UX and more features.

As part of this effort, I am responsible specifically for:

* The design [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) (along with major contributions from Alistair Singh, Adrian Catangiu, and Francisco Aguirre)
* The ethereum contracts: [https://github.com/Snowfork/snowbridge/pull/1300](https://github.com/Snowfork/snowbridge/pull/1300)

## XCMv5

Along with my team, I helped review the ongoing XCMv5 development effort. The Parity XCM/Bridges and Snowbridge team met up in September 2024 in Berlin to finalize XCMv5 requirements, among other things.

As one of the outputs of this retreat, I wrote up a semi-formal [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) for Snowbridge V2, which relies heavily on XCMv5, and helps validate its design with an actual user-facing project. Other contributors to this document included Alistair Singh, Adrian Catangiu, and Francisco Aguirre.

## Miscellanous

* Minor contribution to pallet-assets: [https://github.com/paritytech/substrate/pull/9742](https://github.com/paritytech/substrate/pull/9742)
* Minor contribution to XCMv4: [https://github.com/paritytech/polkadot/pull/6286](https://github.com/paritytech/polkadot/pull/6286)
* Utility pallets:
    * Snowbridge governance CLI: [https://github.com/Snowfork/snowbridge/tree/main/control](https://github.com/Snowfork/snowbridge/tree/main/control)

## Governance

I created a successful OpenGov [proposal](https://polkadot.polkassembly.io/referenda/680) to activate Snowbridge. This was a complex proposal that orchestrated changes on multiple chains, including AssetHub, BridgeHub, and Ethereum.

Add Vincent Geddes as DAN II

# Fellowship application for Vincent Geddes

# Details

Matrix username: [@vgeddes](https://collectives.polkassembly.io/user/vgeddes):matrix.org

Github: [https://github.com/vgeddes](https://github.com/vgeddes)

Mail: vincent.geddes@gmail.com

Polkadot address: 16YdterMH6axUsZP52fF3M7JJePfNB3yCd8dXwniEofpTSiP

# Motivation

I have been part of the Polkadot community since 2020, leading the effort to build and deliver Snowbridge, a trustless and decentralized bridge between Polkadot and Ethereum. This is a major system compromising many different subcomponents spread over multiple chains, including AssetHub, BridgeHub, and Ethereum.

Snowbridge is active and is currently holds over $80 million in bridged assets. In terms of user traction, It is a key component allowing the Mythos and KILT chains to deliver their products. Integrations with other parachain systems are in development.

Joining the fellowship will allow me to more effectively participate in fellowship governance topics related to trustless bridges.

I would like to apply for the *Dan II* level as I have fulfilled the following requirements:

* I am the primary individual responsible for the technical development and delivery of Snowbridge.
* I am deeply familiar with:
    * Trustless bridging protocols, design, and implementation
    * BEEFY consensus protocol
    * XCM, XCM Executor, and ongoing XCMv5 development
    * AssetHub and BridgeHub system parachains
* I have published a long-form technical article about Snowbridge:
    * [https://docs.snowbridge.network/architecture/overview](https://docs.snowbridge.network/architecture/overview)
* I developed the reference implementation for a system that is described in a [paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf) by W3F and is currently pending submission to academic journals.

# Contributions

## Random-sampling BEEFY client

In collaboration with W3F (Alistair Stewart, Bhargav Bhatt), we designed a novel random-sampling light-client for the BEEFY consensus gadget.

I implemented the specification, which today is powering verification of Polkadot→Ethereum messages for Snowbridge.

* Code: [BeefyClient.sol](https://github.com/Snowfork/snowbridge/blob/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol) [[Blame](https://github.com/Snowfork/snowbridge/blame/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol)]
* [Implementation Article](https://docs.snowbridge.network/architecture/verification/polkadot)
* [Research Paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf)

## Snowbridge BridgeHub Pallets

Snowbridge includes several pallets that are currently operational on the BridgeHub system chain.

Primary author:

* [snowbridge-pallet-system](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/system)
* [snowbridge-pallet-inbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/inbound-queue)
* [snowbridge-pallet-outbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/outbound-queue)

Major contributor:

* [snowbridge-pallet-ethereum-client](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/ethereum-client)
* [Primitive crates](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/primitives)

Note that these pallets originated in our separate team [repository](https://github.com/Snowfork/snowbridge), and were later [duplicated](https://github.com/paritytech/polkadot-sdk/pull/2522) into the Polkadot-SDK. As such, historical commit history was lost, and I won’t appear as a committer to the relevant files.

Refer to this [snapshot](https://github.com/Snowfork/snowbridge/tree/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets) to view the original pallets. For example, here is a [blame](https://github.com/Snowfork/snowbridge/blame/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets/outbound-queue/src/lib.rs) showing my commits to the original inbound-queue pallet.

## Snowbridge Ethereum Contracts

I designed and authored all the contracts on the Ethereum side of the bridge:

[https://github.com/Snowfork/snowbridge/tree/main/contracts](https://github.com/Snowfork/snowbridge/tree/main/contracts)

## Snowbridge Off-chain relayers

I am a major contributor to our off-chain relayers, which synchronize state between the BridgeHub and Ethereum:

* BEEFY consensus relay
* Beacon consensus relay
* Polkadot user message relay
* Ethereum user message relay

[https://github.com/Snowfork/snowbridge/tree/main/relayer](https://github.com/Snowfork/snowbridge/tree/main/relayer)

## Snowbridge V2

More recently, a new version Snowbridge is under development, which makes use of XCMv5 to provide better UX and more features.

As part of this effort, I am responsible specifically for:

* The design [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) (along with major contributions from Alistair Singh, Adrian Catangiu, and Francisco Aguirre)
* The ethereum contracts: [https://github.com/Snowfork/snowbridge/pull/1300](https://github.com/Snowfork/snowbridge/pull/1300)

## XCMv5

Along with my team, I helped review the ongoing XCMv5 development effort. The Parity XCM/Bridges and Snowbridge team met up in September 2024 in Berlin to finalize XCMv5 requirements, among other things.

As one of the outputs of this retreat, I wrote up a semi-formal [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) for Snowbridge V2, which relies heavily on XCMv5, and helps validate its design with an actual user-facing project. Other contributors to this document included Alistair Singh, Adrian Catangiu, and Francisco Aguirre.

## Miscellanous

* Minor contribution to pallet-assets: [https://github.com/paritytech/substrate/pull/9742](https://github.com/paritytech/substrate/pull/9742)
* Minor contribution to XCMv4: [https://github.com/paritytech/polkadot/pull/6286](https://github.com/paritytech/polkadot/pull/6286)
* Utility pallets:
    * Snowbridge governance CLI: [https://github.com/Snowfork/snowbridge/tree/main/control](https://github.com/Snowfork/snowbridge/tree/main/control)

## Governance

I created a successful OpenGov [proposal](https://polkadot.polkassembly.io/referenda/680) to activate Snowbridge. This was a complex proposal that orchestrated changes on multiple chains, including AssetHub, BridgeHub, and Ethereum.

# Fellowship application for Vincent Geddes

# Details

Matrix username: [@vgeddes](https://collectives.polkassembly.io/user/vgeddes):matrix.org

Github: [https://github.com/vgeddes](https://github.com/vgeddes)

Mail: vincent.geddes@gmail.com

Polkadot address: 16YdterMH6axUsZP52fF3M7JJePfNB3yCd8dXwniEofpTSiP

# Motivation

I have been part of the Polkadot community since 2020, leading the effort to build and deliver Snowbridge, a trustless and decentralized bridge between Polkadot and Ethereum. This is a major system compromising many different subcomponents spread over multiple chains, including AssetHub, BridgeHub, and Ethereum.

Snowbridge is active and is currently holds over $80 million in bridged assets. In terms of user traction, It is key component allowing the Mythos and KILT chains to deliver their products. Integrations with other parachain systems are in development.

Joining the fellowship will allow me to more effectively participate in fellowship governance topics related to trustless bridges.

I would like to apply for the *Dan II* level as I have fulfilled the following requirements:

* I am the primary individual responsible for the technical development and delivery of Snowbridge.
* I am deeply familiar with:
    * Trustless bridging protocols, design, and implementation
    * BEEFY consensus protocol
    * XCM, XCM Executor, and ongoing XCMv5 development
    * AssetHub and BridgeHub system parachains
* I have published a long-form technical article about Snowbridge:
    * [https://docs.snowbridge.network/architecture/overview](https://docs.snowbridge.network/architecture/overview)
* I developed the reference implementation for a system that is described in a [paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf) by W3F and is currently pending submission to academic journals.

# Contributions

## Random-sampling BEEFY client

In collaboration with W3F (Alistair Stewart, Bhargav Bhatt), we designed a novel random-sampling light-client for the BEEFY consensus gadget.

I implemented the specification, which today is powering verification of Polkadot→Ethereum messages for Snowbridge.

* Code: [BeefyClient.sol](https://github.com/Snowfork/snowbridge/blob/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol) [[Blame](https://github.com/Snowfork/snowbridge/blame/20a804669e0da59cff01b09588e16f1267d98862/contracts/src/BeefyClient.sol)]
* [Implementation Article](https://docs.snowbridge.network/architecture/verification/polkadot)
* [Research Paper](https://research.web3.foundation/assets/files/beefy-83fa77754436908399299de4bf1310b6.pdf)

## Snowbridge BridgeHub Pallets

Snowbridge includes several pallets that are currently operational on the BridgeHub system chain.

Primary author:

* [snowbridge-pallet-system](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/system)
* [snowbridge-pallet-inbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/inbound-queue)
* [snowbridge-pallet-outbound-queue](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/outbound-queue)

Major contributor:

* [snowbridge-pallet-ethereum-client](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/pallets/ethereum-client)
* [Primitive crates](https://github.com/paritytech/polkadot-sdk/tree/master/bridges/snowbridge/primitives)

Note that these pallets originated in our separate team [repository](https://github.com/Snowfork/snowbridge), and were later [duplicated](https://github.com/paritytech/polkadot-sdk/pull/2522) into the Polkadot-SDK. As such, historical commit history was lost, and I won’t appear as a committer to the relevant files.

Refer to this [snapshot](https://github.com/Snowfork/snowbridge/tree/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets) to view the original pallets. For example, here is a [blame](https://github.com/Snowfork/snowbridge/blame/ffe241f357ba234b68c33da1c9fcf4a92e277eae/parachain/pallets/outbound-queue/src/lib.rs) showing my commits to the original inbound-queue pallet.

## Snowbridge Ethereum Contracts

I designed and authored all the contracts on the Ethereum side of the bridge:

[https://github.com/Snowfork/snowbridge/tree/main/contracts](https://github.com/Snowfork/snowbridge/tree/main/contracts)

## Snowbridge Off-chain relayers

I am a major contributor to our off-chain relayers, which synchronize state between the BridgeHub and Ethereum:

* BEEFY consensus relay
* Beacon consensus relay
* Polkadot user message relay
* Ethereum user message relay

[https://github.com/Snowfork/snowbridge/tree/main/relayer](https://github.com/Snowfork/snowbridge/tree/main/relayer)

## Snowbridge V2

More recently, a new version Snowbridge is under development, which makes use of XCMv5 to provide better UX and more features.

As part of this effort, I am responsible specifically for:

* The design [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) (along with major contributions from Alistair Singh, Adrian Catangiu, and Francisco Aguirre)
* The ethereum contracts: [https://github.com/Snowfork/snowbridge/pull/1300](https://github.com/Snowfork/snowbridge/pull/1300)

## XCMv5

Along with my team, I helped review the ongoing XCMv5 development effort. The Parity XCM/Bridges and Snowbridge team met up in September 2024 in Berlin to finalize XCMv5 requirements, among other things.

As one of the outputs of this retreat, I wrote up a semi-formal [specification](https://github.com/paritytech/polkadot-sdk/blob/master/bridges/snowbridge/docs/v2.md) for Snowbridge V2, which relies heavily on XCMv5, and helps validate its design with an actual user-facing project. Other contributors to this document included Alistair Singh, Adrian Catangiu, and Francisco Aguirre.

## Miscellanous

* Minor contribution to pallet-assets: [https://github.com/paritytech/substrate/pull/9742](https://github.com/paritytech/substrate/pull/9742)
* Minor contribution to XCMv4: [https://github.com/paritytech/polkadot/pull/6286](https://github.com/paritytech/polkadot/pull/6286)
* Utility pallets:
    * Snowbridge governance CLI: [https://github.com/Snowfork/snowbridge/tree/main/control](https://github.com/Snowfork/snowbridge/tree/main/control)

## Governance

I created a successful OpenGov [proposal](https://polkadot.polkassembly.io/referenda/680) to activate Snowbridge. This was a complex proposal that orchestrated changes on multiple chains, including AssetHub, BridgeHub, and Ethereum.

- **Problem Statement:** Vincent Geddes is seeking a fellowship to enhance his participation in governance topics related to trustless bridges within the Polkadot community.
- **Audience:** Polkadot community, fellowship governance topics stakeholders.
- **Significance:** Vincent Geddes has been instrumental in developing Snowbridge, a trustless bridge between Polkadot and Ethereum, holding over $80 million in bridged assets.
- **Proposed Solution:** Applying for the Dan II fellowship level due to his technical expertise in trustless bridging protocols, BEEFY consensus protocol, and ongoing XCMv5 development.
- **Expected Outcomes:** Increased effectiveness in participating in fellowship governance topics related to trustless bridges within the Polkadot community.

#35 Add Vincent Geddes as DAN II