| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-07-25 | 1.6 kB | |
| start-sdk v2.0.8 source code.tar.gz | 2026-07-25 | 17.1 MB | |
| start-sdk v2.0.8 source code.zip | 2026-07-25 | 18.7 MB | |
| Totals: 3 Items | 35.8 MB | 0 | |
What's Changed
Added
sdk.host.getBridgeAddressresolves the address another container reaches a dependency at, replacing a helper every package was copy-pasting. Packages resolved a dependency by readingbindings[<internalPort>].net.assignedPortand prefixinggetOsIp. That field is raw metadata: only one ofassignedPort/assignedSslPortis ever populated, and which one is a property of how the dependency bound the port — a binding withaddSslandsecure.sslfreesassignedPortentirely and carries onlyassignedSslPort, a passthrough binding is the reverse. So every caller was implicitly asserting how its dependency terminates TLS, and resolvednullthe day that changed, which is exactly what happened to LND's dependents when LND moved its REST interface behind the OS reverse proxy. The new helper resolves the binding's own derived address instead, which is correct under either arrangement, and returns aWatchableso callers get the sameconst/once/watch/onChange/waitForstrategies assdk.host.get. Because it keys off the binding rather than an exported interface, it also resolves bridge-only ports such as tor's SOCKS proxy.sslnarrows a binding that publishes both a plaintext and a TLS address (protocol: 'http'/'ws', orsecure: nullwithaddSsl— bitcoind's RPC is reachable at both);fallbackPortkeeps the value non-null while the dependency is absent, for a flag that must be passed unconditionally against an allocator-guaranteed port