Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feature] RPC Node Discovery

See original GitHub issue

We want to have some sort of discovery mechanism for neon-js to be able to independently decide on the best RPC node to hook onto.

Currently, we rely on neon-wallet-db or neoscan to provide a best node URL. However, best merely means best in terms of block height. We also want to be able to function independently to determine the best node ourselves.

Specifics

Given only the seed nodes, discover new nodes and collate them.
Identify open RPC ports on nodes and determine if the network is the same (nodes can host different networks running on different ports)
Do a latency and blockheight test to detemine if the node is good enough.

Issue Analytics

State:
Created 6 years ago
Comments:13 (12 by maintainers)

Top GitHub Comments

2reactions

CHAOWEICHIUcommented, Apr 27, 2018

Yeah, let me work on Network class.

1reaction

snowypowerscommented, Apr 27, 2018

that would be nice. Though I think that the proper way is to provide the interface where you can have a Network class which holds the RPC endpoints and a separate method call to fill this Network class with RPC addresses. This way, the user can choose whether he wants to trust the COZ list or provide their own list (they might want to use their private nodes for example).

Are you looking to work on this? Else I will start working on building up the Network class.

Top Results From Across the Web

Interacting with a node - R3 Documentation

To interact with your node, you need to build an RPC client. This RPC client enables you to connect to a specified server...

Change an RPC node password | Citrix ADC 13.1

One RPC node exists on each Citrix ADC appliance and stores information, such as the IP ... In Configure RPC Node, type the...

Discovery :: Choria Orchestrator

The native Choria discovery system is tailored to this dynamic world, it can discover nodes and operate on the ones that's there now....

Nomad Client allocation discovery - HashiCorp Discuss

When using a localhost http client to communicate with the local Nomad node, I can expect a subset of RPC calls to not...

RPC node encounter `Cannot create a runtime error=Other ...

The RPC node runs with this message in the log Cannot create a runtime error=Other(\"runtime requires function imports which are not present on ......