Copy from: https://polkadot.polkassembly.io/post/101

Github: [https://github.com/patractlabs/redspot-0.2](https://github.com/patractlabs/redspot-0.2)

Redspot's goal is to standardise the contract development process, hide the underlying compilation details of the contract, and combine the sandbox, library, API, SDK and other plugins to create a one-stop smooth contract development process. We have finished the first [proposal](https://polkadot.polkassembly.io/motion/7) requirements for v0.1,  and written a development [report](https://polkadot.polkassembly.io/post/78).

### Summary of Redspot's future plan:

1. v0.1: Build core available functions based on Truffle framework.
2. v0.2: Migrate to the [Buidler](https://buidler.dev/) framework to enhance plugin extensibility and add some functions to provide a smoother development workflow.
3. v0.3: Imitating Buidler's plugins, combined with the characteristics of Substrate to add various plugins, such as waffle, and began to integrate multi-language SDK.
4. v0.4: Following the case of Buidler, add appropriate libraries, such as typechain, etc.

### Problems of Redspot v0.1:

Although we have completed all the basic functions of Redspot, there are still some inconveniences in use. E.g:

* There is no convenient interactive cli for simple interaction with deployed contracts;
* Only the private key in plain text is supported in the configuration file, derivation through seed is not supported, and the password cannot be hidden;
* Under the default instantiation address logic of pallet-contracts, the contract address generated by a single account with the same parameters and the same WASM code is unique. This is not like Ethereum's single account can repeatedly deploy the same contract with different addresses. Therefore, after the deployment script and test script are written in Redspot, they can only be executed once. Otherwise, during the second execution, the execution will be interrupted during the deployment phase because it cannot be deployed. This requires script developers to pay careful attention to the writing method, otherwise it is easy to make mistakes. Redspot hopes to simplify this process.
* When deploying scripts and test scripts are instantiating or calling contracts, gas_limit needs to be written in after estimated whether the current assets are sufficient to support contract execution. Redspot currently simply fills in a default value, and does not have an estimation method, and does not know the gas consumption after execution;

### Detailed design of v0.2 (6 weeks, 21 Sept ~ 2 Nov):

The Buidler framework provides a "plugin" model, which can give Redspot great scalability and flexibility. This framework can also support Redspot to connect with contract modules on different parachains. For example, you can replace the environment of the target chain through plugins, add SDKs in other languages, and add extensible functions. In v0.2, Redspot will migrate all the functions of v0.1 to the new Buidler framework, and write various plugins to solve the problems of v0.1.

**Milestone 1: (3 developers * 1 weeks )**

Fork Buidler framework and modify it to suit the Substrate blockchain, then migrate all the current features in  Redspot v0.1 as inner plugins to this new framework.

**Milestone 2: (3 developers * 1 weeks)**

Support an interactive cli to operate deployed contracts, this cli will include injected polkadot.js interface and other helper functions, global env, key pairs, and connected node.

**Milestone 3: (3 developers * 1 weeks)**

Plugin 1: key pair support.
* Developers can use a private key directly;
* Developers can use a seed, and can derive account from this seed;
* Developers can use indicate a path for the keystore file, so that the private key will not appear in the config file.

**Milestone 4: (3 developers * 1 weeks)**

Plugin 2: multiple executing test support. This plugin provides a way to allow developer to deploy contracts more than once using same account and parameters in tests.
* Developers can use “beforeTest” to derive accounts and transfer some balance to this new account.
* Developers can use this new account to deploy contracts.
* Every executing test command will derive new accounts automatically.

**Milestone 5: (3 developers * 0.5 week)**

Plugin 3: [Jupiter](https://github.com/patractlabs/jupiter) test-net support as deploying environment;
* Jupiter test-net will use a flag storage to allow developers to use same account, same parameters and same code to deploy more than once.
* This plugin will develop a matching interface to interactive with Jupiter to set flag.
* This plugin’s env will allow developers to do deploying and testing in a normal way.

**Milestone 6: (3 developers * 1.5 weeks)**

Plugin 4: gas usage report.
* This plugin can print gas usage per test phase and deploying actions.
* This plugin can print gas usage per interactive cli.

### Cost of v0.2 (18 developers * weeks)
* Operating activities: $3600 ( Rent and Devices: $200 per developer * week )
* Employee payments: $27000 ($1500 per developer * week)
* —————————— +
* Total Cost: $30600
* Exchange Rate: $4/ New DOT
* Treasury Proposal: 7650 New DOT

### How to verify v0.2: Youtube demo video & Github source

* Replay all v0.1 tests in v0.2
* Show how Redspot v0.2 interactive cli works

**Workflows:**

* Use "deploy" command and execute deploying scripts
* Use interactive cli
* Call deployed contract
* Send extrinsics to call a contract
* Deploy a new contract in cli

**Plugins:**

* key pair plugin:
    * allowing developers to use seed, private key or a keystore path in config
* multiple executing test plugin:
    * could repeat any test command without any changes in test scripts.
* Jupiter test-net plugin:
    * could connect with Jupiter test-net by using a config flag in config files
    * could repeat any test command without any changes in test scripts.
* Gas usage report plugin:
    * could print gas usage for every test phase
    * could print gas usage after calling a contract in interactive cli

Awarded

Patract Labs' treasury proposal for Redspot v0.2

Untitled - treasury proposal #12

Proposal:#10 (motion 17)

Proponent: 146GTTVAZhU8epotD6ymKpRfhUwVLYrhL8Ho28LVeox4GrWC

Proposal date: 7.9.2020

Requested DOT: 1500

Short description: Polkadot Meetup in China

8btc.com (the proponent)  hosted a Polkadot meetup in Hangzhou, China.

[8btc](https://www.8btc.com/) is one of earliest and biggest crypto media in China. 8btc was founded by Changjia and Jihan Wu in 2011, and translated the very first Chinese version of bitcoin whitepaper. 8btc is an information and education platform for crypto users and people interested in cryptos in China. In 2016, [8btc English News](https://news.8btc.com/) was founded to act as a bridge between Chinese and foreign communities. 

8btc is also a host of [Hangzhou Blockchain Week](https://www.8btc.com/gbsf-2020?lang=en) and [World Blockchain Conference](https://www.8btc.com/wbc-2019/?lang=en), which will be held every year. Besides these two conferences, 8btc will host plenty of meetups with different themes every year. [Chainge](https://www.8btc.com/author/61023) is the name we gave to tech-related meetups, which is also for the Polkadot meetup we are about to host. Chainge has seen most famous blockchain teams in China joined in, including IRISnet, Nervos and PlatOn.

As a validating node of Polkadot, 8btc appreciates what Polkadot brings to the blockchain world and Web3 development. Though Polkadot is already a well-known project in China, most people know little about the related tech and what Polkadot can bring to the blockchain revolution.

So the meetup named ‘[Polkadot and the Trust World it Brings](https://www.chainnode.com/event/469852)’ will get more people to truly learn about what Polkadot is and will be, instead of pure speculation. Hangzhou is only our first station, there will be more in different cities of China.

The meetup was from 1:30pm to 5:00pm, on Sep. 12th (GMT+8). Entrance was free and there were more than 130 people to attend the meetup.

Please checked [here](https://docs.google.com/document/d/1RDutByvYe6n5nvIl2Jbx7PmQQwtS5xzYOe6iKc1v_Js/edit#heading=h.z7n65nftppgq) to see more budget details.

Pls feel free to ask me anything. Thanks!

Wendy, 
Head of 8btc English News


Polkadot Meetup in China - Proposal:#10 (motion 17)

please see https://polkadot.polkassembly.io/post/52 for the full description of our proposal

Treasury Proposal: Encointer Self-Sovereign Identity Parachain for Polkadot

Untitled - treasury proposal #8

Untitled - treasury proposal #7

Rejected

Untitled - treasury proposal #5

Untitled - treasury proposal #2

** Labs Introduction & Overall Proposals: ** https://polkadot.polkassembly.io/post/15

## Redspot v0.1

Github: https://github.com/patractlabs/redspot

Patract Labs' first project is "Redspot", named after Jupiter's Great Red Spot, which is also the largest DOT in the solar system. Redspot is inspired by Truffle (https://github.com/trufflesuite/truffle) in Truffle Suite. Redspot is a development environment, testing framework and asset pipeline for pallet-contracts. Redspot is trying to let the development of ink! be projectized and simplify the testing and interacting with contracts.

### Milestones : 3 weeks (20 Aug - 11 Sept)

**  M1: Testnet (1 developer * 2 weeks) **

1. Quickly deploy a local Substrate node with smart contract pallet that can be debugged locally
1. Launch a public testnet (named with Jupiter) with smart contract pallet, , and continuously maintain and upgrade it.

** M2: Environment (2 developers * 2 weeks)**

1. Provide command-line tools to pull resources from the network and build a local contract development and test environment by one command. 
1. Provide several built-in different contract template frameworks, such as single contract and multi-contract projects.

** M3: Compile and Deploy (3 developers * 3 weeks)**

1. Check whether the local Rust environment and contract development toolchain are complete
1. Automatically discover the contract code existing in the specified directory of the project, especially for multi-contract projects, support independent compilation between contracts, generate metadata, etc.
1. Support deploying contracts to the corresponding network through configuration files and command line options.

** M4: Testing (3 developers * 3 weeks)**

1. Provide a basic contract testing framework based on Mocha Assert or Jest
1. Support connecting different networks for contract testing through configuration files
1. Provide global parameters for common usage such as default accounts and network configuration, and provide some commonly used tools and assertion functions for testing
1. Get the deployed contract instance through Javascript and support simple interaction with the contract interface

### Cost

- Operating activities: $5000 ( Rent: $1000 per week, Servers & Devices: $2000)
- Employee payments: $24000  ( $1000 per developer * week)
- -------------------- +
- Total Cost: $29000
- Exchange Rate: $2.90/DOT
- Treasury Proposal: 10000 DOT

### How to Verify: Youtube demo video & Github source

1. Can simply deploy a local testnet to test.
1. Can connect with the public testnet (Jupiter) to verify.
1. Can generate a smart contract project's directory.
1. Can use Redspot commands to do “compile”, “deploy”, “test”