{'title': 'EvmTransaction', 'properties': {'id': {'title': 'Id', 'description': 'The unique identifier of the object in the Fordefi platform.', 'type': 'string', 'format': 'uuid'}, 'created_at': {'title': 'Created At', 'description': 'The date and time when the object was created.', 'type': 'string', 'format': 'date-time'}, 'modified_at': {'title': 'Modified At', 'description': 'The date and time when the object was last modified. Any change to any field of the resource is considered a modification.', 'type': 'string', 'format': 'date-time'}, 'managed_transaction_data': {'description': 'Managed transaction data. Presented if the transaction was initiated from the Fordefi system itself, in contrast to unmanaged transactions (which are, for example, transfers of funds into a vault visible to Fordefi). ', '$ref': '#/components/schemas/ManagedTransactionData'}, 'signatures': {'title': 'Signatures', 'description': 'The transaction signatures.', 'items': {'$ref': '#/components/schemas/Signature'}, 'type': 'array'}, 'note': {'title': 'Note', 'description': 'An optional transaction note.', 'type': 'string'}, 'spam_state': {'$ref': '#/components/schemas/TransactionSpamState'}, 'direction': {'$ref': '#/components/schemas/TransactionDirection'}, 'type': {'title': 'Type', 'description': 'EVM transaction type.', 'const': 'evm_transaction'}, 'evm_transaction_type_details': {'title': 'Evm Transaction Type Details', 'description': 'Details of EVM transaction based on its type.', 'oneOf': [{'$ref': '#/components/schemas/EvmNativeTransferDetails'}, {'$ref': '#/components/schemas/TokenTransferDetails'}, {'$ref': '#/components/schemas/AllowanceDetails'}, {'$ref': '#/components/schemas/ContractCallDetails'}, {'$ref': '#/components/schemas/BridgeDetails'}], 'discriminator': {'propertyName': 'type', 'mapping': {'allowance': '#/components/schemas/AllowanceDetails', 'contract_call': '#/components/schemas/ContractCallDetails', 'cross_chain_bridge': '#/components/schemas/BridgeDetails', 'native_transfer': '#/components/schemas/EvmNativeTransferDetails', 'token_transfer': '#/components/schemas/TokenTransferDetails'}}}, 'chain': {'$ref': '#/components/schemas/EnrichedEvmChain'}, 'from': {'$ref': '#/components/schemas/EnrichedEvmAddress'}, 'to': {'$ref': '#/components/schemas/EnrichedEvmAddress'}, 'value': {'title': 'Value', 'description': 'The value of the transaction.', 'type': 'string', 'pattern': '^\\d+$', 'example': '1000000000000000000'}, 'data': {'title': 'Data', 'description': 'The Base64 data of the contract call, as a serialized method-call with its arguments. See [data field format for transactions on Ethereum](https://ethereum.org/en/developers/docs/transactions/#the-data-field).', 'type': 'string', 'example': 'SGVsbG8='}, 'hex_data': {'title': 'Hex Data', 'description': 'The hex data of the contract call, as a serialized method-call with its arguments.', 'type': 'string', 'pattern': '^0[xX][a-fA-F0-9]+$'}, 'parsed_data': {'$ref': '#/components/schemas/EvmTransactionParsedData'}, 'hash': {'title': 'Hash', 'description': 'The hash of the transaction.', 'type': 'string', 'maxLength': 66, 'minLength': 66, 'pattern': '^0[xX][a-fA-F0-9]+$', 'example': '0x780f21260f89d610f24eed21b34d29229611a37e0003e83dd0da91981d7131ae'}, 'nonce': {'title': 'Nonce', 'description': 'The nonce of the transaction.', 'type': 'integer'}, 'block': {'description': 'Details of the block the transaction was mined in.', '$ref': '#/components/schemas/EvmBlockData'}, 'expected_result': {'description': 'The expected (simulated) result of the transaction.', '$ref': '#/components/schemas/EvmTransactionResult'}, 'simulation_status_result': {'description': 'Whether simulation succeeded, reverted or failed.', '$ref': '#/components/schemas/SimulationStatusResult'}, 'mined_result': {'description': 'The result of the transaction after it was mined.', '$ref': '#/components/schemas/EvmTransactionResult'}, 'gas_submitted': {'title': 'Gas Submitted', 'description': 'The gas details submitted for the transaction.', 'oneOf': [{'$ref': '#/components/schemas/LegacyGas'}, {'$ref': '#/components/schemas/DynamicGas'}], 'discriminator': {'propertyName': 'type', 'mapping': {'dynamic': '#/components/schemas/DynamicGas', 'legacy': '#/components/schemas/LegacyGas'}}}, 'state': {'$ref': '#/components/schemas/EvmTransactionState'}, 'state_changes': {'title': 'State Changes', 'description': 'The state changes of the transaction.', 'items': {'$ref': '#/components/schemas/EvmTransactionStateChange'}, 'type': 'array'}, 'parent_transaction_id': {'title': 'Parent Transaction Id', 'description': 'The unique identifier of the parent transaction. Parent and child transactions form in cases where a transaction become stuck and is then either canceled or accelerated. If, for example, the original transaction (`t1`) is the parent and the related, adjustment transaction is the child (`t2`), then relative to itself, the parent field of `t1` is `null` and the child field is `t2_id`. Compare with field `child_transaction_id`.', 'type': 'string', 'format': 'uuid'}, 'child_transaction_id': {'title': 'Child Transaction Id', 'description': 'The unique identifier of the child transaction. Compare with field `parent_transaction_id`. Relative to itself, the parent field of transaction `t2` would aquire the identifier `t1_id` and the child field of `t2` would be `null`. ', 'type': 'string', 'format': 'uuid'}, 'funding_for_transaction_id': {'title': 'Funding For Transaction Id', 'description': 'Funding transaction ID.', 'type': 'string', 'format': 'uuid'}, 'funded_by_transaction_id': {'title': 'Funded By Transaction Id', 'description': 'Funded transaction ID.', 'type': 'string', 'format': 'uuid'}, 'funded_by_vault': {'description': 'Funding vault.', '$ref': '#/components/schemas/VaultRef'}, 'current_preceding_pushed_to_blockchain_transaction_id': {'title': 'Current Preceding Pushed To Blockchain Transaction Id', 'description': 'The unique identifier of the transaction that was pushed to the blockchain, In case this transaction is QUEUED.', 'type': 'string', 'format': 'uuid'}, 'is_cancelation': {'title': 'Is Cancelation', 'description': '`True` if this transaction is a cancelation of a previous transaction, `False` otherwise. ', 'type': 'boolean'}, 'is_acceleration': {'title': 'Is Acceleration', 'description': '`True` if this transaction is an acceleration of a previous transaction, `False` otherwise.', 'type': 'boolean'}, 'use_secure_node': {'title': 'Use Secure Node', 'description': '`True` if Fordefi sends this transaction through a secure node, `False` otherwise. By using a secure node, you avoid maximal extractable value (MEV) attacks.', 'type': 'boolean'}, 'explorer_url': {'title': 'Explorer Url', 'description': 'The URL of this transaction in a blockchain explorer.', 'example': 'https://etherscan.io/tx/0x123', 'type': 'string', 'maxLength': 2083, 'minLength': 1, 'format': 'uri'}, 'raw_transaction': {'title': 'Raw Transaction', 'description': 'The raw transaction data, encoded as a hex string.', 'type': 'string', 'pattern': '^0[xX][a-fA-F0-9]+$'}}, 'type': 'object', 'required': ['id', 'created_at', 'modified_at', 'signatures', 'direction', 'type', 'evm_transaction_type_details', 'chain', 'from', 'to', 'value', 'data', 'parsed_data', 'gas_submitted', 'state', 'state_changes', 'is_cancelation', 'is_acceleration', 'use_secure_node'], 'x-konfig-properties': {'spam_state': {'description': '`automatically_set` if the transaction was automatically set as spam by Fordefi, `manually_set` if the transaction was manually set as spam by a user, and `unset` if the transaction was not set as spam.', 'default': 'unset'}, 'direction': {'description': 'The direction of the transaction.'}, 'chain': {'description': 'The details of the chain this transaction is on'}, 'from': {'description': 'The sender of the transaction.'}, 'to': {'description': 'The recipient of the transaction.'}, 'parsed_data': {'description': 'The parsed data of the transaction.'}, 'state': {'description': 'The current status of the transaction. Can be one of the following:

`waiting_for_approval`: If a transaction has not been auto-approved, it waits in this state until it has received all the required approvals.
`approved`: The transaction moves into this state on approval. Then, a notification is sent to the mobile device of the creator of the transaction for signing or to the API Signer (depending on the flow that was defined). The transaction remains in this state until it is signed.
`pushed_to_blockchain`: Once signed, the transaction is pushed to the blockchain, awaiting mining. From that moment, control of the transaction passes from Fordefi to the blockchain. This status resolves into one of the following: `completed`, `reverted`, `stuck`.
`completed`: The transaction was successfully mined into the blockchain.
`reverted`: The transaction was mined into the blockchain and was then reverted.
`stuck`: The transaction did not reach `completed` or `reverted` after 24 hours.
`error_pushing_to_blockchain`: Failed to push the transaction to the blockchain.
`aborted`: Either the transaction was not approved or the transaction was approved but the creator aborted the process.

For more information about statuses in the transaction lifecycle, see: [Transaction Lifecycle](https://docs.fordefi.com/docs/transaction-lifecycle). '}}} is not valid under any of the given schemas