chore: update readme

README.md

@@ -54,8 +54,8 @@
 # Deployments
 
 
-**L1 Deployer**: `0x`
-**STB Role Manager**: `0x`
+**L1 Deployer**: `0x1316a3312CfF738aDCBF011bCE9D1e7B9C88C817`
+**STB Role Manager**: `0x51b76329d2C6b8974053C9655484e231f7dcd418`
 
 
 In order to integrate your Polygon CDK chain with STB you will need to 
@@ -77,10 +77,12 @@ $ cd yearn-stb
 $ cp .env.example .env
 ```
 
-Fill in the ful .env with your specific rollup RPC, Polygon CDK based rollup ID, and the desired addresses. 
+Fill in the full .env with your specific rollup RPC, Polygon CDK based rollup ID, and the desired addresses. 
 
 **NOTE**: To deploy a L2 Deployer during the script leave the `L2_DEPLOYER` variable as address(0). If one is already deployed, insert the address in that variable to not re-deploy.
 
+To just deploy the L2 Deployer and not send the registerRollup Safe txn put 0 as the `ROLLUP_ID`.
+
 If you have not added a keystore private key to foundry before add your address to use
 
 ```shell

scripts/RegisterRollup.s.sol

@@ -10,7 +10,7 @@ contract RegisterRollup is BatchScript {
 
     address public ZK_EVM_BRIDGE = 0x2a3DD3EB832aF982ec71669E178424b10Dca2EDe;
 
-    L1Deployer public L1_DEPLOYER = L1Deployer(0x49dC846d5EDA92dDC4985b7B7BBaD4F9b05B7597);
+    L1Deployer public L1_DEPLOYER = L1Deployer(0x1316a3312CfF738aDCBF011bCE9D1e7B9C88C817);
 
     function run() external {