runtime tx unexpected fields

[pro-wh]

cc @matevz @csillag

https://explorer.oasis.io/mainnet/sapphire/tx/7224d59e6b74d9b2caf55ab40dfe0757cef4f71c66d3a7aba3de1d267d2ea409

this tx has error set while the status is unknown. api should clear out the error

also its method is blank, which isn't right. allegedly it's supposed to be accounts.Transfer

[lukaw3d]

Looks like a successful tx to me: it emitted events, and did transfer ROSE

So:

• status: should be success
• amount / Value: should be 199.809878 ROSE
• to_eth: should be 0xAaF64683099cF03c69007fdD39b21e91a32d05be (tho this is a native (non-EVM) transfer?)

[pro-wh]

oh was this an encrypted transaction?

edit: explorer says plain 👀

[lukaw3d]

Hm this tx is causing issues to oasisscan too

• https://www.oasisscan.com/ search finds this transaction by hash and redirects to it on sapphire
• it lists it in the round https://www.oasisscan.com/paratimes/000000000000000000000000000000000000000000000000f80306c9858e7279/round/3995186
• but it errors when opening the details https://www.oasisscan.com/paratimes/000000000000000000000000000000000000000000000000f80306c9858e7279/transactions/7224d59e6b74d9b2caf55ab40dfe0757cef4f71c66d3a7aba3de1d267d2ea409?round=3995186
• https://api.oasisscan.com/mainnet/runtime/transaction/info?id=000000000000000000000000000000000000000000000000f80306c9858e7279&hash=7224d59e6b74d9b2caf55ab40dfe0757cef4f71c66d3a7aba3de1d267d2ea409 err 500

[ptrus]

This is what oasis cli reports for the tx:

./cli paratime show 3995186 --paratime sapphire 4
...
=== Transaction 4 ===
Kind: oasis
Hash: 7224d59e6b74d9b2caf55ab40dfe0757cef4f71c66d3a7aba3de1d267d2ea409
Signer(s):
  1. AgGWYtk5tcLUzmh5XYrDn1iW3ZcyfLtfCHSgPnzAeaPp
     (signature: MEQCIClN4/jJvGNaFIuHz0QICbeXHRRsXFAzKj+Z6zPuccxsAiBmOu16GkZ5CQtQh3jWAZGC2kfRD4dHVPa3IeISKvmJGA==)
Content:
  Format: encrypted/x25519-deoxysii
  Body:
    {
      "data": "M+EtPEsK0Jx6YBWovQqDc8Vfmwy86L0EE66kv1++2RYxbXYj2zQsPmHPJLhC1VELHKVJQ/WKF+lTYhV3XhPdjTl1CiY8HiY7BcbL+t4nHB77mrGAeDBZV3nAJt4=",
      "nonce": "p8fnoq24sBge89XBVnvG",
      "pk": "ZDSfM+5QCZez+7fEjVOGmY2UlF82Q/KKR7Void3UHUQ="
    }
  Authorized signer(s):
    1. AgGWYtk5tcLUzmh5XYrDn1iW3ZcyfLtfCHSgPnzAeaPp (secp256k1eth)
       Nonce: 27
  Fee:
    Amount: 0.0012389 ROSE
    Gas limit: 12389
    (gas price: 0.0000001 ROSE per gas unit)

=== Result of transaction 4 ===
Status: unknown
Data:
  {
    "data": "9e845df1c05276f79f67b2d2f8eb68bc516438a473",
    "nonce": "00000000003cf63100000004000000"
  }

=== Events emitted by transaction 4 ===
Events: 2

  --- Event 0 ---
  Module: accounts
  Code:   1
  Data:
    [
      {
        "Burn": null,
        "Mint": null,
        "Transfer": {
          "amount": {
            "Amount": {},
            "Denomination": ""
          },
          "from": "oasis1qqugfeelqtp3qaxhdrwfv9nhpvwckjxr7yk369p7",
          "to": "oasis1qzy0yk6hwxx7e236cmawlt7xukpn8avtqq6le3l8"
        }
      },
      {
        "Burn": null,
        "Mint": null,
        "Transfer": {
          "amount": {
            "Amount": {},
            "Denomination": ""
          },
          "from": "oasis1qqugfeelqtp3qaxhdrwfv9nhpvwckjxr7yk369p7",
          "to": "oasis1qp3r8hgsnphajmfzfuaa8fhjag7e0yt35cjxq0u4"
        }
      }
    ]

  --- Event 1 ---
  Module: core
  Code:   1
  Data:
    [
      {
        "amount": 12389
      }
    ]

so it is indeed encrypted

[kostko]

Looks like an encrypted transaction, incorrectly interpreted by the explorer as plain?

[csillag]

Explorer recognizes encrypted transactions based on the presence of the encryption_envelope field, but here, we don't get one from nexus.

[csillag]

oh was this an encrypted transaction?

Yes this was.

edit: explorer says plain 👀

@pro-wh Yes it does, because Nexus is not including an encryption_envelope, which it usually does for encrypted TXs. Is there any chance to find out this reason for that?

[pro-wh]

should step through the analyzer on this tx

[Andrew7234]

Some early observations:

• The transaction AuthProof module is empty. Nexus expects this to be evm.ethereum.v0 for eth transactions, for which it extracts the eth hash.
• The sdk Call.Method is empty. Nexus currently expects this field to be populated, eg evm.Call. This is the primary reason why Nexus is unable to parse this transaction.

If this transaction style is intentional, we'll need to figure out some new heuristic for Nexus to determine whether a tx is evm/non-evm. (or brute force it and just try every runtime tx)

[kostko]

The above transaction is not an Ethereum transaction (which is why the auth proofs are regular signatures).

It is an encrypted SDK transaction, see the above CLI dump. The method is empty as is the case with all non-Ethereum encrypted transactions. The actual method name is encrypted.

[pro-wh]

ok yeah this transaction style is intentional. we need something similar to EVMMaybeUnmarshalEncryptedData but for the oasis level of encryption