# Important Community Update on ic0.app domain being flagged by an anti-spam blocklist **URL:** \ **Category:** Developers\ **Created:** [February 17, 2023, 8:26pm UTC](https://forum.dfinity.org/t/important-community-update-on-ic0-app-domain-being-flagged-by-an-anti-spam-blocklist/18537 "2023-02-17T20:26:44Z")\ **Posts on this page:** 1\ **Showing post:** 107
**Author:** ![Roman](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/roman/32/6307_2.png) [@Roman](https://forum.dfinity.org/u/Roman)\ **Post date:** [April 18, 2023, 6:38pm UTC](https://forum.dfinity.org/t/important-community-update-on-ic0-app-domain-being-flagged-by-an-anti-spam-blocklist/18537/107 "2023-04-18T18:38:25Z")
> [@bjoern](#): > > We are currently designing a scheme that allows _any_ canister on the Internet Computer to use the ICP hardware wallet app for securely displaying and signing transactions, and that would work as follows: > > - The canister developer specifies for each pair of (canister id, method name) a schema for rendering the parameters. That would likely be a transaction name and a structure that specifies for each field of the Candid argument whether it should be displayed and the title that should be used. (We need to devise a format for this, this actually is the main open design task.) > - The canister then signs said schema with the IC’s threshold ECDSA signature method. > - The dapp front end sends the unsigned transaction along with the signed schema to the hardware wallet. > - The hardware wallet derives the canister’s ECDSA public key from the IC’s ECDSA root public key and the canister id, and verifies the signature on the schema. It then uses the schema to display the transaction to the user, and signs the transaction when the user approves. Hi @bjoern, hope this message finds you well. Any ETA of this wonderful feature ? --- _[View the full topic](https://forum.dfinity.org/t/important-community-update-on-ic0-app-domain-being-flagged-by-an-anti-spam-blocklist/18537)._