文件列表:

Cargo.lock (202631, 2023-05-22)
Cargo.toml (562, 2023-05-22)
LICENSE (1055, 2023-05-22)
docker-compose.yml (463, 2023-05-22)
docs (0, 2023-05-22)
docs\Leadership.svg (13738, 2023-05-22)
docs\Portfolio.svg (5802, 2023-05-22)
docs\Problem_Solution.svg (15672, 2023-05-22)
docs\Project_score_schelling_game.svg (12361, 2023-05-22)
docs\Shivarthu.md (16017, 2023-05-22)
docs\Winners.svg (82639, 2023-05-22)
docs\approval_voting.svg (46156, 2023-05-22)
docs\effectiveness_schelling_game.md (2026, 2023-05-22)
docs\rust-setup.md (7878, 2023-05-22)
docs\web3_foundation_grants.svg (10565, 2023-05-22)
node (0, 2023-05-22)
node\Cargo.toml (5186, 2023-05-22)
node\build.rs (154, 2023-05-22)
node\src (0, 2023-05-22)
node\src\chain_spec.rs (4648, 2023-05-22)
node\src\cli.rs (1246, 2023-05-22)
node\src\command.rs (4283, 2023-05-22)
node\src\lib.rs (69, 2023-05-22)
node\src\main.rs (206, 2023-05-22)
node\src\rpc.rs (2742, 2023-05-22)
node\src\service.rs (10738, 2023-05-22)
node\src\silly_rpc.rs (437, 2023-05-22)
pallets (0, 2023-05-22)
pallets\department-funding (0, 2023-05-22)
pallets\department-funding\Cargo.lock (70906, 2023-05-22)
pallets\department-funding\Cargo.toml (3623, 2023-05-22)
pallets\department-funding\src (0, 2023-05-22)
pallets\department-funding\src\benchmarking.rs (482, 2023-05-22)
pallets\department-funding\src\extras.rs (635, 2023-05-22)
pallets\department-funding\src\lib.rs (11757, 2023-05-22)
pallets\department-funding\src\mock.rs (4076, 2023-05-22)
pallets\department-funding\src\tests.rs (628, 2023-05-22)
... ...

# Shivarthu ### Decentralized democracy with experts as leaders. https://shivarthu.reaudito.com/#/ ## Yew/Rust Frontend https://github.com/amiyatulu/shivarthu_client ## React Frontend https://github.com/amiyatulu/shivarthu_frontend ## Whitepaper https://shivarthu.reaudito.com/paper/Shivarthu_whitepaper.pdf ## Technical Details https://github.com/amiyatulu/shivarthu/blob/main/docs/Shivarthu.md # Substrate Node Template [](https://playground.substrate.dev/?deploy=node-template) [](https://matrix.to/#/#substrate-technical:matrix.org) A fresh FRAME-based [Substrate](https://www.substrate.io/) node, ready for hacking :rocket: ## Getting Started Follow the steps below to get started with the Node Template, or get it up and running right from your browser in just a few clicks using [Playground](https://playground.substrate.dev/) :hammer_and_wrench: ### Using Nix Install [nix](https://nixos.org/) and optionally [direnv](https://github.com/direnv/direnv) and [lorri](https://github.com/target/lorri) for a fully plug and play experience for setting up the development environment. To get all the correct dependencies activate direnv `direnv allow` and lorri `lorri shell`. ### Rust Setup First, complete the [basic Rust setup instructions](./docs/rust-setup.md). ### Run Use Rust's native `cargo` command to build and launch the template node: ```sh cargo run --release -- --dev --tmp ``` ### Build The `cargo run` command will perform an initial build. Use the following command to build the node without launching it: ```sh cargo build --release ``` ### Test Use the following command to test the contract ```sh cargo test ``` ### Generate docs To generate docs use command ```sh cargo doc --no-deps --open ``` To view in the python server, go to target folder ```sh cd target/doc python3 -m http.server ``` View the docs at: http://localhost:8000/election/ Schelling game shared docs: http://localhost:8000/schelling_game_shared/pallet/struct.Pallet.html ### Embedded Docs Once the project has been built, the following command can be used to explore all parameters and subcommands: ```sh ./target/release/node-template -h ``` ## Run The provided `cargo run` command will launch a temporary node and its state will be discarded after you terminate the process. After the project has been built, there are other ways to launch the node. ### Single-Node Development Chain This command will start the single-node development chain with persistent state: ```bash ./target/release/node-template --dev ``` Purge the development chain's state: ```bash ./target/release/node-template purge-chain --dev ``` Start the development chain with detailed logging: ```bash RUST_BACKTRACE=1 ./target/release/node-template -ldebug --dev ``` ### Connect with Yew Apps Front-end The front end repository: https://github.com/amiyatulu/shivarthu_client ```bash cd shivarthu_client trunk serve ``` ### Multi-Node Local Testnet If you want to see the multi-node consensus algorithm in action, refer to [our Start a Private Network tutorial](https://substrate.dev/docs/en/tutorials/start-a-private-network/). ## Template Structure A Substrate project such as this consists of a number of components that are spread across a few directories. ### Node A blockchain node is an application that allows users to participate in a blockchain network. Substrate-based blockchain nodes expose a number of capabilities: - Networking: Substrate nodes use the [`libp2p`](https://libp2p.io/) networking stack to allow the nodes in the network to communicate with one another. - Consensus: Blockchains must have a way to come to [consensus](https://substrate.dev/docs/en/knowledgebase/advanced/consensus) on the state of the network. Substrate makes it possible to supply custom consensus engines and also ships with several consensus mechanisms that have been built on top of [Web3 Foundation research](https://research.web3.foundation/en/latest/polkadot/NPoS/index.html). - RPC Server: A remote procedure call (RPC) server is used to interact with Substrate nodes. There are several files in the `node` directory - take special note of the following: - [`chain_spec.rs`](./node/src/chain_spec.rs): A [chain specification](https://substrate.dev/docs/en/knowledgebase/integrate/chain-spec) is a source code file that defines a Substrate chain's initial (genesis) state. Chain specifications are useful for development and testing, and critical when architecting the launch of a production chain. Take note of the `development_config` and `testnet_genesis` functions, which are used to define the genesis state for the local development chain configuration. These functions identify some [well-known accounts](https://substrate.dev/docs/en/knowledgebase/integrate/subkey#well-known-keys) and use them to configure the blockchain's initial state. - [`service.rs`](./node/src/service.rs): This file defines the node implementation. Take note of the libraries that this file imports and the names of the functions it invokes. In particular, there are references to consensus-related topics, such as the [longest chain rule](https://substrate.dev/docs/en/knowledgebase/advanced/consensus#longest-chain-rule), the [Aura](https://substrate.dev/docs/en/knowledgebase/advanced/consensus#aura) block authoring mechanism and the [GRANDPA](https://substrate.dev/docs/en/knowledgebase/advanced/consensus#grandpa) finality gadget. After the node has been [built](#build), refer to the embedded documentation to learn more about the capabilities and configuration parameters that it exposes: ```shell ./target/release/node-template --help ``` ### Runtime In Substrate, the terms "[runtime](https://substrate.dev/docs/en/knowledgebase/getting-started/glossary#runtime)" and "[state transition function](https://substrate.dev/docs/en/knowledgebase/getting-started/glossary#stf-state-transition-function)" are analogous - they refer to the core logic of the blockchain that is responsible for validating blocks and executing the state changes they define. The Substrate project in this repository uses the [FRAME](https://substrate.dev/docs/en/knowledgebase/runtime/frame) framework to construct a blockchain runtime. FRAME allows runtime developers to declare domain-specific logic in modules called "pallets". At the heart of FRAME is a helpful [macro language](https://substrate.dev/docs/en/knowledgebase/runtime/macros) that makes it easy to create pallets and flexibly compose them to create blockchains that can address [a variety of needs](https://www.substrate.io/substrate-users/). Review the [FRAME runtime implementation](./runtime/src/lib.rs) included in this template and note the following: - This file configures several pallets to include in the runtime. Each pallet configuration is defined by a code block that begins with `impl $PALLET_NAME::Config for Runtime`. - The pallets are composed into a single runtime by way of the [`construct_runtime!`](https://crates.parity.io/frame_support/macro.construct_runtime.html) macro, which is part of the core [FRAME Support](https://substrate.dev/docs/en/knowledgebase/runtime/frame#support-library) library. ### Pallets The runtime in this project is constructed using many FRAME pallets that ship with the [core Substrate repository](https://github.com/paritytech/substrate/tree/master/frame) and a template pallet that is [defined in the `pallets`](./pallets/template/src/lib.rs) directory. A FRAME pallet is compromised of a number of blockchain primitives: - Storage: FRAME defines a rich set of powerful [storage abstractions](https://substrate.dev/docs/en/knowledgebase/runtime/storage) that makes it easy to use Substrate's efficient key-value database to manage the evolving state of a blockchain. - Dispatchables: FRAME pallets define special types of functions that can be invoked (dispatched) from outside of the runtime in order to update its state. - Events: Substrate uses [events](https://substrate.dev/docs/en/knowledgebase/runtime/events) to notify users of important changes in the runtime. - Errors: When a dispatchable fails, it returns an error. - Config: The `Config` configuration interface is used to define the types and parameters upon which a FRAME pallet depends. ### Run in Docker First, install [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/install/). Then run the following command to start a single node development chain. Create a folder .local inside `shivarthu` folder And run `docker compose up` inside the `shivarthu` folder ```bash cd shivarthu mkdir .local docker compose up ``` This command will firstly compile your code, and then start a local development network. You can also replace the default command (`cargo build --release && ./target/release/node-template --dev --ws-external`) by appending your own. A few useful ones are as follow. # Purge the local dev chain `cargo build --release && ./target/release/node-template purge-chain --dev` # Check whether the code is compilable `cargo check`

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：