> For the complete documentation index, see [llms.txt](https://docs.bitoftrade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitoftrade.com/for-developers/cross-chain-messaging-protocol/how-it-works/signer-service.md).

# Signer Service

Signer service is used to verify specific events. By request the service produces the proof for events. Proof of the event is a signature created by the signer's address. 

*Under the hood, Signer could implement any protocol to sign messages.* 

To create an event signature **Signer** signs a specific [`eventHash`](broken://pages/g7yqh32PATsvCWuyRP4n). 

After the signature was generated, it could be used on your smart contract to verify the event. After successful verification, you could trust this event and do your dApp logic.  

See the [Signer Interface](/for-developers/cross-chain-messaging-protocol/how-it-works/signer-service/signer-interface.md) page to get endpoint params to sign the event. 

You could also interact with our public [Signer](http://20.56.51.41:4000/api/).