infernet-1.0.0 update

projects/prompt-to-nft/prompt-to-nft.md

@@ -262,7 +262,7 @@ Notice that in [one of the steps above](#check-the-running-containers) we have a
 
 By default, the [`anvil-node`](https://hub.docker.com/r/ritualnetwork/infernet-anvil) image used deploys the
 [Infernet SDK](https://docs.ritual.net/infernet/sdk/introduction) and other relevant contracts for you:
-- Coordinator: `0x5FbDB2315678afecb367f032d93F642f64180aa3`
+- Registry: `0x663F3ad617193148711d28f5334eE4Ed07016602`
 - Primary node: `0x70997970C51812dc3A010C7d01b50e0d17dc79C8`
 
 ### Deploy our NFT Consumer contract
@@ -296,7 +296,7 @@ You should expect to see similar Anvil logs:
 eth_getTransactionReceipt
 
 Transaction: 0x0577dc98192d971bafb30d53cb217c9a9c16f92ab435d20a697024a4f122c048
-Contract created: 0x663f3ad617193148711d28f5334ee4ed07016602
+Contract created: 0x13D69Cf7d6CE4218F646B759Dcf334D82c023d8e
 Gas used: 1582129
 
 Block Number: 1
@@ -307,7 +307,7 @@ eth_getTransactionByHash
 ```
 
 From our logs, we can see that the `DiffusionNFT` contract has been deployed to address
-`0x663f3ad617193148711d28f5334ee4ed07016602`.
+`0x13D69Cf7d6CE4218F646B759Dcf334D82c023d8e`.
 
 ### Call the contract