Constraint System

[jakehemmerle]

Overview

This issue serves as an issue tracker for the constraint system. While some of these tasks and ideas are sourced from this hackmd doc, that will continue to serve as an active and up-to-date (dis)organization of my thoughts for now.

Devnet

For devnet, we just want to be able to do recipient whitelisting and blacklisting for an EVM. For this, we need:

• Unsigned TX distribution flow (Client -> Server, Substrate)
  • Add new endpoint for receiving unsigned transactions in crypto/server #233
  • Add new storage method mapping the transaction hash to the transaction in the KVDB #234
  • Add frontend logic for sending an unsigned transaction #235
  • Add a new substrate event for alice to get all the IP addresses #236
  • Add frontend logic for alice to get all the IP addresses #237
• TX Parsing and constraint checking (Server)
  • Parse EVM TX to basic generic transaction #238
  • entropy-constraints: ACL evaulation #241

Post-Devnet

• Add constraint version storage (Substrate)
• New constraint - max tx amount per time (Substrate/Server)
• Custom constraint engine
• Custom constraints as a Rust DSL
  • Constraint config as single storage (Substrate/Server)
• Remove web3 dep from server (pretty heavy)

It'd be super cool to do constraints in zk, and have signers coordinate blinded threshold ECDSA. This would eliminate the hash being stored on-chain and the servers even knowing the unsigned tx. While I've had some basic discussions with Thor on Halo2 for zk constraints and I see at least one blind TSS based on discrete log, I will leave details of this to the crypto team.

[jakehemmerle]

Constraints scoping/roadmap meeting 11/17/22 - notes

Derive Substrate keys from the user's threshold keyshare

#244

Schedule a meeting with product to go through what constraints should look like from a UI perspective; meeting with Hermie(?).

[jakehemmerle]

closing because this can't ref stuff across repos and this needs to get broken down into more chunks