Neo: NEO 3 RPC Update List

[lock9]

This is a checklist for updates in our RPC features. This list is based on previous issues and comments (I will try to list them here when possible).
I believe this will remain open until NEO 3 is officially released.

REST update (#726) :

• [ ] Create swagger documentation (#1003)
• [ ] Add REST uri endpoints (#1004 )
• [ ] Update error messages (#975)
• [ ] Update SDK to use REST API
• [ ] Add REST API section to the documentation

GraphQL update (#623) :

• [ ] Create GraphQL schema
• [ ] Update data serialization methods
• [ ] Add GraphQL endpoint
• [ ] Update SDK to support GraphQL
• [ ] Add GraphQL section to the documentation

[Jarbas666]

Nice thing about this.

[Tommo-L]

Can we implement them in NEO3, and also the SPV?

[lock9]

Hi @Tommo-L is the SPV something provided using RPC? We need MPT before this is implemented, right?

[Tommo-L]

Is the SPV something provided using RPC? We need MPT before this is implemented, right?

Yes

[wanglongfei88]

@lock9 we are going to keep both RPC and REST, right ?

[lock9]

Hi!
I think so, I consider REST very important if we expect to onboard “web” developers (both frontend and backend)

Sent from my iPhone

On 10 Oct 2019, at 10:56, wanglongfei [e-mail] wrote:


@lock9 we are going to keep both RPC and REST, right ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[wanglongfei88]

Hi! I think so, I consider REST very important if we expect to onboard “web” developers (both frontend and backend)

I agree. I think it is good for us to provide both options. And I see this "Update SDK to use REST API" in the list. Do you mean SDK to support both, or update SDK to only use REST?