📢 Gate Square #MBG Posting Challenge# is Live— Post for MBG Rewards!
Want a share of 1,000 MBG? Get involved now—show your insights and real participation to become an MBG promoter!
💰 20 top posts will each win 50 MBG!
How to Participate:
1️⃣ Research the MBG project
Share your in-depth views on MBG’s fundamentals, community governance, development goals, and tokenomics, etc.
2️⃣ Join and share your real experience
Take part in MBG activities (CandyDrop, Launchpool, or spot trading), and post your screenshots, earnings, or step-by-step tutorials. Content can include profits, beginner-friendl
The JAM protocol leads the new standards for Blockchain, with multiple languages and teams promoting the Web3 vision.
JAM protocol may become a new standard in the Blockchain industry
Last month, a group of developers and students completed their studies on Web3 in Lucerne, Switzerland. Gavin attended the graduation ceremony, conveying his blessings and vision to everyone. At the same time, several JAM protocol implementation teams shared their experiences of participating in JAM and their understanding of the protocol.
Whether you are a developer looking to join JAM or an ordinary user optimistic about the future of JAM, this article is worth a read.
The main content includes:
Introduction to the JAM Implementation Team
Tomek from Fluffy Labs stated that they implemented the JAM protocol using TypeScript, called Typeberry. In addition to development, they are also building a JAM-related toolchain to improve the development experience for other teams.
Daniel works in the jamixir team, implementing JAM with the Elixir language. He started this job after participating in the PBA course, learning while developing, and simultaneously sharing content on social media.
Maciej from the Graymatter team has also built the JAM implementation using Elixir. They are a part-time team of 4, focusing on collaboration with other teams. Maciej believes that JAM is the future of Polkadot, and its abstraction capabilities will unlock new possibilities.
Alistair is currently the Chief Scientist at the Web3 Foundation, primarily supporting the design of JAM from a theoretical perspective.
Kian works as a project manager in the Graymatter team and is involved in the JAM development part-time. He hopes to prepare for the future production environment launch by participating in early milestones.
Why Join JAM Development?
Tomek initially just found it interesting and wanted to participate part-time. He had participated in the development of Polkadot at Parity and believed that JAM was a great opportunity to return.
As a Polkadot developer, Maciej is often consulted about JAM-related issues. He believes it is his responsibility to understand, and the best way to do that is to build and read the gray paper himself.
Alistair is attracted to the data availability design of JAM. He believes that the understandable protocol specifications developed by JAM through the gray paper are an important step towards higher performance systems.
Daniel started to engage with JAM after participating in PBA. He believes in the Web3 vision proposed by Gavin and thinks that JAM is the best opportunity to achieve this goal.
Kian pointed out that regardless of background, anyone willing to invest in learning and practice can become a part of promoting JAM.
JAM Development Status: 38 Teams, 15 Languages
Currently, 38 teams have publicly participated in JAM development, covering about 15 programming languages. The goal of this diversity is not to deploy all versions in the production environment, but to cultivate an expert community and lay a talent foundation for future upgrades.
The core purpose of the award program is to promote ecological prosperity through knowledge decentralization. Currently, JAM has gathered hundreds of developers, who are ahead in deploying knowledge decentralization. In the future, the maintenance and upgrades of JAM will be completely independent of any single organization's control.
JAM and the Development Team's Short to Mid-term Goals
Tomek hopes to have a stable running testnet within a year. Their team plans to move on to developing a browser light client after completing the basic functionalities.
Daniel plans to stay in the JAM ecosystem for at least the next ten years. He really enjoys the current way of working: no company, no boss, no clients, just a group of like-minded people collaborating freely.
Maciej hopes to see preliminary execution environment results on JAM within a year (ELVES).
Alistair is concerned about what features can be included in the first version of JAM and which need to be postponed. He mentioned that in the future, JAM may need to establish its own fork management mechanism.
Polkadot Migration Path to JAM
Parachains still have a place in JAM, and there will be services to support their migration and operation. The specific migration plan is still under discussion. The basic idea is to first develop the Core Chain Service, which supports running parachains on JAM.
The goal of Parity and Fellowship is to achieve a seamless migration as much as possible. This year's multiple upgrades of Polkadot, especially the migration of functions from the Relay Chain to the System Chain, are preparing for a future switch to JAM.
Feelings about JAM and Future Expectations
Tomek believes that the versatility of JAM far exceeds the existing Polkadot architecture. He looks forward to seeing new services and new models based on JAM.
Daniel firmly believes that only Polkadot and JAM are still adhering to the true ideals of Web3. He thinks that if we are to achieve a genuine Web3, Polkadot and JAM are the only choices.
Alistair stated that the abstraction and generalization design in JAM can open up new possibilities, such as the Coreplay concept.
Maciej expects JAM to reconstruct the protocol in a more concise and abstract way, making it easier for developers and the community to understand.
The Potential Impact of JAM on the Blockchain Market
Maciej believes that JAM has the potential to become the industry standard. JAM will cover different segments and user groups, and in the future, the Polkadot ecosystem may cover the vast majority of needs.
Alistair emphasized that in addition to technical advantages, JAM also needs to improve in deployment and user experience, allowing more developers to conveniently build applications.
Daniel introduced the five stages of JAM development, from basic functionality implementation to production-level performance. Currently, there are 20-25 teams actively推进, and it is expected that at least 8 mature JAM implementation versions may ultimately be born.
Overall, the JAM protocol is attracting many developers to participate and is expected to become a new standard in the Blockchain industry. It not only inherits the philosophy of Polkadot but also brings higher performance and a better development experience. Whether JAM can truly realize the Web3 vision in the future is worth our continued attention.