Last active
October 21, 2025 10:40
-
-
Save SulaimanAminuBarkindo/dfce9e079f2b7782d86a1044585479d7 to your computer and use it in GitHub Desktop.
vls-hsmd-mac-setup
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 1. Run brew install autoconf automake libtool gmp sqlite3 pkg-config \ | |
| python3 git gettext protobuf grpc openssl libpq jq gawk mold \ | |
| libsodium curl lowdown | |
| 2. Run brew install pipx | |
| pipx ensurepath | |
| pipx install poetry to install poetry | |
| 3. if you’re not inside a venv yet: | |
| python3 -m venv .venv | |
| source .venv/bin/activate | |
| then run pip install mistune==0.8.4 mrkd==0.2.0 | |
| 4. git clone https://gitlab.com/lightning-signer/vls-hsmd.git && cd vls-hsmd | |
| git checkout <branch-tag-or-main> | |
| make setup | |
| git fetch --all --recurse-submodules --tags | |
| 5. ./scripts/enable-githooks | |
| 6. if trouble with "KeyringLocked": | |
| export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring | |
| cd ~/lightning-signer/vls-hsmd && make build | |
| if it err due to race condition with sed run: | |
| cd lightning | |
| make distclean | |
| poetry install --no-root | |
| ./configure | |
| poetry run make -j1 | |
| then next step: | |
| cd ~/lightning-signer/vls-hsmd/lightning && poetry run make | |
| ensure you are using python3.11 or below may work I guess have not tried | |
| then poetry env use /opt/homebrew/bin/python3.11 | |
| 7. cd ~/lightning-signer/vls-hsmd && \ | |
| make test-one TEST=tests/test_pay.py::test_pay | |
| Note: you may come across an error `OSError: AF_UNIX path too long` happens due to the length of the tmp folder path stored in the bash variable $TMPDIR is too long. so just maybe move the repo to /tmp or somewhere with short path. | |
| you can run mv ~/lightning-signer/vls-hsmd /tmp/vls | |
| cd /tmp/vls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment