Improve Oracle request submission errors #1152

Open
opened 2025-12-28 17:15:25 +00:00 by sami · 0 comments
Owner

Originally created by @AnnaShaleva on GitHub (Jul 25, 2023).

Currently we have a set of Oracle-specific RPC error codes, but some of them are unused from the NeoGo side (-603, -604, -605). We have to improve our Oracle service to be able to properly return all Oracle-related error codes. Within the scope of this task we have to:

After that we have to adapt all unused Oracle-related codes. Ref. https://github.com/nspcc-dev/neo-go/pull/3063.

Originally created by @AnnaShaleva on GitHub (Jul 25, 2023). Currently we have a set of Oracle-specific RPC error codes, but some of them are unused from the NeoGo side (-603, -604, -605). We have to improve our Oracle service to be able to properly return all Oracle-related error codes. Within the scope of this task we have to: * Add ability to distinguish finished Oracle requests (https://github.com/nspcc-dev/neo-go/pull/3063#discussion_r1272431597). * Return a proper error from the response submission method in case if the account used by service isn't designated Oracle (https://github.com/nspcc-dev/neo-go/pull/3063#discussion_r1272435202). * Distinguish the case of missing request on response submission (https://github.com/nspcc-dev/neo-go/pull/3063#discussion_r1272449350). After that we have to adapt all unused Oracle-related codes. Ref. https://github.com/nspcc-dev/neo-go/pull/3063.
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#1152
No description provided.