serai/orchestration
Luke Parker 3f0f4d520d Remove the Sandbox contract
If instead of intaking calls, we intake code, we can deploy a fresh contract
which makes arbitrary calls *without* attempting to build our abstraction
layer over the concept.

This should have the same gas costs, as we still have one contract deployment.
The new contract only has a constructor, so it should have no actual code and
beat the Sandbox in that regard? We do have to call into ourselves to meter the
gas, yet we already had to call into the deployed Sandbox to achieve that.

Also re-defines the OutInstruction to include tokens, implements
OutInstruction-specified gas amounts, bumps the Solidity version, and other
such misc changes.
2024-09-19 23:36:32 -07:00
..
dev Misc changes in response to prior two commits 2024-09-19 23:36:32 -07:00
runtime Rust 1.80 2024-07-26 19:28:10 -07:00
src Remove the Sandbox contract 2024-09-19 23:36:32 -07:00
testnet Misc changes in response to prior two commits 2024-09-19 23:36:32 -07:00
Cargo.toml One Round DKG (#589) 2024-09-19 21:43:26 -04:00
README.md Redo Dockerfile generation (#530) 2024-02-09 02:48:44 -05:00

Orchestration

This folder contains the tool which generates various dockerfiles and manage deployments of Serai.

To start, run:

cargo run -p serai-orchestrator

to generate all of the dockerfiles needed for development.