Cwd proposal delegate

contracts/proposal/cwd-proposal-delegate/.cargo/config

@@ -0,0 +1,4 @@
+[alias]
+wasm = "build --release --lib --target wasm32-unknown-unknown"
+unit-test = "test --lib"
+schema = "run --bin schema"

contracts/proposal/cwd-proposal-delegate/.gitignore

@@ -0,0 +1,16 @@
+# Build results
+/target
+/schema
+
+# Cargo+Git helper file (https://github.com/rust-lang/cargo/blob/0.44.1/src/cargo/sources/git/utils.rs#L320-L327)
+.cargo-ok
+
+# Text file backups
+**/*.rs.bk
+
+# macOS
+.DS_Store
+
+# IDEs
+*.iml
+.idea

contracts/proposal/cwd-proposal-delegate/Cargo.toml

@@ -0,0 +1,60 @@
+[package]
+name = "cwd-proposal-delegate"
+version = "1.0.0-beta"
+authors = ["baoskee"]
+edition = "2021"
+repository = "https://github.com/DA0-DA0/dao-contracts"
+description = "Proposal execute delegation to any smart contract"
+exclude = [
+  # Those files are rust-optimizer artifacts. You might want to commit them for convenience but they should not be part of the source code publication.
+  "contract.wasm",
+  "hash.txt",
+]
+
+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
+[lib]
+crate-type = ["cdylib", "rlib"]
+
+[features]
+# for more explicit tests, cargo test --features=backtraces
+backtraces = ["cosmwasm-std/backtraces"]
+# use library feature to disable all instantiate/execute/query exports
+library = []
+
+[dependencies]
+cosmwasm-std = { workspace = true, features = ["ibc3"] }
+cosmwasm-storage = { workspace = true }
+cosmwasm-schema = { workspace = true }
+cw-storage-plus = { workspace = true }
+cw-utils = { workspace = true }
+cw2 = { workspace = true }
+cw20 = { workspace = true }
+cw3 = { workspace = true }
+thiserror = { version = "1.0" }
+dao-core = { workspace = true, features = ["library"] }
+dao-macros = { workspace = true }
+dao-pre-propose-base = { workspace = true }
+dao-interface = { workspace = true }
+dao-voting = { workspace = true }
+cw-hooks = { workspace = true }
+cw-paginate = { workspace = true }
+dao-proposal-hooks = { workspace = true }
+dao-vote-hooks = { workspace = true }
+dao-pre-propose-multiple = { workspace = true }
+voting-v1 = { workspace = true }
+
+[dev-dependencies]
+cw-multi-test = { workspace = true }
+dao-voting-cw4 = { workspace = true }
+dao-voting-cw20-balance = { workspace = true }
+dao-voting-cw20-staked = { workspace = true }
+dao-voting-native-staked = { workspace = true }
+dao-voting-cw721-staked = { workspace = true }
+cw-denom = { workspace = true }
+dao-testing = { workspace = true }
+cw20-stake = { workspace = true }
+cw20-base = { workspace = true }
+cw721-base = { workspace = true }
+cw4 = { workspace = true }
+cw4-group = { workspace = true }
+rand = { workspace = true }

contracts/proposal/cwd-proposal-delegate/README.md

@@ -0,0 +1,95 @@
+# Introduction
+
+Delegation is basically: “we trust you have the judgment, we give you the power to do this specific action within some X time frame. You have the right but not the obligation.”
+
+## Examples 
+- You have the power to kick this specific member after review. Perhaps you make an investigative committee after a member is accused of something, and delegate the power to a multisig to execute the message: “Kick this member”
+- You can pause one of our SubDAOs for 1 week if necessary
+- You have the power to add a specific item to our DAO config at any time
+- You have the power to increase Bob’s salary by 800 JUNO through DAO treasury
+- Liquidate 8000 JUNO through JunoSwap at any time. Perhaps you want to delegate this to a hedge fund who promises to “time the market”
+
+## When would it not be useful?
+
+- **You can compose it through something other than a proposal module**. A separate option contract. However, this would not allow you to execute messages through the core module. Only proposal modules can pass messages through the core module.
+  - In order to control Treasury funds, you can siphon off to a SubDAO, and then SubDAO can make the decisions. However, this does not constrain the action of the SubDAO. It can totally misuse those funds. We want allowance of specific and concrete messages.
+  - In most cases, an escrow contract would do the job, but in certain cases, we want to be very granular with the actions we delegate
+
+## When would it be useful?
+
+- **For specific, constrained DAO-related actions**. For the things the DAO control and in which an escrow would give too much power over the resource. The DAO wants delegation on specific message that gives the delegate constrained power
+- **Time-based actions**. Actions where the time of execution matters, and an executive decision maker needs power to execute at any time
+- **Judgment-based actions**. Perhaps another DAO or oracle service specializes in identity-proving activities, and you would like to mark certain members as a real person for some sort of one person one vote thing. Or, perhaps, you want to remove a multisig member, and decide to delegate said action to a Judiciary DAO, some sort of tribunal
+
+
+
+# Design
+
+This is kind of a “messages escrow” module in which the execution of the proposal is wrapped into an option and execution is given to another party.
+
+
+It would be a “proposal module” that allows arbitrary wrapping of messages, and would be required for the DAO to add as a Proposal Module. However, it would not use a voting module, but rather, another proposal module like `cwd-proposal-single` would pass a delegation message to the Core module, whereby the core module would execute a delegation message.
+
+Execution messages:
+
+```rust
+// Gives back a delegation ID
+Delegate { msgs: Vec<CosmosMsg<Empty>>, addr: String, expiration: Expiration }
+// Authorized execution only
+Execute  { delegation_id: u64 }
+```
+
+State:
+
+```rust
+struct Config {
+    admin: Addr,
+}
+
+struct Delegation {
+	addr: Addr,
+	msgs: Vec<CosmosMsg<Empty>>,
+	expiration: Expiration,
+}
+
+const DELEGATIONS: Map<u64, Delegation> = Map::new("delegations");
+const CONFIG: Item<Config> = Item::new("config");
+```
+
+## How could a DaoDao core module use this?
+
+1. Add as a proposal module
+2. Pass a delegation message through another proposal module (single or multiple-choice) as a Wasm message (converted into Cosmos message)
+
+   ```rust
+   WasmMsg::Execute {
+   	contract_addr: // address of Delegation Proposal Module
+   	msg: to_binary(&DelegationExecuteMsg::Delegate {
+   		msgs: // Cosmos messages to delegate,
+   	  addr: "0x2342", // Delegate with power to execute, possibly another DAO
+   	  expiration: 123123324
+   	})?,
+   	funds: vec![]
+   }
+   ```
+
+3. The delegate has the power to execute said proposal through the Delegate Proposal Module at any time up until expiration. Said execution would go through the DaoDao core module
+
+
+# Smart Contract Risks
+Proposal modules can route arbitrary messages to
+the core module so we have to take special care.
+I can classify risks into these domains:
+* Un-authorized delegation  
+* Un-authorized execution
+* Un-authorized revocation
+* Multiple execution
+* Expired execution 
+
+Policy risks: 
+* Forbidden revoking when policy enabled
+* Does not preserve on failure when policy enabled
+
+
+Of all the risks, un-authorized delegation will definitely
+compromise the core module.

contracts/proposal/cwd-proposal-delegate/src/bin/schema.rs

@@ -0,0 +1,11 @@
+use cosmwasm_schema::write_api;
+
+use cwd_proposal_delegate::msg::{ExecuteMsg, InstantiateMsg, QueryMsg};
+
+fn main() {
+    write_api! {
+        instantiate: InstantiateMsg,
+        execute: ExecuteMsg,
+        query: QueryMsg,
+    }
+}