Enhance Logging Practices for Cadence Transactions

[monilpat]

Is your feature request related to a problem? Please describe.

Current logging within the Cadence transaction scripts lacks structure and meaningful context, making it difficult to debug and trace issues effectively.

Describe the solution you'd like

Implement structured logging for Cadence transaction scripts, such as create_new_account_with_coa.cdc and transfer_erc20.cdc. This involves:

• Using a consistent JSON format for logs.
• Including standard fields like timestamp, transaction ID, and log level.
• Capturing input parameters and execution results in logs.
• Logging specific error messages with stack traces when transactions fail.

Describe alternatives you've considered

• Using plain text logs, which are harder to parse and aggregate.
• Relying on external monitoring tools without improving in-script logging.

Additional context

Structured logging will significantly improve observability and debugging capabilities, especially in production environments where real-time insights are critical.

Related Issues

No related issues found at this time.