initial commit

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+*       @robik75 @mcarilli
+/.github/workflows/ @matter-labs/devops

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug report
+about: Use this template for reporting issues
+title: ''
+labels: bug
+assignees: ''
+---
+
+### 🐛 Bug Report
+
+#### 📝 Description
+
+Provide a clear and concise description of the bug.
+
+#### 🔄 Reproduction Steps
+
+Steps to reproduce the behaviour
+
+#### 🤔 Expected Behavior
+
+Describe what you expected to happen.
+
+#### 😯 Current Behavior
+
+Describe what actually happened.
+
+#### 🖥️ Environment
+
+Any relevant environment details.
+
+#### 📋 Additional Context
+
+Add any other context about the problem here. If applicable, add screenshots to help explain.
+
+#### 📎 Log Output
+
+```
+Paste any relevant log output here.
+```

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Use this template for requesting features
+title: ''
+labels: feat
+assignees: ''
+---
+
+### 🌟 Feature Request
+
+#### 📝 Description
+
+Provide a clear and concise description of the feature you'd like to see.
+
+#### 🤔 Rationale
+
+Explain why this feature is important and how it benefits the project.
+
+#### 📋 Additional Context
+
+Add any other context or information about the feature request here.

.github/pull_request_template.md

@@ -0,0 +1,20 @@
+# What ❔
+
+<!-- What are the changes this PR brings about? -->
+<!-- Example: This PR adds a PR template to the repo. -->
+<!-- (For bigger PRs adding more context is appreciated) -->
+
+## Why ❔
+
+<!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? -->
+<!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. -->
+
+## Checklist
+
+<!-- Check your PR fulfills the following items. -->
+<!-- For draft PRs check the boxes as you complete them. -->
+
+- [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
+- [ ] Tests for the changes have been added / updated.
+- [ ] Documentation comments have been added / updated.
+- [ ] Code has been formatted via `cargo fmt` and checked with `cargo check` for any errors or warnings.

.github/workflows/build.yaml

@@ -0,0 +1,100 @@
+name: era-cuda build and test
+
+on:
+  pull_request:
+    branches: [main]
+  push:
+    branches: [main]
+
+jobs:
+  era-cuda-build:
+    runs-on: [ubuntu-latest]
+    strategy:
+      matrix:
+        cuda: ["12.2.0-devel-ubuntu20.04", "12.0.0-devel-ubuntu20.04"]
+    container:
+      image: nvidia/cuda:${{ matrix.cuda }}
+    steps:
+      - name: Prepare environment
+        env:
+          DEBIAN_FRONTEND: noninteractive
+        run: |
+          apt update && apt install -y libclang-dev wget jq
+          echo "/usr/local/nvidia/bin:/usr/local/cuda/bin" >> $GITHUB_PATH
+
+      - uses: actions/checkout@93ea575cb5d8a053eaa0ac8fa3b40d7e05a33cc8 # v3
+
+      - name: Setup rustup
+        run: |
+          wget -q -O - https://sh.rustup.rs | bash -s -- -y
+          echo "${HOME}/.cargo/bin" >> "${GITHUB_PATH}"
+          echo "export PATH=\"$HOME/.cargo/bin:\$PATH\"" >> "${HOME}/.bash_profile"
+
+      - name: Check CUDA version
+        run: |
+          nvcc --version
+
+      - name: Setup rust
+        run: |
+          rustup set profile minimal
+          rustup toolchain install nightly-2023-04-17
+          rustup default nightly-2023-04-17
+
+      - name: Build tests and copy binaries to a separate dir
+        shell: bash
+        run: |
+          mkdir artifacts
+          CARGO_TARGET_DIR=./build \
+          cargo +nightly-2023-04-17 test --no-run --release --message-format=json -q \
+          | jq -r 'select(.executable != null) | .executable' \
+          | while read binary; do
+            cp "$binary" artifacts/
+          done
+
+      - name: Upload test binaries as a single artifact
+        uses: actions/upload-artifact@v3
+        with:
+          name: era-cuda-${{ matrix.cuda }}-test-binaries
+          path: artifacts/
+          if-no-files-found: error
+
+  era-cuda-test:
+    runs-on: [matterlabs-ci-gpu-runner]
+    needs: era-cuda-build
+    steps:
+      - name: Prepare environment
+        run: |
+          echo "/usr/local/nvidia/bin:/usr/local/cuda/bin" >> $GITHUB_PATH
+
+      - name: Check Nvidia driver version
+        run: |
+          nvidia-smi
+
+      - name: Download test binaries built with CUDA 12.2
+        uses: actions/download-artifact@v3
+        with:
+          name: era-cuda-12.2.0-devel-ubuntu20.04-test-binaries
+          path: era-cuda-test-binaries/12.2
+
+      - name: Download test binaries built with CUDA 12.0
+        uses: actions/download-artifact@v3
+        with:
+          name: era-cuda-12.0.0-devel-ubuntu20.04-test-binaries
+          path: era-cuda-test-binaries/12.0
+
+      - name: Run test binaries built with CUDA 12.2
+        id: test_cuda_12_2
+        continue-on-error: true
+        run: |
+          for binary in era-cuda-test-binaries/12.2/*; do
+            chmod +x $binary
+            $binary
+          done
+
+      - name: Run test binaries built with CUDA 12.0
+        if: steps.test_cuda_12_2.outcome == 'failure' || steps.test_cuda_12_2.outcome == 'success'
+        run: |
+          for binary in era-cuda-test-binaries/12.0/*; do
+            chmod +x $binary
+            $binary
+          done

.github/workflows/cargo-license.yaml

@@ -0,0 +1,8 @@
+name: Cargo license check
+on: pull_request
+jobs:
+  cargo-deny:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    - uses: EmbarkStudios/cargo-deny-action@v1

.github/workflows/ci.yaml

@@ -0,0 +1,15 @@
+name: "Rust CI"
+on:
+  pull_request:
+
+jobs:
+  formatting:
+    name: cargo fmt
+    runs-on: [ubuntu-latest]
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions-rust-lang/setup-rust-toolchain@v1
+        with:
+          components: rustfmt
+      - name: Rustfmt Check
+        uses: actions-rust-lang/rustfmt@v1

.github/workflows/secrets_scanner.yaml

@@ -0,0 +1,17 @@
+name: Leaked Secrets Scan
+on: [pull_request]
+jobs:
+  TruffleHog:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c # v3
+        with:
+          fetch-depth: 0
+      - name: TruffleHog OSS
+        uses: trufflesecurity/trufflehog@0c66d30c1f4075cee1aada2e1ab46dabb1b0071a
+        with:
+          path: ./
+          base: ${{ github.event.repository.default_branch }}
+          head: HEAD
+          extra_args: --debug --only-verified

.gitignore

@@ -0,0 +1,14 @@
+# Generated by Cargo
+# will have compiled files and executables
+/target/
+
+# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries
+# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
+Cargo.lock
+
+# These are backup files generated by rustfmt
+**/*.rs.bk
+
+# Ignore folders created by VSCode or JetBrain's IDEs
+/.idea/
+/.vscode/

CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contribution Guidelines
+
+Hello! Thanks for your interest in joining the mission to accelerate the mass adoption of crypto for personal
+sovereignty! We welcome contributions from anyone on the internet, and are grateful for even the smallest of fixes!
+
+## Ways to contribute
+
+There are many ways to contribute to the ZK Stack:
+
+1. Open issues: if you find a bug, have something you believe needs to be fixed, or have an idea for a feature, please
+   open an issue.
+2. Add color to existing issues: provide screenshots, code snippets, and whatever you think would be helpful to resolve
+   issues.
+3. Resolve issues: either by showing an issue isn't a problem and the current state is ok as is or by fixing the problem
+   and opening a PR.
+4. Report security issues, see [our security policy](./SECURITY.md).
+5. [Join the team!](https://matterlabs.notion.site/Shape-the-future-of-Ethereum-at-Matter-Labs-dfb3b5a037044bb3a8006af2eb0575e0)
+
+## Fixing issues
+
+To contribute code fixing issues, please fork the repo, fix an issue, commit, add documentation as per the PR template,
+and the repo's maintainers will review the PR.
+[here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+for guidance how to work with PRs created from a fork.
+
+## Licenses
+
+If you contribute to this project, your contributions will be made to the project under both Apache 2.0 and the MIT
+license.
+
+## Resources
+
+We aim to make it as easy as possible to contribute to the mission. This is still WIP, and we're happy for contributions
+and suggestions here too. Some resources to help:
+
+1. [In-repo docs aimed at developers]()
+2. [zkSync Era docs!](https://era.zksync.io/docs/)
+3. Company links can be found in the [repo's readme](README.md)
+
+## Code of Conduct
+
+Be polite and respectful.
+
+### Thank you

Cargo.toml

@@ -0,0 +1,3 @@
+[workspace]
+members = ["criterion-cuda", "cudart", "cudart-sys"]
+resolver = "2"