All requests that do not require signing will be routed directly to the network regardless of the Role assigned to the API Key. SYBL only intercepts and signs calls that would require a signing operation.
For example:
RPC Method
SYBL Intercepts
personal_sign
True
eth_sign
True
eth_signTypedData_v1/3/4
True
eth_signTransaction
True
eth_sendTransaction
True
chain_id
False
eth_getBalance
False
eth_call
False
All other non signing operations
False
You can generate a Testnet or a Mainnet SYBL API Key in the dashboard.
Keep your API Keys secure as they have access to the Roles and Wallets you assign.
It is recommended to limit the Role to only what your service would require.
Currently only one Wallet can be assigned per API Key.