Applications closed. Reviews done. It’s time to share who’s joining the Web3j mentorships this year under the Linux Foundation Decentralized Trust program. This year, there are two projects aimed at advancing Web3j, which is a highly modular, reactive, type safe Java and Android library for working with Smart Contracts and integrating with clients (nodes) on the Ethereum network.
Web3j Libraries Full Development Lifecycle Mentorship
We had 80 applications for this track. That meant reading through dozens of GitHub profiles, project write-ups, and technical goals. With so many strong candidates, choosing one didn’t make sense—so we didn’t.
AbdElrahman Hedia and Fangshuo Cao (Alston) are both coming on board. AbdElrahman impressed us with his familiarity with blockchain and a clear commitment to building clean, maintainable code. Fangshuo showed solid experience with Java tooling in his previous internships. Between them, we’re expecting serious momentum on improving web3j-unit, web3j-evm and web3j-openAPI. This includes syncing with recent EIPs, improving testing support, and simplifying life for anyone building long-term with Java and Ethereum.
Web3j: Enhancing JVM Android Support with Kotlin Wrappers Mentorship
For the Android-focused mentorship—building Kotlin-based wrappers for Solidity contracts—we had 50 applications. There’s growing interest in bringing Ethereum to Android in a native, modern way, and a lot of developers had smart takes on how to move that forward.
Gautham Mohanraj will be leading the effort. His Android experience is solid, and he made a strong case for how to improve both the usability and maintainability of web3j-android. The goal is to make contract interaction smoother in Kotlin, not just by porting the Java wrappers but by thinking through what a good Kotlin-native developer experience should look like.
What’s Next
All three mentees started on Monday, June 2nd. They’ll be working closely with George Tebrean (@gtebrean) and Nischal Sharma (@NickSneo), who are back again this year as mentors.
Everything will be happening in the open. Code, discussions, decisions—it’ll all be public in the #web3j-maintainers channel on Discord. If you want to follow the process, give feedback, or just see how things evolve over the next few months, hop in.
We’re thankful to every single person who applied. There were a lot of strong developers in the mix, and choosing just three wasn’t easy. If you didn’t get selected, we hope you’ll still stay involved. This community works best when more people show up, contribute, and share what they know. You can join our Web3j Contributors call to find out more.
Looking forward to what comes out of this round. Let’s keep shipping.
