feat(protocol-kit): Add Abitype for contract types and use EIP-1193

.github/workflows/e2e-test.yml → .github/workflows/api-kit-e2e-test.yml

@@ -1,4 +1,4 @@
-name: e2e Test
+name: API Kit - E2E Tests
 on:
   pull_request:
   push:
@@ -18,7 +18,15 @@ jobs:
         with:
           node-version: ${{ matrix.node-version }}
           cache: yarn
-      - run: |
-          yarn install --frozen-lockfile
-          yarn build
-          yarn test:ci
+      - name: Yarn install
+        run: yarn install --frozen-lockfile
+
+      - name: Build
+        run: yarn build
+
+      - name: Test
+        run: |
+          cd packages/api-kit
+          yarn test:ci:ethers
+          yarn test:ci:web3
+          yarn test:ci:viem

.github/workflows/test_contracts.yml → .github/workflows/protocol-kit-e2e-test.yml

@@ -1,5 +1,6 @@
-name: Safe Core SDK Test - Contracts
+name: Protocol Kit - E2E Tests
 on:
+  workflow_dispatch:
   pull_request:
   push:
     branches:
@@ -11,7 +12,7 @@ jobs:
     strategy:
       matrix:
         node-version: [20.x]
-        provider: [ethers, web3]
+        provider: [ethers, web3, viem]
         contract-version: [v1.0.0, v1.1.1, v1.2.0, v1.3.0, v1.4.1]
     steps:
       - uses: actions/checkout@v4

.github/workflows/test.yml → .github/workflows/sdk-test.yml

@@ -1,4 +1,4 @@
-name: Monorepo Test
+name: SDK - Unit Tests
 on:
   pull_request:
   push:

.gitignore

@@ -54,9 +54,6 @@ cache
 artifacts
 deployments
 
-# Typechain
-typechain
-
 openapi/
 
 .idea

guides/integrating-the-safe-core-sdk.md

@@ -24,16 +24,14 @@ To integrate the [Safe Core SDK](https://github.com/safe-global/safe-core-sdk) i
 
 ## <a name="initialize-sdks">2. Initialize the SDK’s</a>
 
-### Instantiate an EthAdapter
+### Select your Ethereum `provider` and `signer`
 
-First of all, we need to create an `EthAdapter`, which contains all the required utilities for the SDKs to interact with the blockchain. It acts as a wrapper for [web3.js](https://web3js.readthedocs.io/) or [ethers.js](https://docs.ethers.org/v6/) Ethereum libraries.
+To use our kits, you need to provide an Ethereum provider and a signer. The provider is the connection to the Ethereum network, while the signer is an account that will sign the transactions (a Safe owner). When using an injected provider like MetaMask, the signer is the account selected in the wallet.
 
-Depending on the library used by the Dapp, there are two options:
+In the examples below, you can see `provider` and `signer` properties, which represent:
 
-- [Create an `EthersAdapter` instance](https://github.com/safe-global/safe-core-sdk/tree/main/packages/protocol-kit/src/adapters/ethers)
-- [Create a `Web3Adapter` instance](https://github.com/safe-global/safe-core-sdk/tree/main/packages/protocol-kit/src/adapters/web3)
-
-Once the instance of `EthersAdapter` or `Web3Adapter` is created, it can be used in the SDK initialization.
+- `provider`: You can provide an EIP-1193 compatible provider or an HTTP/WebSocket RPC URL.
+- `signer`: This is an optional parameter. It should be the provider's address you want to use or a private key. If not set, it will try to fetch a connected account from the provider.
 
 ### Initialize the Safe API Kit
 
@@ -59,27 +57,28 @@ const safeService = new SafeApiKit({
 ```js
 import Safe, { SafeFactory } from '@safe-global/protocol-kit'
 
-const safeFactory = await SafeFactory.create({ ethAdapter })
+const safeFactory = await SafeFactory.create({ provider, signer })
 
-const safeSdk = await Safe.create({ ethAdapter, safeAddress })
+const safeSdk = await Safe.create({ provider, signer, safeAddress })
 ```
 
 There are two versions of the Safe contracts: [Safe.sol](https://github.com/safe-global/safe-contracts/blob/v1.4.1/contracts/Safe.sol) that does not trigger events in order to save gas and [SafeL2.sol](https://github.com/safe-global/safe-contracts/blob/v1.4.1/contracts/SafeL2.sol) that does, which is more appropriate for L2 networks.
 
 By default `Safe.sol` will be only used on Ethereum Mainnet. For the rest of the networks where the Safe contracts are already deployed, the `SafeL2.sol` contract will be used unless you add the property `isL1SafeSingleton` to force the use of the `Safe.sol` contract.
 
 ```js
-const safeFactory = await SafeFactory.create({ ethAdapter, isL1SafeSingleton: true })
+const safeFactory = await SafeFactory.create({ provider, signer, isL1SafeSingleton: true })
 
-const safeSdk = await Safe.create({ ethAdapter, safeAddress, isL1SafeSingleton: true })
+const safeSdk = await Safe.create({ provider, signer, safeAddress, isL1SafeSingleton: true })
 ```
 
 If the Safe contracts are not deployed to your current network, the property `contractNetworks` will be required to point to the addresses of the Safe contracts previously deployed by you.
 
 ```js
-import { ContractNetworksConfig } from '@safe-global/protocol-kit'
+import { ContractNetworksConfig, SafeProvider } from '@safe-global/protocol-kit'
 
-const chainId = await ethAdapter.getChainId()
+const safeProvider = new SafeProvider({ provider, signer })
+const chainId = await safeProvider.getChainId()
 const contractNetworks: ContractNetworksConfig = {
   [chainId]: {
     safeSingletonAddress: '<SINGLETON_ADDRESS>',
@@ -101,16 +100,16 @@ const contractNetworks: ContractNetworksConfig = {
   }
 }
 
-const safeFactory = await SafeFactory.create({ ethAdapter, contractNetworks })
+const safeFactory = await SafeFactory.create({ provider, signer, contractNetworks })
 
-const safeSdk = await Safe.create({ ethAdapter, safeAddress, contractNetworks })
+const safeSdk = await Safe.create({ provider, signer, safeAddress, contractNetworks })
 ```
 
 The `SafeFactory` constructor also accepts the property `safeVersion` to specify the Safe contract version that will be deployed. This string can take the values `1.0.0`, `1.1.1`, `1.2.0`, `1.3.0` or `1.4.1`. If not specified, the `DEFAULT_SAFE_VERSION` value will be used.
 
 ```js
 const safeVersion = 'X.Y.Z'
-const safeFactory = await SafeFactory.create({ ethAdapter, safeVersion })
+const safeFactory = await SafeFactory.create({ provider, signer, safeVersion })
 ```
 
 ## <a name="deploy-safe">3. Deploy a new Safe</a>
@@ -140,37 +139,37 @@ This method takes an array of `MetaTransactionData` objects that represent the i
 
 When the array contains only one transaction, it is not wrapped in the MultiSend.
 
-  ```js
-  import { SafeTransactionOptionalProps } from '@safe-global/protocol-kit'
-  import { MetaTransactionData } from '@safe-global/safe-core-sdk-types'
-
-  const transactions: MetaTransactionData[] = [
-    {
-      to,
-      data,
-      value,
-      operation
-    },
-    {
-      to,
-      data,
-      value,
-      operation
-    }
-    // ...
-  ]
-
-  const options: SafeTransactionOptionalProps = {
-    safeTxGas, // Optional
-    baseGas, // Optional
-    gasPrice, // Optional
-    gasToken, // Optional
-    refundReceiver, // Optional
-    nonce // Optional
+```js
+import { SafeTransactionOptionalProps } from '@safe-global/protocol-kit'
+import { MetaTransactionData } from '@safe-global/safe-core-sdk-types'
+
+const transactions: MetaTransactionData[] = [
+  {
+    to,
+    data,
+    value,
+    operation
+  },
+  {
+    to,
+    data,
+    value,
+    operation
   }
+  // ...
+]
+
+const options: SafeTransactionOptionalProps = {
+  safeTxGas, // Optional
+  baseGas, // Optional
+  gasPrice, // Optional
+  gasToken, // Optional
+  refundReceiver, // Optional
+  nonce // Optional
+}
 
-  const safeTransaction = await safeSdk.createTransaction({ transactions, options })
-  ```
+const safeTransaction = await safeSdk.createTransaction({ transactions, options })
+```
 
 We can specify the `nonce` of our Safe transaction as long as it is not lower than the current Safe nonce. If multiple transactions are created but not executed they will share the same `nonce` if no `nonce` is specified, validating the first executed transaction and invalidating all the rest. We can prevent this by calling the method `getNextNonce` from the Safe API Kit instance. This method takes all queued/pending transactions into account when calculating the next nonce, creating a unique one for all different transactions.
 

package.json

@@ -7,7 +7,6 @@
     "build": "lerna run build --stream",
     "lint:check": "eslint './packages/**/*.{js,jsx,ts,tsx}'",
     "test": "FORCE_COLOR=1 lerna run test --stream",
-    "test:ci": "FORCE_COLOR=1 lerna run test:ci --stream",
     "play": "ts-node ./playground/config/run.ts",
     "format": "lerna run format && prettier --write \"playground/**/*.ts\"",
     "prepare": "husky install"
@@ -20,20 +19,20 @@
   "author": "Safe (https://safe.global)",
   "license": "MIT",
   "devDependencies": {
-    "@types/jest": "^29.5.11",
+    "@types/jest": "^29.5.12",
     "@types/node": "^18.18.8",
     "@typescript-eslint/eslint-plugin": "^6.15.0",
     "@typescript-eslint/parser": "^6.15.0",
     "eslint": "^8.56.0",
     "eslint-config-prettier": "^9.1.0",
-    "eslint-plugin-prettier": "^5.0.1",
+    "eslint-plugin-prettier": "^5.1.3",
     "husky": "^8.0.3",
     "jest": "^29.7.0",
     "lerna": "^7.4.2",
     "lint-staged": "^14.0.1",
-    "prettier": "^3.1.1",
+    "prettier": "^3.2.5",
     "rimraf": "^3.0.2",
-    "ts-jest": "^29.1.1",
+    "ts-jest": "^29.1.2",
     "ts-node": "^10.9.2",
     "tsc-alias": "^1.8.8",
     "typescript": "^5.3.3"

packages/account-abstraction-kit/jest.config.js

@@ -5,7 +5,6 @@ const config = {
     '^.+\\.ts?$': 'ts-jest'
   },
   moduleNameMapper: {
-    '^@safe-global/protocol-kit/typechain/(.*)$': '<rootDir>/../protocol-kit/typechain/$1',
     '^@safe-global/protocol-kit/(.*)$': '<rootDir>/../protocol-kit/src/$1',
     '^@safe-global/relay-kit/(.*)$': '<rootDir>/../relay-kit/src/$1',
     '^@safe-global/account-abstraction-kit-poc/(.*)$': '<rootDir>/src/$1'

packages/account-abstraction-kit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@safe-global/account-abstraction-kit-poc",
-  "version": "2.1.0",
+  "version": "3.0.0-alpha.0",
   "description": "Safe Account Abstraction Kit PoC",
   "main": "dist/src/index.js",
   "typings": "dist/src/index.d.ts",
@@ -34,8 +34,8 @@
     "access": "public"
   },
   "dependencies": {
-    "@safe-global/protocol-kit": "^3.1.0",
-    "@safe-global/relay-kit": "^2.1.0",
-    "@safe-global/safe-core-sdk-types": "^4.1.0"
+    "@safe-global/protocol-kit": "^4.0.0-alpha.0",
+    "@safe-global/relay-kit": "^3.0.0-alpha.0",
+    "@safe-global/safe-core-sdk-types": "^5.0.0-alpha.0"
   }
 }