# Argument-0004: Retention at Rank I

|                 |                                                                                             |
| --------------- | ------------------------------------------------------------------------------------------- |
| **Report Date** | 2025/05/10 (YYYY/MM/DD)                                                                     |
| **Submitted by**| Francisco Aguirre                                                                           |

## Member details

- Matrix username: `@cisco:parity.io`
- Polkadot address: `129EYiTbv2J4LkYqRNssUfMuxNLYN8TW2LgfG1Gqyj8wCcs7`
- Current rank: `1`
- Date of initial induction: `2024/05/31`
- Date of last report: `2025/02/13`
- Area(s) of Expertise/Interest: `XCM, Smart Contracts`

## Reporting period

- Start date: 2025/02/13
- End date: 2025/05/10


## Argument

During this retention period my focus has mainly remained the same, improving documentation and helping others with XCM.
I've also been learning about solidity and PVM smart contracts to be able to help in the upcoming [Polkadot Hub](https://forum.polkadot.network/t/asset-hub-migration-2025/11129).

I [wrote a document](https://hackmd.io/@n9QBuDYOQXG-nWCBrwx8YQ/BJaLiT4c1x) on what XCM support in Smart Contracts would look like.
It was useful to use this for collaboration on what was needed.
As part of my efforts, I made [a PR for handling ERC20 tokens in XCM](https://github.com/paritytech/polkadot-sdk/pull/7762).
I've also been helping with [the XCM precompile](https://github.com/paritytech/polkadot-sdk/pull/8471) and [creating a query-response framework for Smart Contracts](https://github.com/paritytech/polkadot-sdk/issues/7735) alongside Tiago Bandeira.

I've been collaborating with the [ParaSpell](https://paraspell.github.io/docs/) team to improve their [XCM SDK](https://github.com/paraspell/xcm-tools) with features from XCMv5, dry-running and fee estimation.
I [wrote a guide](https://hackmd.io/@n9QBuDYOQXG-nWCBrwx8YQ/SJ-rbyFkee) for wallets to dry-run cross-chain transfers to prevent errors and trapping funds.
Out of that, I started [release 1.5.1](https://github.com/polkadot-fellows/runtimes/pull/712) for system parachains to enable the `ExchangeAsset` instruction which can be used to automatically fix problems with ED when transferring to Asset Hub.

On the education front, I attended [PBA Campus wave 6 in Lucerne](https://x.com/AcademyPolkadot/status/1918330507324260621) as an instructor for the Polkadot SDK module.
There, I [created exercises for XCMv5](https://github.com/shawntabrizi/polkadot-sdk-workshop-xcm/) meant to be useful for creating documentation out of it.
I gave another live lecture at the second wave of the PBA-X.

[Documentation for XCMv5](https://github.com/polkadot-developers/polkadot-docs/pull/477) is on its way.

Over the next period, my plan is to have full XCM support in smart contracts and double down on documentation for XCM.

## Voting record

|  Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
|---|---|---|---|---|
|I  |90%   |N/A   |100%   |I have voted on 0 out of 0 referenda in which I was eligible to vote (i.e 100% voting activity).  |
|II |80%   |N/A   |   |  |
|III|70%   |100%  |   |  |
|IV |60%   |90%   |   |  |
|V  |50%   |80%   |   |  |
|VI |40%   |70%   |   |  |