DataHighway Node. A blockchain being built with Substrate to become a parachain on the Polkadot network. Planned features include a decentralized LPWAN roaming hub for LoRaWAN IoT devices and network operator roaming agreements, participative mining, an inter-chain data market, and DAO governance. http://www.datahighway.com
Morning, actually reading by https://substrate.dev/docs/en/tutorials/start-a-private-network/customspec it looks like the chain spec and definition files are generated only for custom chains which in our case would be brickable, harbour and westlake. So we just remove the files for --dev and --local chains and would have to update docs to use --dev or --local for those chain names instead of using files.
Why would it matter on which machine the files are generated, it should be possible to share and use them everywhere right? If there are still issues with wrong genesis or peer IDs then I think either a local chain DB is used and needs purging or the .env file sets a wrong node-key or peer-id.
Morning, actually reading by https://substrate.dev/docs/en/tutorials/start-a-private-network/customspec it looks like the chain spec and definition files are generated only for custom chains which in our case would be brickable, harbour and westlake. So we just remove the files for --dev and --local chains and would have to update docs to use --dev or --local for those chain names instead of using files.
Why would it matter on which machine the files are generated, it should be possible to share and use them everywhere right? If there are still issues with wrong genesis or peer IDs then I think either a local chain DB is used and needs purging or the .env file sets a wrong node-key or peer-id.