readme

Author: douglasgalico

README.md

@@ -8,35 +8,74 @@ spoken - this is a very complex piece of software which targets a bleeding-edge,
 Mistakes happen, and no matter how hard you try and whether you pay someone to audit it, it may eat your tokens, set
 your printer on fire or startle your cat. Cryptocurrencies are a high-risk investment, no matter how fancy.
 
-## Testing Flow
+## Testing with Tilt
 
-> 🚧 This is a work in progress!
-
-First tilt up.
+To run tests using Tilt, execute the following command:
 
 ```bash
 tilt up
 ```
 
-Next, deploy integration contracts to each chain.
+This will spin up a local development environment with all necessary components including Anvil chains and the executor service.
+
+After Tilt is running, the test suite will run automatically in the `e2e` step.
+
+````
+
+## Capabilities and Supported Platforms
+
+| Capability | Status | Description |
+|------------|--------|-------------|
+| NTT V1 | ✅ Supported | Native Token Transfer protocol integration |
+| VAA V1 | ✅ Supported | Verified Action Approvals V1 protocol |
+
+| Platform | Status | Networks |
+|----------|--------|----------|
+| EVM | ✅ Supported | Ethereum, BSC, Polygon, Avalanche, etc. |
+
+## Running the Docker Image
+
+You can run the executor using the published Docker image. To override the default configuration:
 
 ```bash
-forge create ExecutorVAAv1Integration -r http://localhost:8545 --broadcast --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 --constructor-args 0x4a8bc80Ed5a4067f1CCf107057b8270E0cC11A78 0xD0fb39f5a3361F21457653cB70F9D0C9bD86B66B 200
-forge create ExecutorVAAv1Integration -r http://localhost:8546 --broadcast --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 --constructor-args 0x79A1027a6A159502049F10906D333EC57E95F083 0x51B47D493CBA7aB97e3F8F163D6Ce07592CE4482 200
-```
+docker run -v /path/to/your/config.json:/app/config.json \
+  -e CONFIG_PATH=/app/config.json \
+  example-executor:latest
+````
+
+The configuration file should contain your chain settings, RPC endpoints, and other necessary parameters.
 
-Finally, bun test
+## Customizing Your Anvil Environment
+
+The local Anvil chains can be customized to deploy additional integration contracts or modify the blockchain state for testing purposes. You can:
+
+- Deploy custom contracts using Forge or other deployment tools
+- Modify chain state using Anvil's RPC methods
+- Configure custom accounts and balances
+- Set up specific testing scenarios
+
+Example of deploying additional contracts:
 
 ```bash
-bun test
+forge create YourContract -r http://localhost:8545 --private-key <your-private-key>
 ```
 
-Click the link! It should be `pending` at first and then after a couple seconds, refresh and it should be `submitted`!
+## Deployed Contracts
+
+The following contracts are used as part of this repository infrastructure:
+
+| Contract | Network | Address | Description |
+|----------|---------|---------|-------------|
+| NTT Shim Contract | Sepolia | [0x54DD7080aE169DD923fE56d0C4f814a0a17B8f41](https://sepolia.etherscan.io/address/0x54DD7080aE169DD923fE56d0C4f814a0a17B8f41) | Handles NTT protocol integration |
+| Executor | Sepolia | [0xD0fb39f5a3361F21457653cB70F9D0C9bD86B66B](https://sepolia.etherscan.io/address/0xD0fb39f5a3361F21457653cB70F9D0C9bD86B66B) | Main executor contract |
+| MultiReceiveWithGasDropOff | Base Sepolia | [0xe3cc16Cffa085C78e5D8144C74Fa97e4Fe53d68d](https://sepolia.basescan.org/address/0xe3cc16Cffa085C78e5D8144C74Fa97e4Fe53d68d) | Manages multi-receiver operations |
 
-Next steps
+## Using the Executor Explorer
+
+You can monitor and explore executor transactions using the Executor Explorer. For local development:
+
+```
+https://wormholelabs-xyz.github.io/executor-explorer/#/chain/10002/tx/${hash}?endpoint=http%3A%2F%2Flocalhost%3A3000&env=Testnet
+```
 
-- Support NTT v1
-- Publish the executor docker image
-- Support passing the executor chain config from env or command line so that someone using the docker image can configure the chain info
-- Deploy the contracts within the e2e test and actually confirm the messages send both ways and update the contract number.
-- Trigger the e2e test in CI
+Replace `${hash}` with your transaction hash. The explorer will connect to your local executor instance running on port 3000.