Start blockchain module

[kashepavadan]

No description provided.

[danisharora099]

I couldn't get past Step 2 on macOS, so flagging this as blocking. lgpm install rejects the released module:

package '...darwin.lgx' has no variant matching this platform:
         tried [darwin-arm64-dev], package provides [darwin-arm64].
Error: Package does not contain variant for platform: darwin-arm64-dev (package provides: darwin-arm64)

The tutorial-v3 lgpm/logoscore want a darwin-arm64-dev variant, but the v0.0.1 release only ships darwin-arm64 (unpacked the .lgx to confirm). There's no flag or env var to override it — --variant doesn't exist and LGPM_PORTABLE_BUILD=1 makes no difference. I confirmed the variant name is the only thing in the way: hand-staging the module and relabeling its variant to -dev is what finally let logoscore load it. The aarch64-linux/x86_64-linux assets are the same non--dev shape, so this probably isn't mac-only.

So this needs a fix outside the doc — either a release that ships the -dev variant the toolchain expects (v0.0.1 doesn't), the toolchain accepting the portable variant, or changing the doc to build the module from source like the other module tutorials. As written, the "macOS (aarch64)" support claim doesn't hold.

Because install is blocked I couldn't verify Steps 3–4 (load → generate_user_config → start → get_cryptarchia_info) — after my manual workaround the plugin hit a Qt @rpath issue that's almost certainly an artifact of hand-staging, not the doc, so those steps still need a real run once install works. The devnet deployment-settings fetch in 4.2 does work.

Smaller stuff inline. Blocking on the install.

[danisharora099]

This is the blocking step on macOS — lgpm install rejects the v0.0.1 release: tried [darwin-arm64-dev], package provides [darwin-arm64]. The tutorial-v3 lgpm/logoscore want the -dev variant but the release only ships darwin-arm64, and there's no flag/env to override (LGPM_PORTABLE_BUILD=1 doesn't help; relabeling the variant to -dev by hand is the only thing that got it to load). Needs a release shipping the -dev variant, the toolchain accepting the portable one, or a build-from-source path here.

[kashepavadan]

@strinnityk Take a look at this issue please.

[danisharora099]

This never says where the config goes, but Step 4.3 then feeds user_config.yaml to start. Worth stating that generate_user_config writes user_config.yaml (and to which directory).

[weboko]

Dogfooded on x86_64 Linux. Confirming the variant mismatch that danisharora099 found on macOS is a cross-platform issue that blocks Step 2 on all supported platforms.

Confirmed blocking — variant mismatch on Linux x86_64 too:

$ ./lgpm/bin/lgpm --modules-dir ./modules install --file logos-module-x86_64-linux.lgx
Warning: package 'logos-module-x86_64-linux.lgx' has no variant matching this platform: tried [linux-x86_64-dev, linux-amd64-dev], package provides [linux-amd64].
Error: Package does not contain variant for platform: linux-x86_64-dev (package provides: linux-amd64)

The v0.0.1 release ships linux-amd64 and darwin-arm64 variants; lgpm (tutorial-v3) expects linux-x86_64-dev/linux-amd64-dev (Linux) and darwin-arm64-dev (macOS). Every supported platform fails at Step 2.3. This needs a module release with -dev variants, or lgpm accepting the non-dev variant, before the tutorial is followable.

Missing Linux examples in Step 2: The doc claims to support Linux (x86_64 and aarch64) in the prerequisites but Step 2.1 (curl -L -O ...) and Step 2.2 (lgpm install ...) show only a macOS example. A Linux reader has no curl URL or install command to follow. Both steps need Linux equivalents alongside the macOS blocks.

generate_user_config output path (Step 4.1, unresolved from danisharora099): The step runs the command but never says where user_config.yaml is written. Step 4.3 then uses user_config.yaml by name, assuming it is in the working directory, but this should be stated explicitly.