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
Fast-near has a built specialised RPC solution which has a lot of performance benefits for READ calls especially.
We should use that for our view calls. However, we should build a failover logic incase fast-near fails we should use traditional rpc endpoints.
Example API - https://rpc.web4.near.page/account/<contract_account_id>/view/<method_name>?<arg_name>=<string_arg_value>&<arg_name.json>=<json_arg_value>
Are you willing to provide a PR to address this?
None
The text was updated successfully, but these errors were encountered:
What is your idea or feature suggestion?
Fast-near has a built specialised RPC solution which has a lot of performance benefits for READ calls especially.
We should use that for our view calls. However, we should build a failover logic incase fast-near fails we should use traditional rpc endpoints.
Benefits
Better performance on READ calls.
Where can we find information about this?
Link to fast-near docs - https://github.com/fastnear/fast-near?tab=readme-ov-file#get
Example API -
https://rpc.web4.near.page/account/<contract_account_id>/view/<method_name>?<arg_name>=<string_arg_value>&<arg_name.json>=<json_arg_value>
Are you willing to provide a PR to address this?
None
The text was updated successfully, but these errors were encountered: