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
[Perhaps for much later on... e.g. when user-defined smart contracts are enabled.]
The spec currently has a MultiSig Account Actor which can support backups and sharing funds. Below are 2 additional types of advanced Wallet constructions popular in the Ethereum community (although many wallets are still simple HD wallets). The Gnosis Safe wallet, uPort, 3Box and Status among others implement some variation of these features and they inspire dapp developers with improved on-boarding and persistent identity for their end-users.
Proxy Identity Contracts
Proxy contracts enable identity addresses and metadata to be persisted, while their Controller contracts that manage them can change when keys are rotated or lost. Controller Contracts control access control and recovery logic while forwarding messages to the proxy that initiates transactions.
Simple Proxy Account (ERC-725)
“The proxy has 2 abilities: (1) it can execute arbitrary contract calls, and (2) it can hold arbitrary data through a generic key/value store. One of these keys should hold the owner of the contract with long-lasting identifiable profiles.”
Verified Claims (EIP 735) can be attached to the Proxy Contract which enables identity verifications signed by other parties.
Persistent identity and metadata
Key rotation as a security best practice
Digital Signatures
Reputation
Signing with secp256k1 to a proxy that uses BLS?
Meta Transactions and Relayers
Executable Signed Messages & Transaction Relayer (EIP-1077)
Embedding a signed transaction as the payload of another transaction. Allows users to sign a message to show intent, but a 3rd party Transaction Relayer submits it to the chain & a proxy contract on chain checks the signature and executes it on the original user’s behalf. (Use Cases, Implementation)
“Gas as a Service” - users can submit signed transactions to a relayer that pays gas on behalf of the user
Batching multiple transactions so users only have to sign once
Disposable keys and Burner Wallets for easier on-boarding
End-users not having to acquire FIL on an exchange before use
Later:
Other types of tokens as gas (e.g. stablecoins)
If there's interest in this we can collect more research on implementations.
The text was updated successfully, but these errors were encountered:
[Perhaps for much later on... e.g. when user-defined smart contracts are enabled.]
The spec currently has a MultiSig Account Actor which can support backups and sharing funds. Below are 2 additional types of advanced Wallet constructions popular in the Ethereum community (although many wallets are still simple HD wallets). The Gnosis Safe wallet, uPort, 3Box and Status among others implement some variation of these features and they inspire dapp developers with improved on-boarding and persistent identity for their end-users.
Proxy Identity Contracts
Proxy contracts enable identity addresses and metadata to be persisted, while their Controller contracts that manage them can change when keys are rotated or lost. Controller Contracts control access control and recovery logic while forwarding messages to the proxy that initiates transactions.
Simple Proxy Account (ERC-725)
“The proxy has 2 abilities: (1) it can execute arbitrary contract calls, and (2) it can hold arbitrary data through a generic key/value store. One of these keys should hold the owner of the contract with long-lasting identifiable profiles.”
Verified Claims (EIP 735) can be attached to the Proxy Contract which enables identity verifications signed by other parties.
Meta Transactions and Relayers
Executable Signed Messages & Transaction Relayer (EIP-1077)
Embedding a signed transaction as the payload of another transaction. Allows users to sign a message to show intent, but a 3rd party Transaction Relayer submits it to the chain & a proxy contract on chain checks the signature and executes it on the original user’s behalf. (Use Cases, Implementation)
Later:
If there's interest in this we can collect more research on implementations.
The text was updated successfully, but these errors were encountered: