Overview
There is an issue regarding the Darwinia chain integration in the DSafe application, which manifests in two core phenomena:
- Within the DSafe interface, the Darwinia chain's Mastercopy contract is identified and flagged as an L2 type.
- Multisig transactions executed via DSafe do not appear in the transaction history after completion.
Problem Description
-
Mastercopy Flagging Issue: When interacting with the Darwinia chain in DSafe, its Mastercopy contract is systematically flagged as L2. The specific reason for this classification and its impact on subsequent functionalities are unclear.
-
Missing Transaction History: After a multisig transaction is successfully executed, the completed transaction record does not appear in the DSafe history list. This prevents users from tracking their completed operations.
Overview
There is an issue regarding the Darwinia chain integration in the DSafe application, which manifests in two core phenomena:
Problem Description
Mastercopy Flagging Issue: When interacting with the Darwinia chain in DSafe, its Mastercopy contract is systematically flagged as L2. The specific reason for this classification and its impact on subsequent functionalities are unclear.
Missing Transaction History: After a multisig transaction is successfully executed, the completed transaction record does not appear in the DSafe history list. This prevents users from tracking their completed operations.