feat: Adds new tx contract data model [REFACTOR]

[moraesjeremias]

WIP DON'T MERGE

Will later adjust frontend layer.
Will do some local tests over the week.

Changes

• Adds new tx contract data model
• Moves tx request from bridge indexer to bridge api

Reason for change

• New Bridge Indexer is now deployed on Hex and old one will soon be sunset in all networks.
• We gotta adjust frontend layer to support new API contracts for transaction endpoint.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bridge-ui	❌ Failed (Inspect)			Feb 26, 2025 2:08am

[greptile-apps]

PR Summary

This PR refactors the transaction handling system to support the new Hex bridge API, replacing the soon-to-be-sunset bridge indexer across all networks.

• Removed bridgeIndexerBaseUrl from config and updated bridgeApiBaseUrl to point to the new production sandbox URL
• Added new TransactionResponseType enum in types/common.ts with AVAIL_SEND and ETH_SEND values
• Significantly restructured the Transaction interface by removing chain-specific fields and consolidating token address fields into a single tokenId
• Critical issue in validateParams function in services/transactions.ts where it returns an empty array in error cases instead of properly handling errors

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{4 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: This function doesn't handle the case where queryParam is not one of the keys in chainAddressResponseMapping, which could lead to undefined being returned.

Suggested change

	function validateTransactionResponseType(queryParam: string) : string {
	const chainAddressResponseMapping: Record<string, TransactionResponseType> = Object.freeze({
	"ethAddress": TransactionResponseType.ETH_SEND,
	"availAddress": TransactionResponseType.AVAIL_SEND
	})
	return chainAddressResponseMapping[queryParam];
	}
	function validateTransactionResponseType(queryParam: string) : TransactionResponseType {
	const chainAddressResponseMapping: Record<string, TransactionResponseType> = Object.freeze({
	"ethAddress": TransactionResponseType.ETH_SEND,
	"availAddress": TransactionResponseType.AVAIL_SEND
	})
	const type = chainAddressResponseMapping[queryParam];
	if (!type) {
	throw new Error(`Invalid query parameter: ${queryParam}`);
	}
	return type;
	}

[moraesjeremias]

In fact early return/throws validation is way better.

e.g:

#L28 if !["",""].includes(queryParams) throw new Error(`Invalid query parameter: ${queryParam}`)