Update timeline

applications/dot-login.md

@@ -162,12 +162,12 @@ Please note that above comparisons are based on our current understanding and re
 
 ### Overview
 
-- **Total Estimated Duration:** 1 months
+- **Total Estimated Duration:** 6 months
 - **Full-Time Equivalent (FTE):** 3 FTE
 - **Total Costs:** 17000 USD (2.5 FTE covered)
 
 ### Milestone 1 — Wallet Creation Flow
-- **Estimated Duration:** 1 month
+- **Estimated Duration:** 6 months
 - **FTE:** 3
 - **Costs:** 17000 USD (2.5 FTE covered)
 
@@ -181,7 +181,7 @@ Please note that above comparisons are based on our current understanding and re
 | 2. | `address` Pallet | Substrate pallet for deriving wallet addresses from OAuth2 JWT. |
 | 3. | `jwtValidation` Pallet | Substrate pallet for JWT validation. |
 | 4. | `JWK Registry` Pallet | Pallet that stores a hard-coded list of public keys from supported OAuth2 providers. |
-| 5. | Client and OAuth Integrations | A rust-based client that allows the user to log into their gmail account, receive a JWT, paste the JWT to the client CLI, generate the ephemeral public/private keypair, generate the salt, generate the ZK proof using (jwt, public key, salt) as an input, and send it to the collator by calling the appropriate extrinsic. Integrate the Google OAuth provider with the `JWK Registry` pallet. |
+| 5. | Client and OAuth Integrations | A rust-based client that allows the user to log into their gmail account, receive a JWT, paste the JWT to the client CLI, generate the ephemeral public/private keypair, generate the salt, generate the ZK proof using jwt, public key, and salt as an input, and send it to the collator by calling the appropriate extrinsic. Client-side jwt signature validation using the jwk present in the jwt header. The client will directly communicate with the node, assumingly it runs on wss://127.0.0.1:9944.  |
 
 ## Future Plans