What happens if a specific wallet policy does not utilise TCSS automated rules?

If an outbound wallet policy chooses not to utilise TCSS rules (such as automated address book lookups), it defaults completely to the manual human quorum by design.

While removing TCSS rules strips away automated address book pre-filtering, the un-bypassable hardware barrier remains perfectly intact. The transaction cannot be executed unless the necessary human signers (e.g., the 2-of-5 iOS device quorum) cryptographically sign and authorize the transfer on their devices.

Was this article helpful?
0 out of 0 found this helpful