Temporal for transfers

[youngkidwarrior]

Create transfer tempora workflow

New trpc route that starts transfer workflow

Encapsulate temporal into a package

Call transfer trpc mutation from frontend

Create transfer temporal workflow

Encapsulate temporal into a package

Create transfer tempora workflow

Encapsulate temporal into a package

Temporal cloud changes

remove debug env

Show pending transfers from temporal in UI

[youngkidwarrior]

• save temporal transfer workflows in supabase #1049
• Temporal for transfers #965 👈 (View in Graphite)
• Fix mobile button row refetches and fix types #962
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[0xBigBoss]

are there cases where we don't get a workflowId? we should throw an error if we don't get one back.

[youngkidwarrior]

we throw in the temporal api

sendapp/packages/api/src/routers/temporal.ts

Lines 27 to 48 in d623de1

	try {
	const client = await getTemporalClient()
	const chainId = baseMainnetClient.chain.id
	const entryPoint = entryPointAddress[chainId]
	const userOpHash = getUserOperationHash({
	userOperation: userOp,
	entryPoint,
	chainId,
	})
	const { workflowId } = await client.workflow.start(TransferWorkflow, {
	taskQueue: 'monorepo',
	workflowId: `temporal/transfer/${user.id}/${userOpHash}`,
	args: [userOp],
	})
	log(`Workflow Created: ${workflowId}`)
	return workflowId
	} catch (error) {
	throw new TRPCError({
	code: 'INTERNAL_SERVER_ERROR',
	message: error instanceof Error ? error.message : 'Unknown error',
	})
	}

the catch should handle it. Though we could probably clean it up

[0xBigBoss]

this is so we don't show pending transfers to the recipient right?

[youngkidwarrior]

yeah

[0xBigBoss]

typo

[0xBigBoss]

we should not set a default then.

[0xBigBoss]

Hmmm. most likely not going to happen, but instead of blocking the write. Let's just raise a notice with the workflow ID and then return early.

[0xBigBoss]

maybe a one liner comment explaining why this is a good idea or why we did it this way