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
Implement 'ENABLE' mode support in the Smart Sessions Module of the Nexus SDK. This mode allows permissions to be granted off-chain by the user and then activated on-chain by the dapp just before use.
Benefits & Outcomes
Enhance flexibility in permission management for smart sessions
Reduce on-chain transactions for granting permissions, potentially lowering gas costs
Allow dapps to manage permissions more dynamically, activating them only when needed
Improve user experience by reducing the number of on-chain transactions users need to approve
Provide a more versatile toolkit for developers implementing smart sessions
Implementation Ideas
Extend the SmartSessionMode enum in the Smart Sessions Module:
Feature or Improvement Description
Implement 'ENABLE' mode support in the Smart Sessions Module of the Nexus SDK. This mode allows permissions to be granted off-chain by the user and then activated on-chain by the dapp just before use.
Benefits & Outcomes
Implementation Ideas
Extend the
SmartSessionMode
enum in the Smart Sessions Module:Implement off-chain permission granting functionality:
Develop on-chain activation for 'ENABLE' mode:
Update the
toSmartSessionsValidator
function to support 'ENABLE' mode:Extend the Nexus client with new actions for 'ENABLE' mode:
Implement new methods for the extended client:
grantOffChainPermission
: For users to grant permissions off-chainactivatePermission
: For dapps to activate the off-chain granted permission on-chainUpdate existing smart session creation and use flows to accommodate 'ENABLE' mode
Implement proper error handling and edge case management for the new mode
Develop comprehensive unit and integration tests for 'ENABLE' mode functionality
Update documentation to reflect the new 'ENABLE' mode and its usage
References
Any References?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: