Patract Weekly Report
The 3rd Week, April
Work of Council
Patract had participated in the discussion about the Polkadot Alliance Pact in the Polkadot Direction group. The Pact believes that because Polkadot is a project driven by governance such as councillors and referenda, it is not completely controlled by static code logic and needs to maintain the interests for token holders. Therefore, Proper management of the community should not allow unethical fork projects to appear arbitrarily, such as trying to build a bridge to access in the Polkadot ecosystem, or even defrauding the Treasury or Grant for fund.
The community is facing with complex and diversified ecological projects. Considering the community can’t quickly distinguish between good and bad, multiple relay chains may appear in the community, resulting the ecosystem into a fragmented direction, which is greatly detrimental to the long-term development of the Polkadot community and Web 3.0 vision. Some Councillors believes that for decentralized blockchain projects and open source community culture, it is impossible to build a wall of friends or enemies, or to limit the convention to basic principles. Such issues should not be raised to the political level and at the referendum level, it will hinder possible innovation.
- Voted nay for Kusama Treasury Proposal #86, because no explanation was provided.
- Voted aye for Polkadot Treasury Proposal #44, regarding the development of Redspot v0.4.
- Voted aye for Polkadot Treasury Proposal #45, regarding the privacy-related events held by ZKV, Patract’s zkMega project will participate, and other privacy-related projects in the community are welcome to contact ZKV.
- Created a docker repository and added an automatic publishing process.
- Updated the CI, and the later version releases will be more semantic.
- Created plug-in of the Redspot types.
- Added the ability to write and throw an exception when the contract has the same name.
- Extracted redspot-template to the independent repository and updated redspot-new cli.
- Fixed bugs in the implementation of @event.
- Completed the implementation of @packed annotation.
- Optimized inheritance development.
- In the ask , globally introduced the object Msg, Storage, etc.
- By defining the interface, completed cross-contract calls and started development.
- Prepare to submit v0.3 proposal.
- Completed the product design.
- Directly used the mock runtime function of node runtime to run normally.
- Removed the mock runtime of the node runtime and entered the call link of the execution block. There is a temporary storage problem at present.
Ceres has currently iterated 5 versions, view for details.
- Completed the beta version of Ceres command line tool.
- fix: the logic of not canceling the kv message subscription.
- feature: Feishu robot monitor
- Feature: PM2 error log.
- Completed 90% of the basic data structure document.
- Summarized and analyzed all extrinsic and event types, and written 60% of special display information.
- Streamlined 10% of the data structure class diagram.
- Completed the prototype drawing and the writing of the requirements document.
- Supplemented to the Council proposal.
Marketing and Opertation
#Substrate Contract Book
The Substrate Contract Book is led by Patract, and its CTO Aten is responsible for writing a series of knowledge related to Substrate and the Wasm contract system. It is currently online on the official website (https://docs.patract.io/) and is continuously updated. Welcome to check.
At the same time, We also welcome some interested developers to contribute to this book together.
In the first issue of TechShare, Patract’s CTO, Aten shared How To Quickly Get Started With Smart Contracts of ink! . Welcome to watch the video. Click for view.
Patract is providing solutions for the development of Parachains and DApps in the Wasm smart contract ecosystem of Polkadot. We help the community to design and develop on-chain contract modules and Runtime support, and provide DApp developers with full-stack tools and services support, covering development, testing, debugging, deployment, monitoring, data provider and front-end development stages.