Transferring host... Transaction result: tecHOOK_REJECTED

[mworks-proj]

**Issue: Unable to Transfer Due to tecHOOK_REJECTED **

Environment

• Current Version: v0.12.1
• Target Version: v1.0.0
• OS: Ubuntu 24.0

---

Problem Description

We are encountering a recurring issue where transactions are being rejected with the error code tecHOOK_REJECTED. This is preventing us from completing necessary transfers in preparation for upgrading to Evernode v1.0.0.

The logs indicate that the transaction is being rejected by a hook on either the sending or receiving account. Below is a detailed snippet of the logs for reference.

---

Relevant Logs

Jan 04 01:06:05 everTrans node[14886]: [dbg] Transaction result: tesSUCCESS
Jan 04 01:06:24 everTrans node[14886]: [err] Rejected by hook on sending or receiving account.
Jan 04 01:06:43 everTrans node[14886]: [err] Rejected by hook on sending or receiving account.
Jan 04 01:10:49 everTrans node[14886]: [dbg] Reporting heartbeat at Moment 9283...
Jan 04 01:10:55 everTrans node[14886]: [dbg] Transaction result: tesSUCCESS
Jan 04 01:25:30 everTrans node[14886]: [dbg] Instance created for rKuQf6A8qGa87KvyycwSkMqBTUwnYJQGxk
Jan 04 01:25:36 everTrans node[14886]: [dbg] Transaction result: tesSUCCESS
Jan 04 01:53:52 everTrans node[14886]: [dbg] Reporting heartbeat at Moment 9284...
Jan 04 01:53:56 everTrans node[14886]: [dbg] Transaction result: tesSUCCESS
Jan 04 01:55:57 everTrans node[14886]: [err] Rejected by hook on sending or receiving account.
Jan 04 01:56:14 everTrans node[14886]: [err] Rejected by hook on sending or receiving account.

From the logs:
- **Registry Account**: `rmv53yu8Wid6kj6AC6NvmiwSXNxRa8vTH`
- **Governor Account**: `rBvKgF3jSZWdJcwSsmoJspoXLLDVLDp6jg`
- **Heartbeat Account**: `rHktfGUbjqzU4GsYCMc1pDjdHXb5CJamto`

---

## **Steps Taken**
1. **Cleared All Hooks**: Verified and successfully removed all hooks from the sending account (`r4sfoGVS9o2rMpMLRHFzYhTJ3zwXYuEvAX`) using the `SetHook` transaction with an empty `CreateCode`.
2. **Checked Hooks on Destination Account**: Queried the `AccountObjects` of the receiving account (`rmv53yu8Wid6kj6AC6NvmiwSXNxRa8vTH`) and found active hooks, likely contributing to the rejection.
3. **Tested Simple Transactions**: Attempted a simple EVR payment, which was successful to and from host account.

---

## **Observed Behavior**
- The issue appears to be tied to the logic in a hook deployed on the destination account (`./src/registry.c`).
- The hook execution result consistently shows:
  ```json
  {
    "result": 2,
    "returnCode": 645,
    "message": "./src/registry.c"
  }

---

Impact

This issue is blocking our ability to transfer and complete the upgrade process to Evernode v1.0.0 on Ubuntu 24.0.

---

Request for Assistance

1. Hook Logic Review:

   • Could the current hook logic on the destination account (rmv53yu8Wid6kj6AC6NvmiwSXNxRa8vTH) be shared or explained, particularly the conditions leading to tecHOOK_REJECTED with return code 645?
   • Are there specific parameters or configurations required to make transactions pass?

2. Upgrade Guidance:

   • Is there a recommended process to bypass or adjust the hook logic temporarily to allow these transfers for the upgrade?

3. Best Practices for v1.0.0 Migration:

   • Any suggestions to avoid similar issues in the future during upgrades?

---

Supporting Information

• Transaction Metadata:

  {
    "TransactionType": "URITokenCreateSellOffer",
    "Account": "r4sfoGVS9o2rMpMLRHFzYhTJ3zwXYuEvAX",
    "Amount": "1",
    "Destination": "rmv53yu8Wid6kj6AC6NvmiwSXNxRa8vTH",
    "Fee": "12666",
    "TransactionResult": "tecHOOK_REJECTED"
  }

• Logs from /var/log/systemd and everTrans: Provided above.

---

Please advise on the next steps to resolve this and proceed with the upgrade. Let me know if further details or logs are required.