Worktop

The worktop is its own native blueprint. Each transaction has a worktop where resources are placed during the transaction.

The worktop cannot be accessed by user-created blueprints directly. It is created by the transaction-processor blueprint and used there.

Because the worktop is not directly accessible by user code but by instructions that are specified through the transaction manifest, we will not be covering the functions in detail here.

However, it is important to note that the worktop code does ensure that that buckets added to it are not empty and that amounts of resources taken out of it do exist in the worktop. This prevents users from submitting transactions that attempt to gain access to resources that do not exist.