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

# EOSC Weekly Report #59

09/02/2019 - 09/08/2019

**Work Completed**

1.Tested the compatibility of sync blocks on EOSC v1.8.0, fixed the appeared problems.

2.Improved the support for EOSC snapshot.

3.Optimized the Node Punishment Mechanism, fixed the design that affects performance.

4.Reconstructed EOSC node heartbeat plugin.

5.Integrated the on-chain configuration and feature-related functions of EOSC.

6.Transplanted a new EOSJS library for EOSC, collated JS development document.

7.Cooperated with the community to launch EOSC test network, and made preparations for the update of new functions.

8.Improved the front-end support of the decentralized budget system.


---

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