Here’s a summary of Cobo Argus V2.1,

*Support for multiple blockchains, more DeFi protocols, and wallet integrations.

*UI Optimization: Redesigned with a focus on user business needs, renamed the “Strategy” and “Bot” pages into “Farming” and “Trading”.

*Improved Role-based Access Control and Workflow Management : Expanded the permissions of the “Operator” role, allowing them to edit and configure single-sig authorizations and strategies bots. Introduced transaction bundle for convenient single-Sig approvals.

*Enhanced “Organization” Interface: Renamed the "Team" menu to “Organization”. Added a drop-down menu under Safe{Wallet} to allow members of the organization to view all wallet operations details within the organizational structure.

*Two Important Features Added: Bot now supports Webhook configuration, and it is compatible with account abstraction (AA) wallets under the Safe{Wallet} modular standard.

Below, we will provide an in-depth introduction to this update:

1. Add Support for Base, Mantle, and Gnosis Chain, DeFi Protocols, and Wallet Integrations

• DeFi protocols added: Lybra V2 and Pendle-Equilibria.

• Rabby Wallet is now supported for importing into Cobo Argus, allowing users to choose Rabby for on-chain interactions, further enhancing the user experience.

• Added support for Base, Mantle, and Gnosis Chain.

2. Webhook Configuration for Bots

The addition of webhook configuration for bots is a key update in the Argus V2.1 release. It signifies a significant stride towards revolutionizing on-chain security infrastructure from  “passive monitoring” to “active prevention”, unlocking new revenue streams for on-chain security providers. Argus's solution of “let the robots do it for you” will become an essential component of security infrastructure.

Before we delve into Argus 2.1, let's first understand what webhooks are, how they work in Web3, and what problems the new webhook configuration solves for clients.

In the online world that is highly interconnected, systems often perform suboptimally when isolated from each other. This means that it is essential for systems to communicate with each other to share data. Webhooks provide an effective way for systems to communicate across systems. When a specific event occurs in the source system, it can communicate with another target system by sending an HTTP request to the webhook URL. In the process, the source system shares additional information about the related event in the “request payload”.

In simple terms, a webhook is a sequence of HTTP requests triggered by specific events within the source system (sender) and automatically sent to the target system (receiver).

Similar to traditional webhooks, Web3 webhook systems also support cross-system communication. However, what sets them apart is that in the context of Web3, webhooks listen for events originating from the blockchain, and the real-time request payload is transmitted to the backend. In this context, the source system is the blockchain, and the target system corresponds to a user's project.

Like traditional webhooks, Web3 webhooks do not require periodic polling of applications to check for new status updates. Instead, they leverage blockchain webhooks to autonomously detect specific events and trigger request payloads. This means that events such as on-chain asset transfers, price movement in DeFi, loan liquidation alerts, specific wallet actions, or contract initiations can all trigger real-time notifications off-chain.

The introduction of webhook configuration support in Argus V2.1 means that Argus will now support event trigger condition configurations from external systems. This not only caters to the more complex and nuanced needs of professional teams but also allows projects with existing internal monitoring systems to seamlessly integrate their risk control algorithms with Argus. They can then invoke Argus' webhook automation execution robots to enhance operational efficiency.

For a professional quant trading team, to meet their business requirements, they often develop an in-house monitoring system to track various metrics related to their trades. In such cases, the quant team can continue to use their internal monitoring system, leveraging the wealth of business data and analytical resources they already possess. They can then initiate monitoring and execute subsequent actions through Argus' webhook automation robots.

For services like BlockSec, Hypernative, and ChainBot (which currently support Cobo Argus channels) that primarily focus on on-chain security monitoring, they can directly use their existing robust AI risk control algorithm configurations for alert strategies and business processes. They can then invoke webhooks to integrate with Argus robots for subsequent automated execution.

Before this, security efforts were confined to the "monitoring" level. However, by integrating Argus and customizing Webhook configurations, the accumulated capabilities within the security domain can be leveraged effectively. These signal recognition and risk capture capabilities can be transformed into practical risk prevention and withdrawal operations. When triggered by the corresponding risk conditions, invoking webhooks can initiate real-time execution by Argus, promptly blocking the occurrence of risks.

Incidents that could have led to hacks are thwarted, and assets that might have been lost are recovered. Consequently, security solutions are transformed into productivity tools, delivering tangible value to users. Once real value is generated, it also implies the possibility of users being willing to pay for this service.

For security service providers, from risk monitoring and signal recognition to actual security prevention and control, a complete business model cycle is realized. It turns monitorable risk signals into quantifiable cash flows, thereby achieving genuine value gains.

From proactive monitoring to real-time prevention, the security service infrastructure is embarking on the next frontier. The entire industry chain is becoming more complete, with the potential for downstream quantifiable revenue streams. For security service providers, it's a matter of focusing on their core competencies, which include optimizing trigger conditions, configuring alert strategies, and recognizing risk signals. The execution part is what Argus has always excelled at - "let the robots do it for you."

Of course, "Let Argus bots do it for you" is conditional on security and efficiency. Over the years, Argus has accumulated expertise in ACL authorization systems, multisignature solutions, and non-custodial configurations for major blockchains, making it a battle-tested DeFi investment management tool. The mechanism of ensuring limited execution and flexible authorization perfectly balances security and efficiency.

At this point, Argus is not just a DeFi investment management tool that balances security and efficiency; it is also becoming an integral part of automated operational systems in the security service infrastructure. Argus bots monitor attacks in real-time and identify risks, allowing for immediate responses to ongoing security issues, vulnerabilities, and financial risks.

3. Enhancing the User Experience for Product Interactions

As a DeFi investment management product that emphasizes teamwork, we have always prioritized usability, convenience, and security in our product design. Our ultimate goal has been to create a seamless and more convenient collaborative experience for teams.

This brings us to the core objective of this version update - we aim to provide new users with a quicker onboarding experience while also catering to the diverse preferences of our existing user base

Over the past period, we have engaged in one-on-one conversations with several key users to gather insights into their usage patterns. These discussions covered topics such as wallet preferences, DeFi protocol configurations, and DeFi bot preferences, catering to both casual and experienced users. Based on the valuable feedback we received, we've made adjustments and refinements to our product pages.

Our efforts to enhance the product interaction experience are evident in several key areas:

3.1 Redesign of Operation Pages with a User-focused Approach, Transforming the "Strategy" and "Bot" Pages into the "Farming" and "Trading" Sections

Operations related to liquidity mining have been consolidated within the “Farming” section. Activities related to DEX trading are now located under the “Trading” section. Given that DEX trading often involves multiple single-signature authorization steps, we've streamlined the process in the "Trading" section, allowing users to complete these authorizations with a single click, such as with 1inch's single-signature authorization. For protocols associated with liquidity mining rewards (such as Curve, EQB, etc.), which typically involve more intricate multi-step operations like setting single-signature authorizations, configuring claiming bots, and managing withdrawal bots, we have empowered users to flexibly add and configure these elements within the “Farming” section based on their unique requirements.

The complex multi-step operations involving "Farming" activities can be configured on a single tab.

"Trading" tab for one-click single-signature authorization configuration.

The new version places the user at the center, directly presenting "Farming" and "Trading" options on the left sidebar. This approach ensures that all specific business needs can be efficiently configured on a single page, resulting in a more intuitive user interface and a smoother overall process.

3.2  Introducing the Transaction Bundle for Streamlined Decision-Making

In Argus V2.1, we have introduced support for the feature of “Transaction Bundle”, coupled with expanded permissions for the "Operator" role, which now allows this role to edit and configure single-signature authorizations and bot strategies.

Here is how it works: when an organization's “Operator/Admin role” configures “Single-Signature Authorizations” and “Bot Strategies”, team members can opt to add these configurations to the transaction bundle. Subsequently, these configurations undergo a unified review and approval process by the “Safe Owner(s)”. Once the Safe Owner(s) review the configurations and reach the multisig threshold, all operations within the bundle are batched and submitted as a single transaction, ultimately taking effect on-chain.

By empowering the "Operator" role to engage in single-signature authorizations and configure bot strategies, and by introducing the transaction bundle interface to showcase pending multisig approvals, this well-structured workflow management—where Operators are involved in operations and Safe Owner(s) provide unified approvals—enhances work efficiency, streamlines workflow processes, and boosts internal organizational productivity, all while maintaining robust security. Rather than scattered approvals during fragmented time intervals, a unified “transaction bundle” approval interface consolidates multiple submissions into a single approved transaction, effectively bolstering security.

The current transaction bundle feature exclusively accommodates multisig processes initiated through configurations within the "Farming" and "Trading" sections. This includes both bot setups and single-signature authorizations. Please note that it does not extend to multisig operations initiated via user-defined permissions or token approval management.

3.3 Safe{Wallet} Dropdown Menu: A New Way for Institutions to Manage Their Wallet Assets

Team members now have the ability to toggle between different “organizations” via the left sidebar. This grants them access to detailed insights regarding Safe{Wallet} imports within the chosen organization. Further to that, a novel “Home” page has been added to display the total assets, Cobo Safe, strategy authorizations, and bot information for the selected Safe{Wallet}. This feature simplifies asset management for teams, allowing them to switch between various Safe{Wallets} as needed.

Browse the details of Safe{Wallet} imported under the "Organization."

3.4 The “Team” menu has been renamed to "Organization" and the "Settings" menu has been merged into the "Organization" menu, making it easier for Admins to manage team members.

4. Compatibility with AA Wallets under the Safe{Wallet} Modular Standard

Cobo Argus, built on the foundation of Safe{Wallet}, inherits its well-established contract security. Safe was an early pioneer in account abstraction, predating EIP 4337, and it has a significant user base in wallets. As of November 3, 2023, the Dune dashboard titled “Safe across chains” developed by Safe indicates over 4.69 million Safe accounts spanning across more than 12 chains. Cobo Argus plays a pivotal role in the Safe{Core} AA modular ecosystem, catering to an extensive user community of Safe wallets since its inception. It offers robust DeFi investment management tools that bolster the broader Safe{Core} AA modular ecosystem.

Cobo Argus also brings value to other wallet ecosystems compatible with the Safe{Core} modular architecture. By adhering to the standards of Safe{Core} modular architecture, Cobo Argus seamlessly integrates with these ecosystems, providing extension plugin services. This means that users of smart contract wallets that conform to the Safe{Core} modular architecture (including Safe and those inspired by Safe's modular approach like Biconomy) can enhance their wallet functionalities by incorporating Cobo Argus plugins. These plugins expand upon the capabilities outlined in the ERC-4337 interface, including DeFi authorization, DeFi bots, batch token approvals, on-chain risk monitoring, and notifications.

One notable advantage of smart contract wallets over Externally Owned Account (EOA) wallets is their support for modular design. This implies that developers (both third-party and otherwise) can easily extend wallet functionalities through plug-and-play contract modules, allowing users to tailor their wallet experience to their specific needs.

From a user experience standpoint, this design effectively tackles account-level challenges. End-users can expand their features by simply switching plugins, akin to adding new functionalities to a wallet, much like installing Google extensions. There is no need for contract upgrades or account address changes, making it comparable to changing banks while retaining the same account.

For users new to Web3, this nearly Web2-intuitive experience comes with zero learning curve or cognitive burdens. It's exceptionally user-friendly for "newbie conversion" and has the potential to expedite mainstream adoption, facilitating the "seamless onboarding" of incremental users.

While account abstraction (AA) has not gained widespread adoption, Cobo Argus firmly believes it represents a progressive direction in the crypto industry, paving the way for mainstream adoption. As a crypto-native enterprise, Cobo Argus has consistently taken an active role in exploring and spearheading the development of related crypto infrastructure.  Leveraging our industry expertise in areas like DeFi investment management and institutional custody, we have turned challenges into product demands, resulting in a range of products focusing on DeFi investment management and institutional custody solutions.

In the future, Cobo Argus will continue to contribute to the ultimate goal of account abstraction and endeavor to “onboard billions of people”.