docs: update README

Author: Doge-is-Dope

README.md

@@ -11,60 +11,41 @@ Drip Protocol is a smart contract system that enables users to create and manage
 - DripProfile: Handles user profiles and their associated data
 - DripVault: Manages token deposits and withdrawals
 
-## Contract Addresses
-
-Challenge: 0xaDcaAe61b8983940FB2c8098BDe112e507A0e1f0
-ChallengeManager: 0xB3084eF0Dc7440e32A6cD64e2E5072FBCd9AEEeE
-DripProfile: 0x0E69Ba1FF53c36D0fbb4fccC0e9B732D58593B2f
-
-### Testnet (Goerli)
-
-- Challenge: [Contract Address]
-- ChallengeManager: [Contract Address]
-- DripProfile: [Contract Address]
-- DripVault: [Contract Address]
-
 ## Architecture
 
 The protocol consists of four main contracts:
 
 1. **Challenge.sol**: Core contract for challenge creation and management
 
-   - Handles challenge parameters
+   - Creates new challenges
    - Manages challenge states
-   - Processes challenge completion
+   - Retrieves challenges for a given epoch
 
-2. **ChallengeManager.sol**: Orchestration layer for challenges
+2. **ChallengeManager.sol**: Orchestration layer for challenges management
 
-   - Creates new challenges
-   - Manages challenge lifecycle
-   - Handles challenge verification
+   - Creates new epochs
+   - Manages epoch lifecycle
+   - Manages epoch rewards
 
 3. **DripProfile.sol**: User profile management
 
-   - Stores user information
-   - Tracks challenge participation
-   - Manages user achievements
+   - Creates new profiles
+   - Manages profile data
+   - Submits daily completions
 
 4. **DripVault.sol**: Token management
-   - Handles token deposits
-   - Processes withdrawals
-   - Manages challenge stakes
-
-## Libraries
-
-### TimeLib
+   - Manages token deposits & withdrawals
 
-Utility library for time-based calculations and validations used throughout the protocol.
-
-### Types
-
-Contains core data structures and custom types used across the protocol.
+## Contract Addresses
 
-## Security
+Unified CREATE2 addresses:
 
-This protocol has been designed with security in mind. However, it has not been audited yet. Use at your own risk.
+- Challenge: 0xaDcaAe61b8983940FB2c8098BDe112e507A0e1f0
+- ChallengeManager: 0xB3084eF0Dc7440e32A6cD64e2E5072FBCd9AEEeE
+- DripProfile: 0x0E69Ba1FF53c36D0fbb4fccC0e9B732D58593B2f
 
-## License
+The contracts are deployed on the following networks:
 
-This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+- Base Sepolia
+- Mantle Sepolia
+- Polygon zkEVM Cardona

deploy.sh

@@ -4,6 +4,7 @@
 CONFIGS=(
     "base-sepolia|https://base-sepolia.blockscout.com"
     "mantle-sepolia|https://explorer.sepolia.mantle.xyz"
+    "polygonzkevm-cardona|https://explorer-ui.cardona.zkevm-rpc.com"
 )
 
 # Function to display usage
@@ -41,7 +42,9 @@ deploy_to_chain() {
         --rpc-url "$rpc_url" \
         --verify \
         --verifier blockscout \
-        --verifier-url "$verifier_url/api/"
+        --verifier-url "$verifier_url/api/" \
+        --sender 0x8D0B05b837FB0e28e78b8939dDaD8CE7B91b678D \
+        --legacy
 }
 
 # Validate the option number

foundry.toml

@@ -7,4 +7,5 @@ libs = ["lib"]
 [rpc_endpoints]
 sepolia = "${RPC_SEPOLIA}"
 base-sepolia = "${RPC_BASE_SEPOLIA}"
-mantle-sepolia = "${RPC_MANTLE_SEPOLIA}"
+mantle-sepolia = "${RPC_MANTLE_SEPOLIA}"
+polygonzkevm-cardona = "${RPC_POLYGONZKEVM_CARDONA}"