General errors
These errors are non-category specific failures.
Code | Name | Description | Customer Advice |
---|---|---|---|
300 |
| 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 |
| 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 |
| This error is thrown when the signed hash is in the incorrect format. | Confirm that your ETH transaction object is correctly formatted |
303 |
| Deprecated from the codebase | Deprecated from the codebase |
304 |
| Deprecated from the codebase | Deprecated from the codebase |
305 |
| 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 |
| 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 |
| 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 |
| This error is thrown when the ETH Transaction is incorrect | Confirm that your ETH transaction object is correctly formatted |
309 |
| 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 |
| 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 |
| 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 |
| This error is a generic catch for errors when converting key pairs into a ECDSA elliptic curve point | Contact Portal support. |
313 |
| 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 |
| 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 |
| 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 |
| This error is from calling out to the getMe endpoint. | Check the message for more details. |
Last updated