diff --git a/src/cairo/world.md b/src/cairo/world.md index 9170d953..0d1fdab2 100644 --- a/src/cairo/world.md +++ b/src/cairo/world.md @@ -1,5 +1,7 @@ > **To think about:** Consider Autonomous Worlds as sovereign blockchains residing within another blockchain - a nested blockchain, so to speak. Just as you can deploy contracts onto Ethereum to enhance its functionality, you can similarly introduce systems into the World contract to enrich its features. While anyone can contribute to the World, akin to Ethereum, authorization is required to interact with model state. There is a dedicated topic to [Authorisation](./authorization.md). +![overview](../images/world-map.png) + ## The World Contract The world contract functions as a central store for the world models and systems. Every contract that interacts with the world, must use the world contract address as the first parameter. This is how the world contract is able to manage the state of the world. diff --git a/src/images/world-map.png b/src/images/world-map.png new file mode 100644 index 00000000..4fc2664f Binary files /dev/null and b/src/images/world-map.png differ