# Acki Nacki News ### Update - 29.05.26 #### Node & Network & SDK TVM-SDK 3.0.0 with new addressing scheme is coming. All the applications MUST migrate to it before StateV2 release. #### Bridge End-to-end positive deposit/withdraw scenarios testing is ongoing. The audit excludes BK set update proof verification, as Shellnet currently does not perform BK set updates. User documentation for transfers from the test EVM network to Shellnet is also in preparation. Stay tuned for upcoming announcements! #### DEX.DO * Added account balance APIs covering both collateral and per-market outcome tokens. * Exposed maker and taker commission rates on the markets endpoint. * Published the OpenAPI specification. * Released POST `/api/v1/buyFullSet` for buying a full set of outcome tokens with collateral; \ the matching sellFullSet and claim endpoints are specified and will follow. An open-source release of the DEX.DO stack - including halo2 libraries, the indexer, API, and exchange integration libraries - is coming. Stay tuned. 🚀 #### Documentation A new [Synchronization and Consensus Mechanism](https://docs.ackinacki.com/synchronization-and-consensus-mechanism) section was added. It explains how Acki Nacki reaches consensus on block order and validation, including finalization and error handling. #### Support Support requests were simplified and now go through a single bot: [@ackinackisupport\_bot](https://t.me/ackinackisupport_bot). A questionnaire and screenshot upload option were added. Bot links are available in all official chats, and requests are reviewed daily. We established a new automated process of collecting feedback from the community across all chat channels for further discussion and follow-up with the core team. ## Update - 22.05.26 ### Node & Network After the Durable State release, the network team identified a bug in external message processing. Patch releases [`v0.16.1`](https://github.com/ackinacki/ackinacki/releases/tag/v0.16.1) and [`v0.16.2`](https://github.com/ackinacki/ackinacki/releases/tag/v0.16.2) were prepared and have already been rolled out to the network. Work on State V2 is currently in progress. {% hint style="danger" %} **Attention!!!!!** Account addressing in State V2 will use the DApp ID + address format. At the moment, all applications are still using the old addressing scheme. We are planning to prepare a migration guide for applications to support the transition. The SDK with new account addressing support is already available (latest version: [v2.24.21](https://github.com/tvmlabs/tvm-sdk/releases/tag/v2.24.21.an)) {% endhint %} ### API Access Degraded public API performance over the last 1.5 week was caused by increased miner bot activity. These bots abused public infrastructure from a set of IP addresses. To prevent this load from affecting other network users, the rate limit policy for public endpoints was tightened. API request optimizations were also made to improve response speed. Miner applications may acquire a Block Manager license to avoid these limits. There will be an additional post on this topic the next week. **The internal network economy is evolving, and that is great to see!** ### Bridge Changes made to the TokenBridge event circuit based on the results of the Pruvendo audit. Decision was made to replace `vergrth16WithVK` instruction with `ZKHALO2VERIFYWITHVK` - this will simplify the integration a lot. ### DODEX Dodex development focused on the Market Maker API and Shellnet testing tools. Added Cancel Order API, all orders API (including cancelled, rejected and fulfilled orders), and batched API support. Prepared the first version of scripts for producing artificial load for end-to-end API testing on Shellnet. Maker and Taker commission supported in DODEX core smart contracts. ### Wallet A wallet release with support for the new DAPP ID + Account ID addressing format is planned in the near future. Please follow upcoming announcements.\ After the State V2 release, the old addressing format will no longer be supported.\ We will keep you updated. ### Documentation & Developer Experience A separate documentation page was added for receiving test tokens on Shellnet: [Get test tokens from giver in Shellnet](https://dev.ackinacki.com/readme/get-test-tokens-from-giver-in-shellnet). ## Update - 15.05.26 ### Node & Network * Durable State was released in [`v0.16.0`](https://github.com/ackinacki/ackinacki/releases/tag/v0.16.0). Network providers are coordinating the update to keep the transition aligned across the network. ### Bridge On the bridge side, we continue building the infrastructure for ZKP-proof verification and safe asset movement between EVM and Acki Nacki. * The SDK now includes the `vergrth16WithVK` instruction for proving an EVM-to-Acki Nacki transfer proof on the Acki Nacki side. The instruction is not included in a public release yet. The next step in this direction is integrating `vergrth16WithVK` instruction into the Acki Nacki bridge and testing the full deposit to Acki Nacki scenario. * The `Exchange` contract was renamed to `TokenBridge` and withdrawal bridge interface was added to `TokenBridge`: it will allow initiating USDC withdrawals to the EVM network with event generation for a later ZKP-proof on the EVM side. The withdrawal bridge interface is currently under audit by the Pruvendo team. These changes are in Shellnet only, not in Mainnet. * The circuit for layer hash movement, which proves that a block belongs to network history, was tested in an EVM test network. Based on the test results, the node-side logic for storing hash movement data needs additional refinement. {% hint style="info" %} There are no `Mainnet` changes yet: integration testing is running on `Shellnet` {% endhint %} ### DODEX For Dodex, we are continuing to develop the API and contract layer * The orderbook API is complete. * The first synchronous version of the API for order creation and cancellation has been prepared. But, based on market maker scenarios, we decided to move the order creation and cancellation API to an asynchronous model to make placing large numbers of orders easier. This is a WIP. * The API for fetching a market maker's open orders is in progress. * Contract fixes were made based on new test results. ### Wallet In wallet, we continue improving the user experience and adding developer tools. * In the coming release `Dev setting` page is added * When developer mode is enabled, * the Multifactor contract address, its `DAPP ID`, and the network switcher become visible. * users can see an option to send SHELL to a precomputed contract address for a future deployment; this option is hidden in the regular mode. * The release is already available as an APK. App Store publication is coming, and Google Play publication will be later. * Transaction history and SHELL sell order history display were fixed: the data no longer disappears in the scenarios reported by a user. * Fixed an Android login issue for test wallets on `Shellnet`. ### Popits We are preparing Popits 3.0 for the new boosts season. In the new season, users will be able to create AI tracks as Popits and receive boosts for them. We are also preparing a NACKL mining scenario while listening to tracks from the bucket feed or minted Popcoins. ### Documentation & Developer Experience * A new developer documentation section on cryptography, mnemonic phrases, and keys was added: [Mnemonics and Keys](https://dev.ackinacki.com/cryptography/mnemonics-and-keys). * A prominent [SHELL purchase](https://docs.ackinacki.com/for-users/buy-sell-shell) button was added to the [developer portal documentation](https://dev.ackinacki.com/) so users can find the token purchase flow more easily Thanks to everyone who asks questions, reports issues, and helps make Acki Nacki clearer and more convenient for the community. ## Update - 08.05.26 This week, the team made progress across several Acki Nacki workstreams: ecosystem integrations, DEX infrastructure, Bridge, SDK, and documentation. ### Ecosystem A PR has been opened to register Acki Nacki in the SLIP-0044 registry under number `1331`. This is an important step toward deeper integration with wallet infrastructure and ecosystem tools. \ Support our PR :rocket: [satoshilabs/slips#2016](https://github.com/satoshilabs/slips/pull/2016) ### State Durable state (3/4) is in the final testing phase. ### Bridge This week, the Bridge team focused on reliable verification of Acki Nacki data from the EVM infrastructure side. * The circuit for proving attestations in Acki Nacki block on the EVM network side has been successfully tested in an EVM testnet. * Integration and testing are underway for the circuit that proves Layer Hashes movement. This mechanism confirms that a block belongs to the Acki Nacki network history. ### Dodex Dodex continues to expand the infrastructure needed by market makers and applications to work with the DEX effectively. #### Completed * Finalized the DEX API specification for market makers and web applications. * Prepared a library for writing to the Orderbook, including order creation and cancellation. * Implemented an API for retrieving the list of Prediction Markets. #### In progress * Orderbook read API * Orderbook write API for market makers. ### Documentation In parallel, we continue improving the documentation so users, developers, and partners can better understand the ecosystem and complete key flows faster. * Published a detailed overview of the network architecture and participant roles: \ [Network Architecture and Participants](https://docs.ackinacki.com/network-architecture-and-participants). * Updated the documentation for buying SHELL tokens to reflect the simplified user flow in [shellbuy.ackinax.com](https://shellbuy.ackinax.com): \ [Purchase with crypto or card](https://docs.ackinacki.com/for-users/buy-sell-shell/buying-shell/purchase-with-crypto-or-card-credit-debit). * Clarified the steps for obtaining `app_dapp_id` in the Bee Engine SDK integration documentation: \ [Bee Engine SDK Integration Documentation](https://dev.ackinacki.com/bee-engine/bee-engine-sdk-integration-documentation). Thank you to everyone following Acki Nacki's progress, supporting the team's initiatives, and helping move the ecosystem forward. --- # Agent Instructions: 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: ``` GET https://docs.ackinacki.com/acki-nacki-news.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.