Secret was successfully upgraded with the Shockwave Omega update!

Update the Gas expectations
Please adjust the gas costs in your UIs so that they reflect the most recent decrease in prices. Especially Txs that call multiple contracts at once will get a lot cheaper.

SecretJS v1.5 is awesome, use it!
Secret JS v1.5 is Tons faster as it uses Grpc gateways and also has new tools included like cross IBC TX checking and more.

For an example of porting your code check: https://github.com/chainapsis/keplr-wallet/pull/597

The library is also available for REACT : https://www.npmjs.com/package/secretjs - Example Repo https://github.com/scrtlabs/react-native-secretjs

Happy Developing!

Secret is hiring for a technical writer and developer relations role.

If you are interested please apply here: https://secretjobs.niceboard.co/job/794012-technical-writer-devrel-secret-agency

If you have questions please DM @ Ertemann on Telegram

Dear Application/Ecosystem developers and teams,

Package/Deprecation REMINDERS

1. The last update has lowered the Gas costs for smart contract interactions significantly. If you havent yet please consider updating the GAS settings in your front-end so that the reduced costs are actionable for users on your UI

2. Secret JS v1.6 is available and is Tons faster as it uses Grpc-gateways (Over LCD). It also brings new tools for improved UX like cross IBC TX checking and more verbose TX error messages.

For an example of porting your code check: https://github.com/chainapsis/keplr-wallet/pull/597 or https://github.com/scrtlabs/wrap.scrt.network/commit/7a2c14a98ec4073c13f1b2d7995c9204a419b1b2

The library is also available for REACT : https://www.npmjs.com/package/secretjs - Example Repo https://github.com/scrtlabs/react-native-secretjs

Testnet and Mainnet upgrade Announcement

The Secret Network Pulsar-2 testnet will upgrade at Tuesday Jan 24th at 3PM UTC - A Mainnet date is still TBD but will be shortly after if testing is succesfull.

The upgrade will bring Seed Rotation to ensure better privacy protection. A localSecret version is available at: https://github.com/scrtlabs/LocalSecret/pkgs/container/localsecret/64153543?tag=v1.7.0-beta.2

- This upgrade WILL have breaking changes impacting Secret.JS!! For secret.js you will have to use: "1.7.1-beta.0"

Beyond that work continues to bring several features over the coming months including Bridge migration to Axelar, Gramine/DCAP (Intel Machine Upgrade), Iterators and Contract upgradeabillity.

Ending Notes:

A. The Secret2.0 Feedback period is ending with a signalling proposal coming to the chain very soon, if you are interested in the tokenomics and want to share your opinion please check out: https://discord.com/channels/360051864110235648/788435027356549220/1059507774729507036

*B. We have a role/channel on the Secret Network Discord (chat.scrt.network) called "Leaders", and every Monday at 3pm UTC we hold a meeting on there where we discuss Secret Network news and priorities. If you dont have access yet please ping @Ertemann or @cryptocurnc and join to stay up to date.

C. If you are looking for talent to improve your team, consider posting your jobs on: https://secretjobs.niceboard.co/

D. If you are looking for Enterprise API infrastructure - Secret is now Supported by ANKR: https://twitter.com/SecretNetwork/status/1615725547014717440
The community has also provided an API, for information on how to use these public endpoints visit: https://docs.scrt.network/secret-network-documentation/development/connecting-to-the-network


We hope this information helps, if there are any questions please dont hesitate to reach out. More details regarding the update schedule and the Changelog will follow.

Hey Developers.

The Pulsar-2 testnet will be retrying the failed update of last week to V1.7 in about 15-minutes. https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.7.0-rc.2

The network will hopefully be down only for a little while after which RPC nodes and other services should be coming back online.

If there are complications we will inform you.

Please be reminded that the only stable releases of Secret.JS post upgrade are:
v1.5.x, v1.6.x -> v1.7.1-beta.2 (Recommended)
v1.4.x -> v1.4.6
v0.17.8 - can still be used

We also announce these updates in the Dev-updates channel in discord (chat.scrt.network)

The Testnet is back up and running, the consensus seed has rotated successfully.

A time for the mainnet upgrade will be set soon.

Hey 👋
Archive nodes are back https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.2.0-archive
(updated docs) https://docs.scrt.network/secret-network-documentation/node-runners/archive-nodes

Quoting the docs:
You will need to use the designated archive-node binaries (https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.2.0-archive) when available. For the rest of the upgrades, use the binaries for the respective version from the releases page (https://github.com/scrtlabs/SecretNetwork/releases).

Secret Network 1.7 Release Notes

Target Date - 01/03/2023 (1st of March)

New Features

- Added the ability to rotate consensus seed during a network upgrade - this will be executed during this update
- Added expedited gov proposals - this allows for special proposals that can be voted on in 24 hours for emergencies
- Added auto-restaking - this is a feature that enables automatic compounding of staking rewards
- Added light-client validation for blocks - this protects against forking attacks, as well as enables trusted block heights and block time to be relied on by contracts

Bug Fixes

- Fixed OSX Ledger disconnection issues in secretcli
- Fixed /cosmos/base/node/v1beta1/config
- Fixed an issue when sending multiple message types in the same tx
- Fixed an issue with the IBC controller module

Breaking Changes

Mandatory secret.js update (non-API breaking)

The tx encryption key format has changed, requiring an update of secret.js. After the upgrade goes live, secret.js will require an update to one of the following versions to continue to function:

v1.5.x, v1.6.x -> v1.7.x
v1.4.x -> v1.4.6
v0.17.8 - can still be used

This update should be a simple version bump that will not change any existing APIs, and will not break functionality.
In order to test this version, secret.js 1.7.1-beta3 is available for testing on Pulsar-2, which is already on the 1.7 update.

Side note: This update will not affect Keplr

Other

- Ubuntu 18.04 is no longer supported in this version. Please update to Ubuntu 20.04 or 22.04 for continued support
- To ensure a smooth upgrade process, please verify that all nodes are running on patched and updated hardware prior to the upgrade. To do so, please use the check-hw tool found here: https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.6.1

Testnet was halted/down for ~12 hours overnight due to a massive block that crashed almost all nodes.

Restart worked and Pulsar-2 is back up but will take some time before all services included API and explorer are back up again.

Some more context:
https://vxtwitter.com/assafmo/status/1639942236791095297

Sorry for the inconvenience, you can get testing again soon 😁

-- This message goes out to all Secret dApps and developer announcer channels --

Mainnet and Testnet upgrade - IBC v4 + SecretVRF

Timeline
Code freeze -- 02/05/2023
Testnet upgrade to V1.9 -- 02/05/2023
Mainnet upgrade to v1.9 -- 16/05/2023

Summary:
This upgrade will bring native private randomness to the Secret Network. The verifiable random function has a random item for every block which negated multiple attacks previously possible with contract based randomness. The VRF function is free to use and can be used cross-IBC in for example lotteries, gaming, secure authentication and more. Additionally a "FinalizeTX" call is added which allows contracts to force TXs to finalize at a certain point. This negated rollbacks, sandwhich attacks which apply for ex to Game of chance outcomes.

Documentation for this feature: https://docs.scrt.network/secret-network-documentation/development/development-concepts/secret-vrf-on-chain-randomness

Additionally the upgrade brings an array of additional IBC solutions including the Packet-forward-middleware (thank you Strangelove!), IBC fee middleware, IBC-go V4 (interchain account host module and other features) and an IBC panic button to freeze transfers in case of emergency. The packet-forward-middleware will allow easier routing of Tokens from, to and through secret improving the UX for users and simplify front-end design for IBC applications (EX: https://twitter.com/assafmo/status/1646472957106028544).

The IBC fee middleware will allow relayers to start prioritising IBC transactions based on an additional fee set for relayers, this brings back fees to relayers which is now merely a common good. IBC-go v4 brings ICA host-modules allowing DAOs, defi vaults and more to host accounts from a secret Contracts on another Cosmos chain and interact with contracts there. Lastly the IBC-panic button is a start in securing IBC for secret further as we rely on it more and more. Exact implementation details will come in a forum post coming week.

Changelog: https://github.com/scrtlabs/SecretNetwork/blob/master/CHANGELOG.md

implementation details
This upgrade will not have breaking changes to Secret.js or other packages, both testnet and mainnet dApps should see little impact on their service.

It is however advised to start with altering front-ends to allow for IBC fees and Middleware and Alter applications with required randomness to use the renewed SecretVRF function.

For ICA account implementations documentation is still lacking, please refer to these awesome examples by Quasar finance to learn more: https://github.com/quasar-finance/interchain-accounts-demo . if as a dApp you require these specific IBC channels on main or testnet then please reach out to @Ertemann!

-- End of update --

For additional questions please reach out to @ertemann or @cryptocurnc

Hey Developers

Sorry for the late notice but please be aware that Pulsar-2 will be upgraded in ~1 hour to the same version as the current mainnet. This upgrade includes the patches made during the 1.9 upgrade process on mainnet that took over 12 hours to complete and will bring Pulsar-2 back to the same binary as mainnet.

Additionally I would like to mention that SCRT labs and the Testnet committee are looking into Deprecating Pulsar-2 in favour of Pulsar-3. Pulsar-3 will be a more close copy of the current mainnet including the various modules so that errors in upgrades can actually be caught by pushing them to testnet first (unlike the breaking bugs that happened during the V1.9 upgrade).

A final timeline for Pulsar-3 has not yet been set as we are gathering feedback from dApps on the best launch date and Pulsar-2 deprecation.

If you have any feedback on the upcoming Pulsar-3 testing suite please contact me or @Taariq

Dear dApp developer,

This announcement covers the upcoming feature contract upgradeabillity and the upcoming testnet change pulsar-3.

1. Pulsar-3
After much consideration SCRT Labs deems pulsar-2 insufficient to properly test upgrades due to the many differences it has with the Secret-4 mainnet. These differences were one of the causes for the hardships during the last upgrade and preventing this into the future is of paramount importance.

Because of this SCRT Labs proposes to sunset pulsar-2 in favour of a new testnet pulsar-3. Preferably this around the beginning giving us 1 month to collect timelines and feedback from dApp developers.

What we want from you:
Please let us know your timelines for testing on pulsar-2 and if there are important testing dates that can not be moved or altered. We plan to only deprecate pulsar-2 and migrate fully when teams are ready to migrate as well.

The new testnet will be supported by the same committee providing API endpoints and maintenance. If you have more questions about this upcoming change please let us know.

2. Contract upgradeability

As explained in https://forum.scrt.network/t/feedback-for-contract-upgradeability-design/6643/29 Secret contracts will become upgradeable soon (v1.10 or v1.11 probably) - this is only for new contracts. We however want to provide the same functionality for older contracts with the method described in the forums.

If you want your old contracts to become upgradeable please file this form: https://forms.monday.com/forms/6ef9177487f3bee0e1680e3df6c018f2?r=use1

If you have any questions or want to deliver a complete/long list of contracts instead then let me know.

Please be reminded that this will be a one time thing, old contracts can only become upgradeable during this upgrade.

Best regards
Secret network development team

Pulsar-3, migrateabillity and Roadmap Announcement

1. Pulsar-3 is NOW live! - Please migrate your testing suites before end of july using: https://docs.scrt.network/secret-network-documentation/development/resources-api-contract-addresses/connecting-to-the-network/testnet-pulsar-3

2. Contract Migrateabillity Implementation is completed and expected in the upcoming upgrade.
- If you want your older contracts to become upgradeable please provide the required information using this form: https://forms.monday.com/forms/6ef9177487f3bee0e1680e3df6c018f2?r=use1

More info on the feature can be found on the forum: https://forum.scrt.network/t/an-update-on-the-contract-upgrade-feature/7012

3. IBC hooks implementation for Secret has been finalised and will go live next upgrade. Can be leveraged for corss-chain dApps or improved UX leveraging SNIP-20 autowrapping. More info: https://twitter.com/assafmo/status/1682101114320343040

------
Upgrade containing migrateabillity and Hooks is expected before end of October at the latest - Final date to be determined.
-------

4. Core Roadmap for rest of the year / q1 2024
- Hardening SGX leveraging in-enclave Light client and Merkle proofs. Will improve Input data verification further to prevent offline and replay attacks and allow for less centralized form of Consensus seed re-generation. This also ties into a potential switch to Mr.enclave for decentralized Enclave seed sealing.
- Additional PAAS Apis - Hardned private voting is expected as the first Demo to land leveraging the newly added Additive HME
- Secret Tunne/bridge Asset migration - Deprecation of the old bridge is to be expected before end of October including renewed issuance of wSCRT via Axelar
- DCAP attestation - full support of the newer generation Intel CPUs and addition to attestation service.
- Iterator support for Secret CosmWasm contracts - More complicated than originally intended but effort is ongoing
- Threshold cryptography for Secret validators - Secret 2.0 research for improved consensus seed regeneration and MPC key sharding of the network encryption key amongst the validator set.

Want to learn a bit more about whats going on at SCRT labs? feel free to listen to Guys latest talks at Prague (https://www.youtube.com/watch?v=vFhjn6TcVJc) or later today at Nebular summit in Paris at 13:30 UTC (https://www.youtube.com/watch?v=8d9ERiS9JcM)

Secret Network V1.10 Preliminary upgrade timeline

Testnet (pulsar-3) planned for: August 29th
Mainnet (secret-4) planned for: September 12th

Upgrade contains:
1. Contract upgradeabillity
2. IBC Hooks

Full changelog: https://github.com/scrtlabs/SecretNetwork/blob/master/CHANGELOG.md

- Pulsar-3 is now supported by Leap, Fina, Keplr and Starshell. Pulsar-2 is still supported by Keplr via the add experimental chain feature. Keplr support will be hardcoded ~20th of august after which pulsar-2 will be deprecated before the V1.10 testnet upgrade.

Expedited upgrade - SGX patch enforcement

Dear teams/developers,

Please be aware that the Secret mainnet (Secret-4) will be performing an expedited upgrade (https://www.mintscan.io/secret/proposals/264) today (August 14th) at ~1700 PM UTC to combat the downfall SGX vulnerabilities. The upgrade will re-enable Node registrations and kickoff a 1 week grace period for node runners to update to the latest patches. After a week unpatched platforms will no longer be able to register or restart their node.

You can track the upgrade time here: https://www.mintscan.io/secret/blocks/%2010186400

Please Expect the network to be halted for ~15-30 minutes and a delayed restart of all public API services and Wallets.

If any questions remain please feel free to contact us!

V1.11 Secret Network Update.

After a small unexpected delay the testnet Pulsar-3 is now upgraded to v1.11 and has contract upgradeabillity and IBC hooks live.

Please expect the mainnet (Secret-4) upgrade for Secret to V1.11 on September 26th

Please find the full changelog here: https://github.com/scrtlabs/SecretNetwork/blob/master/CHANGELOG.md

We welcome everyone to test out the migrateabillity feature. There will likely be another hardcoded-admin upgrade coming to Pulsar-3 to make sure that feature completely works as intended.
Tutorial: https://docs.scrt.network/secret-network-documentation/development/development-concepts/contract-migration

Please read up on the state of Code-hash usage following the migrateability update and make sure your front-ends and other smart-contracts remain compatible!
https://forum.scrt.network/t/an-update-on-the-contract-upgrade-feature/7012

The first partnerships with IBC hooks (Axelar GMP and Andromeda) are closing in. Also the UX of wrapping Secret tokens will become significantly easier.
Want to try out Hooking - ;) - in to Secret network Liquidity and functionality? Find your tutorial here: https://docs.scrt.network/secret-network-documentation/development/development-concepts/ibc/ibc-hooks

Hey everyone,

There seems to be an issue with a testnet patch that was executed yesterday to test contract upgradeabillity a 2nd time.

As far as we can tell for now it seems all contracts uploaded pre-patch can NOT be interacted with at the moment.

Simply re-uploading your contracts should for now allow you to keep testing.

As its weekend and also an Israeli holiday I expect it will take atleast another day before the full issue is found and patched.

Whether this impacts the mainnet is unknown for now as the core team hasnt dived deeper yet. Might very well not be as this patch is not included in the mainnet v1.11 binary.

More info to follow.

Hey everyone,

please be aware that following some bugs in the hardcoded upgradeabillity patch included in v1.11 this functionality did not work as expected. Because of this an upgrade to v1.12 will be proposed on-chain shortly to fix this issue.

This upgrade will also add the hardcoded admins from proposal 269 and 270 and fix a bug in the PFM for IBC contracts.

The upgrade is expected on October 17th with the testnet (pulsar-3) upgrading today at 2:30 pm UTC.

changelog - https://github.com/scrtlabs/SecretNetwork/blob/master/CHANGELOG.md

-- Additionally:

SCRT labs is seeking feedback for a proposed migration to MRenclave signing and thereby increased upgrade transparancy and reduced trust assumptions. Please leave a note on the forum post with any questions or feedback on the proposed design!

https://forum.scrt.network/t/request-for-feedback-migrating-from-mrsigner-to-mrenclave-sealing/7112