status-desktop/ui/app/AppLayouts/Wallet/services/dapps/plugins/qmldir

ChainsSupervisorPlugin 1.0 ChainsSupervisorPlugin.qml
DAppConnectionsPlugin 1.0 DAppConnectionsPlugin.qml
SiweRequestPlugin 1.0 SiweRequestPlugin.qml
SiweLifeCycle 1.0 SiweLifeCycle.qml
SignRequestPlugin 1.0 SignRequestPlugin.qml
feat(WC): Handle unavailable chains or internet connection This commits implements the `connect` `disconnect` session events for WC and also disables primary buttons for WC whenever there is no connection to internet or chains. + update tests 2024-10-23 15:58:45 +03:00			`ChainsSupervisorPlugin 1.0 ChainsSupervisorPlugin.qml`
fix(WC): Refactor dapps service to work with multiple SDKs This PR is refactoring the dapps service to avoid code duplication between SDKs and also to avoid overlapping requests/responses. It brings Browser Connect inline with Wallet Connect in terms of session management and sign transactions. New architecture: WalletConnectService becomes DAppsService. Its responsibility is to provide dapp access to the app. This is the component currently used by the UI What does it do: 1. Provide dapp APIs line connect, disconnect, session requests etc 2. Spawn app notifications on dapp events 3. Timeout requests if the dapp does not respons DAppsRequestHandler becomes DAppsModule. This component is consumed by the DAppService. Its responsibility is to aggregate all the building blocks for the dapps, but does not control any of the dapp features or consume the SDKs requests. What does it do: 1. Aggregate all the building blocks for dapps (currently known as plugins) DAppConnectionsPlugin - This component provides the session management features line connect, disconnect and provide a model with the connected dapps. SignRequestPlugin - This component provides the sign request management. It receives the sign request from the dapp, translates it to what Status understands and manages the lifecycle of the request. 2024-11-07 11:10:10 +02:00			`DAppConnectionsPlugin 1.0 DAppConnectionsPlugin.qml`
feat(WC): Implementing SIWE flows To squash - Implementing SIWE flows 2024-10-19 00:22:06 +03:00			`SiweRequestPlugin 1.0 SiweRequestPlugin.qml`
fix(WC): Refactor dapps service to work with multiple SDKs This PR is refactoring the dapps service to avoid code duplication between SDKs and also to avoid overlapping requests/responses. It brings Browser Connect inline with Wallet Connect in terms of session management and sign transactions. New architecture: WalletConnectService becomes DAppsService. Its responsibility is to provide dapp access to the app. This is the component currently used by the UI What does it do: 1. Provide dapp APIs line connect, disconnect, session requests etc 2. Spawn app notifications on dapp events 3. Timeout requests if the dapp does not respons DAppsRequestHandler becomes DAppsModule. This component is consumed by the DAppService. Its responsibility is to aggregate all the building blocks for the dapps, but does not control any of the dapp features or consume the SDKs requests. What does it do: 1. Aggregate all the building blocks for dapps (currently known as plugins) DAppConnectionsPlugin - This component provides the session management features line connect, disconnect and provide a model with the connected dapps. SignRequestPlugin - This component provides the sign request management. It receives the sign request from the dapp, translates it to what Status understands and manages the lifecycle of the request. 2024-11-07 11:10:10 +02:00			`SiweLifeCycle 1.0 SiweLifeCycle.qml`
			`SignRequestPlugin 1.0 SignRequestPlugin.qml`