> For the complete documentation index, see [llms.txt](https://eosforce-1.gitbook.io/eosc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eosforce-1.gitbook.io/eosc/weelky-report/eosc-weekly-report/eosc-weekly-report-52.md).

# EOSC Weekly Report #52

07/15/2019 - 07/21/2019

**Work Completed**

1\. Transplanted the new EOSForce system contract of eosio.lock and eosio.msig.

2\. Implemented the common assetage mechanism and unicode.

3\. Added global voting state to display voting data and efficiency of optimization and execution.

4\. Improved Ricardian Contract of EOSForce system contract.

5\. Reconstructed the code of EOSForce system contract, adjusted the code structure.

6\. Updated EOSForce system contract based on the new EOSForce economic model scheme

7\. Cooperated with the community to update EOSForce mainnet to force-v1.6.0, preparing for the subsequent updates.

8\. Cooperated with the community to test Codex cross-chain system.

9\. Fixed the Codex.Relay problem reported in the testing.

10\. Planned the development of EOSForce system contract according to FIP#7 proposal.

11\. Designed the scheme of EOSForce fix-time voting, planned the update of compatibility mechanism.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://eosforce-1.gitbook.io/eosc/weelky-report/eosc-weekly-report/eosc-weekly-report-52.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.