BlueHorseShoe · public node intelligence
Before you open, see the evidence.
A concise prospective-peer view for operators considering a channel. Start with the node's public posture, then inspect historical signals and reachability through its existing channels.
Inspect another public node
Paste a compressed node public key to request the same bounded view.
Public-network evidence is point-in-time and may be incomplete. BHS does not inspect private wallet or forwarding data.
Node under review
LIGHTNINGAUTO
0286cd362ed33373f669c7ac14241e8a71bf6efcd6fe578d9f02f2682dcd404eb9
No BHS snapshot yet
BHS has not assessed this node yet. You can request an assessment when ready.
Glossary
Definitions for the reachability evidence shown above.
- Direct Node → Peer
- Can a public route cross this specific channel from the node to a peer?
- Direct Peer → Node
- Can a public route cross this specific channel from the peer back to the node?
- Outbound From Node
- Can this channel act as the first step in routes from the node onward to the tested destinations?
- Inbound To Node
- Can this channel act as the final step in routes from the tested destinations back to the node?
- Route observations
- Public route results observed during the prepared tests. Routes observed means a route was constructed; Mixed results means results were not consistent across the tested conditions; Insufficient evidence means the evidence was not enough to assess the direction.
- Route-construction coverage
- The proportion of tested route constructions that produced a result, for example 1/1 (100%).
- Destination coverage
- The proportion of tested destinations for which a route result was observed, for example 1/1 (100%).
- Observed amount
- The payment amount used in a public routing test or the highest amount observed to route. It is not private liquidity, a channel balance or guaranteed forwarding capacity.