The following transaction:

{
  "ref_block_num": 60166,
  "ref_block_prefix": 2531945151,
  "expiration": "2026-03-24T18:55:48",
  "operations": [[
    "transfer", {
      "from": "alice",
      "to": "bob",
      "amount": "1.000 HIVE",
      "memo": ""
    }
  ]],
  "extensions": []
}

Is being serialized as

06ebbf6aea9634dec269010205616c69636503626f62e80300000000000003535445454d0000000000

where

06eb = 60166(LE)
bf6aea96 = 2531945151(LE)
34dec269 = 1774378548(LE) = 24 March 2026 at 18:55:48 UTC
01 = 1 operation
02 = transfer operation
05 = length of "from"
616c696365 = "alice"
03 = length of "to"
626f62 = "bob"
e803000000000000 = "1000"(LE)
03 = precision
535445454d0000 = "STEEM\0\0"
00 = memo size(no memo)
00 = no operation extension(size 0)
00 = no transaction extension(size 0)

Just something I noticed while testing Hive serialization by hand and comparing to the results given by cli_wallet. Is this just legacy code or Hive still serializes/accepts transactions using the "STEEM" symbol?