Predict smart account address
Predicts the address for a new OneBalance smart account based on the provided EVM-compatible signer addresses (session and admin). This allows you to determine the smart account’s on-chain address before its actual deployment. This predicted address serves as a primary identifier for the user within the OneBalance ecosystem.
Authorizations
The OneBalance API uses API keys to authenticate requests. All API requests require authentication using an API key passed in the x-api-key
header:
curl -X 'GET' \
'https://be.onebalance.io/api/path-to/endpoint' \
-H 'x-api-key: ${ONEBALANCE_API_KEY}' \
...
A public API key is available for testing purposes with limited usage: 42bb629272001ee1163ca0dbbbc07bcbb0ef57a57baf16c4b1d4672db4562c11
.
All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
Learn how to generate API access tokens at OneBalance Docs.
Body
The input parameters vary based on account type:
Role-based Account: Requires sessionAddress
(used for signing operations) and adminAddress
(backup admin that can perform rage quit).
Basic Account: Requires type
(account type identifier) and signerAddress
(ECDSA signer address).
Input parameters for predicting a smart account address.
Learn more about account types and their capabilities at OneBalance Account Models.
Input for role-based account prediction using sessionAddress and adminAddress
Input parameters for predicting a smart account address.
Learn more about account types and their capabilities at OneBalance Account Models.
Input for role-based account prediction using sessionAddress and adminAddress
Input parameters for predicting a smart account address.
Learn more about account types and their capabilities at OneBalance Account Models.
Input for basic account prediction using account type and signerAddress
Response
Predicted address
The response is of type object
.