> For the complete documentation index, see [llms.txt](https://docs.creditcoin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creditcoin.org/cc-enterprise/creditcoin-change-log/version-2.1-2022-05-02.md). # Version 2.1 - 2022-05-02 **Please note:** This version utilizing the Substrate framework is still in beta. The following updates/fixes were released to the Creditcoin network: * Improved loan command structure for more seamless partner integration. Created more structure around interest rate declaration of type in terms (whether it is simple or compounding, rate per period, decimal declaration and period). This also extended to a rework and improvement to Register Transfer. * Improved security of Register Address by requiring “proof” of ownership via a signed message. * Established check on nonce when verifying Ethless transfers, and updated error messaging accordingly. * Improved fee structure to correlate with extrinsic weighting, runtime benchmarking and command structure. * Per miner requests, we exposed metrics for monitoring hash rates, and established alerts to monitor RPC nodes. --- # 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://docs.creditcoin.org/cc-enterprise/creditcoin-change-log/version-2.1-2022-05-02.md?ask=&goal= ``` `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.