You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding this here rather than the secret toolkit repo, though it would probably be more fitting there -
Would be interesting to be able to validate Ethereum EIP-712 signed messages as permits. This could allow contracts to give Ethereum/EVM users the option to view private data, which can be useful in applications such as private messaging, NFT ownership, lotteries, etc.
For example, the Killroy Was Here mint could allow users to supply an Ethereum viewer address - that way they could view the movie without actually having a Secret address (or even installing Keplr), and if at a later stage they wanted to associate the NFT with an address on Secret to be able to sell/transfer it, the Ethereum permit could be supplied to the contract for ownership proof.
Since we already have secp256k1 signature validation as an API performance should be good (though RLP encoding/sha3 might not be super great - todo maybe we'll want to add sha3/keccak to the api for futureproofing).
Working with eth signatures is a bitch and a half, but with some tinkering this could be really interesting - thoughts?
The text was updated successfully, but these errors were encountered:
Adding this here rather than the secret toolkit repo, though it would probably be more fitting there -
Would be interesting to be able to validate Ethereum EIP-712 signed messages as permits. This could allow contracts to give Ethereum/EVM users the option to view private data, which can be useful in applications such as private messaging, NFT ownership, lotteries, etc.
For example, the Killroy Was Here mint could allow users to supply an Ethereum viewer address - that way they could view the movie without actually having a Secret address (or even installing Keplr), and if at a later stage they wanted to associate the NFT with an address on Secret to be able to sell/transfer it, the Ethereum permit could be supplied to the contract for ownership proof.
Since we already have secp256k1 signature validation as an API performance should be good (though RLP encoding/sha3 might not be super great - todo maybe we'll want to add sha3/keccak to the api for futureproofing).
Working with eth signatures is a bitch and a half, but with some tinkering this could be really interesting - thoughts?
The text was updated successfully, but these errors were encountered: