networks/ethereum/schnorr/build.rs

fn main() {
  let artifacts_path = std::env::var("OUT_DIR").unwrap().to_string() + "/ethereum-schnorr-contract";
  build_solidity_contracts::build(&[], "contracts", &artifacts_path).unwrap();
}
Dedicated crate for the Schnorr contract 2024-09-15 00:41:16 -04:00			`fn main() {`
Remove artifacts for serai-processor-ethereum-contracts 2024-09-15 12:04:57 -04:00			`let artifacts_path = std::env::var("OUT_DIR").unwrap().to_string() + "/ethereum-schnorr-contract";`
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-15 05:56:57 -04:00			`build_solidity_contracts::build(&[], "contracts", &artifacts_path).unwrap();`
Dedicated crate for the Schnorr contract 2024-09-15 00:41:16 -04:00			`}`