Add pseudo code reference to BN eligibity check (#1425)

Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
Signed-off-by: Michael Garber <michael.garber@hashgraph.com>
Co-authored-by: Michael Garber <michael.garber@hashgraph.com>
Co-authored-by: Joseph S. <121976561+jsync-swirlds@users.noreply.github.com>

Author: 3 people

HIP/hip-1357.md

@@ -14,7 +14,7 @@ hedera-acceptance-decision: Accepted
 status: Approved
 last-call-date-time: 2026-02-11T07:00:00Z
 created: 2025-12-02
-updated: 2026-02-10
+updated: 2026-03-11
 requires: 1056, 1086, 1137
 ---
 
@@ -56,13 +56,23 @@ year and converted to the native cryptocurrency to determine the daily reward is
 ## Specification
 During nightly reward fee calculations, when a `Node` in state is found to be eligible for consensus node rewards (based
 on participation in enough consensus rounds) the logic may iterate of over the non-null `Node.associated_registered_node`
-list. If an entry is found to match a registered node of type `BLOCK_NODE` then the network should issue an additional 
+list. If an entry is found to match a registered node with an endpoint of type `BlockNodeEndpoint` that declares PUBLISH API support
+then the network should issue an additional 
 `CryptoTransfer` of `(targetYearlyBlockNodeRewardsUsd ($) / # of staking periods per year) * exchangeRate (h/$)`
 to the `Node.AccountId`.
 
 This ensures that governing authority members only receive block node rewards if they satisfy both consensus and block
 node operation obligations.
 
+The following pseudo-code depicts the logic
+```
+If CN is eligible for CN rewards
+  For each RegisteredNode present in Node.associated_registered_node
+    For each RegisteredServiceEndpoint 
+      If (RegisteredServiceEndpoint.endpoint_type is of type BlockNodeEndpoint) & (BlockNodeEndpoint has endpoint_api of type PUBLISH)
+        then CN is eligible for block node rewards
+```
+
 
 ### Consensus Node Specification