Conflicts when adding pallet to substrate-node-template
I am running substrate-node-template version v2.0.0-rc6. I am able to build the stock image fine.
When I add
[dependencies.pallet-did]
default-features = false
git = 'https://github.com/substrate-developer-hub/pallet-did.git'
tag = 'v2.0.0-rc4'
version = '2.0.0-rc4'
to runtime/Cargo.toml and try to build I get the following error:
Updating git repository `https://github.com/substrate-developer-hub/pallet-did.git`
Updating git repository `https://github.com/paritytech/substrate.git`
Updating crates.io index
error: failed to select a version for `parity-util-mem`.
... required by package `sp-core v2.0.0-rc4 (https://github.com/paritytech/substrate.git?tag=v2.0.0-rc4#00768a1f)`
... which is depended on by `frame-support v2.0.0-rc4 (https://github.com/paritytech/substrate.git?tag=v2.0.0-rc4#00768a1f)`
... which is depended on by `frame-system v2.0.0-rc4 (https://github.com/paritytech/substrate.git?tag=v2.0.0-rc4#00768a1f)`
... which is depended on by `pallet-did v2.0.0-rc4 (https://github.com/substrate-developer-hub/pallet-did.git?tag=v2.0.0-rc4#03d58d86)`
... which is depended on by `node-template-runtime v2.0.0-rc6 (/home/ubuntu/Documents/synced/runtime)`
... which is depended on by `node-template v2.0.0-rc6 (/home/ubuntu/Documents/synced/node)`
versions that meet the requirements `^0.6.1` are: 0.6.1
I have also followed HOWTO.md and changed the version to rc3, same issue.
I get the same issue when trying to install the EVM Pallet version 2.0.0 into a substrate template version 3.0.0 when following the first section of the Frontier Workshop
Please help!
Hi @srinjoychakravarty - for the path of least resistance, closely follow the commits that that Fronier workshop is based on. This diff also gives you what you'll need to make things compile. For EVM pallet version 2.0.0 its advised to stick to the Node template 2.0. Hope this helps!
@sacha-l is there any node config that has both the evm pallet and the ink contracts pallet combined that you can point me to? Or is this currently not possible due to version mismatch... 🤔
It's possible if you configure it yourself :)
@MatthewDarnell did you find a solution in the end?
@NunoAlexandre I don't remember but I don't think so, I usually follow up open issues/questions with a found solution.
I have the same problem...@MatthewDarnell did you solve it?
I have the same problem...@MatthewDarnell did you solve it?
@NunoAlexandre I don't remember but I don't think so, I usually follow up open issues/questions with a found solution.
I'm also getting this issue in parity-kitty template when trying to add pallet-commodity in that.
Hi @stephanJ248 - the pallet_commodity you referenced is very out-dated. It uses a version of Substrate that won't work with the latest node template out of the box (unless you downgrade all dependencies to some Substrate commit from circa early-mid 2020 I would guess).
If there are functionalities you are looking to integrate such as mint, burn or transfer, I recommend you either write your own pallet or use the existing pallet_uniques which is what is used in several production chains.