> 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-56.md).

# EOSC Weekly Report #56

08/12/2019 - 08/18/2019

**Work Completed**

1. Tested EOSForce new system contract, and prepared for the update of v1.7.0.
2. Tested the merged version of Codex.relay, and fixed the compilation problem.
3. According to the community feedback, added Action of revoting based on the unredeemed vote to the fix-time voting and current voting system contract.
4. Added a temporary extension interval to support the system contract update.
5. Collated the design plan of Codex.Relay new economy model , and updated Codex.Relay system contract accordingly.
6. Tested the compilation of the upgraded EOSForce compiler version to merge with EOSIO v1.8.0 conveniently.
7. Collated the new EOSForce system contract document.
8. Reconstructed the codes of Codex.relay system contract according to the new cdt.
9. Improved the support for the new feature of the wallet.


---

# 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-56.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.