Hello everyone! I'm Cisco and I've been working for Parity in the FRAME team, now Bridges+XCM, since March 2023. I would like to join Polkadot's technical fellowship as a Dan I member. Github: https://github.com/franciscoaguirre/ Polkadot address: 129EYiTbv2J4LkYqRNssUfMuxNLYN8TW2LgfG1Gqyj8wCcs7 Some of my contributions: - [XCMv4](https://github.com/paritytech/polkadot-sdk/pull/1230) - Had to refactor every xcm-related code to include a fix that reduces memory size of the `Instruction` enum by 10x. - [`claim_assets` extrinsic on pallet-xcm](https://github.com/paritytech/polkadot-sdk/pull/3403) - Also made guide on how to claim assets - There was no way to claim assets on the live runtimes because they didn't allow arbitrary execution. This helped users recover their funds, stuck because of either bugs or misuse. - Worked with Unique Network on the [XcmPaymentApi](https://github.com/paritytech/polkadot-sdk/pull/3607). - Exposes necessary components for XCM fee estimation. - [XcmDryRunApi](https://github.com/paritytech/polkadot-sdk/pull/3872) - Runtime API able to dry-run both extrinsics and XCM programs, useful in conjunction with the XcmPaymentApi for estimating fees, but also on its own. - [PayFees RFC](https://github.com/paritytech/xcm-format/pull/53) - As part of redesigning XCM fees. Meant to fix wrong handling of fees by the executor to prevent bugs. - [Prototype](https://github.com/paritytech/polkadot-sdk/pull/3450) - [Xcm builder pattern](https://github.com/paritytech/polkadot-sdk/pull/2107) - More ergonomic and IDE friendly way of building XCM programs.