> For the complete documentation index, see [llms.txt](https://docs.itheum.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itheum.io/product-docs/pre-aithra/pre-aithra-developers/release-notes/data-marshal-network.md). # Data Marshal Network As we test and ship devnet versions to mainnet, the release version notes appear below. You may see .patch versions appear and not rounded versions. i.e. V3.4.3 and not V3.4.0, this just means that there were patches on devnet that were added to a base version target before shipping to mainnet/production. ## V3.12.2 (Brontes) **Main Features / Changes** **This release has a lot of smaller changes, and one big one... namely the following** * Big Update: caching support for data streams if requested, powered by redis * Enable Data NFT-PH types to work, if the min required fields are on top level OR inside the nested attributes level * Better Solana cNFT handling and usage reporting to reporting plugin **Bug Fixing / Other Updates** * MVX RPC comes from ENV so we can update as needed * Better error reporting to Sentry plugin to reduce the "false negative" and "noise" *** {% hint style="info" %} 3.13 release noted above cover the key updates since last update. Also please note that moving forward, only the Brontes node will be supported and the older Achilles node will be decommissioned as it's no longer used by network participants. {% endhint %} *** ## V3.10.0 (Brontes) **Main Features / Changes** * Proof of concept for optional data stream caching (not finalized) **Bug Fixing / Other Updates** * N/A *** ## V3.7.0 (Brontes) **Main Features / Changes** * Data NFT watermarking now supports Solana address as "creator" **Bug Fixing / Other Updates** * N/A *** ## V3.6.0 (Brontes) **Main Features / Changes** * Solana Support! Compresses Data NFT support has been added so the Marshal nodes can no broker data on the Solana chain. **Bug Fixing / Other Updates** * Improvement for how Sentry reports errors and other fixes *** ## V3.4.3 (Brontes) **Main Features / Changes** * Support for ipfs\:// and ipns\:// data stream URLs. Swap IPNS and IPFS base links hashes through a default gateway for fast live streaming of the data. * Add a timeout for uptime checks so it resolves with better UX on frontends. * When it sees the nestedIdxToStream param, it defaults to Nested Streams. This is helpful if a data stream is on IPFS or IPNS and can't set the response headers. But this is ONLY partial nested stream support as the primary manifest is fully viewable not protected with the nested stream rules. See next point for the "right" way to enable nested streams via a URL param: * We also support full nested stream workflow by using a question string param that can be added instead of a header. This query string is dmf-nestedstream=1. [Read more](https://docs.itheum.io/product-docs/developers/software-development-kits-sdks/data-nft-sdk/guide-3-using-nested-streams-to-access-nested-data-assets-from-a-primary-data-stream#step-1-configure-data-stream-origin-backend-for-nested-streams) * Support for Data NFT-PH is here! [See guide](https://docs.itheum.io/product-docs/developers/software-development-kits-sdks/data-marshal-network-sdk/guide-1-make-your-regular-nft-collection-to-be-data-nft-ph-compatible) **Bug Fixing / Other Updates** * MAJOR: Fixed header forwarding issue that broke MultiversX Native Auth protected data stream on mainnet/production. * Add a timeout for uptime checks so it resolves with better UX on frontends. *** ## V3.3.0 (Brontes) **Main Features / Changes** * Deputy / Deputy Appointer Feature, * 10 origins allowed for NativeAuth token **Bug Fixing / Other Updates** * Nested Stream fix for forwardAllHeaders * Sentry only in Prd and send all exceptions to sentry --- # 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.itheum.io/product-docs/pre-aithra/pre-aithra-developers/release-notes/data-marshal-network.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.