General Errors
These errors are non-category specific failures.
Code | Name | Description | Customer Advice |
|---|---|---|---|
300 | FAILED_TO_COMPUTE_ETH_ADDRESS | This error is thrown when there is a mismatch in the X and Y key shares that are provided | Confirm that the client key share sent to Portal is what is saved on file as the active client key share |
301 | FAILED_TO_CREATE_SHARE_OBJECT | This error is either a networking issue or an issue with the. It could be on the Portal side or due to network errors. | Check our status page to see if Portal is having an outage or retry the request. |
302 | INCORRECT_INPUT_TO_SIGN | This error is thrown when the signed hash is in the incorrect format. | Confirm that your ETH transaction object is correctly formatted |
303 | FAILED_TO_CONVERT_PUBLIC_KEY_BYTES | Deprecated from the codebase | Deprecated from the codebase |
304 | FAILED_TO_COMPUTE_SIGNATURE | Deprecated from the codebase | Deprecated from the codebase |
305 | FAILED_TO_PARSE_INPUT_SHARE_OBJECT | This error is thrown when your DKG object is incorrectly formatted. | Confirm that the portalDKG object sent from the client is correct and the format is correct |
306 | INCORRECT_SHARE_OBJECT_TYPE | This error is thrown when the DKG object is missing any of its 4 fields. | Confirm that the DKG object being sent from the client is complete |
307 | FAILED_TO_CONVERT_STRING_TO_BIG_INT | This error is thrown when the share represented as a string fails to be converted to type big int | Confirm the client key share is sent in as a String |
308 | FAILED_TO_POPULATE_TRANSACTION | This error is thrown when the ETH Transaction is incorrect | Confirm that your ETH transaction object is correctly formatted |
309 | FAILED_TO_BUILD_MESSAGE | This error is throw when there is an issue with the has provided for a sign function | Confirm that the ETH Sign Object is correct and complete |
310 | UNSUPPORTED_ETH_METHOD | This error is thrown when provided with an incorrect ETH method | Confirm that the method is correctly spelled and that it exists as a supported method by Portal |
311 | NODE_RPC_ERROR | This error is thrown by a node gateway provider, (like Alchemy). Often, the error is related to a formatting error. | Confirm that you are addressing the error response that is sent back. It provides the context to fix this error as it is set directly by the gateway provider |
312 | FAILED_TO_INITIALIZE_PUBLIC_KEY | This error is a generic catch for errors when converting key pairs into a ECDSA elliptic curve point | Contact Portal support. |
313 | FAILED_TO_CALCULATE_SELF_PUBLIC_KEY | This error is a networking issue. It could be on the Portal side or due to network errors. | Check our status page to see if Portal is having an outage or retry the request. |
314 | FAILED_TO_UNMARSHAL_PARTIAL_PUBLIC_KEY_FROM_SOCKET | This error is either a networking issue or an issue with the. It could be on the Portal side or due to network errors. | Check our status page to see if Portal is having an outage or retry the request. |
315 | FAILED_TO_MARSHAL_PARTIAL_PUBLIC_KEY | This error is either a networking issue or an issue with the. It could be on the Portal side or due to network errors. | Check our status page to see if Portal is having an outage or retry the request. |
320 | API_GET_ME | This error is from calling out to the getMe endpoint. | Check the message for more details. |
Last modified 19d ago