Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams are starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets going on sale again July 30 [here](<https://tickets.devcon.org/>) ). and sub0 proposed to happen in LATAM, we would like propose a JAM0 event to bring these teams together.

We have  at least \*SIX\* *serious implementors* who are interested in going to Devcon 7  and can connect their JAM implementations with each other.  This proposal aims to support their Devcon tickets and get the bulk of each team's travel budget reimbursed, up to $7.5K/team (with travel receipts, like 3-4 people/team on average). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](<https://hackmd.io/@polkadot/jamsnp>) at an event like this.

Budget: (estimated $118,313=19K DOT*$6.227/DOT)

- $75,000 Travel (10 teams x $7.5K/team)
- $43,313 Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Any unused budget from securing will be applied to a similar JAM0 event at sub0 (also focussed on _implementers+protocol devs_). 

Everyone will be required to follow the [official W3F rules](<https://jam.web3.foundation/rules>) and [unofficial "Rules" (from Gav)](<https://hackmd.io/@polkadot/jamprize>).

<h3>Venue:</h3>

We are collaborating with OneBlock on this, see [OpenGov Ref #897](https://polkadot.polkassembly.io/referenda/897).  The final venue  will be announced in August.  We will set up a JAM0 Matrix room for teams to follow along.

<h3>Teams:</h3>

See below.  If you are a serious implementor (or a protocol dev), please comment below!




Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams are starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets going on sale again July 30 [here](<https://tickets.devcon.org/>) ). and sub0 proposed to happen in LATAM, we would like propose a JAM0 event to bring these teams together.

We have  at least \*SIX\* *serious implementors* who are interested in going to Devcon 7  and can connect their JAM implementations with each other.  This proposal aims to support their Devcon tickets and get the bulk of each team's travel budget reimbursed, up to $7.5K/team (with travel receipts, like 3-4 people/team on average). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](<https://hackmd.io/@polkadot/jamsnp>) at an event like this.

Budget: (estimated $118,313=19K DOT*$6.227/DOT)

- $75,000 Travel (10 teams x $7.5K/team)
- $43,313 Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Any unused budget from securing will be applied to a similar JAM0 event at sub0 (also focussed on _implementers+protocol devs_).  If no sub0 event happens in early 2025, all excess funds wil.   

Everyone will be required to follow the [official W3F rules](<https://jam.web3.foundation/rules>) and [unofficial "Rules" (from Gav)](<https://hackmd.io/@polkadot/jamprize>).

<h3>Venue:</h3>

We are collaborating with OneBlock on this, see [OpenGov Ref #897](https://polkadot.polkassembly.io/referenda/897).  The final venue  will be announced in August.  We will set up a JAM0 Matrix room for teams to follow along.

<h3>Teams:</h3>

See below.  If you are a serious implementor (or a protocol dev), please comment below!




JAM0 Event @ Devcon 7 

Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams are starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets going on sale again July 30 [here](<https://tickets.devcon.org/>) ). and sub0 proposed to happen in LATAM, we would like propose a JAM0 event to bring these teams together.

We have  at least \*SIX\* *serious implementors* who are interested in going to Devcon 7  and can connect their JAM implementations with each other.  This proposal aims to support their Devcon tickets and get the bulk of each team's travel budget reimbursed, up to $7.5K/team (with travel receipts, like 3-4 people/team on average). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](<https://hackmd.io/@polkadot/jamsnp>) at an event like this.

Budget: ($118,313=19K DOT*$6.227/DOT)

- $75,000 Travel (10 teams x $7.5K/team)
- $43,313 Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Any unused budget from securing will be applied to a similar JAM0 event at sub0 (also focussed on _implementers+protocol devs_).  If no sub0 event happens in early 2025, all excess funds wil.   

Everyone will be required to follow the [official W3F rules](<https://jam.web3.foundation/rules>) and [unofficial "Rules" (from Gav)](<https://hackmd.io/@polkadot/jamprize>).

<h3>Venue:</h3>

We are collaborating with OneBlock on this, see [OpenGov Ref #897](https://polkadot.polkassembly.io/referenda/897).  The final venue  will be announced in August.  We will set up a JAM0 Matrix room for teams to follow along.

<h3>Teams:</h3>

See [https://polkadot.polkassembly.io/post/2397](2397)





<p>Amazingly, there are over <em>10+</em> teams implementing JAM:</p>
<p><a href="https://jamcha.in/clients">https://jamcha.in/clients</a></p>
<p>Some teams are starting to pass the first few tests with available <a href="https://github.com/w3f/jamtestvectors/">test vectors, </a>are asking detailed questions about the <a href="https://graypaper.com">JAM Gray Paper</a> in the <a href="https://matrix.to/#/#graypaper:polkadot.io">GP Chat Room</a> and <a href="https://matrix.to/#/#jam:polkadot.io">JAM Chat Room</a>.</p>
<p>With Devcon 7 in Thailand in November (tickets going on sale again July 30 <a href="https://tickets.devcon.org/">here</a>&nbsp; ). and sub0 proposed to happen in LATAM, we would like propose a JAM0 event to bring these teams together.</p>
<p>We should like to see at least *SIX* <em>serious implementors</em> who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like ~3 people/team).&nbsp;As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know _exactly_ where they are bottlenecked, and basically be ready to network their implementations with other teams with <a href="https://hackmd.io/@polkadot/jamsnp">QUIC</a> at an event like this.</p>
<p>Budget: (very back of the envelope)</p>
<ul>
<li>$48K-60K Travel (8-10 teams x $6K/team)</li>
<li>$48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling</li>
</ul>
<p>Everyone will be required to follow the <a href="https://jam.web3.foundation/rules">official W3F rules</a> and <a href="https://hackmd.io/@polkadot/jamprize">unofficial "Rules" (from Gav)</a>.</p>
<p>Interested? Please share your interest below!</p>
<ol>
<li>Team name (add to <a href="https://jamcha.in/clients">https://jamcha.in/clients</a> )</li>
<li>Confirm you believe your team is a <em>serious</em> implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025</li>
<li>Number of people on your team you want reimbursement for Devcon 7</li>
<li>Number of people on your team you want reimbursement for sub0 LATAM</li>
<li>Indication that you want to volunteer to help organize JAM0 events&nbsp;(coordinate food, usher people, man a desk, etc.)</li>
</ol>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>

JAM0 Event @ Devcon 7 and/or Sub0 LATAM?

<p>Amazingly, there are over <em>10+</em> teams implementing JAM:</p>
<p><a href="https://jamcha.in/clients">https://jamcha.in/clients</a></p>
<p>Some teams starting to pass the first few tests with available <a href="https://github.com/w3f/jamtestvectors/">test vectors, </a>are asking detailed questions about the <a href="https://graypaper.com">JAM Gray Paper</a> in the <a href="https://matrix.to/#/#graypaper:polkadot.io">GP Chat Room</a> and <a href="https://matrix.to/#/#jam:polkadot.io">JAM Chat Room</a>.</p>
<p>With Devcon 7 in Thailand in November (tickets going on sale again July 30 <a href="https://tickets.devcon.org/">here</a>&nbsp; ).</p>
<p>We should like to see at least *SIX* <em>serious implementors</em> who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like ~3 people/team).&nbsp;As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know _exactly_ where they are bottlenecked, and basically be ready to network their implementations with other teams with <a href="https://hackmd.io/@polkadot/jamsnp">QUIC</a> at an event like this.</p>
<p>Budget: (very back of the envelope)</p>
<ul>
<li>$48K-60K Travel (8-10 teams x $6K/team)</li>
<li>$48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling</li>
</ul>
<p>Everyone will be required to follow the <a href="https://jam.web3.foundation/rules">official W3F rules</a> and <a href="https://hackmd.io/@polkadot/jamprize">unofficial "Rules" (from Gav)</a>.</p>
<p>Interested? Please share your interest below!</p>
<ol>
<li>Team name (add to <a href="https://jamcha.in/clients">https://jamcha.in/clients</a> )</li>
<li>Confirm you believe your team is a <em>serious</em> implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025</li>
<li>Number of people on your team you want reimbursement for Devcon 7</li>
<li>Number of people on your team you want reimbursement for sub0 LATAM</li>
<li>Indication that you want to volunteer to help organize JAM0 events&nbsp;(coordinate food, usher people, man a desk, etc.)</li>
</ol>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>

Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Everyone will be required to follow the [official W3F rules](https://jam.web3.foundation/rules) and [unofficial "Rules" (from Gav)](https://hackmd.io/@polkadot/jamprize).  

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](https://jamcha.in/clients) )
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Number of people on your team you want reimbursement for Devcon 7 
4. Number of people on your team you want reimbursement for sub0 LATAM
5. Indication that you want to volunteer to help organize JAM0 events (coordinate food, usher people, man a desk, etc.)


Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Everyone will be required to follow the [official W3F rules](https://jam.web3.foundation/rules) and [unofficial "Rules" (from Gav)](https://hackmd.io/@polkadot/jamprize).  

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](https://jamcha.in/clients) )
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Number of people on your team you want reimbursement for Devcon 7 
4. Number of people on your team you want reimbursement for sub0 LATAM
5. Indication that you want to volunteer to help organize JAM0 events (coordinate food, usher people, man a desk, etc.)


Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Here are some "Rules":

- Cooperation between teams is essential but anything which goes beyond trivial misunderstandings of the Graypaper should be documented, either as issues in the GP repo or as side notes of the implementation to be submitted at the time of Fellowship review.
- Teams should stay away from implementation specifics and definitely NOT be sharing code at an event like this.   It's ok to ruminate on high level approaches to solve problems or optimize, it's not so ok to be looking at some other implementation's specific solution. What the Fellowship will be looking out for is for undeclared collusion between teams. Code which appears to be a little too similar for it to have been independently written. A big red flag would be the same bug popping up in two implementations.
- But this is not to detract from the fun of getting two cleanroom implementations talking to each other. This is a big part of this JAM0 and _is_ explicitly allowed. However, teams must be sure to document anything which are discovered alongside another team so _everyone can benefit_.

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](https://jamcha.in/clients) )
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Number of people on your team you want reimbursement for Devcon 7 
4. Number of people on your team you want reimbursement for sub0 LATAM
5. Indication that you want to volunteer to help organize JAM0 events (coordinate food, usher people, man a desk, etc.)


Amazingly, there are over *10+* teams implementing JAM and many many more ([58](https://x.com/alice_und_bob/status/1813261453488758875)) that have applied:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).  

We envision a couple of rooms capable of holding 50 implementors with PLENTY of food open for 14 hours (e.g. 9am-11pm).  We imagine very few talks and people just working together to connect JAM implementations, but potentially we could have a topic per day from a key protocol engineer.  

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Here are some "Rules":

- Cooperation between teams is essential but anything which goes beyond trivial misunderstandings of the Graypaper should be documented, either as issues in the GP repo or as side notes of the implementation to be submitted at the time of Fellowship review.
- Teams should stay away from implementation specifics and definitely NOT be sharing code at an event like this.   It's ok to ruminate on high level approaches to solve problems or optimize, it's not so ok to be looking at some other implementation's specific solution. What the Fellowship will be looking out for is for undeclared collusion between teams. Code which appears to be a little too similar for it to have been independently written. A big red flag would be the same bug popping up in two implementations.
- But this is not to detract from the fun of getting two cleanroom implementations talking to each other. This is a big part of this JAM0 and _is_ explicitly allowed. However, teams must be sure to document anything which are discovered alongside another team so _everyone can benefit_.

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](<https://jamcha.in/clients)>))
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Specify number of team members you have at Devcon 7 for your JAM team at a "JAM0" event
4. Specify number of team members you have sub0 LATAM for your JAM team at a "JAM0" event
5. Indication that you want to volunteer to help organize JAM0 events 


JAM0 Event @ Devcon 7 and/or Sub0 LATAM

Amazingly, there are over *10+* teams implementing JAM and many many more ([58](https://x.com/alice_und_bob/status/1813261453488758875)) that have applied:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Here are some "Rules":

- Cooperation between teams is essential but anything which goes beyond trivial misunderstandings of the Graypaper should be documented, either as issues in the GP repo or as side notes of the implementation to be submitted at the time of Fellowship review.
- Teams should stay away from implementation specifics and definitely NOT be sharing code at an event like this.   It's ok to ruminate on high level approaches to solve problems or optimize, it's not so ok to be looking at some other implementation's specific solution. What the Fellowship will be looking out for is for undeclared collusion between teams. Code which appears to be a little too similar for it to have been independently written. A big red flag would be the same bug popping up in two implementations.
- But this is not to detract from the fun of getting two cleanroom implementations talking to each other. This is a big part of this JAM0 and _is_ explicitly allowed. However, teams must be sure to document anything which are discovered alongside another team so _everyone can benefit_.

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](<https://jamcha.in/clients)>))
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Reimbursement request for Devcon 7 for your JAM team
4. Reimbursement request for sub0 for your JAM team
5. Indication that you want to volunteer to help organize JAM0 events 


Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Here are some "Rules":

- Cooperation between teams is essential but anything which goes beyond trivial misunderstandings of the Graypaper should be documented, either as issues in the GP repo or as side notes of the implementation to be submitted at the time of Fellowship review.
- Teams should stay away from implementation specifics and definitely NOT be sharing code at an event like this.   It's ok to ruminate on high level approaches to solve problems or optimize, it's not so ok to be looking at some other implementation's specific solution. What the Fellowship will be looking out for is for undeclared collusion between teams. Code which appears to be a little too similar for it to have been independently written. A big red flag would be the same bug popping up in two implementations.
- But this is not to detract from the fun of getting two cleanroom implementations talking to each other. This is a big part of this JAM0 and _is_ explicitly allowed. However, teams must be sure to document anything which are discovered alongside another team so _everyone can benefit_.

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](<https://jamcha.in/clients)>))
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Number of people on your team you want reimbursement for Devcon 7 
4. Number of people on your team you want reimbursement for sub0 LATAM
5. Indication that you want to volunteer to help organize JAM0 events (coordinate food, usher people, man a desk, etc.)


Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Here are some "Rules":

- Cooperation between teams is essential but anything which goes beyond trivial misunderstandings of the Graypaper should be documented, either as issues in the GP repo or as side notes of the implementation to be submitted at the time of Fellowship review.
- Teams should stay away from implementation specifics and definitely NOT be sharing code at an event like this.   It's ok to ruminate on high level approaches to solve problems or optimize, it's not so ok to be looking at some other implementation's specific solution. What the Fellowship will be looking out for is for undeclared collusion between teams. Code which appears to be a little too similar for it to have been independently written. A big red flag would be the same bug popping up in two implementations.
- But this is not to detract from the fun of getting two cleanroom implementations talking to each other. This is a big part of this JAM0 and _is_ explicitly allowed. However, teams must be sure to document anything which are discovered alongside another team so _everyone can benefit_.

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](<https://jamcha.in/clients)>))
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. # of people on your team you want reimbursement for Devcon 7 
4. # of people on your team you want reimbursement for sub0 LATAM
5. Indication that you want to volunteer to help organize JAM0 events (coordinate food, usher people, man a desk, etc.)


Amazingly, there are over *10+* teams implementing JAM:

[https://jamcha.in/clients](<https://jamcha.in/clients>)

Some teams starting to pass the first few tests with available [test vectors, ](<https://github.com/w3f/jamtestvectors/>)are asking detailed questions about the [JAM Gray Paper](<https://graypaper.com>) in the [GP Chat Room](<https://matrix.to/#/#graypaper:polkadot.io>) and [JAM Chat Room](<https://matrix.to/#/#jam:polkadot.io>).

With Devcon 7 in Thailand in November (tickets went on sale [https://tickets.devcon.org/](<https://tickets.devcon.org/),>)), I suggest that we have a JAM presence there and/or do something similar in sub0 LATAM (see this [post](<../post/2396>)).

We should like to see at least \*SIX\* *serious implementors* who are basically going to Devcon 7 and/or sub0 LATAM and wish to connect their JAM implementations with each other. I think we should support their Devcon tickets and get a bit of travel budget reimbursed, like $6K/team (with travel receipts, like \~3 people/team). As of Fall 2024, "serious implementors" should be pretty close to passing "JAM Milestone 1" and not be in "just learning" mode, be able to pass "Block Import" tests (when available) or at least passing most all test vectors available and know \_exactly\_ where they are bottlenecked, and basically be ready to network their implementations with other teams with [QUIC](https://hackmd.io/@polkadot/jamsnp) at an event like this.

Budget: (very back of the envelope)

- $48K-60K Travel (8-10 teams x $6K/team)
- $48K-60K Venue + Food for JAM Implementors + core devs working on PolkaVM + related tooling

Here are some "Rules":

- Cooperation between teams is essential but anything which goes beyond trivial misunderstandings of the Graypaper should be documented, either as issues in the GP repo or as side notes of the implementation to be submitted at the time of Fellowship review.
- Teams should stay away from implementation specifics and definitely NOT be sharing code at an event like this.   It's ok to ruminate on high level approaches to solve problems or optimize, it's not so ok to be looking at some other implementation's specific solution. What the Fellowship will be looking out for is for undeclared collusion between teams. Code which appears to be a little too similar for it to have been independently written. A big red flag would be the same bug popping up in two implementations.
- But this is not to detract from the fun of getting two cleanroom implementations talking to each other. This is a big part of this JAM0 and _is_ explicitly allowed. However, teams must be sure to document anything which are discovered alongside another team so _everyone can benefit_.

Interested? Please share your interest below!

1. Team name (add to [https://jamcha.in/clients](<https://jamcha.in/clients)>))
2. Confirm you believe your team is a *serious* implementor dedicated to passing Milestone 1 by Devcon 7 / sub0 LATAM by November 2024 / Feb 2025
3. Reimbursement request for Devcon 7 for your JAM team
4. Reimbursement request for sub0 for your JAM team
5. Indication that you want to volunteer to help organize JAM0 events 


- **Problem Statement:** Organizing a JAM0 event to bring together teams implementing JAM, aiming to support Devcon 7 tickets and reimburse travel budgets up to $7.5K/team.
- **Significance:** Facilitating collaboration among serious implementors close to passing "JAM Milestone 1" and ready to network their implementations with other teams.
- **Proposed Solution:** Hosting a JAM0 event with a budget of $118,313, covering travel costs for 10 teams and venue/food expenses for JAM Implementors and core devs.
- **Expected Outcomes:** Strengthened networking among implementers and protocol developers, following official W3F rules and guidelines.

#2397 JAM0 Event @ Devcon 7

No Active Proposals