We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Universal wallet uses the MetaMask Delegation Framework for handling wallet delegations, authorizations and intents. The framework includes 20+ enforcer smart contract modules for dictating transaction execution capabilities.
Right now the Universal dashboard only uses the ERC20TransferAmountEnforcer.sol on the authorizations page to enable wallet-to-wallet spending permissions.
We want to add the ability to include BlockNumberEnforcer.sol and TimestampEnforcer.sol enforcers in the delegations, so users can add timing conditionals to spending limits.
apps/wallet
apps/popup
apps/api-universal
The feature is dependent on the Multi-Enforcer Support Upgrade completition.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Context
The Universal wallet uses the MetaMask Delegation Framework for handling wallet delegations, authorizations and intents. The framework includes 20+ enforcer smart contract modules for dictating transaction execution capabilities.
Right now the Universal dashboard only uses the ERC20TransferAmountEnforcer.sol on the authorizations page to enable wallet-to-wallet spending permissions.
We want to add the ability to include BlockNumberEnforcer.sol and TimestampEnforcer.sol enforcers in the delegations, so users can add timing conditionals to spending limits.
Scope
apps/wallet
authorization form to include a "conditionals" field with timestamp options.apps/popup
app to support these new conditionals in the signTypedData render view.apps/api-universal
app to exclude delegations with invalid/expired timestamps.The feature is dependent on the Multi-Enforcer Support Upgrade completition.
The text was updated successfully, but these errors were encountered: