Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation Warning for Legacy JSON-RPC Functions in Substrate-connect and unable to connect to chain. #2145

Open
adi-a11y opened this issue Apr 25, 2024 · 1 comment

Comments

@adi-a11y
Copy link

Issue Description

  1. When attempting to connect to a Substrate-based standalone chain using substrate-connect, I encountered the following error message:

The JSON-RPC client has just called a JSON-RPC function from the legacy JSON-RPC API (system_health). Legacy JSON-RPC functions have loose semantics and cannot be properly implemented on a light client. You are encouraged to use the new JSON-RPC API https://github.com/paritytech/json-rpc-interface-spec/ instead. The legacy JSON-RPC API functions will be deprecated and removed in the distant future.

  1. Configuration is not happening.

Steps to reproduce the issue

Steps to reproduce the issue

  1. Take the code snippet from the official docs
  2. replace the json file
  3. run the code

Describe the results you received

Describe the results you received

First I get this error
The JSON-RPC client has just called a JSON-RPC function from the legacy JSON-RPC API (system_health). Legacy JSON-RPC functions have loose semantics and cannot be properly implemented on a light client. You are encouraged to use the new JSON-RPC API https://github.com/paritytech/json-rpc-interface-spec/ instead. The legacy JSON-RPC API functions will be deprecated and removed in the distant future.

Then the execution stops

Describe the results you expected

Describe the results you expected

Substrate-Connect version

0.4.4

Provider

Brave

Browser version

1.64.122

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

Screenshots

No response

@ryanleecode
Copy link
Collaborator

Issue Description

  1. When attempting to connect to a Substrate-based standalone chain using substrate-connect, I encountered the following error message:

The JSON-RPC client has just called a JSON-RPC function from the legacy JSON-RPC API (system_health). Legacy JSON-RPC functions have loose semantics and cannot be properly implemented on a light client. You are encouraged to use the new JSON-RPC API https://github.com/paritytech/json-rpc-interface-spec/ instead. The legacy JSON-RPC API functions will be deprecated and removed in the distant future.

  1. Configuration is not happening.

Steps to reproduce the issue

Steps to reproduce the issue

  1. Take the code snippet from the official docs
  2. replace the json file
  3. run the code

Describe the results you received

Describe the results you received

First I get this error The JSON-RPC client has just called a JSON-RPC function from the legacy JSON-RPC API (system_health). Legacy JSON-RPC functions have loose semantics and cannot be properly implemented on a light client. You are encouraged to use the new JSON-RPC API https://github.com/paritytech/json-rpc-interface-spec/ instead. The legacy JSON-RPC API functions will be deprecated and removed in the distant future.

Then the execution stops

Describe the results you expected

Describe the results you expected

Substrate-Connect version

0.4.4

Provider

Brave

Browser version

1.64.122

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

Screenshots

No response

Link the code snippet please. Not sure what the "official docs" you are reffering to are.

@paritytech paritytech deleted a comment Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants