Skip to content

Solo-dev node setup + Dockerfile lockfile fix #925

@linear

Description

@linear

What

A fresh single-node deployment of the stabilisation branch does not produce blocks until its own identity is seeded into the genesis validator set. The legacy genesis path explicitly does not auto-seed, so a new operator hits a silent stall on first run.

A second item, separate but related, is a Dockerfile snag around COPY ... bun.lock with --frozen-lockfile: a plain bun install unblocks the image build but the documented setup hits the frozen-lockfile error first.

Why this matters — and why it is low priority

Pure operator experience. Anyone bringing up a node solo for the first time has a confusing onboarding moment. The fix does not affect any deployed network and does not change consensus. Worth landing once the higher-severity items (#922, #923) are clear.

Fix

A "solo-dev mode" setup change that seeds the operator's identity into the genesis validator set on first run, plus the Dockerfile tweak so the image builds without a lockfile workaround.

Source

PATH-OS L2PS hardening report (item 4). They offered to send the setup PR.

Status

Todo. Low priority.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions