chore(docs): fix dead ERC-4337 links

docs/architecture/builder.md

@@ -42,7 +42,7 @@ Once a candidate bundle is constructed, each UO is re-simulated and validation r
 
 After 2nd simulation the entire bundle is validated via an `eth_call`, and ops that fail validation are again removed from the bundle. This process is repeated until the entire bundle passes validation.
 
-NOTE: This procedure implements an old version of the spec and will be updated to conform soon. See [here](https://github.com/eth-infinitism/account-abstraction/blob/develop/erc/ERCS/erc-4337.md#bundling) for more details on the new implementation.
+NOTE: This procedure implements an old version of the spec and will be updated to conform soon. See [here](https://eips.ethereum.org/EIPS/eip-4337#bundling) for more details on the new implementation.
 
 ## Transaction Signers
 

docs/architecture/pool.md

@@ -6,9 +6,9 @@ The `Pool` task is responsible for receiving, validating, sorting, and storing u
 
 Upon each `add_operation` call the `Pool` will preforms a series of checks.
 
-1. Run a series of [prechecks](https://github.com/eth-infinitism/account-abstraction/blob/develop/erc/ERCS/erc-4337.md#client-behavior-upon-receiving-a-useroperation) to catch any reasons why the UO may not be mined.
+1. Run a series of [prechecks](https://eips.ethereum.org/EIPS/eip-4337#client-behavior-upon-receiving-a-useroperation) to catch any reasons why the UO may not be mined.
 
-2. Simulate the UO via a `debug_traceCall` as per the [ERC-4337 spec](https://github.com/eth-infinitism/account-abstraction/blob/develop/erc/ERCS/erc-4337.md#simulation).
+2. Simulate the UO via a `debug_traceCall` as per the [ERC-4337 spec](https://eips.ethereum.org/EIPS/eip-4337#simulation).
 
 If violations are found, the UO is rejected. Else, the UO is added to the pool. 
 
@@ -18,7 +18,7 @@ A typescript based tracer is used to collect relevant information from the `debu
 
 ## Reputation
 
-The `Pool` tracks the reputation of entities as per the [ERC-4337 spec](https://github.com/eth-infinitism/account-abstraction/blob/develop/erc/ERCS/erc-4337.md#reputation-scoring-and-throttlingbanning-for-global-entities).
+The `Pool` tracks the reputation of entities as per the [ERC-4337 spec](https://eips.ethereum.org/EIPS/eip-4337#reputation-scoring-and-throttlingbanning-for-global-entities).
 
 
 ### Allowlist/Blocklist

docs/architecture/rpc.md

@@ -15,7 +15,7 @@ It also supports a health check endpoint.
 
 ### `eth_` Namespace
 
-Methods defined by the [ERC-4337 spec](https://github.com/eth-infinitism/account-abstraction/blob/develop/erc/ERCS/erc-4337.md#rpc-methods-eth-namespace).
+Methods defined by the [ERC-4337 spec](https://eips.ethereum.org/EIPS/eip-4337#rpc-methods-eth-namespace).
 
 | Method | Supported |
 | ------ | :-----------: |
@@ -28,7 +28,7 @@ Methods defined by the [ERC-4337 spec](https://github.com/eth-infinitism/account
 
 ### `debug_` Namespace
 
-Method defined by the [ERC-4337 spec](https://github.com/eth-infinitism/account-abstraction/blob/develop/erc/ERCS/erc-4337.md#rpc-methods-debug-namespace). Used only for debugging/testing and should be disabled on production APIs.
+Method defined by the [ERC-4337 spec](https://eips.ethereum.org/EIPS/eip-4337#rpc-methods-debug-namespace). Used only for debugging/testing and should be disabled on production APIs.
 
 | Method | Supported | Non-Standard |
 | ------ | :-----------: | :--: |