@solana/rpc-spec-types
Advanced tools
This package contains core types that can be used on both RPC and RPC Subscriptions specifications. It can be used standalone, but it is also exported as part of the Solana JavaScript SDK @solana/web3.js@next.
RpcRequestAn object that describes the elements of an RPC or RPC Subscriptions request. It consists of the following properties:
methodName: The name of the RPC method or subscription requested.params: The parameters to be passed to the RPC server.RpcRequestTransformerA function that accepts an RpcRequest and returns another RpcRequest. This allows the RpcApi to transform the request before it is sent to the RPC server.
RpcResponseA type that represents the response from an RPC server. This could be any sort of data which is why RpcResponse defaults to unknown. You may use a type parameter to specify the shape of the response — e.g. RpcResponse<{ result: number }>.
RpcResponseTransformerA function that accepts an RpcResponse and returns another RpcResponse. This allows the RpcApi to transform the response before it is returned to the caller.
FAQs
Shared generic JSON RPC specifications
We found that @solana/rpc-spec-types demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 14 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.