Skip to main content
Added example program
Source Link

The requestHeapFrame instruction adds an additional 8 compute units per 32K heap requested.

This means if you have a compute budget instruction for requestHeapFrame and use SetComputeUnitPrice to set the microLamport price to 1 microLamport, you would incur 8 * (heapRequested / 32K) * computeUnitPrice more in microLamports on your transaction.

If you're interested in requesting more heap for your program, you'll have to add some code in order to make it possible to increase the total heap available.

The requestHeapFrame instruction adds an additional 8 compute units per 32K heap requested.

This means if you have a compute budget instruction for requestHeapFrame and use SetComputeUnitPrice to set the microLamport price to 1 microLamport, you would incur 8 * (heapRequested / 32K) * computeUnitPrice more in microLamports on your transaction.

The requestHeapFrame instruction adds an additional 8 compute units per 32K heap requested.

This means if you have a compute budget instruction for requestHeapFrame and use SetComputeUnitPrice to set the microLamport price to 1 microLamport, you would incur 8 * (heapRequested / 32K) * computeUnitPrice more in microLamports on your transaction.

If you're interested in requesting more heap for your program, you'll have to add some code in order to make it possible to increase the total heap available.

Source Link

The requestHeapFrame instruction adds an additional 8 compute units per 32K heap requested.

This means if you have a compute budget instruction for requestHeapFrame and use SetComputeUnitPrice to set the microLamport price to 1 microLamport, you would incur 8 * (heapRequested / 32K) * computeUnitPrice more in microLamports on your transaction.