Keep track of features that are fully supported in services but not yet in mirror node

[quiet-node]

Problem

Certain features are fully supported in Services but not yet in the Mirror Node due to the ongoing rework of the Web3 module. As a workaround, these features can be invoked in non-view functions to ensure they are executed against the Consensus Node rather than the Mirror Node.

Once the Web3 module rewrite in the Mirror Node is complete, these methods should be transitioned back to view functions instead of non-view functions.

Tasks

Beta Give feedback

1. HRC719 isAssociated()