# Spica Release - rc/v1.8.0 **URL:** \ **Category:** Releases\ **Created:** [August 5, 2024, 7:15pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458 "2024-08-05T19:15:39Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![schimih](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@schimih](https://agora.multiversx.com/u/schimih)\ **Post date:** [August 5, 2024, 7:15pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/1 "2024-08-05T19:15:39Z")
This document explains the contents of the rc/v1.7.next1 release codenamed Spica. It is split in 2 sections: - the **features** list containing detailed insights of the feature along with the external impact and the relevant pull requests list - the **smaller features and fixes** area contains the one-pull request small features or fixes along with the external impact details This documentation is relevant for the `tags/v1.7.16` tag release. # Features ## 1. Relayed v3 [#5741](https://github.com/multiversx/mx-chain-go/pull/5741) Relayed v3 feature brings a cheaper, improved version of relayed transactions, that can hold multiple inner transactions. The inner transactions will be full transactions. Additionally, a fix on the base cost of relayed transactions was implemented, to follow the minimum gas rule. This fix affects all types of relayed transactions. _ **Note:** _ Relayed v1 and v2 will be deprecated and marked for removal once v3 will be fully adopted. The official relayed v3 docs are found [here](https://docs.multiversx.com/developers/relayed-transactions/#relayed-transactions-version-3). ## 2. ESDT improvements [#5821](https://github.com/multiversx/mx-chain-go/pull/5821) The improvements implemented on ESDTs enable the dynamic NFT functionality. ## 3. Crypto API, new Opcodes and EGLD in MultiESDTTransfer [#6139](https://github.com/multiversx/mx-chain-go/pull/6139) With this feature, new opcodes were enabled for developers, among with new crypto VM endpoints(`VerifySecp256r1`, `VerifyBLSSignatureShare`, `VerifyBLSMultiSig`). Additionally, EGLD(native tokens) can be now sent within MultiESDTTransfer (token identifier: EGLD-000000) along with custom tokens. _Note:_ When using native tokens as part of MultiESDTTransfer, transaction value must be 0. ## 4. Refactor persister factory [#6001](https://github.com/multiversx/mx-chain-go/pull/6001) The storage unit package was refactored, adding the option of using static and non-static storers. # Smaller features or fixes can be found here. ---
**Author:** ![schimih](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@schimih](https://agora.multiversx.com/u/schimih)\ **Post date:** [August 5, 2024, 7:15pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/2 "2024-08-05T19:15:44Z")
---
**Author:** ![schimih](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@schimih](https://agora.multiversx.com/u/schimih)\ **Post date:** [August 6, 2024, 6:13pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/3 "2024-08-06T18:13:37Z")
---
**Author:** ![prettyflacko](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@prettyflacko](https://agora.multiversx.com/u/prettyflacko)\ **Post date:** [October 19, 2024, 3:59pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/4 "2024-10-19T15:59:25Z")
Any update on the date of the release? ---
**Author:** ![drmelone](https://dub1.discourse-cdn.com/flex005/user_avatar/agora.multiversx.com/drmelone/32/20_2.png) [@drmelone](https://agora.multiversx.com/u/drmelone)\ **Post date:** [October 19, 2024, 8:11pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/5 "2024-10-19T20:11:39Z")
Yes +1… It’s been almost 3 months… Why even announce it so early when it’s clearly not at all ready. (Since after almost 90 days it’s still not ready)… ---
**Author:** ![robert](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@robert](https://agora.multiversx.com/u/robert)\ **Post date:** [October 21, 2024, 6:51am UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/6 "2024-10-21T06:51:10Z")
Simple. We thought it is ready. We found several bugs. We did penetration testings and found even more. We want to make a statement around this when the release date is set. Even last week we found bugs on relayedV3, sadly. It is really frustrating, especially for us, when we think everything is ready like 99% and than we find some problems and we have to code a lot again. The team is doing non stop overtime. ---
**Author:** ![prettyflacko](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@prettyflacko](https://agora.multiversx.com/u/prettyflacko)\ **Post date:** [October 21, 2024, 3:03pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/7 "2024-10-21T15:03:36Z")
Thank you @robert for the update! Everyone will (AND NEED TO) understand that delays can happen (especially for security reasons, when bugs are being fixed), but we really need more communication around those delays to avoid the community getting frustrated. I really believe people will truely appreciate receiving updates on these important updates every 3 weeks. If I take as an example your latest twitter post from yersterday evening on the progress from Consensus 1.0 to Consensus 3.0, this kind of tweet is SUPER usefull; but I really think it should also be shared by official communication channels (MultiversX twitter account, Agora, Website blogpost, etc.) in a proper way and on a regular basis. You can’t be the only one responsible for sharing this kind of stuff. I also like how @AdrianDobrita also share updates on the work being done on finality improvements but again, these tweets should also be shared by an official communication channel. Anyway, thanks a lot for the amazing work ---
**Author:** ![prettyflacko](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@prettyflacko](https://agora.multiversx.com/u/prettyflacko)\ **Post date:** [October 21, 2024, 3:05pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/8 "2024-10-21T15:05:11Z")
Also, it would be superb if the team could update the [roadmap](https://multiversx.com/roadmap) items being worked on more regularly Last time it was updated on June 26 ---
**Author:** ![janniksam](https://avatars.discourse-cdn.com/v4/letter/j/edb3f5/32.png) [@janniksam](https://agora.multiversx.com/u/janniksam)\ **Post date:** [October 21, 2024, 3:05pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/9 "2024-10-21T15:05:43Z")
This is what I mean with lack of communication. Why haven’t you just given us this feedback whenever these bugs/problems were found? Everyone would have totally understand it and everyone would have just been informed. Regular feedback is important, even feedback that says "“Hey, bad news, we found 2 more bugs, we will have to rewrite a lot of code, this will take a while, we will give you more updates in 2 weeks.”. It’s better than leaving everyone in the dark for months, with nobody knowing what is taking so long. I hope you understand what I mean… ---
**Author:** ![robert](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@robert](https://agora.multiversx.com/u/robert)\ **Post date:** [October 22, 2024, 6:24am UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/10 "2024-10-22T06:24:49Z")
Developers/Core teams posting/writing about progress or bugs is an official channel. All the developers who depend on these features were informed, all whom we are in contact with. Developing L1 is not easy, it is hardcore. ---
**Author:** ![schimih](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@schimih](https://agora.multiversx.com/u/schimih)\ **Post date:** [October 22, 2024, 6:33am UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/11 "2024-10-22T06:33:21Z")
Hey @prettyflacko, Just a heads-up, we update the roadmap every week. You can check it out at [https://multiversx.featurebase.app/roadmap](https://multiversx.featurebase.app/roadmap) and follow the points that are relevant to you. By the end of this week, the website should be fully synced with Featurebase. The June 26 date you mentioned is just a placeholder. If you had been regularly checking Featurebase, you’d notice there are comments, updates, and even estimated timelines (ETAs) for each task. We take all feedback seriously and act accordingly based on what makes sense at the time. For instance, when it comes to security bugs, we don’t make any announcements until the issue is fixed, deployed, and confirmed to no longer be a threat. Otherwise, we risk exposing vulnerabilities to potential attackers. I hope that addresses most of your concerns. Is there any specific feature in SPICA that you’d like to use in your project? Thanks! ---
**Author:** ![prettyflacko](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@prettyflacko](https://agora.multiversx.com/u/prettyflacko)\ **Post date:** [October 22, 2024, 10:05pm UTC](https://agora.multiversx.com/t/spica-release-rc-v1-8-0/458/12 "2024-10-22T22:05:47Z")
Thank you @schimih! I was not aware of this more detailed page with the activity updates and all the comments, this is very informative