Merge pull request #109 from Leonets/dao-challenge

Dao challenge

Author: klembee

.gitignore

@@ -13,3 +13,6 @@ Cargo.lock
 # Flamegraph profiles
 flamegraph.svg
 3-lending/LendingDApp/node_modules
+3-lending/LendingDApp/public/lending_dapp.wasm
+3-lending/LendingDApp/public/loan_application.wasm
+3-lending/LendingDApp/TODO.md

4-portfolio-management-yield-farming/BiddingDApp/transactions/take1.rtm

@@ -0,0 +1,2 @@
+[build]
+rustdocflags = ["--document-private-items"]

5-DAO/ArchDAO/.cargo/config

@@ -0,0 +1,2 @@
+*~
+old/

5-DAO/ArchDAO/.gitignore

@@ -0,0 +1,31 @@
+[package]
+name = "archdao"
+version = "1.0.0"
+edition = "2021"
+
+[dependencies]
+sbor = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "v0.6.0" } 
+scrypto = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "v0.6.0" } 
+regex = "1"
+lazy_static = "1.4.0"
+
+[dev-dependencies]
+radix-engine = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "v0.6.0" } 
+#transaction = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "v0.6.0" } 
+#scrypto-unit = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "v0.6.0" } 
+
+[profile.release]
+opt-level = 's'     # Optimize for size.
+lto = true          # Enable Link Time Optimization.
+codegen-units = 1   # Reduce number of codegen units to increase optimizations.
+panic = 'abort'     # Abort on panic.
+strip = "debuginfo" # Strip debug info.
+overflow-checks = true # Panic in the case of an overflow. 
+
+[lib]
+crate-type = ["cdylib", "lib"]
+
+
+
+
+

5-DAO/ArchDAO/Cargo.toml

@@ -0,0 +1,61 @@
+![](./archdao_black_mini.jpg)
+
+# ArchDAO - A proposal DAO
+
+This project aims to manage the votes of a group of people who wish to express their choices with respect to a series of projects that are already partially funded by the founders of the DAO and who therefore wish to be helped in defining the priorities of each individual project.
+
+ArchDAO implements a crypto dao that serves for decentralized governance of business proposal from the initial stage to the approval and the execution stage
+
+Proposers receive fungible vote tokens in return for their registering, with vote tokens representing shares of decision of the
+whole proposal approval process. 
+Right to vote can be transferred and whoever holds them can at any time vote for a proposal. 
+
+Proposers can also fund the ArchDao with XRD tokens and receive back ARCH tokens, as the projects funded by ArchDAO makes profits the value of each ARCH token will increase.
+
+The ArchDAO's managers can dynamically add and remove proposal, or ask to verify if the proposal trigger is satisfied for promoting a proposal into a into a project ready to be funded.
+
+The votes are calculated using a conviction system, that means that each vote gets calculated at its value only after some epochs have passed (for at least 1000epoch) the same when you remove the vote, the removed vote will continue to be calculated for at least the some amount of epochs. 
+
+The ArchDAO can charge protocol fees, intended at producing profits for the ArchDAO's managers. Some or all of these protocol fees can go
+towards rewards for both the managers and the voters.
+
+Both the managers and the voters can earn rewards when the project gets executed and when the execution produces a profit.
+
+## Example
+
+For this kind of project there are many use cases, since the cases can be innumerable then let's try to describe a specific use case for Radix.
+
+Let's say that during one of the appointments defined 'RoundTable' it is decided that an extra funding of 1,000,000xrd should be divided between the departments, so each one will propose his idea which will then be voted through the DAO to obtain funding for each project that is proportional to the result of the votes obtained.
+
+## Development issues
+
+Unfortunately I was not able to dedicate the right time to the project and the features present are at most 50% of what I would have liked. In any case, considering the time spent, the result is a good starting point, moreover in this way it was possible to verify the progress with Scrypto 0.6 and run the first publication on Alphanet.
+
+This time various transaction manifest files were developed and their testing was performed without the new TestRunner but using Resim through the test library, I also wanted to change the design and use owned components but this was not possible due to time.
+
+I have to thank my friend Gigi who always prepares me some very nice logos and Jake who answered several of my questions!
+
+## How to build the blueprints
+
+Make sure you have the necessary toolchain installed, including the
+resim tool, see
+[here](https://docs.radixdlt.com/main/scrypto/getting-started/install-scrypto.html)
+for details. You will need Scrypto 0.6.0.
+- From the command line, in the `archdao` directory, run `cargo build`
+
+### How to run the test suite
+
+- Make sure you have the resim tool installed, see above.
+- From the command line, in the `archdao` directory, run `cargo test -- --test-threads=1 --nocapture`
+
+### How to generate the documentation
+
+- From the command line, in the `archdao` directory, run `cargo doc`
+
+The generated web pages contain detailed documentation on how the blueprints work.
+
+### Useful command
+scrypto test -- --nocapture
+cargo test -- --test-threads=1 --nocapture
+
+

5-DAO/ArchDAO/README.md

@@ -0,0 +1,25 @@
+# Parameters:
+#
+# component: Address of the ArchDAO instance to use
+#
+# account: Account of user running the transaction. Must 
+#          be able to create proof of the admin badge.
+#
+# admin_badge: ResourceAddress of the admin badge.
+#
+# proposalProject: ComponentAddress of proposal component to add.
+CALL_METHOD 
+    ComponentAddress("${account}")
+    "lock_fee"
+    Decimal("10");
+
+CALL_METHOD
+   ComponentAddress("${account}")
+   "create_proof"
+   ResourceAddress("${admin_badge}");
+
+CALL_METHOD
+   ComponentAddress("${component}")
+   "add_proposal"
+   ComponentAddress("${proposal_project}")
+   "${proposal}";