Inconsistent Error Handling in wallets.js

[BrosG]

The error handling in the file wallets.js is currently inconsistent. For instance, in the functions addWalletTron, getWalletTron, getWalletTronV2, wrapNative and unWrapNative, there are different ways of dealing with errors. This can lead to confusion when trying to debug the application, and it can make it harder to ensure that all errors are handled appropriately.

Suggestion: Implement a consistent error handling strategy across all functions. This could be done by defining a standard for how errors should be caught and handled. It might involve creating a custom error class that can hold additional information about the error, or wrapping all function bodies in a try/catch block and using a centralized error handling middleware to handle all errors.

Verification: Once the changes are implemented, you should verify that all functions in wallets.js follow the same error handling strategy. You could do this by reviewing the code and running tests to confirm that errors are handled correctly.