We JAM Implementers (as many as 3 dozen teams) are a dedicated community of engineers implementing JAM, which almost certainly will form the foundation of Polkadot’s technical future.
Under @gavofyork’s leadership, we are building nothing less than the future of trustless supercomputing together, from JAM to CoreChains+CoreVM+Coreplay and beyond.
Many JAM implementers are going to become JAM Service builders, JAM tool builders, JAM educators and generally missionaries of JAM, well beyond implementing JAM according to the graypaper.com spec.
The JAM Prize 10MM DOT pool, if distributed in accordance with Rule 25, contemplates the majority of it being locked and vesting over 2 years as teams race towards M5 and make impact as significant stakeholders in DOT+JAM’s future.
This will mean there will be a dozen or two significant stakeholders fully dedicated to Polkadot/JAM’s future, and support its future growth through OpenGov-based decision making.
We invite the W3F to consider JAM implementers as a DV in Cohort 4. Our collective participation will enable JAM implementers who are new to OpenGov to learn not only JAM but OpenGov and for JAM Implementers how to function as a “DAO” within it.
While collectively JAM implementers have NO experience voting together, we are going to learn how to work together as a group to achieve the “anti-fragile” future we seek going from tiny testnet to the JAM toaster.
Needless to say, a few teams have senior Polkadot fellowship members who know how OpenGov works on a technical basis (and the Polkadot SDK inside out!), a few teams have been significant OpenGov proposers/recipients/voters already. Many of us have met each other in person last November at JAM0, at JAM Meetups and increasingly in online monthly sessions.
The JAM Implementers DAO proposes to to conduct ourselves with 1 implementer, 1 vote publicly on all OpenGov tracks diligently and others as possible, utilizing JAM Testnet Telegram Group, docs.jamcha.in and the same Telegram bot used by Permanance DAO to coordinate our voting on a timely basis, and providing meaningful feedback similar to exemplary DVs in previous cohorts.
It is difficult to say what the “philosophy” of JAM implementers are on non-JAM topics, but biases toward JAM-centric decisions may be expected. We would anticipate issuing votes with at least 8-10 teams participating, and may coordinate voting as an social activity to engage with others while implementing JAM. If any conflicts of interest appear with members of the JAM Implementers DAO, those members will be excluded from the log.
Requirements to be part of the JAM DAO are simply to be listed on jamcha.in, which requires a PR to this repo maintained by JAMBrains.
Together, we look forward to ushering in Polkadot’s JAM/CoreVM/Coreplay/… future and engaging with the broader Polkadot community in the years ahead.
