Native contract address 0000000000000000000000000000000000000009 haven't been registered · Issue #670 · ontio/documentation · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By clicking &
7ABA
ldquo;Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
I got an error "[NeoVmService] service system call error!: [SystemCall] service execution error!: Native contract address 0000000000000000000000000000000000000009 haven't been registered." from the TestNet when I lock some oep-4 tokens. How can I do with that?
SmartX log response:
Invoke: {"Action":"sendrawtransaction","Desc":"INTERNAL ERROR, ErrUnknown","Error":-1,"Id":700818583,"Result":"[NeoVmService] service system call error!: [SystemCall] service execution error!: Native contract address 0000000000000000000000000000000000000009 haven't been registered.","Version":"1.0.0"}
The text was updated successfully, but these errors were encountered:
I got an error "[NeoVmService] service system call error!: [SystemCall] service execution error!: Native contract address 0000000000000000000000000000000000000009 haven't been registered." from the TestNet when I lock some oep-4 tokens. How can I do with that?
SmartX log response:
Invoke: {"Action":"sendrawtransaction","Desc":"INTERNAL ERROR, ErrUnknown","Error":-1,"Id":700818583,"Result":"[NeoVmService] service system call error!: [SystemCall] service execution error!: Native contract address 0000000000000000000000000000000000000009 haven't been registered.","Version":"1.0.0"}
The text was updated successfully, but these errors were encountered: