End to end example or link to relevant docs

[KarimJedda]

The tool works great for creating the contract files locally.

This issue is to either udpate the README or add the necessary steps to deploy the contract, and verify it has successfully deployed on either Paseo, Kusama or Polkadot.

If we can add "common failure scenarios and how to troubleshoot them", it's even better. If these steps above can be tested and validated (not on a local dev machine, and not with already existing developer accounts, then better).

Thank you very much!

[pgherveou]

@KarimJedda

Indeed having integration testing on everything that the tool does here would be nice.
I suppose we can easily add some testnet private key in GH and have these account funded so that they can run the whole thing and report back

[smiasojed]

This could probably be part of our Foundry. It supports custom compilers, testing, uploading, and verification.
Foundry currently supports Vyper and Solidity and could likely be extended to Rust. That way, we’d have everything in one place. WDYT?

[KarimJedda]

@smiasojed That’s an interesting idea for a future enhancement but let's not lose focus on the immediate objective here.

I need this specific repository to be self-contained. We should not require a dependency on Foundry to deploy a contract created by cargo-pvm-contract.

We need to be careful not to stop at the technical feat and forget the "last mile" of usability. Currently, our product teams are having to reverse-engineer tooling from first principles just to figure out how to document it. We should treat the tool and its internal docs as a complete input for them and not a puzzle to solve.

To consider this issue closed, I need a guide residing in this repo that takes the user to a fully working, deployed state (on Paseo/Polkadot etc) without external tooling dependencies. If we want adoption, we need to do better than the current status quo.

To get you started, from our team:

• https://github.com/paritytech/cargo-pvm-contract/blob/charles/cdm-integration/docs/guide.md#deployment-papi