RPC: Implement missing API endpoints #1

Closed
opened 2025-12-28 17:11:53 +00:00 by sami · 3 comments
Owner

Originally created by @anthdm on GitHub (Feb 1, 2018).

The basic setup for this is done. There's 1 method implemented (getconnectioncount). More could be implemented once the network and core package has more functionality.

Originally created by @anthdm on GitHub (Feb 1, 2018). The basic setup for this is done. There's 1 method implemented (getconnectioncount). More could be implemented once the network and core package has more functionality.
sami 2025-12-28 17:11:53 +00:00
  • closed this issue
  • added the
    task
    label
Author
Owner

@anthdm commented on GitHub (Apr 29, 2018):

@stevenjack could you list up what is already implemented in neo-go for the RPC server? A checklist would be awesome. <3

@anthdm commented on GitHub (Apr 29, 2018): @stevenjack could you list up what is already implemented in neo-go for the RPC server? A checklist would be awesome. <3
Author
Owner

@stevenjack commented on GitHub (May 3, 2018):

@anthdm They're all in the README https://github.com/CityOfZion/neo-go/tree/master/pkg/rpc 👍

@stevenjack commented on GitHub (May 3, 2018): @anthdm They're all in the README https://github.com/CityOfZion/neo-go/tree/master/pkg/rpc 👍
Author
Owner

@hal0x2328 commented on GitHub (Feb 25, 2019):

Closing old issue in favor of rewrite suggested in #128

@hal0x2328 commented on GitHub (Feb 25, 2019): Closing old issue in favor of rewrite suggested in #128
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neo-go#1
No description provided.