Feat/optional sender #491

p2arthur · 2025-09-03T00:25:34Z

#Optional Sender for Simulation

Status: Open
Goal: Let users simulate transactions without manually entering a sender. If the sender is left empty, we auto-resolve the “best” account by network. The Send button still requires explicit senders on all transactions.

Summary of Changes

Optional sender implemented in browser runtime.
Auto-resolution rules when sender is empty:
- LocalNet: local dispenser account
- TestNet: fee sink (or dispenser API address)
- MainNet: fee sink address
- Custom networks: not supported → show clear error
UX/Styling
- Auto-populated senders are subtly highlighted (e.g., bg-red-50) and show an indicator/tooltip:
  “This address was auto-populated for simulation.”
- Send remains disabled until every txn has a sender; hover tooltip explains why.

Integrated Builders (10/15)

Acceptance Criteria (Quick Map)

Sender can be omitted for simulation; resolved per network.
Send disabled until all txns have senders (+ hover tooltip).
Resolution rules: LocalNet/TestNet/MainNet; Custom → error.

Testing Notes

Leave sender empty on LocalNet/TestNet/MainNet → auto-populated sender + highlight + tooltip.
On custom network with empty sender → clear error.
Send disabled if any txn lacks sender; hover explains reason. - Can simulate with using the auto populated sender address
When a manual sender is provided → no auto highlight/tooltip.

Follow-ups (Post-Draft)

Complete the remaining 5 builders.
Unit tests for defineSenderAddress per network.
Integration tests to check if the process of auto populating works correctly and is displayed in the ui
Brief README note on optional sender + simulation UX.

…lora into feat/optional-sender

…nder address with auto populate using feeSink addr

… sender in localnet

… in the browser

…action types - 7 missing

cloudflare-workers-and-pages · 2025-09-04T03:55:09Z

Deploying algokit-lora with Cloudflare Pages

Latest commit:	`206971b`
Status:	✅ Deploy successful!
Preview URL:	https://2890fb69.algokit-lora.pages.dev
Branch Preview URL:	https://feat-optional-sender.algokit-lora.pages.dev

View logs

…n types

…saction

…tion types

…ender

PatrickDinh

Some initial comments. I'll resume my review later.

PatrickDinh · 2025-09-12T06:12:02Z

src/features/accounts/components/address-or-nfd-link.tsx

+        {autoPopulated && (
+          <span className="group  ml-1 cursor-help text-yellow-500">
+            <span>?</span>
+            <div className="absolute z-10 hidden rounded-sm border-2 border-gray-300/20 p-1 group-hover:block">auto populated</div>


TIL group-hover

PatrickDinh · 2025-09-12T06:12:51Z

src/features/accounts/components/address-or-nfd-link.tsx

      <div className="flex items-center overflow-hidden">
        {link}
+        {autoPopulated && (
+          <span className="group  ml-1 cursor-help text-yellow-500">


nitpick: there is double spaces here

PatrickDinh · 2025-09-12T06:16:08Z

src/features/common/components/description-list.tsx

        <dl key={index} className={cn('grid grid-cols-subgrid col-span-2')}>
          <dt className={cn('font-medium', dtClassName)}>{item.dt}</dt>
-          <dd className={cn('overflow-ellipsis whitespace-normal overflow-hidden')}>
+          <dd className={cn('overflow-ellipsis whitespace-normal overflow-hidden', item.highlightedDD && 'font-medium text-green-500')}>


I think this should be implemented as a ddClassNames props, i.e.

<dd className={cn('overflow-ellipsis whitespace-normal overflow-hidden', item.ddClassNames)}

the consumer if this component can decide how they want to style it. This way it's more flexible.

Interesting, will try that.

To be honest we don't need that change. I think it slipped while I was trying to figure out the inner workings of the transaction wizard in order to add highlighting if auto populated.

Reverting this change

PatrickDinh · 2025-09-12T06:29:46Z

src/features/transaction-wizard/data/common.ts

+export const SenderSchema = z.object({
+  value: z.string().optional(),
+  resolvedAddress: z.string().optional(),
+})
+
+// TODO Arthur - Added this shape to make the sender optional in the forms that required it
+export const optionalSenderFieldShape = {
+  sender: SenderSchema,
+} as const


I haven't looked at this code for a while so maybe I missed something.
Something isn't quite right here because the value field will miss the isAddress and isNfd validations.
Is it possible to use the optionalAddressFieldSchema?

Yes we can. Just updated it to use the optionalAddressFieldSchema instead

PatrickDinh · 2025-09-12T06:31:16Z

src/features/transaction-wizard/components/account-close-transaction-builder.tsx

        id: transaction?.id ?? randomGuid(),
        type: BuildableTransactionType.AccountClose,
-        sender: data.sender,
+        sender: await defineSenderAddress(data.sender!, networkId),


I don't think you need ! in data.sender!

PatrickDinh · 2025-09-12T06:31:52Z

src/features/transaction-wizard/utils/defineSenderAddress.ts

the file name should be snake-case to follow the project file name convention

PatrickDinh · 2025-09-12T06:36:52Z

src/features/transaction-wizard/mappers/as-algosdk-transactions.ts


+const ensureSender = (sender: AddressOrNfd | undefined) => {
+  const validSender = sender ?? {
+    value: 'TGIPEOKUFC5JFTPFMXGSZWOGOFA7THFZXUTRLQEOH3RD3LGI6QEEWJNML4',


what is this address? you should avoid using magic string and define a constant?

PatrickDinh · 2025-09-13T05:33:48Z

src/features/transaction-wizard/models/index.ts

 export type AddressOrNfd = {
  value: Address | Nfd
  resolvedAddress: Address
+  autoPopulated?: boolean


I think adding autoPopulated field to this type doesn't feel right. This type is used across the app to represent an address or nfd, it shouldn't have to concern about whether the data was auto populated or not.
As a suggestion, I'd create another type

export type TransactionSender { value: AddressOrNfd autoPopulated: boolean }

to represent this logic

I tried many solutions but the one that generated the least amount of collateral errors was Solved it like this

PatrickDinh · 2025-09-13T05:35:56Z

src/features/transaction-wizard/models/index.ts

 type CommonBuildTransactionResult = {
  id: string
-  sender: AddressOrNfd
+  sender: AddressOrNfd | undefined


does this need to be undefined? maybe I missed something but after a quick look I see that the value of the sender field is always populated with defineSenderAddress function

PatrickDinh · 2025-09-13T05:37:56Z

src/features/transaction-wizard/mappers/as-description-list-items.tsx

      dt: 'Sender',
-      dd: <AddressOrNfdLink address={params.sender} />,
+      dd: (
+        <AddressOrNfdLink


Similar logic to the comment on AddressOrNfd type, I think we should create another component that wraps the AddressOrNfdLink component to display the sender of a transaction.

PatrickDinh · 2025-09-13T05:38:58Z

src/features/transaction-wizard/mappers/as-algosdk-transactions.ts

+    resolvedAddress: 'TGIPEOKUFC5JFTPFMXGSZWOGOFA7THFZXUTRLQEOH3RD3LGI6QEEWJNML4',
+  }
+
+  invariant(validSender, 'Sender must be set')


I think this invariant is not needed, validSender must be a truthy from above.

PatrickDinh · 2025-09-13T05:53:35Z

There is an UX issue that I think we should review, in the below recording:

I created a payment txn without the sender
the default sender was set and there is an indicator shown
when I edit the transaction, the sender field is set to the default sender. I think this shouldn't happen
when I save the transaction, there is no "auto populated" indicator because the form thinks that I set the sender field.
https://github.com/user-attachments/assets/c11acf9e-903b-4df6-970e-fdd34b204596

…ult address

…tation

PatrickDinh · 2025-09-22T22:53:45Z

src/features/transaction-wizard/components/transactions-builder.tsx

+    transactions.forEach((transaction) => {
+      if (transaction.sender?.autoPopulated === true) setOnlySimulateOptionalSender(true)
+    })
+
+    if (onlySimulateOptionalSender) {
+      return {
+        disabled: true,
+        disabledReason: onlySimulateOptionalSenderMessage,
+      }
+    }


it seems that onlySimulateOptionalSender is only used within this useMemo, I don't think you need a separate onlySimulateOptionalSender state

PatrickDinh · 2025-09-22T22:55:18Z

src/features/transaction-wizard/components/transactions-table.tsx

            {table.getRowModel().rows?.length ? (
-              table
-                .getRowModel()
-                .rows.map((row) => (
+              table.getRowModel().rows.map((row) => {
+                return (
                  <TransactionRow
                    key={row.id}
                    row={row}
                    transactionPositions={transactionPositions}
                    onEditTransaction={onEditTransaction}
                    onEditResources={onEditResources}
                  />
-                ))
+                )
+              })


does this need to be changed? If it doesn't need to be, I suggest to revert it to make PR review easier.

PatrickDinh · 2025-09-22T22:57:43Z

src/features/transaction-wizard/components/account-close-transaction-builder.tsx


+import defineSenderAddress from '../utils/define-sender-address'


no need an extra empty line above this. Also, I think resolveSenderAddress is a better name. The logic inside this function doesn't define anything new.

PatrickDinh · 2025-09-22T22:58:08Z

src/features/transaction-wizard/components/application-create-transaction-builder.tsx

 import { TransactionBuilderNoteField } from './transaction-builder-note-field'
 import { asAddressOrNfd } from '../mappers/as-address-or-nfd'
 import { ActiveWalletAccount } from '@/features/wallet/types/active-wallet'



Remove empty line here

PatrickDinh · 2025-09-22T23:05:21Z

src/features/transaction-wizard/components/payment-transaction-builder.tsx

            field: 'sender',
            label: 'Sender',
-            helpText: 'Account to pay from. Sends the transaction and pays the fee',
+            helpText: 'Account to pay from. Sends the transaction and pays the fee - optional for simulating',


Is there any reason why the helpText is updated here but not for other transaction types?

…imulating

…e lora transaction wizard

… tests

…est practices

… transaction wizard page

PatrickDinh · 2025-10-02T03:43:10Z

src/features/accounts/components/address-or-nfd-link.tsx

    ) : (
      <div className="flex items-center overflow-hidden">
        {link}
+


nitpick: no need this newline

PatrickDinh · 2025-10-02T03:43:19Z

src/features/accounts/components/transaction-sender-link.tsx

+export default function TransactionSenderLink({
+  address,
+  short,
+


remove this empty line

PatrickDinh · 2025-10-02T03:45:33Z

src/features/accounts/components/transaction-sender-link.tsx

+import { Address } from '../data/types'
+import { cn } from '@/features/common/utils'
+
+export type AddressOrNfdLinkProps = PropsWithChildren<{


Rename this type to avoid conflicts with address-or-ndf-link.tsx. If it isn't used anywhere else, I'd just call it Props

Suggested change

export type AddressOrNfdLinkProps = PropsWithChildren<{

type Props = PropsWithChildren<{

PatrickDinh · 2025-10-02T03:46:57Z

src/features/network/data/index.ts

  pera: 'Pera',
  exodus: 'Exodus',
  lute: 'Lute',
-  // The below providers aren't used


I think we should still keep this comment

PatrickDinh · 2025-10-02T03:54:05Z

src/features/transaction-wizard/mappers/as-address-or-nfd.ts

    resolvedAddress: addressOrAccount,
  } satisfies AddressOrNfd
 }
+export const asOptionalAddressOrNfd = (transactionSender?: Partial<TransactionSender>): TransactionSender => {


This function doesn't look right, the name is asOptionalAddressOrNfd but return TransactionSender:

The type in the function name doesn't match with the return type

The name implies optional but the return type is not
I think you should create a new function just to handle transaction sender and revert this back to the original state.

I did a quick hack. I think you can use something like below

export const asTransactionSender = (transactionSender?: Partial<TransactionSender>): TransactionSender | undefined => { if (!transactionSender) return undefined if (transactionSender.autoPopulated) return undefined return transactionSender.value && transactionSender.resolvedAddress ? ({ value: transactionSender.value, resolvedAddress: transactionSender.resolvedAddress, autoPopulated: false, } satisfies TransactionSender) : undefined }

You will need to test to ensure it works. Additionally, it should be in a new file as-transaction-sender

PatrickDinh · 2025-10-02T03:55:01Z

src/features/transaction-wizard/components/account-close-transaction-builder.tsx

+        sender: await resolveSenderAddress(data.sender),
        closeRemainderTo: data.closeRemainderTo,
-        receiver: asOptionalAddressOrNfd(data.receiver),
+        receiver: { value: data.receiver.value!, resolvedAddress: data.receiver.resolvedAddress! },


I'm not sure why the logic for receiver needed to be updated, maybe it was related to the asOptionalAddressOrNfd function I commented on earlier, you should revert this.

PatrickDinh · 2025-10-02T04:03:24Z

src/features/transaction-wizard/models/index.ts

 export type BuildPaymentTransactionResult = CommonBuildTransactionResult & {
  type: BuildableTransactionType.Payment
  receiver: AddressOrNfd
+  sender: AddressOrNfd


I think you should remove this, the sender is already in CommonBuildTransactionResult

PatrickDinh · 2025-10-02T04:04:04Z

src/features/transaction-wizard/mappers/as-algosdk-transactions.ts

  return {
-    sender: transaction.sender.resolvedAddress,
-    receiver: transaction.receiver ? transaction.receiver.resolvedAddress : transaction.sender.resolvedAddress,
+    sender: ensureSender(transaction.sender),


do you need to call ensureSender anymore?

PatrickDinh · 2025-10-02T04:07:59Z

src/features/transaction-wizard/transaction-wizard-page.test.tsx

+            const sendButton = await waitFor(() => {
+              const sendButton = component.getByRole('button', { name: sendButtonLabel })
+              expect(sendButton).not.toBeDisabled()
+              return sendButton!
+            })
+            await user.click(sendButton)


I thought that if the sender is auto populated only "Simulate" is allowed but this test seems to be able to "Send" transaction, can you please confirm?

have you had a chance to look into this?

src/features/transaction-wizard/transaction-wizard-page.test.tsx

… related types

Co-authored-by: Hoang Dinh <[email protected]>

PatrickDinh · 2025-10-06T23:03:59Z

src/features/accounts/components/transaction-sender-link.tsx

+export type Props = PropsWithChildren<{
+  address: Address
+  short?: boolean
+  className?: string
+  showCopyButton?: boolean
+  showQRButton?: boolean
+  nfd?: Nfd
+  autoPopulated?: boolean
+}>


nitpick

Suggested change

export type Props = PropsWithChildren<{

address: Address

short?: boolean

className?: string

showCopyButton?: boolean

showQRButton?: boolean

nfd?: Nfd

autoPopulated?: boolean

}>

export type Props = AddressOrNfdLinkProps & {

autoPopulated?: boolean

}

The type of the address field is incorrect, it should be

address: string | Address;

The Address is from algosdk

PatrickDinh · 2025-10-06T23:05:30Z

src/features/accounts/components/transaction-sender-link.tsx

+      <AddressOrNfdLink
+        address={address}
+        short={short}
+        className={cn(autoPopulated && 'text-yellow-500')}


the className prop needs to be passed in here too, I think this would become something like

className={cn(className, autoPopulated && 'text-yellow-500')}

I think you can rewrite this bit to

export default function TransactionSenderLink(props: Props) { const { autoPopulated, className, ...rest } = props return ( <div className="flex items-center"> <AddressOrNfdLink className={cn(className, autoPopulated && 'text-yellow-500')} {...rest} /> ...

PatrickDinh · 2025-10-06T23:13:05Z

src/features/transaction-wizard/components/account-close-transaction-builder.tsx

+        sender: await resolveSenderAddress(data.sender),
        closeRemainderTo: data.closeRemainderTo,
-        receiver: asOptionalAddressOrNfd(data.receiver),
+        receiver: asAddressOrNfd(data.receiver.value!),


I think something isn't right here. This change potentially breaks existing logic. On main, the receiver field is

receiver: asOptionalAddressOrNfd(data.receiver),

this is an optional field.
In this PR, it was changed to

receiver: asAddressOrNfd(data.receiver.value!),

Some concerns:

Now it isn't an optional field anymore. This is incorrect. For an account close transaction, the receiver field is: "Account to receive the amount. Leave blank if 'Close remainder to' account should receive the full balance"

PatrickDinh · 2025-10-06T23:13:52Z

src/features/transaction-wizard/data/common.ts


 export const senderFieldSchema = { sender: addressFieldSchema }
+
+// TODO Arthur - Added this shape to make the sender optional in the forms that required it


Do you need this TODO anymore?

PatrickDinh · 2025-10-06T23:18:37Z

src/features/transaction-wizard/components/application-update-transaction-builder.tsx

        approvalProgram: transaction.approvalProgram,
        clearStateProgram: transaction.clearStateProgram,
-        sender: transaction.sender,
+        sender: asTransactionSender(transaction.sender),


I don't think you need the method asTransactionSender, I could be completely wrong here but you should try something simple like

sender: transaction.sender?.autoPopulated ? undefined : transaction.sender

In the above logic, the sender should be set to undefined if it was autoPopulated

PatrickDinh · 2025-10-06T23:22:01Z

src/features/transaction-wizard/utils/resolve-sender-address.ts

+import { betanetId, mainnetId, testnetId, fnetId, localnetId } from '@/features/network/data'
+import { algorandClient } from '@/features/common/data/algo-client'
+
+export default async function resolveSenderAddress<T extends OptionalSenderFieldSchema>(


Is the generic <T extends ...> required here?

PatrickDinh · 2025-10-06T23:22:14Z

src/features/transaction-wizard/utils/resolve-sender-address.ts

+
+export default async function resolveSenderAddress<T extends OptionalSenderFieldSchema>(
+  data: T
+): Promise<AddressOrNfd & TransactionSender> {


Can just be Promise<TransactionSender>

PatrickDinh · 2025-10-06T23:23:58Z

src/features/transaction-wizard/components/transactions-builder.tsx

  }, [activeAddress, commonButtonDisableProps, requireSignaturesOnSimulate])

  const sendButtonDisabledProps = useMemo(() => {
+    // derive it, don't store it


Why do we need this comment here?

PatrickDinh · 2025-10-06T23:25:19Z

src/features/transaction-wizard/components/asset-opt-out-transaction-builder.tsx

 export const assetOptOutFormSchema = z.object({
  ...commonSchema,
-  ...senderFieldSchema,
+  ...optionalSenderFieldShape,


I think you can skip the optionalSenderFieldShape and use

sender: optionalAddressFieldSchema

directly. It's just 1 line of code and it will make reading a lot easier

PatrickDinh · 2025-10-06T23:28:48Z

src/features/transaction-wizard/data/common.ts

 export const senderFieldSchema = { sender: addressFieldSchema }
+
+// TODO Arthur - Added this shape to make the sender optional in the forms that required it
+export const optionalSenderFieldShape = {
+  sender: optionalAddressFieldSchema,
+} as const


Why is the new const optionalSenderFieldShape introduced? Since this PR changing sender to optional, I think you can update

export const senderFieldSchema = { sender: optionalAddressFieldSchema }

PatrickDinh · 2025-10-06T23:33:57Z

src/features/accounts/components/transaction-sender-link.tsx

+export type Props = PropsWithChildren<{
+  address: Address
+  short?: boolean
+  className?: string
+  showCopyButton?: boolean
+  showQRButton?: boolean
+  nfd?: Nfd
+  autoPopulated?: boolean
+}>


The type of the address field is incorrect, it should be

address: string | Address;

The Address is from algosdk

PatrickDinh · 2025-10-06T23:34:27Z

src/features/transaction-wizard/mappers/as-description-list-items.tsx

    {
      dt: 'Sender',
-      dd: <AddressOrNfdLink address={params.sender} />,
+      dd: <TransactionSenderLink autoPopulated={txn.sender.autoPopulated} address={String(params.sender)} />,


After you fixed the TransactionSenderLink, you can replace String(params.sender) with params.sender

PatrickDinh · 2025-10-06T23:36:39Z

src/features/transaction-wizard/models/index.ts

+  value: Address | Nfd | undefined
+  resolvedAddress: Address | undefined


Can these fields be undefined? I think not

PatrickDinh · 2025-10-06T23:37:29Z

src/features/transaction-wizard/mappers/as-algosdk-transactions.ts


  return {
-    sender: transaction.sender.resolvedAddress,
+    sender: transaction.sender.resolvedAddress!,


I don't think the ! is needed here, feel like it is a result of the incorrect type

export type TransactionSender = { value: Address | Nfd | undefined resolvedAddress: Address | undefined autoPopulated?: boolean }

that I pointed out earlier

PatrickDinh · 2025-10-06T23:41:50Z

src/features/transaction-wizard/utils/transform-search-params-transactions.ts

-    value: params.sender,
-    resolvedAddress: params.sender,
-  },
+  sender: asTransactionSender({ value: params.sender!, resolvedAddress: params.sender!, autoPopulated: false }),


resolveSenderAddress needs to be call here. This user flow should work exactly like when a user creates the transaction from the transaction wizard

PatrickDinh and others added 6 commits July 28, 2025 10:26

wip - making sender optional

c92354e

Merge branch 'main' of https://github.com/algorandfoundation/algokit-…

80ec848

…lora into feat/optional-sender

feat(optional_sender): implement basic working version of optional se…

2c8d8fb

…nder address with auto populate using feeSink addr

add(optional_sender) implement the use of dispenser address for empty…

9130179

… sender in localnet

refactor(optional_sender) refactor optional sender to working version…

5b5ad14

… in the browser

feat(optional_sender): implement optional sender to 8 different trans…

13011ab

…action types - 7 missing

p2arthur requested review from PatrickDinh and lempira September 3, 2025 00:25

fix(lint): fix lint errors and warning

d4c3f71

p2arthur added 5 commits September 5, 2025 08:43

feat(optional_sender): implement optional sender in 4 more transactio…

681f3bd

…n types

feat(optional): add optional sender support to asset reconfigure tran…

2eb565d

…saction

feat(optional_sender) finish implement optional sender to all transac…

35f8ec5

…tion types

test(optionalSender) add test to confirm that optional sender works

78fb4a5

test(optionalSender) remove expect cases where sender was required

6f0be92

p2arthur requested a review from neilcampbell September 12, 2025 05:54

p2arthur marked this pull request as ready for review September 12, 2025 05:54

fix(optionalSender): fix tooltip not showing when hovering optional s…

7a29bab

…ender

PatrickDinh reviewed Sep 12, 2025

View reviewed changes

PatrickDinh reviewed Sep 13, 2025

View reviewed changes

p2arthur added 6 commits September 15, 2025 11:36

fix(testnet_address): add testnet fee sink address to be used as defa…

60930a8

…ult address

refactor(sender_address): refactor defineSender to be network aware

39ed51a

fix(lint) fix linting errors

6b170e0

refactor(reviews) updat code to follow PR reviews for better implemen…

3a0c3b7

…tation

fix(build): fix build errors

09acee5

fix(type): implement transaction sender type

c715c55

PatrickDinh reviewed Sep 22, 2025

View reviewed changes

p2arthur added 2 commits September 24, 2025 18:32

fix(update_sender) update auto populated on updating transaction

829589b

fix(update_op_sender) fix optional sender for editing transactions

1c9d7e5

p2arthur added 8 commits September 25, 2025 23:12

refactor(helpers) update helper text to mention optional sender for s…

0c29eaf

…imulating

fix(build) fix build errors

bbee3ec

fix(conflict) fix conflict with latest from main

920f098

fix(lint) fix lint errors

80de8e7

fix(update-transaction): fix auto populate editing transactions in th…

0d069a1

…e lora transaction wizard

fix(optional-sender): fix optional address or nfd mapper to work with…

1d255a3

… tests

refactor(resolve_sender): refactor resolve sender address to follow b…

d69ea30

…est practices

test(optional_sender): add more tests to check optional sender in the…

877dcd3

… transaction wizard page

PatrickDinh reviewed Oct 2, 2025

View reviewed changes

p2arthur removed request for lempira and neilcampbell October 2, 2025 15:44

p2arthur and others added 2 commits October 2, 2025 23:05

refactor(asTransactionSender): refactor asTransactionSenderHelper and…

f8f5b31

… related types

Update src/features/transaction-wizard/transaction-wizard-page.test.tsx

206971b

Co-authored-by: Hoang Dinh <[email protected]>

PatrickDinh requested changes Oct 6, 2025

View reviewed changes


		import defineSenderAddress from '../utils/define-sender-address'

	export type AddressOrNfdLinkProps = PropsWithChildren<{
	type Props = PropsWithChildren<{


		export const senderFieldSchema = { sender: addressFieldSchema }

		// TODO Arthur - Added this shape to make the sender optional in the forms that required it

		value: Address \| Nfd \| undefined
		resolvedAddress: Address \| undefined

Feat/optional sender #491

Are you sure you want to change the base?

Feat/optional sender #491

Uh oh!

Conversation

p2arthur commented Sep 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary of Changes

Integrated Builders (10/15)

Acceptance Criteria (Quick Map)

Testing Notes

Follow-ups (Post-Draft)

Uh oh!

cloudflare-workers-and-pages bot commented Sep 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying algokit-lora with Cloudflare Pages

Uh oh!

PatrickDinh left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

p2arthur Sep 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

PatrickDinh commented Sep 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

p2arthur commented Sep 3, 2025 •

edited

Loading

cloudflare-workers-and-pages bot commented Sep 4, 2025 •

edited

Loading

p2arthur Sep 22, 2025 •

edited

Loading