Question about SEV-enabled production subnets

Developers
1

Pierre Samaties recently mentioned that there are already two SEV-enabled production subnets live.

I’m curious to learn more about them.

Which production subnets are currently running with SEV?

Are these publicly identifiable by subnet ID?

Can developers target or discover them?

Is the long-term vision for SEV/TEE to become the default for production subnets over time, or will only selected subnets use confidential computing?

I think this would be valuable information for developers building applications that rely on confidential computing and secrets management.

https://x.com/PierreSamaties/status/2079136324783645163?s=20

2

The statement is correct there are 2. The easiest way to check is to open the Dashboard and you can identify SEV enabled subnet re2t4 as it shows the TYPE Confidential. This is the 1st and currently only one open to public, the second one x4jtx is currently used for testing MultiDEX and it will be opened up later down the road.

3

Can one pay extra and get the public SEV subnet, how?

Joseph Hurtado
Building Satoshi Notes

4

You mean to rent a full subnet ? It is not yet available for Cloud Engines but it is comng soon.
Using the current public one does not require any extra payment.

5

No, I meant to deploy a canister, or several to an SEV enabled subnet so that it has additional security features.

6

Again it is free to deploy on the public one. Go ahead test it, deploy as many as you like.

7

You can deploy to: re2t4-faa75-v3vhk-kdmdr-uyrkl-aik2l-ixd6u-p3fyr-zlfkc-6c5af-zae.

icp deploy -e ic --subnet re2t4-faa75-v3vhk-kdmdr-uyrkl-aik2l-ixd6u-p3fyr-zlfkc-6c5af-zae
8

He is just spamming without reading stuff, he liked the post above as answer that clearly stated the re2t4 subnet, and he is familiar with using the --subnet flag with icp deploy. Did the same nonsense on couple of other post to so it’s all good :wink: