Users will write Anoma programs against transaction functions which are the interface to Anoma applications.
These transaction functions take user input and return transaction candidates that we actually submit to Anoma.
The transaction function to transaction candidate execution does not happen in Anoma, it happens 'offline'. The Anoma node's job is to check the resulting logic function in the transaction candidate.
An example of offline execution is the signing of transactions.
The “Transaction functions” will need to be executed in a way that produces Nockma output. There are several options:
Run the offline computation in the Juvix Core interpreter, then translate the Core output to Nockma
Run the offline computation in a Nockma interpreter (Anoma’s or Juvix’s)
Run the offline computation natively, output Nockma or some format that we can translate to Nockma.
Users will write Anoma programs against transaction functions which are the interface to Anoma applications.
These transaction functions take user input and return transaction candidates that we actually submit to Anoma.
The transaction function to transaction candidate execution does not happen in Anoma, it happens 'offline'. The Anoma node's job is to check the resulting logic function in the transaction candidate.
An example of offline execution is the signing of transactions.
The “Transaction functions” will need to be executed in a way that produces Nockma output. There are several options: