Skip to content

Commit

Permalink
Remove JAM timeframes (#5934)
Browse files Browse the repository at this point in the history
* Remove erroneous timeframe

* remove other timeframe mentions
  • Loading branch information
laboon authored Jun 1, 2024
1 parent 6e45951 commit baa01df
Showing 1 changed file with 5 additions and 10 deletions.
15 changes: 5 additions & 10 deletions docs/learn/learn-jam-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,8 +121,7 @@ but it is too early to jump into specific use cases just yet.

While specific timelines may vary, the development of JAM typically involves ongoing research,
testing, and iteration. The RFC will be published as a first step, where the community gives
feedback and iterates on it. The timeframe that JAM is expected to be production-ready is 20-60
months from its presentation at Token2049 in Dubai (April 2024), not including the service layer.
feedback and iterates on it.

## What about Polkadot? Will there be a hard fork?

Expand All @@ -137,20 +136,16 @@ layer.
## Do parachains need to rewrite their code? How much work is it to build?

Parachains will be one of the “products” that can run on JAM. JAM will only remove the enshrined
parachain consensus and replace it with a model that supports different services. For the first
years after launch, it will still be faster to develop parachains, as the necessary tooling for
developing services would need to be developed and adopted. For the migration support, full
parachain consensus and replace it with a model that supports different services. For some time,
it will likely be easier to develop parachains, as the necessary tooling for
developing services needs to be developed and adopted. For migration support, full
compatibility guarantees will be written into the code.

## Does it even make sense now to build a parachain on Polkadot?

Of course! Parachains will be one of the “products” that can run on JAM, and they will stay
first-class citizens. There will be different use cases, some suitable for parachains and some
suitable for services. Also, JAM is a research project in its very early stages (see
[the Gray paper](https://graypaper.com/)); not even the RFC is out. Until there is a
production-quality version of JAM, we are looking at a minimum time horizon of 20 months from its
presentation at Token2049 in Dubai (April 2024), not including any tooling or the layers needed to
build services on JAM.
suitable for services.

## What about DOT?

Expand Down

0 comments on commit baa01df

Please sign in to comment.