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

# EOSC Weekly Report #54

07/29/2019 - 08/04/2019

**Work Completed**

1\. Planned the upgrade of EOSForce mainnet v1.7.x.

2\. Recomposed EOSForce system contract document, refined the mechanism description, and added the new functional description.

3\. EOSForce chain API added the interfaceof get\_vote\_reward to obtain the account voting reward value.

4\. Improved EOSForce heartbeat mechanism, simplified the heartbeat-related configurations.

5\. Implemented the punishment mechanism of block missing.

6\. Designed the plan of on-chain account system of EOSForce decentralized budget system.

7\. Designed the plan of block extension information compatible with EOSIO v1.8.x and subsequent versions.

8\. Designed the plan of on-chain account system of Codex decentralized budget system.

9\. Refined the testing of Codex.relay transaction contract unit.


---

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