LN-Zap / zap-desktop

13%

master: 22%

LAST BUILD ON BRANCH fix/private-channels-when-using-default

branch: fix/private-channels-when-using-default

CHANGE BRANCH

x

Reset

• fix/private-channels-when-using-default
• build
• build/publish-zap
• crowdin
• feat/assume-chan-valid
• feat/backups
• feat/bip21-address-parsing
• feat/ci-artifacts
• feat/close-channel-transaction-fee
• feat/crowdin
• feat/custom-csv-delay
• feat/hold-invoices
• feat/lnd-0.13.0-beta
• feat/lnd-0.14
• feat/lnd-0.9
• feat/lnd-11
• feat/multiple-themes
• feat/network-pill
• feat/next
• feat/password-confirm
• feat/private-0-conf-autopilot
• feat/settings
• feat/subscribe-htlc-events
• feature/multiple-fiat-currency-support
• fix/bech32-send
• fix/closing-channel-alias
• fix/closing-channel-link
• fix/login-copy
• fix/network-balance
• fix/pay-onchain
• fix/payInvoice
• fix/private-invoice
• fix/promise-resolve-reject
• fix/syncing-spacing
• greenkeeper/initial
• l10n_crowdin
• l10n_master
• master
• next
• v0.2.1-beta

Build # 3819

Build Type

Pull #699

travis-ci

Committed by web-flow

Commit Message

fix(channels): neutrino clients manual channels flagged private

Make sure that if a user of ours is using neutrino that we flag their
channels as private when they manually open them. Reason for this is
because light consumer clients are not expected to have high uptime.

However we cannot hardcode channels as private every time because we
do support more power users driving their remote nodes or BTCPay
Server with Zap. So we only flag channels as private if the
activeConnection is local.

Pull Request Pull Request #699: fix(channels): neutrino clients manual channels flagged private

Run Details

101 of 1242 branches covered (8.13%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 2 files covered. (100.0%)

512 of 3347 relevant lines covered (15.3%)

2.53 hits per line