📝 Creating a draft for upcoming cross-contract tutorial

docs/zkapps/tutorials/12-cross-contract-calls.mdx

@@ -0,0 +1,209 @@
+---
+title: 'Tutorial 12: Cross Contract Calls'
+hide_title: true
+sidebar_label: 'Tutorial 12: Cross Contract Calls'
+description: Guided steps to learn about the ways to interact with a smart contract from another smart contract.
+keywords:
+  - smart contracts
+  - zkapps
+  - zero knowledge proof programming
+  - zk proof
+  - zk
+  - cross contract call
+  - mina
+---
+
+:::info
+
+Please note that zkApp programmability is not yet available on Mina Mainnet, but zkApps can now be deployed to Berkeley Testnet.
+
+:::
+
+
+# Tutorial 12: Cross Contract Calls
+
+In this tutorial, you learn how smart contracts on a blockchain can interact by calling functions in each other's code, enabling building modular and complex decentralized applications.
+
+Cross contract calls allow smart contracts on a blockchain to interact with each other. This enables building complex decentralized applications (dApps) from multiple modular components. In a cross contract call, a function in one smart contract can call a function in another smart contract to leverage existing code and functionality.
+
+In this tutorial you will learn about passing data between contracts, handling events and return values when contracts call each other. 
+
+The full example code is provided in the [12-cross-contract-calls/src/](https://github.com/o1-labs/docs2/tree/main/examples/zkapps/12-cross-contract-calls/src) example files.
+
+## Prerequisites
+
+- Make sure you have the latest version of the zkApp CLI installed:
+
+    ```sh
+    $ npm install -g zkapp-cli
+    ```
+
+- Ensure your environment meets the [Prerequisites](/zkapps/tutorials#prerequisites) for zkApp Developer Tutorials.
+
+This tutorial has been tested with:
+
+- [Mina zkApp CLI](https://github.com/o1-labs/zkapp-cli) version `0.16.0`
+- [o1js](https://www.npmjs.com/package/o1js) version `0.16.2`
+
+## Create a new project
+
+Now that you have the tooling installed, you can start building your application.
+
+1. Create or change to a directory where you have write privileges.
+1. Now, create a project using the `zk project` command:
+
+    ```sh
+    $ zk project 12-cross-contract-calls
+    ```
+
+    As you learned in earlier tutorials, the `zk project` command creates the `12-cross-contract-calls` directory that contains the scaffolding for your project.
+
+1. Change into the `12-cross-contract-calls` directory. 
+
+Like all projects, you run `zk` commands from the root of the `12-cross-contract-calls` directory as you work in the `src` directory on files that contain the TypeScript code for the smart contract. 
+
+Each time you make updates, then build or deploy, the TypeScript code is compiled into JavaScript in the `build` directory.
+
+### Prepare the project
+
+Like earlier tutorials, you can prepare your project by deleting the default files that come with the new project and creating a smart contract called `Composability`.
+
+## Write the ZkProgram
+
+Now, the fun part! Write your smart contract in the `src/Composability.ts` file.
+
+A final version of the smart contract is provided in the [Composability.ts](https://github.com/o1-labs/docs2/blob/main/examples/zkapps/12-cross-contract-calls/src/Composability.ts) example file.
+
+
+### Copy the example
+
+Use the existing code in the [Composability.ts](https://github.com/o1-labs/docs2/blob/main/examples/zkapps/12-cross-contract-calls/src/Composability.ts) example file.
+
+1. First, open the [Composability.ts](https://github.com/o1-labs/docs2/blob/main/examples/zkapps/12-cross-contract-calls/src/Composability.ts) example file.
+
+1. Copy the file's entire contents into your project `src/Composability.ts` file.
+
+### Imports and Incrementer smart contract 
+
+First, bring in imports and set up the first smart contract `Incrementer`.
+
+```typescript
+import {
+  Field,
+  method,
+  Mina,
+  AccountUpdate,
+  PrivateKey,
+  SmartContract,
+  state,
+  State,
+} from 'o1js';
+
+class Incrementer extends SmartContract {
+  @method increment(x: Field): Field {
+    return x.add(1);
+  }
+}
+
+```
+This Incrementer contract will add 1 to the Field argument which is passed.
+
+### Adder smart contract 
+
+Let's bring in the second contract `Adder` which will return the addtion of two numbers and add 1 to the result.
+The addition of 1 to the result is outsourced to the Incrementer smart contract by creating a new object by passing it's address.
+
+```typescript
+class Adder extends SmartContract {
+  @method addPlus1(x: Field, y: Field): Field {
+    let sum = x.add(y);
+    let incrementer = new Incrementer(incrementerAddress);
+    return incrementer.increment(sum);
+  }
+}
+
+```
+
+### Caller smart contract 
+
+The final smart contract `Caller` will call the `addPlus1` method of `Adder` smart contract and emit the stored result return by it.
+
+```typescript
+class Caller extends SmartContract {
+  @state(Field) sum = State<Field>();
+  events = { sum: Field };
+
+  @method callAddAndEmit(x: Field, y: Field) {
+    let adder = new Adder(adderAddress);
+    let sum = adder.addPlus1(x, y);
+    this.emitEvent('sum', sum);
+    this.sum.set(sum);
+  }
+}
+
+```
+
+The code to interact with the smart contract:
+
+```typescript
+const doProofs = true;
+
+let Local = Mina.LocalBlockchain({ proofsEnabled: doProofs });
+Mina.setActiveInstance(Local);
+
+let feePayerKey = Local.testAccounts[0].privateKey;
+let feePayer = Local.testAccounts[0].publicKey;
+
+let incrementerKey = PrivateKey.random();
+let incrementerAddress = incrementerKey.toPublicKey();
+
+let adderKey = PrivateKey.random();
+let adderAddress = adderKey.toPublicKey();
+
+let zkappKey = PrivateKey.random();
+let zkappAddress = zkappKey.toPublicKey();
+
+let zkapp = new Caller(zkappAddress);
+let adderZkapp = new Adder(adderAddress);
+let incrementerZkapp = new Incrementer(incrementerAddress);
+
+if (doProofs) {
+  console.log('compile (incrementer)');
+  await Incrementer.compile();
+  console.log('compile (adder)');
+  await Adder.compile();
+  console.log('compile (caller)');
+  await Caller.compile();
+}
+
+console.log('deploy');
+let tx = await Mina.transaction(feePayer, () => {
+  AccountUpdate.fundNewAccount(feePayer, 3);
+  zkapp.deploy();
+  adderZkapp.deploy();
+  incrementerZkapp.deploy();
+});
+await tx.sign([feePayerKey, zkappKey, adderKey, incrementerKey]).send();
+
+console.log('call interaction');
+tx = await Mina.transaction(feePayer, () => {
+  zkapp.callAddAndEmit(Field(5), Field(6));
+});
+console.log('proving (3 proofs.. can take a bit!)');
+await tx.prove();
+console.log(tx.toPretty());
+await tx.sign([feePayerKey]).send();
+
+console.log('state: ' + zkapp.sum.get());
+
+``` 
+
+In this example, we are spinning up the Mina chain locally and deploying all three smart contracts locally.
+
+Then we are calling `callAddAndEmit` method from `Caller` smart contract which will take two numbers as arguments, then call the `Adder` smart contract which will add these two numbers and pass the result in `Incrementer` smart contract which will increment the result by 1.
+
+In our case we should see state equal to 12.
+
+## Conclusion
+
+Congratulations! You have learned how to implement cross contract calls, allowing smart contracts to interact and unlocking new possibilities for modular blockchain applications.

examples/zkapps/12-cross-contract-calls/.eslintrc.cjs

@@ -0,0 +1,23 @@
+module.exports = {
+  root: true,
+  env: {
+    browser: true,
+    node: true,
+    jest: true,
+  },
+  extends: [
+    'eslint:recommended',
+    'plugin:@typescript-eslint/eslint-recommended',
+    'plugin:@typescript-eslint/recommended',
+    'plugin:o1js/recommended',
+  ],
+  parser: '@typescript-eslint/parser',
+  parserOptions: {
+    ecmaVersion: 'latest',
+  },
+  plugins: ['@typescript-eslint', 'o1js'],
+  rules: {
+    'no-constant-condition': 'off',
+    'prefer-const': 'off',
+  },
+};

examples/zkapps/12-cross-contract-calls/.gitattributes

@@ -0,0 +1,3 @@
+# Use line endings appropriate for the system. This prevents Git from
+# complaining about project template line endings when committing on Windows.
+* text=auto eol=lf

examples/zkapps/12-cross-contract-calls/.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+#
+# ci.yml
+#
+# Run tests for all pushed commits and opened pull requests on Github.
+#
+
+name: CI
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - name: Set up NodeJS
+        uses: actions/setup-node@v4
+        with:
+          node-version: '16'
+      - name: Git checkout
+        uses: actions/checkout@v4
+      - name: NPM ci, build, & test
+        run: |
+          npm install
+          npm run build --if-present
+          npm test
+        env:
+          CI: true

examples/zkapps/12-cross-contract-calls/.gitignore

@@ -0,0 +1,13 @@
+# NodeJS
+node_modules
+build
+coverage
+
+# Editor
+.vscode
+
+# System
+.DS_Store
+
+# Never commit keys to Git!
+keys

examples/zkapps/12-cross-contract-calls/.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx lint-staged

examples/zkapps/12-cross-contract-calls/.npmignore

@@ -0,0 +1,11 @@
+# TypeScript files
+src
+
+# Editor
+.vscode
+
+# System
+.DS_Store
+
+# Never reveal your keys!
+keys

examples/zkapps/12-cross-contract-calls/.prettierignore

@@ -0,0 +1,14 @@
+# NodeJS
+node_modules
+build
+coverage
+.husky
+
+# Editor
+.vscode
+
+# System
+.DS_Store
+
+# Misc
+LICENSE

examples/zkapps/12-cross-contract-calls/.prettierrc

@@ -0,0 +1,6 @@
+{
+  "semi": true,
+  "singleQuote": true,
+  "tabWidth": 2,
+  "trailingComma": "es5"
+}