search

omnilaboratory / obd

OmniBOLT daemon, a golang implementation of OmniBOLT spec, the smart assets lightning network.
MIT License
213 stars 21 forks source link

Fix NodePeerId Check #22

Closed johng closed 3 years ago

johng commented 3 years ago

If Peer is remote it won't appear in local tracker, need to only check P2P channel map

neocarmack commented 3 years ago

Let me clarify it:

you depolyed an obd in remote and a tracker in local? Do you config your obd to connect your tracker? A tracker better has static ip address otherwise obd can not locate it.

At this stage, we suggest user to use public tracker, because currently tracker is not fully decentralized. It helps nodes to find payment path, so that a tracker must collect nodes/channels balances. Multiple trackers cover the entire network.

These days, we are moving more anonymous BTC full node service to tracker, and obd will nolonger need a full node. This will help to deploy an obd node quickly.

I would like to suggest you to connect your node to the tracker we deployed for the community.

neocarmack commented 3 years ago

I will keep this PR open.

johng commented 3 years ago

This is a fully local setup.

Machine A: Tracker 1 OBD 1

Machine B: Tracker 2 OBD 2

When sending a message to remote peer 

findUserOnLine(msg);

Will always fail.

johng commented 3 years ago

Fixed