original_docstring: 
          A SCPayload consists of a timestamp, an action tag, and
          attributes corresponding to various actions (create_agent,
          create_record, etc). The appropriate attribute will be
          selected depending on the action tag, and that information
          plus the timestamp and the public key with which the
          transaction was signed will be passed on to the appropriate
          handler function (_create_agent, _create_record, etc).
          _unpack_transaction gets the signing key, the timestamp, and
          the action tag out of the transaction, then returns the
          signing key, the timestamp, and the appropriate SCPayload
          attribute and handler function.
  
          Besides this, the transaction's timestamp is verified, since
          that validation is common to all transactions.
          
docstring: A SCPayload consists of a timestamp, an action tag, and
  attributes corresponding to various actions (create_agent,
  create_record, etc). The appropriate attribute will be
  selected depending on the action tag, and that information
  plus the timestamp and the public key with which the
  transaction was signed will be passed on to the appropriate
  handler function (_create_agent, _create_record, etc).
  _unpack_transaction gets the signing key, the timestamp, and
  the action tag out of the transaction, then returns the
  signing key, the timestamp, and the appropriate SCPayload
  attribute and handler function.
  
  Besides this, the transaction's timestamp is verified, since
  that validation is common to all transactions.
docstring_tokens: A SCPayload consists of a timestamp an action tag and attributes corresponding to various actions ( create_agent create_record etc ) . The appropriate attribute will be selected depending on the action tag and that information plus the timestamp and the public key with which the transaction was signed will be passed on to the appropriate handler function ( _create_agent _create_record etc ) . _unpack_transaction gets the signing key the timestamp and the action tag out of the transaction then returns the signing key the timestamp and the appropriate SCPayload attribute and handler function . Besides this the transaction ' s timestamp is verified since that validation is common to all transactions .
code: def apply(self, transaction, state):
          '''
          A SCPayload consists of a timestamp, an action tag, and
          attributes corresponding to various actions (create_agent,
          create_record, etc). The appropriate attribute will be
          selected depending on the action tag, and that information
          plus the timestamp and the public key with which the
          transaction was signed will be passed on to the appropriate
          handler function (_create_agent, _create_record, etc).
          _unpack_transaction gets the signing key, the timestamp, and
          the action tag out of the transaction, then returns the
          signing key, the timestamp, and the appropriate SCPayload
          attribute and handler function.
  
          Besides this, the transaction's timestamp is verified, since
          that validation is common to all transactions.
          '''
          signer, timestamp, payload, handler = _unpack_transaction(transaction)
  
          handler(payload, signer, timestamp, state)
code_tokens: def apply ( self , transaction , state ) : signer , timestamp , payload , handler = _unpack_transaction ( transaction ) handler ( payload , signer , timestamp , state )
short_docstring: A SCPayload consists of a timestamp, an action tag, and
  attributes corresponding to various actions (create_agent,
  create_record, etc).
short_docstring_tokens: A SCPayload consists of a timestamp an action tag and attributes corresponding to various actions ( create_agent create_record etc ) .
comment: '''
          A SCPayload consists of a timestamp, an action tag, and
          attributes corresponding to various actions (create_agent,
          create_record, etc). The appropriate attribute will be
          selected depending on the action tag, and that information
          plus the timestamp and the public key with which the
          transaction was signed will be passed on to the appropriate
          handler function (_create_agent, _create_record, etc).
          _unpack_transaction gets the signing key, the timestamp, and
          the action tag out of the transaction, then returns the
          signing key, the timestamp, and the appropriate SCPayload
          attribute and handler function.
  
          Besides this, the transaction's timestamp is verified, since
          that validation is common to all transactions.
          '''