# \[SNIP\] Off-chain signatures (à la EIP712)

**URL:** <https://community.starknet.io/t/snip-off-chain-signatures-a-la-eip712/98029>\
**Category:** SNIPs\
**Created:** [August 2, 2023, 4:19pm UTC](https://community.starknet.io/t/snip-off-chain-signatures-a-la-eip712/98029 "2023-08-02T16:19:36Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![bowlofchilli](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/bowlofchilli/32/73368_2.png) [@bowlofchilli](https://community.starknet.io/u/bowlofchilli)\
**Post date:** [October 17, 2023, 1:19am UTC](https://community.starknet.io/t/snip-off-chain-signatures-a-la-eip712/98029/6 "2023-10-17T01:19:54Z")

</div>

A few questions

1. why does type enum uses starknet keccak? and not Pedersen or Poseidon.
2. ‘StarknetDomain’ instead of ‘StarkNetDomain’ no ?
3. Defining a json schema might be better here to specify the constraints a little more. We have done that for the [sign-in-with-starknet proposal](https://community.starknet.io/t/sign-in-with-starknet-technical-proposal/95683/4) and probably could be utilized here
4. Could we use the byte array type coming in the next release to remove the 31 character limit for strings? Probably a major impediment for any adoption for off chain signing.

---

_[View the full topic](https://community.starknet.io/t/snip-off-chain-signatures-a-la-eip712/98029)._