ambassador

senior_ambassador

head_ambassador

members

proficient_members

fellows

architects

architects_adept

grand_architects

masters

masters_constant

grand_masters

retain_at_i_dan

retain_at_ii_dan

retain_at_iii_dan

retain_at_iv_dan

retain_at_v_dan

retain_at_vi_dan

promote_to_i_dan

promote_to_ii_dan

promote_to_iii_dan

promote_to_iv_dan

promote_to_v_dan

promote_to_vi_dan

fast_promote_to_i_dan

fast_promote_to_ii_dan

fast_promote_to_iii_dan

## Background Information

My name is **Daniel Cukier**, and I hold a **PhD in Computer Science** from the University of São Paulo. 
My doctoral research focused on modeling and understanding [software startup ecosystems](https://link.springer.com/article/10.1186/s13731-018-0091-6) using formal qualitative methods, resulting in a published framework for ecosystem maturity.

This experience strengthened my ability to analyze complex systems, build conceptual models, and work with evolving structures — skills that have been valuable throughout my engineering career.

Recently, my work has centered on the **JAM protocol**. I am one of the core developers of **Jamixir**, an independent Elixir implementation of JAM. This includes interpreting the Graypaper, translating formal definitions into executable semantics, implementing PVM behavior, and experimenting with early node architecture ideas.

I have worked in the software industry for more than twenty years as a developer, founder, and technology leader. I founded a **music analytics startup** that processed billions of data points to help artists understand their audience and receive fair compensation. The company operated for six years and was eventually acquired in Brazil. Although not a large exit, it provided deep experience in building real systems, handling large-scale data, and navigating both technical and organizational complexity.

I also served as CTO of **Elo7** (later acquired by Etsy) and CTO of **Pravaler**, and I have been active in developer communities and engineering education, including contributing to [WEB3DEV](https://w3d.community), the largest Web3 developer community in Latin America.

---

## Motivations for Applying

I am applying to the Polkadot Fellowship because I want to contribute to the long-term evolution of the protocol, especially during its transition into JAM. 
Over the last year, I have spent significant time studying JAM and implementing its components. This has made me want to participate more formally in the work around specification clarity and protocol understanding.

My motivations include:

- **Deepening my protocol expertise** by collaborating with others who are exploring related problems. 
- **Contributing to decentralization** by helping develop and validate alternative implementations. 
- **Improving specification clarity**, both through implementation feedback and direct contributions. 
- **Supporting developer onboarding and education**, helping newcomers understand JAM’s execution model and core concepts. 
- **Participating in a community that values humility, rigor, and long-term commitment.**

I see the Fellowship as the right structure to continue contributing meaningfully in these areas.

---

## Areas of Interest in the Polkadot Ecosystem

My technical areas of interest include:

- JAM architecture and formal semantics 
- Node and runtime responsibilities under JAM 
- Cross-implementation alignment and specification clarity 
- Live network operational challenges 

I am also strongly interested in **developer experience and onboarding**. Throughout my career, I have worked to make complex concepts accessible, and I would like to help produce clearer explanations, runnable examples, and educational materials for developers entering the Polkadot ecosystem.

---

## Contributions to Polkadot / Protocol Work

My contributions so far are primarily related to JAM:

- I am developing **[Jamixir](https://github.com/jamixir)**, an Elixir implementation of the JAM protocol. 
- I have **15 accepted commits to the official JAM Graypaper**, improving clarity, correcting inconsistencies, and refining definitions: 
 <https://github.com/gavofyork/graypaper/commits?author=danicuki> 
- I have taken part in discussions around semantics, determinism, architecture boundaries, and specification interpretation. 
- I have created diagrams, explanations, and conceptual demos to help others understand JAM’s structure and goals. 
- I helped organize JAM meetups and community calls, including the JAM Experience gathering in Lisbon (May 2025).

These contributions reflect both practical implementation work and a sustained engagement with the protocol’s underlying ideas. As JAM evolves, I plan to continue contributing to validation, specification refinement, and developer accessibility.

---

## GitHub Profile 
<https://github.com/danicuki>

---

## Polkadot Address (with verified on-chain identity) 
127XreSJZW91qLc91hwepYZ9pBfuNveqDERv9KDrm2oQf4Lu

Polkadot Technical Fellowship Application: Daniel Cukier



## Background information of the applicant

My name is **Kunal Drall**, and I am a blockchain developer with hands-on experience in **Rust, Go, and Python**. I have been actively involved in the Substrate and Polkadot ecosystem through **hackathons, grants, and open-source development**, focusing on building practical, production-oriented systems.

I recently graduated from **PBA-X Wave 5**, where I gained a strong foundation in decentralized systems, cryptography, governance, interoperability, and hands-on usage of the Polkadot SDK. This experience significantly strengthened my understanding of Polkadot’s architecture and governance model.

---

## Motivation(s) for applying to the Polkadot Technical Fellowship

I am applying to join the **Polkadot Technical Fellowship** because I want to contribute to the **long-term technical development and governance of the Polkadot network**.

I strongly align with the Fellowship’s guiding principles:
- Upholding Polkadot’s long-term interests  
- Respecting its technical philosophy and governance processes  
- Collaborating openly and respectfully with the community  

The Fellowship represents a technical collective where I can learn from experienced contributors while progressively adding value through sustained open-source work.

---

## Area(s) of interest in relation to the Polkadot ecosystem

My primary areas of interest include:

- Substrate & FRAME development  
- Runtime development and core components for parachains  
- Development of CoreJAM and virtual machines  
- Smart contracts, particularly through **Pallet Revive**, to reduce onboarding friction for developers from other ecosystems  
- Improving developer experience while preserving protocol robustness  

I am especially interested in the intersection of **infrastructure and accessibility** within the Polkadot ecosystem.

---

## Contribution(s) to Polkadot SDK (if any)

While I am currently at an early stage of direct Polkadot SDK contributions, I am actively building within the ecosystem.

I am currently working on **Powergrid Network**, a **virtual power plant solution on Polkadot**, applying Substrate-based design patterns to real-world infrastructure coordination.

My near-term contribution goals include:
- Solving beginner- to intermediate-level Polkadot SDK GitHub issues  
- Improving documentation and developer tooling  
- Gradually contributing to runtime- and pallet-level code  

---

## Link to the GitHub profile of the applicant

- GitHub: https://github.com/kunal-drall  
- Project (Powergrid Network): https://github.com/kunal-drall/powergrid_network  

---

## Polkadot address with a verified on-chain identity

- Polkadot address:  
  `1U3JboaBjPViEFDwwzKpFLVeV2LHQx9Jy31FuMgHuRBnmxq`


Application to join the Polkadot Technical Fellowship — Kunal Drall

### Background

I'm **Prasad Kumkar**, a software engineer and technical lead with 5+ years of hands-on experience building blockchain protocols, DeFi systems, and cryptographic infrastructure.

I currently lead engineering at **ChainScore Labs**, where I have worked extensively across Ethereum, Polkadot, Substrate, Solana, NEAR, and more recently **JAM**. My work spans node clients, protocol implementations, cryptography libraries, SDKs, developer tooling, and performance-critical systems.

I am a Polkadot Blockchain Academy Cohort 4 (HK) alumnus and have been deeply involved in Polkadot protocol-level development over the last several years.

GitHub: [https://github.com/prasad-kumkar](https://github.com/prasad-kumkar)

---

### Motivation for Applying to the Polkadot Technical Fellowship

Polkadot is the ecosystem where I have consistently found the deepest technical challenges and the strongest culture of rigorous engineering since been to PBA.

I believe with **JAM**, Polkadot is entering a phase that demands long-term, protocol-first contributors who are willing to invest years into correctness, performance, and developer experience. My motivation for applying to the Technical Fellowship is to formally commit to this long-term stewardship role.

I am already spending the majority of my time working on JAM related infrastructure, including clean-room client implementation, cryptography, and developer tooling. The Fellowship aligns well with how I am already contributing and would allow me to deepen this work in closer coordination with the wider Polkadot technical community.

---

### Areas of Interest in the Polkadot Ecosystem

My primary areas of interest are:

* JAM client implementation
* PVM execution, compilation and performance optimization
* Cryptography for consensus and randomness (VRFs, ring proofs)
* Developer tooling and SDKs for JAM adoption
* Data availability, networking, and protocol correctness

---

### Contributions to Polkadot and JAM

#### **Tessera – JAM Node Client (Python)**

I lead the **Tessera** team, which is building a clean-room implementation of the JAM protocol in Python.

Contributions include:

* PVM interpreter 
* Codec and protocol modules
* QUIC-based P2P networking and gossip
* Erasure coding for JAM data availability
* x86 recompiler for PVM focused on high throughput execution

Repository: [https://github.com/Chainscore/tessera](https://github.com/Chainscore/tessera)

---

#### **Dotring – Cryptography Libraries for Polkadot / JAM**

I worked on **Dotring**, an open source cryptography library implementing:

* IETF VRF
* Pedersen VRF
* Ring signatures and ring proofs
* Fiat–Shamir transcripts
* Support for multiple Twisted Edwards curves including Jubjub, Ed25519, Bandersnatch

This work is based on Web3 Foundation research and is intended for use in Polkadot and JAM consensus related components.

Repository: [https://github.com/chainscore/dot-ring](https://github.com/chainscore/dot-ring)

---

#### **Jamcode.fun – JAM Developer Playground**

I built **Jamcode.fun**, an IDE style playground for developing and invoking services on JAM. The goal is to significantly lower the barrier for developers experimenting with JAM services and execution.

Website: [https://jamcode.fun](https://jamcode.fun)

---

#### **Ajanta – JAM SDK (C, C++ and Python)**

I'm currently working on Ajanta, a multi-language JAM SDK designed to make building applications and services on JAM accessible.

Repository: [https://github.com/Chainscore/ajanta](https://github.com/Chainscore/ajanta)

---

### Closing

I am applying to the Polkadot Technical Fellowship to formalize and deepen my long-term commitment to Polkadot and JAM. My focus is on protocol-level work that improves resilience, performance, and developer experience, and I intend to continue contributing at this level for years to come.

Thank you for your time and consideration.

Application for Technical Fellowship: Prasad Kumkar

### Background information of the applicant
My name is Rohit Sarpotdar. I began working in Solana & ICP ecosystem, building contracts for social interactions since 2020. I graduated from PBAW5 and later joined Parity in Bridges team.
Since last 10 months I'm focusing on building features and maintaining bridges & runtimes.

### Motivation(s) for applying to the Polkadot Technical Fellowship
I’m applying to the Polkadot Technical Fellowship because I work on Polkadot, and would like to add my voice to this collective.

### Area(s) of interest in relation to the Polkadot ecosystem.
- Enhancing Bridges, System Parachains and Runtimes
- Development of CoreJAM and VMs
- SCC and Bulletin chain

### Contribution(s) to Polkadot SDK (if any)

- [Polkadot SDK contributions](https://github.com/paritytech/polkadot-sdk/issues?q=is%3Aissue%20is%3Apr%20author%3Arosarp) : I have contributed to the polkadot-sdk by implementing small features aimed at improving the overall development experience.
- [Bridges Contributions](https://github.com/paritytech/parity-bridges-common/issues?q=is%3Aissue%20is%3Apr%20author%3Arosarp) : I have contributed small features, upgraded and deployed P/K bridge substrate-relayer & runtimes.
- Contributed to SCC testing
- Currently working on testing Bulletin chain


### Link to the GitHub profile of the applicant

https://github.com/rosarp/

### Polkadot address with a verified on-chain identity

[143KKEzwsyjmTAjjpk75mCM4DYopmXTM52s6Lnj8udvX9Pxf](https://polkadot.subsquare.io/user/143KKEzwsyjmTAjjpk75mCM4DYopmXTM52s6Lnj8udvX9Pxf/identity)


Fellowship Application - Rohit Sarpotdar

## Background information of the applicant

My name is Alexandre Baldé. I began working in what is now called Web3 in 2016, in the Cardano protocol.
I currently work at Parity, in the System Parachains team.
I focus on testing, and have, for that purpose, contributed to the Polkadot SDK, the [Polkadot Fellowship runtimes](https://github.com/polkadot-fellows/runtimes)
and the Polkadot Ecosystem Tests [(PET)](https://github.com/open-web3-stack/polkadot-ecosystem-tests) project.

## Motivation(s) for applying to the Polkadot Technical Fellowship

From the Polkadot Fellowship Manifesto: "The Fellowship can be seen as a political collective in that it has an on-chain voice [...]".
I’m applying to the Polkadot Technical Fellowship because I work on Polkadot, and would like to add my voice to this collective.

From my work on PET, I have ideas on how to improve the testing process of Polkadot SDK development.
The Polkadot Technical Fellowship offers a venue in which to discuss and refine these ideas with other techincal
contributors, so that these improvements benefit everyone building on Polkadot.

## Area(s) of interest in relation to the Polkadot ecosystem.

System Parachains, Runtime/FRAME development and testing.

## Contribution(s) to Polkadot SDK (if any)

My contributions to the Polkadot SDK mostly relate to/result from my work on PET.
- I am part of the team working on the Asset Hub Migration, where I assist with testing
    - in paritcular, I've helped test the post-migration relay/asset hub runtimes via Chopsticks/PET
- I've found some issues with FRAME pallets
    - a minor issue with irremovable pure proxy accounts of some types
    - an issue with burning funds on Kusama relay chain post-AHM
    - missing events in some FRAME pallets' extrinsics
        - nomination pools, conviction voting, proxy, identity, vesting
- A refactor of `pallet-revive` to have its gas metering functionality be EIP-150-compliant
- I extended tests for people chain runtimes with the `xcm-emulator` tool

### Links

[Polkadot SDK monorepo contributions](https://github.com/paritytech/polkadot-sdk/issues?q=is%3Aissue%20is%3Apr%20author%3Arockbmb)

[Fellowship Runtimes contributions](https://github.com/polkadot-fellows/runtimes/pulls?q=is%3Apr+author%3Arockbmb)

[Pre-monorepo contributions (from 2019)](https://github.com/paritytech/substrate/pulls?q=is%3Apr+is%3Aissue+author%3Arockbmb+)

## Link to the GitHub profile of the applicant

https://github.com/rockbmb

## Polkadot address with a verified on-chain identity

13jBAtYJar4xujPaEx41FxjSt9PqU7LqJRbySJiVdMtuWN42


Application to join Polkadot Fellowship - Alexandre Baldé

**Background information of the applicant**

My name is Christopher Kalule I am based in Uganda. I come with 8+ years of experience in full stack development but now more focused on Rust & Blockchain. In the past, I have  worked with Golang, Javascript and QA. Proving my ability to build reliable, performant, scalable, and secure Web2 and Web3 systems. I believe open source would help me grow into a better engineer and that is how I stumbled onto Polkadot-SDK. With good rust skills which I earned in the Let's Get Rusty Live program. [Link to certificate](https://drive.google.com/file/d/1yZ9f5L0ap5yOOTmN-8LvvCaO7xnen9a_/view).  Allowed me to tackle some contributions I will Elaborate on below. And also a graduate of [PBA-X Wave #4](https://app.kajabi.com/certificates/d22ebcca). This was a mind blowing experience.  I also volunteered as a technical mentor at Polkadot Africa(Uganda) technical workshop in preparation for sub0, where is spoke on why blockchain & tokens  to building a [Poet Auction smart contract](https://dev.to/chri5_kalul3/building-a-poetry-auction-smart-contract-on-polkadot-with-ink-4aj9) with ink!v6. 

**Motivation(s) for applying to the Polkadot Technical Fellowship**

Becoming Developer Advocate for Polkadot Africa (Uganda) on October 9th crystallized what I want to accomplish. The Fellowship represents the technical depth I need to be effective in that role not just explaining Polkadot, but actively building with it. I want to contribute to the SDK while staying plugged into new implementations so I can create relevant, timely content for developers in my region and others. Working with experienced engineers would accelerate my web3 principles and Rust development while ensuring the guidance I give other developers is grounded in real practice, not just documentation.

**Area(s) of interest in relation to the Polkadot ecosystem.**
    - I'm interested in Node SDK work and runtime development—building the core components that parachains depend on. Smart contracts, especially through Pallet Revive, also fascinate me because that's where we're lowering barriers for developers coming from other ecosystems. It's the intersection of infrastructure and accessibility
    - JAM

**Contribution(s) to Polkadot SDK (if any)**
    - My work on Polkadot SDK spans three main areas: building out runtime support for XCM benchmarking across sibling parachains, collaborating with maintainers to remove legacy feature gates and reduce technical debt in core subsystems, and automating testnet setup for Omni Node to make development more efficient [Link to Contributions](https://github.com/paritytech/polkadot-sdk/pulls?q=is%3Apr+is%3Aclosed+author%3AEleisonC)

**Link to the GitHub profile of the applicant**
    - https://github.com/EleisonC

Application To Join FellowShip - Christopher

### Background

My name is Enoch, a full-stack developer specializing in Rust and TypeScript. Deeply interested in permissionless systems, web security, performance, and accessibility. I’ve made contributions to the Polkadot ecosystem as well as other Substrate-based [codebases](https://github.com/darwinia-network/darwinia/pull/953), and have built several open-source projects focused on developer experience and payment integrations.

I have contributed to the Polkadot ecosystem across its architectural evolution—beginning with the separate polyrepo structure (Substrate, Polkadot) and now actively contributing to the consolidated polkadot-sdk monorepo as runcomet. My engagement deepened after participating in the early [Runtime Developer Guide](https://youtu.be/J2JaavOEDN8?si=G5A-S2k4lXGGMVkD) sessions and its initial study group.

### Motivation
Having been around the ecosystem for some time now I have a unique perspective on the evolution of the technology, The Fellowship represents the next logical step for me to deepen my commitment. I am particularly eager to engage in the technical discussions and RFC processes that shape the platform, as evidenced by my initiative to work on [RFC-0097](https://polkadot-fellows.github.io/RFCs/approved/0097-unbonding_queue.html#proposed-parameters).

### Areas of interest

* Runtime
* Node Development & Tooling
* Join-Accumulate Machine (JAM)

### Contributions to the SDK

Polyrepo Era:
* [Substrate](https://github.com/paritytech/substrate/pulls?q=is%3Apr+author%3AECJ222+is%3Aclosed+is%3Amerged)
* [Polkadot](https://github.com/paritytech/polkadot/pulls/ECJ222)

Monorepo Era (as runcomet):
* [Polkadot-SDK](https://github.com/paritytech/polkadot-sdk/pulls?q=is%3Apr+author%3Aruncomet+is%3Aclosed+is%3Amerged)
* [RFC #0097 (Implementation)](https://github.com/paritytech/polkadot-sdk/pull/7398)

Link to GitHub Profile
* [Current (Primary)](https://github.com/runcomet)
* [Historical](https://github.com/ECJ222)



Application - Runcomet

Dear Polkadot Fellowship Team,

My name is Kaushik and I recently completed the PBA course in Bali where I got to learn so much about the inner workings of everything from Merkle storage to how the different ways in which XCM can make cross chain transfers! After leaving, I have this feeling like I want to contribute more and make a meaningful impact to the ecosystem, so I want to join the fellowship to see how I can do that alongside my current job :)

**Background Information**

I am a blockchain engineer currently working at Dakota, where I contribute to building a stablecoin banking platform. Prior to this, I worked in different-levels of blockchain development, including MEV execution client work, a Solana Trader API to enable traders to more easily trade on market makers like Jupiter and Serum and have even worked on an [open-souce game engine](https://github.com/curio-research/keystone)! I recently graduated from the Polkadot Blockchain Academy in Bali, where I deepened my understanding of Substrate, FRAME, XCM, and consensus mechanisms. My academic background also includes research in computational neuroscience, where I applied mathematical modeling to zebrafish neural activity. I am largely self-taught in programming, beginning after college, and have since built a career at the intersection of protocol engineering, applied cryptography, and distributed systems.

**Motivation for Applying**
I am applying to the Fellowship because I want to contribute to the long-term sustainability of the Polkadot ecosystem. Polkadot has consistently pushed the boundaries of what decentralized networks can achieve—from flexible runtime upgrades to secure cross-chain communication. I want to be part of the technical community that ensures these innovations remain robust, performant, and accessible to builders. The Fellowship also represents an opportunity to learn from and collaborate with engineers whose work I deeply respect, while sharing my own insights from both my PBA experience and ongoing protocol-level development.

**Areas of Interest**

My main areas of interest include:
1. Runtime engineering and governance: designing and refining FRAME pallets, validator/delegator logic, and governance mechanisms that make Polkadot resilient. 
2. Cross-chain communication: improving the developer and user experience of XCM, particularly around asset transfers, error handling, and cross-chain programmability. 
3. Consensus and scalability: exploring performance bottlenecks and contributing to solutions that enhance Polkadot’s throughput and security.

**Work Relevant to Polkadot SDK:**

- Implemented and tested a Delegated Proof-of-Stake pallet during PBA, including partially supporting delegation cycles, validator registering/staking, and reward distribution logic.

- Designed and tested XCM asset transfer flows between parachains and the relay chain, ensuring proper encoding/decoding of messages and error handling.

**GitHub Profile**
https://github.com/kdonthi

**Polkadot Address**
14fnnUEFRnJ1GxXPWxt7paewtKqjcjmAhiNKr1qavTkPRsxk

I look forward to use what I've learned and hopefully get to make an impact :) 

**Resume**
https://docs.google.com/document/d/1-z1mQyb_wbv1prlQ6paTAUX_7nW9zfqeKVNvygj_Csc/edit?usp=sharing


PBA Protocol Graduate and Blockchain Dev with ~4 years of Experience Interested in Making Polkadot Great

### Background Information

Hello, my name is Rodrigo Quelhas. I’m based in Portugal and currently work as a core developer at Moonbeam. I have over seven years of experience as a Blockchain Engineer, with the past four years focused primarily on the Polkadot ecosystem.

### Motivation

Having worked extensively with Substrate, Polkadot, and Cumulus for the past four years, I am eager to take a more active role in shaping the future of the ecosystem. Joining the Polkadot Technical Fellowship would give me the opportunity to stay closely aligned with the direction of core development, participate in important technical discussions, and contribute directly to the long-term health and evolution of the network.

### Areas of Interest

- Enhancing core libraries, runtime development, and performance optimization;
- Consensus and networking.

### Contributions to Polkadot SDK

I have contributed to the polkadot-sdk by fixing bugs, refactoring code, and implementing small features aimed at improving the overall development experience. These contributions have helped enhance code quality, maintainability, and usability for other developers working within the ecosystem.
A list of my merged pull requests can be found here:  [Polkadot SDK Contributions](https://github.com/paritytech/polkadot-sdk/pulls?q=is:pr+author:RomarQ+is:closed)

### GitHub Profile

You can find my GitHub profile here: https://github.com/RomarQ

Rodrigo Quelhas - Application

Dear Polkadot Community,

My name is Juan, and I am a graduate of PBA7 – Bali.

**Background**

I am a Full Stack Developer with 5 years of professional experience. I began my career in blockchain, but later transitioned into Web2 after receiving an opportunity to work on CERN’s open-source project, Indico: https://github.com/indico/indico

My main focus was developing a private plugin for this platform, which serves millions of users worldwide. While most of my contributions remain private, I successfully resolved several bugs and contributed features to the open-source project as well.

At the end of my contract in late 2024, I decided to return to Web3, completing both PBA-X and PBA programs.

**Motivation**

I am now eager to contribute to open-source projects within the Web3 space, and recently discovered the Polkadot Fellowship. My goal is to actively support the growth of the Polkadot ecosystem and, over time, advance within this community based on merit and contribution.

At present, I am familiarizing myself with the initial PR process and actively engaging with the community on Discord to identify areas where I can be most helpful. While my expertise is in backend development, I am also capable of working on frontend tasks, particularly with React, when necessary.

Here is my **GitHub profile** for reference: https://github.com/jbtwist

Given my current stage, I would like to kindly request the **Level 0 rank**.

Sincerely,
Juan

Applicant - Juan

<!DOCTYPE html>
<html lang="en">
<head>
 <meta charset="UTF-8">
</head>
<body>
 My name is Giorge Abdala, and I have over 15 years of experience as a Software Engineer and have been a passionate Linux enthusiast for more than two decades. I have developed a strong foundation in system architecture, complex problem-solving, and a deep passion for open-source technology.

 My involvement with the Polkadot ecosystem is active and growing. As an ambassador, I have represented Polkadot at major events in Brazil such as Blockchain Rio, Blockchain São Paulo, Smart City Expo (2024 and 2025) and Futurecom 2024.

 I co-organized the Decoded Party View Curitiba (2023) and gave talks at events such as 
 <a href="https://x.com/johnrhodelb/status/1802537176682377561?t=fo2umwqFT_zE5a621Z59NQ&s=19" target="_blank">Connection Week 2024</a> and 
 <a href="https://lu.ma/modularcuritiba?tk=SDzWVr" target="_blank">Modular Cripto 2024</a>, where I presented on Substrate and JAM.
 

 In 2025, I also participated in a 
 <a href="https://www.youtube.com/live/Bzs5IQRlagI?si=LEhz0K1S1PKUrZM6" target="_blank">podcast hosted by the Prefeitura de Curitiba</a>, where I spoke about Polkadot.
 

 These efforts reflect my commitment to knowledge-sharing and community building, which are core pillars of the Fellowship (Manifesto, sections 2.3.4 – Nurturing; 6.2 – I Dan). I am also responsible for running the first Polkadot full node in South America.

 It has always been a dream of mine to become a Substrate developer and join the Fellowship. Over the last two years, I have pursued a focused path of study, which included:

 <ul>
 <li>A deep dive into fundamental blockchain concepts: validation, consensus mechanisms, rollup functionality, and Layer 2 solutions.</li>
 <li>Progressive mastery of Rust:</li>
 </ul>

 I have read the entire Rust Book.

 
 I completed the course 
 <a href="https://www.udemy.com/certificate/UC-d98b39b2-f792-46a7-9758-b090d675dc10/" target="_blank">
 Rust: The Complete Developer's Guide</a> by Stephen Grider, which greatly clarified my understanding of ownership, borrowing, and generics.
 

 I also read 
 <a href="https://www.linkedin.com/posts/giorgeabdala_rust-rustaceans-programming-activity-7329130765433180160-B5Dk?utm_source=share&utm_medium=member_desktop&rcm=ACoAAD2V9AwBPpalTaVx7Kn3Rod0t-mv3uWkRsg" target="_blank">
 Rust for Rustaceans</a>, which explores advanced memory management concepts, concurrent programming, ownership, WASM, among others.


 This dedication to learning Rust resulted in practical applications. Professionally, I completely restructured a complex legacy system for processing tax credit requests for the state of Paraná/Brazil. I replaced an outdated architecture with a modern, high-performance Rust-based solution, reducing processing time from up to 48 hours to less than 30 seconds. This transformation demonstrates my ability to deliver “modest but substantial contribution to protocol development” (Manifesto, 6.2.1 - I Dan) and “elegant and, at least sometimes, reusable” implementations (Manifesto, p.9, III Dan).

 To complement my blockchain studies:

 I completed the Rust, Blockchain, and Polkadot Developer Formation course offered by Pontifical Catholic University of Paraná: 
 An advanced training focused on decentralized systems, smart contract development, Rust programming, Substrate-based blockchain networks, and Polkadot parachain architecture.
 

 I completed 
 <a href="https://app.kajabi.com/certificates/7360cc03" target="_blank">PBA-X</a>, the cohort-based, online blockchain course by the Polkadot Blockchain Academy — covering fundamental concepts in cryptography, economics, governance, interoperability, and using the Polkadot SDK.
 

I just finished reading the book 
 <a href="https://www.linkedin.com/posts/giorgeabdala_rust-blockchain-smartcontracts-activity-7335370243084541952-GUuO?utm_source=share&utm_medium=member_desktop&rcm=ACoAAD2V9AwBPpalTaVx7Kn3Rod0t-mv3uWkRsg" target="_blank">
 Rust for Blockchain</a>, which focuses on Rust concepts applied to blockchain, Substrate programming, pallets, FRAME, etc.


 In addition, I completed the 
 <a href="https://www.udemy.com/course/web3-academy-masterclass-rust/learn/lecture/45812449#overview" target="_blank">Web3 Academy Masterclass Rust</a> course by Web3 Surf. This course deepened my knowledge in developing pallets using Substrate FRAME, testing and benchmarking, working with off-chain workers, and performing runtime upgrades and migrations.
 

 I am currently practicing and studying through the Polkadot developer documentation (<a href="https://docs.polkadot.com/" target="_blank">https://docs.polkadot.com/</a>).

 My goal is to become a proficient Substrate developer, and I believe that the Polkadot Fellowship is the ideal environment to accelerate this growth. My aspiration is to reach the level of "Humble Member" (I Dan) and advance further over time. 
 I believe I am ready to face this challenge, and my intention is to start by solving GitHub issues, learning from more experienced members, and gradually taking on more responsibility. If anyone has suggestions for a “better path” or is willing to mentor me, I am completely open to discussion.

 
 Giorge Abdala 
 <a href="mailto:giorgeabdala@gmail.com">giorgeabdala@gmail.com</a> 
 <a href="https://www.linkedin.com/in/giorgeabdala" target="_blank">https://www.linkedin.com/in/giorgeabdala</a> 
 <a href="https://github.com/giorgeabdala" target="_blank">https://github.com/giorgeabdala</a>
 
</body>
</html>

Applications