fix: RPC port and Linux dev wallet + setup guide#22
Open
NorseT82 wants to merge 1 commit into
Open
Conversation
- chain.ts: add explicit :443 port to all DEFAULT_RPC_POOL entries; the
node binary (sentinel-dvpnx) requires an explicit port in RPC addresses
and rejects bare HTTPS URLs with "validating rpc config" — making fresh
deploys fail on v0.1.2 out of the box
- wallet.ts + index.ts: bypass OS keyring requirement in unpackaged Linux
builds so developers on WSL2/Linux can run from source without a system
keyring daemon
- docs/node-setup-guide.{md,html}: end-user Windows setup guide covering
install, Docker, wallet, port forwarding, deploy, and troubleshooting
(including the :443 fix for users with stale settings.json)
- RELEASE-NOTES-v0.1.2.md: full changelog for the v0.1.2 release
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
What
:443port to allDEFAULT_RPC_POOLentries inchain.ts. Thesentinel-dvpnxnode binary requires an explicit port in every RPC address and rejects bare HTTPS URLs, causing fresh deploys to fail with "validating rpc config" on v0.1.2 out of the box.wallet.ts/index.tsbypass the OS keyring requirement when the app runs unpackaged on Linux, so developers on WSL2/Linux can work from source without configuring gnome-keyring or kwallet.docs/node-setup-guide.mdanddocs/node-setup-guide.html: a full end-user Windows setup guide covering install → Docker → wallet → port forwarding → deploy → troubleshoot, including a workaround for the RPC config error for users with a stalesettings.json.RELEASE-NOTES-v0.1.2.mdcovering the full v0.1.2 changelog.Test
Deployed a node from source on WSL2 — confirmed Online status after applying these fixes. The RPC config error no longer appears on fresh deploy.