getNodes

[lllwvlvwlll]

This method incorporates support for grabbing a list of public nodes for interfacing. We can consider using the json in monitor.coz.io.

[kjlevitz]

Should this just simply return an array of servers? Something along these lines:

  {
    protocol: 'https',
    url: 'explorer.o3node.org',
    location: 'US',
    locale: 'us',
    port: '443',
    type: 'RPC'
  },
  {
    protocol: 'https',
    url: 'rpc1.go.nspcc.ru',
    location: 'Russia',
    locale: 'ru',
    port: '10331',
    type: 'RPC'
  },
  {
    protocol: 'https',
    url: 'rpc2.go.nspcc.ru',
    location: 'Russia',
    locale: 'ru',
    port: '10331',
    type: 'RPC'
  },
  {
    protocol: 'https',
    url: 'rpc3.go.nspcc.ru',
    location: 'Canada',
    locale: 'ca',
    port: '10331',
    type: 'RPC'
  },
  {
    protocol: 'https',
    url: 'rpc4.go.nspcc.ru',
    location: 'US',
    locale: 'us',
    port: '10331',
    type: 'RPC'
  }

Or should it be more advanced and poll for online servers / latency?

[lock9]

Hi @ixje , this is an interesting feature. We have to get info from multiple nodes to ensure we are sending our transactions to the correct node. Would it be possible to have something like getNodes, that returns a list, ordered by height & health? (not sure what I mean with health).

[ixje]

What does “correct node” mean? I think we shouldn’t complicate it too much and just grab the list from dora. I think the idea behind this issue is to provide a mechanism to find a node to be used with neon-js. That’s it

…

On 26 Aug 2022, at 20:16, Ricardo Prado ***@***.***> wrote:  Hi @ixje , this is an interesting feature. We have to get info from multiple nodes to ensure we are sending our transactions to the correct node. Would it be possible to have something like getNodes, that returns a list, ordered by height & health? (not sure what I mean with health). — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.