JAM protocol development progress: 38 teams implementing 15 languages reveal Polkadot migration path.

Last month, another group of developers and students completed their learning about Web3 in Lucerne, Switzerland. Several JAM protocol implementation teams shared their journeys in JAM and their deep understanding of the JAM protocol with graduates at the event.

Abstract of the article:

• Introduction to the JAM implementation team and the motivation for joining JAM
• JAM development status: 38 teams, 15 languages, free collaboration model
• JAM and the development team's mid to short-term goals
• Polkadot Migration Path Analysis to JAM
• Feelings about JAM and future expectations
• The impact of JAM on the blockchain market

Introduction of the JAM implementation team

Tomek is from Fluffy Labs, where they implement the JAM protocol using TypeScript, called Typeberry. Daniel works with the jamixir team, implementing JAM in Elixir. Maciej is with the Graymatter team, also building the JAM implementation using Elixir. Alistair serves as the Chief Scientist at the Web3 Foundation, providing theoretical support for JAM design. Kian serves as the Project Manager at the Graymatter team.

Why join JAM development?

Tomek believes that JAM is a good opportunity to return to blockchain development. Maciej is confident that JAM can bring new features. Alistair is attracted by JAM's data availability design. Daniel hopes to participate in creating a truly decentralized, permissionless, and attack-resistant system. Kian states that regardless of background, anyone willing to invest in learning and practice can become a part of promoting JAM.

Current Development Status of JAM

Currently, 38 teams have publicly participated, covering about 15 programming languages. The JAM reward program incentivizes developers from different backgrounds to independently implement the protocol. The JAM testnet will be launched in Lisbon in May, and a data center named JAM Toaster will be built for large-scale network stress testing.

The short and medium-term goals of JAM and the team

Tomek hopes to have a stable running testnet within a year. Daniel plans to stay in the JAM ecosystem for the next ten years. Maciej hopes to see initial execution environment results running on JAM within a year. Alistair is concerned about what features the first version of JAM will include.

Polkadot migration path to JAM

Parachains still have a place in JAM. First, develop the Core Chain Service to support the operation of parachains. The goal of Parity and Fellowship is to achieve seamless migration as much as possible. Polkadot's multiple upgrades this year are preparing for a future switch to JAM.

Feelings and expectations for JAM

Tomek believes that JAM has opened up many new possibilities. Daniel thinks that only Polkadot and JAM are adhering to the true ideals of Web3. Alistair states that the abstract and generalized design of JAM can bring new opportunities. Maciej looks forward to JAM giving birth to new innovations.

The impact of JAM on the blockchain market

Multiple developers believe that JAM has the potential to become the industry standard. It will cover different niche markets and user groups, providing comprehensive smart contract tools. However, further improvements in deployment and user experience are needed.

The development of the JAM protocol is divided into 5 stages, from the implementation of basic functions to the final audit. Currently, there are about 20-25 teams actively promoting development, and ultimately, 8 mature versions of the JAM implementation may emerge.