Hi @BANG, thanks for your questions. I can answer the Subnet Rental Canister (SRC) and ICP related questions:
-
The exchange rate for these 820 TC/day is fixed by the time the proposal was created. When the proposal was created, that meant 41075.50372445 ICP. This means that over the course of 6 months, all of these ICP will be burnt.
-
If an error happens during proposal execution, that will lead to a failed proposal execution. It would require to recreate the proposal. However, given that we use unbounded calls to the external canisters involved here (without a timeout), the responses are essentially guaranteed. The same holds for the future conversions, and there we will retry every day and check if there are ICP to be converted.
-
This will be changed to a push-based mechanism where the NNS would notify the SRC on subnet creation. We will implement this until there is a proposal out to form the swiss subnet on the node level.
-
The nodes used for the Swiss subnet will have the same requirements as all other nodes on the ICP, so the same risks apply as for other nodes.
-
Note that the SRC runs on the NNS subnet, not on the swiss subnet, to avoid these concerns.
-
These are only logs from the SRC itself, not for canisters on the swiss subnet. GDPR/FADP compliance needs to be ensured by the individual apps running on the swiss subnet.
-
We run this job every day, but only every 30 days a customer is “billed”. Together with the monitoring solutions we can timely react if something continues to go wrong.
-
This would be a question for the @Swiss_Subnet team, what I can say is that this is independent of the SRC.
-
For @Swiss_Subnet
-
Again for @Swiss_Subnet. Regarding ICP demand; since the subnet is payed for in ICP, which will be burnt, this is one natural way to decrease ICP supply.