stateproof wip
@@ -16,6 +16,7 @@ There are [six transaction types](https://github.com/algorand/go-algorand/blob/m
- [Asset Freeze](#asset-freeze-transaction)
- [Asset Transfer](#asset-transfer-transaction)
- [Application Call](#application-call-transaction)
+- [State Proof](#state-proof-transaction)
These six transaction types can be specified in particular ways that result in more granular perceived transaction types. As an example, a transaction to [create an asset](../atomic_transfers#creating-an-asset) and [destroy an asset](../atomic_transfers#destroying-an-asset) use the same underlying `AssetConfigTx` type. Distinguishing these two transactions requires knowing which combination of `AssetConfigTx` fields and values result in one versus the other. This guide will help explain those differences. Fortunately, the SDKs provide intuitive methods to create these more granular transaction types without having to necessarily worry about the underlying structure. However, if you are signing a pre-made transaction, correctly interpreting the underlying structure is critical.
@@ -562,6 +563,10 @@ Application NoOp Transactions make up a majority of the Application Call methods
- The ForeignApps (`apfa`) contains the AppId 10
- The OnComplete (`apan`) is set to NoOp (0 value so omitted from the output)
+# State Proof Transaction
+
+A State Proof Transaction is a transaction that's submitted to the network during the consensus process. These types of transactions are not submitted by individuals, nor can a Smart Contract issue inner state proof transactions.
+
# Sending a Transaction in the Future
Algorand transactions are valid for a specific round range and the range maximum is 1000 rounds. If you plan to submit the transaction right away, specifying this round range is trivial. However, when the transaction requires offline signing or you plan to make frequent transactions from that account, it may be beneficial to specify a future round range or ranges that are more convenient. You can sign these transactions in a single secure session, and then submit them to the network when the valid round range is reached.
