> For the complete documentation index, see [llms.txt](https://nexas-ridewiz.gitbook.io/myagents.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexas-ridewiz.gitbook.io/myagents.plus/product-development/changelog/blockchain-web3-changelog.md).

# Blockchain/Web3 (changelog)

<figure><img src="/files/LfLiXObHWKvRDBHtR3eD" alt=""><figcaption></figcaption></figure>

**31 March 2023**

* Maintenance completed.

**20 March 2023**

* Burn test successful for Token.

{% embed url="<https://polygonscan.com/tx/0xf1085aa3e67f3151e918bed861b6482a09557e62ceb7bc5f36eb56c4a12727da>" %}

* Transfer test successful for Token.

{% embed url="<https://polygonscan.com/tx/0x351c81b97e4b9545cf6ea6ea69c05d7d6a7edfd80631c2018b71ca214f9b2986>" %}

**18 March 2022**

* Burn feature updated.
* Transfer feature updated.

**16 March 2023**

* Custom Token infrastructure launched.

{% content-ref url="/pages/guLaEDdWvWWXfs7aLXmG" %}
[SZ Tokens (NEW!)](/myagents.plus/myagents.plus/tokens-or-blockchain/sz-tokens-new.md)
{% endcontent-ref %}

**7 Mar 2023**

* Full v7 Release Target.

**21 Feb 2023**

* (v7 parallel build confirmed)

**01 Dec 2022**

* (v2.0.0)

**06 June 2022**

* (v1.0.0)
* Initial scaffold completed.

## The Core Project Scaffold

* 100% in-house built and custom-coded from scratch.
* Included transactions in core blocks of the chain.
* Created a Transaction Pool for a real-time list of incoming data.
* Signed Transactions with cryptography and digital signature.
* Implemented a proof-of-work algorithm.
* Created a real-time connected peer-to-peer (p2p) server with a pub/sub implementation.
* Created an API around the Blockchain.
* Deployed app to production (with multiple servers).
* Created a full frontend web app.
* Built a Blockchain that's fully OOP-compliant.
* Wrote a full test suite for the backend & deployed.
* The entire codebase is fully test-driven.
* Designed, coded & built a full-on backend.&#x20;

{% content-ref url="/pages/MCDaqi1DE3ttkWhgg8vo" %}
[SZ Airdrops (NEW!)](/myagents.plus/myagents.plus/tokens-or-blockchain/sz-tokens-new/sz-airdrops-new.md)
{% endcontent-ref %}

{% content-ref url="/pages/Lns2ePOqn77UVOzNgfVY" %}
[Blockchain/Web3 (dev)](/myagents.plus/product-development/development/blockchain-web3-dev.md)
{% endcontent-ref %}

{% content-ref url="/pages/tNRwBUKQSfmpRdvEWqrc" %}
[Tokens | Blockchain](/myagents.plus/myagents.plus/tokens-or-blockchain.md)
{% endcontent-ref %}

{% content-ref url="/pages/guLaEDdWvWWXfs7aLXmG" %}
[SZ Tokens (NEW!)](/myagents.plus/myagents.plus/tokens-or-blockchain/sz-tokens-new.md)
{% endcontent-ref %}

{% content-ref url="/pages/LpAEXWpX5c9Be5DbjoVH" %}
[SZ Invest Portal B (ICO/ITO)](/myagents.plus/myagents.plus/tokens-or-blockchain/sz-tokens-new/sz-invest-portal-b-ico-ito.md)
{% endcontent-ref %}


---

# 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://nexas-ridewiz.gitbook.io/myagents.plus/product-development/changelog/blockchain-web3-changelog.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.