update Readme to obtain coretime on Paseo

[seemantaggarwal]

Instructions for coretime purchase on paseo.

[kianenigma]

Reads okay to me, have you tried the steps exactly as-is, and confirm that it works?

[iulianbarbu]

Isn't this guide more or less what we have here: https://docs.polkadot.com/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/?

I am considering just mentioning the links:

1. https://docs.polkadot.com/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/
2. https://docs.polkadot.com/tutorials/polkadot-sdk/parachains/zero-to-hero/obtain-coretime/

Would this work?

[iulianbarbu]

Suggested change

[seemantaggarwal]

Yes, it is more or less that is in https://docs.polkadot.com/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/ however, this is a little more summarised, and adds up to this entire readme altogether, so that once somebody has created a parachain, they can get that dopamine to see its result to completion

[iulianbarbu]

nit (libp2p should be replaced in some places with litep2p, including on paseo)

Suggested change

	1. Before starting a collator, you need to generate a node key. This key is responsible for communicating with other nodes over Libp2p:
	1. Before starting a collator, you need to generate a node key. This key is responsible for communicating with peers as in a p2p network:

[seemantaggarwal]

@kianenigma I verified the original zero to hero tutorial, I will run this entire tutorial again, just to be sure, would also spot any other gaps and fix them, if any

[seemantaggarwal]

I tried it and it works, in case anybody wants to do a second round JIT, happy to wait for that. Additionally, I will just apply suggestions from @iulianbarbu and resolve conflicts before merging

[iulianbarbu]

Yes, it is more or less that is in https://docs.polkadot.com/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/ however, this is a little more summarised, and adds up to this entire readme altogether, so that once somebody has created a parachain, they can get that dopamine to see its result to completion

I see. Actually I don't have a strong opinion for removing the summary. What I would do more is maybe introduce the links to the zero-to-hero at the beginning of the Steps to Deploy section, before the summary. The main thing to mention is that "The links reference the same steps present in the summary below, with images, and they are focused on deploying runtimes in general on Paseo, while more parachain-template focused steps are described in the summary bellow". I'll leave this descision to you though.

LE: this suggestion is more for trying to dedup certain parts of our docs (which are mentioned in a few places), by referencing first and foremost a single place which is kept up to date with every release ideally, and to be first in the list of things people try.

[iulianbarbu]

You'd also need to add these new sections inside the ToC at the beginning of the file.

[iulianbarbu]

Should we have 2 # instead of 4, and 3 for the rest of sub steps? This one feels like a header title.