Clarify macOS and API port setup for blockchain node quickstart#272
Open
Devpen787 wants to merge 1 commit into
Open
Clarify macOS and API port setup for blockchain node quickstart#272Devpen787 wants to merge 1 commit into
Devpen787 wants to merge 1 commit into
Conversation
Contributor
|
We've added macOS release paths to the tutorial. Feel free to resolve the conflicts and we'll review the PR again. |
weboko
reviewed
Jun 19, 2026
weboko
left a comment
Contributor
There was a problem hiding this comment.
Dogfooded on Ubuntu 24.04.4 LTS x86_64. Followed the full quickstart with the changes in this PR applied.
What worked:
- Both URLs (circuits + node) for release 0.1.2 resolve correctly. The original
0.1.3-rc.1circuits URL also resolves but points to a different asset; pinning both to0.1.2is the right call for consistency. tar -xf,mvto~/.logos-blockchain-circuits,initwith bootstrap peers, and--check-configall pass cleanly.lsof -nP -iTCP:8080 -sTCP:LISTENworks on Linux. Node API came up correctly on the default port.- Both
curlAPI endpoints (/cryptarchia/info,/network/info) returned expected JSON. Node started and reachedBootstrappingmode. Bootstrap peers at 65.108.203.235 timed out — expected, doc correctly says to use current addresses from the release notes.
Cannot verify: macOS (macos-aarch64) section — running on Linux x86_64. macOS asset URLs verified via HEAD request (HTTP 302 → valid).
Pre-existing gap (not introduced by this PR): jq is used in the curl commands but not listed in prerequisites. Worth a follow-up in the base doc.
Changes are accurate and improve the doc. LGTM.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.1.2Related to #213.
Why
I dogfooded the headless Logos Blockchain node quickstart from
logos-co/logos-docs#213.On an Apple silicon Mac, the latest
0.1.2release includes runnablemacos-aarch64node and circuits assets, but the quickstart prerequisites only mention Linux x86_64 and Raspberry Pi. The macOS binary ran locally,initgenerateduser_config.yaml, and--check-configpassed.I also hit a local port collision on
8080. The node logged that it could not bind the API server, but the process continued running. Because another local service was already listening on8080, the guide'scurl localhost:8080/...checks returned a response from the wrong service. After changingapi.backend.listen_addressto127.0.0.1:18080, the documented API checks worked with the adjusted port.Evidence
logos-blockchain/logos-blockchainlatest release0.1.2logos-blockchain-circuits-v0.4.2-macos-aarch64.tar.gzlogos-blockchain-node-macos-aarch64-0.1.2.tar.gz./logos-blockchain-node --version./logos-blockchain-node --help./logos-blockchain-node init ..../logos-blockchain-node --check-config user_config.yaml./logos-blockchain-node user_config.18080.yamlcurl -s http://localhost:18080/cryptarchia/infocurl -s http://localhost:18080/network/info./logos-blockchain-node --versionoutput:Observed API output after using port
18080:{ "lib": "646088a81f76e6a6ae35b3cc87f33c9081c12b02932604eee427593251f72bec", "lib_slot": 0, "tip": "646088a81f76e6a6ae35b3cc87f33c9081c12b02932604eee427593251f72bec", "slot": 0, "height": 0, "mode": "Bootstrapping" }{ "listen_addresses": [ "/ip4/127.0.0.1/udp/3000/quic-v1", "/ip4/192.168.1.4/udp/3000/quic-v1" ], "peer_id": "12D3KooWAqVd6dspmppz6Zu7988avyfoBqPB7tCwT7Yyauq6LWg1", "n_peers": 4, "n_connections": 4, "n_pending_connections": 0 }Notes
I did not continue to faucet/token steps because the guide says to wait until the node reaches
Onlinemode first.