package
0.0.0-20230816035547-f94ef0f6cb83
Repository: https://github.com/digitallabs-web3/neo-go-evm.git
Documentation: pkg.go.dev

# Packages

No description provided by the author

# Functions

GetEventIDFromString converts input string into an EventID if it's possible.
NewError is an Error constructor that takes Error contents from its parameters.
NewInternalServerError creates a new error with code -32603.
NewInvalidParamsError creates a new error with code -32602.
NewInvalidRequestError creates a new error with code -32600.
NewMethodNotFoundError creates a new error with code -32601.
NewParseError creates a new error with code -32700.
NewRPCError creates a new error with code -100.
NewSubmitError creates a new error with specified error code and error message.
No description provided by the author
WrapErrorWithData returns copy of the given error with specified data and cause.

# Constants

BlockEventID is a `block_added` event.
ExecutionEventID is used for `transaction_executed` events.
InvalidEventID is an invalid event id that is the default value of EventID.
MissedEventID notifies user of missed events.
NotificationEventID represents `notification_from_execution` events.
TransactionEventID corresponds to `transaction_added` event.

# Variables

ErrAlreadyExists represents SubmitError with code -501.
ErrInvalidParams represents a generic 'invalid parameters' error.
ErrOutOfMemory represents SubmitError with code -502.
ErrPolicyFail represents SubmitError with code -505.
ErrUnableToVerify represents SubmitError with code -503.
ErrUnknown represents SubmitError with code -500.
ErrValidationFailed represents SubmitError with code -504.

# Structs

Abstract represents abstract JSON-RPC 2.0 response, it differs from Raw in that Result field is an interface here.
No description provided by the author
Header is a generic JSON-RPC 2.0 response header (ID and JSON-RPC version).
HeaderAndError adds an Error (that can be empty) to the Header, it's used to construct type-specific responses.
Notification is a type used to represent wire format of events, they're special in that they look like requests but they don't have IDs and their "method" is actually an event name.
Raw represents a standard raw JSON-RPC 2.0 response: http://www.jsonrpc.org/specification#response_object.
No description provided by the author

# Interfaces

AbstractResult is an interface which represents either single JSON-RPC 2.0 response or batch JSON-RPC 2.0 response.

# Type aliases

AbstractBatch represents abstract JSON-RPC 2.0 batch-response.
EventID represents an event type happening on the chain.