kevaundray / neo-go-api Goto Github PK

Currently it is a problem to ask a node for it's connected nodes and build a nodelist from that information. With the addition of two new rpc calls; getsys and getnodestatusthis will become easier. A new port of 10555 will be used.

getnodestatus request:

{
"jsonrpc": "2.0",
"method": "getnodestatus",
"params":["http://seed4.travala.com:1055"],
"id": 1
}

getnodestatus repsonse:

{
"jsonrpc": "2.0",
"id": 1,
"result": {
"p2p" : 10334,
"json-rpc" : 10332,
"monitor" : true
}

}
getsys request:

{
"jsonrpc": "2.0",
"method": "getsys",
"params":["http://seed4.travala.com:1055"],
"id": 1
}

getnodestatus repsonse:

{
"jsonrpc": "2.0",
"id": 1,
"result": {
"cpu" : 2,
"memory" : "2GB",
}

}

If monitor is true and the cpu and memory requirements meet the standard, then we will add them to the list. By default, monitor will be false, and port 1055 should always be on.

Instead of putting the information in dynamodb, we could use leveldb and make this client a speaker node.

A speaker node is a node which uses a lot more memory and storage than a normal node. rpc calls such as gettxout and network statistics, could be delegated to these nodes, lessening the burden on the other nodes. If the database was ported locally, then the speaker node, could use a rpc server to serve out the network statistics instead. The traditional nodes would therefore be tasked solely with upholding the status of the network.

This thread will be used to brainstorm the historical information that we can collect from each node

P2p status and web socket status:

Previously: the ports, were pinged however this may not be a reliable solution and instead a handshake protocol should be built so that the nodes are asked directly.