URGENT: Unaudited funds cannot be spent after HF v11 — transactions rejected (`Invalid transaction type for HF_VERSION > HF_VERSION_V11`)

[szgnyldrm]

I have unaudited ZEPH outputs in my wallet that are no longer spendable after Hardfork v11. Attempts to audit / audit_all or transfer these outputs result in rejection by the daemon with the error:

Invalid transaction type for HF_VERSION > HF_VERSION_V11

This is urgent: the funds are visible in my wallet's transfers but the network refuses the transactions. I need an official remediation path (migration tool, permitted on-chain conversion, or other recovery mechanism) from the core team.

Wallet / node context

• Wallet address (source): ZEPHYR2Bk (shown in my wallet prompt)
• Destination address used for tests: ZEPHYR3TwWsYLkCdMgURQig4...69cg9x4a
• Node / chain: mainnet
• Node status (from ./zephyrd status while synced):

Height: 619369/619369 (100.0%) on mainnet, not mining, net hash 145.64 MH/s, v11, 12(out)+0(in) connections, uptime 0d 0h 8m 13s

• I ran rescan_bc / refresh and wallet shows the outputs as unaudited (see show_transfers below).

Commands I ran (summary)

1. Rescan & refresh:

rescan_bc
refresh

2. Show transfers (wallet output):

show_transfers
142480     in unlocked      2023-12-15 21:03:07Z      73.030000000000 ZEPH (unaudited) 6bd63fb83de003092cad63491bc4459fd073b54f052136497a709498689ed3da ...
352475     in unlocked      2024-10-03 00:30:29Z     451.250000000000 ZEPH (unaudited) 426b97930e7502b3d8bf1f97dd795fd1f86ee3a815f23a8b12b034a44ac1ec9d ...
361589     in unlocked      2024-10-15 17:06:28Z      26.680000000000 ZEPH (unaudited) 17decc4933349211f16a1fc836aa2504d44f6e06f50f37015e4ab88fbb2a6826 ...

3. Attempted audit (test 0.1 ZEPH):

audit ZEPHYR3TwWsYLk... 0.1

# Confirmed (Yes) on prompt

Result:

Error: transaction <6a1e42020dcce4132c883a7087e4d73fc7516ed5beb375bc03168fd033e08c6a> was rejected by daemon

4. Attempted audit_all (spent all unaudited outputs); after confirming the wallet published the tx, the daemon rejected with the HF error:
   Rejected tx ids from logs (examples):

d402288778885f92f88b1139196c36b7eca49618339635dabe3b36205936d006
6a1e42020dcce4132c883a7087e4d73fc7516ed5beb375bc03168fd033e08c6a
6a281ecaf251535ab5957456ae49afa338e237602a1f8d184602c5916728356c
be5d395fca57aaeb379308378fdbd8bfd8219d5f439df4827f3286d5c03f381a
e7c0cd9ef9328481dc9e249aae81b4e230f9fc8babacfb404a211fb4673f6bb3

Relevant daemon log lines

2025-10-09 11:47:06.404  E Invalid transaction type for HF_VERSION > HF_VERSION_V11: <d40228877...>
2025-10-09 11:51:21.603  E Invalid transaction type for HF_VERSION > HF_VERSION_V11: <6a1e4202...>
...

Problem description

• The wallet shows unaudited outputs (see show_transfers), but any attempt to convert/spend them is rejected by the network with the Invalid transaction type for HF_VERSION > HF_VERSION_V11 error.
• rescan_bc / refresh do not change the status — outputs remain unaudited.
• The rejection appears to be an HF enforcement: transactions with the old "audit" type are refused on v11+ network nodes.

Requested action (what I need from maintainers)

Please advise urgently on one of the following (or provide an official alternative):

1. A supported, documented migration/recovery tool or on-chain migration transaction that converts unaudited outputs into HF v11-compatible outputs, or
2. An official exception / operator-side migration procedure for wallets with unaudited outputs, or
3. A script or wallet patch I (and other affected users) can run to safely migrate funds (including any required node version / settings), or
4. Clear confirmation that unaudited outputs are permanently unusable and whether any compensatory procedure will be offered.

For whichever path you propose, please include:

• Exact commands and minimal required versions (daemon & wallet).
• Expected fees and whether transactions must be split (due to tx-size / privacy).
• Whether a signed tool will be provided by the core team (preferred).
• If this is a known issue that will be resolved automatically by the network, please provide timeline and whether users should stop attempting to publish transactions (to avoid mempool spam / repeated rejects).

Reproducible steps (for devs)

1. Open a wallet with unaudited outputs (as in show_transfers above).
2. Run audit or audit_all to convert/send outputs. Confirm prompts.
3. Observe daemon rejection with Invalid transaction type for HF_VERSION > HF_VERSION_V11 in node logs.

Attachments / supporting data

• show_transfers output (included above).
• Rejected tx ids and the zephyrd log lines (included above).
• ./zephyrd status (included above).

Privacy / security

I am not including any private keys/seed. I am providing public wallet address and tx ids only. I have already backed up my wallet files and seeds offline.

[szgnyldrm]

I've wasted a week because of this error. You need to provide an urgent fix!

[szgnyldrm]

I read the comments and, from what I understand, you have put a ridiculous action into effect. Years ago you introduced an 'innovation' that treats investors who stored their wallets as fools. This is not an innovation — it is theft! If you have no solution to recover these coins, you are worth nothing.

[szgnyldrm]

He kicked me out of the Discord group while I was discussing this solution. Don't be foolish about investing in this chain!