With the BTC Integration just two weeks away, I'm curious if any user has thought about the implications of such an event. All node providers have the capacity to view the contents of their nodes, isn't that a huge attack vector for any BTC stored in 'cryptographically' secured canisters? And what if they shut down a canister? Surely they can't release the btc integration with such a huge design flaw in the midst.
Genuine Concern with ICP
Other urls found in this thread:
Nobody will use that shit anyway
>icy pee
test
>All node providers have the capacity to view the contents of their nodes
this is some of your best yet
It's not even FUD, it's genuine concern. The nodes CAN do that. Just like AWS CAN shut down your canister if they want to. Reminds me of Pic related where disinfo just gets thrown around. Like ICP could avoid all firewalls is fucking stupid, but anons bought that because hey look it's a schizo image, good enough research for me
AWS CAN shutdown whatever you are hosting*
Keys are distributed amongst many nodes afaik. And they’re actively working on encrypting the nodes too
>in two weeks
actually, it’s 2 more weeks. trust the plan
soon
trust the plan
So if data centers collude when BTC integration goes live they can steal?
your reasoning is that because node operators can see what they're hosting (because it's not encrypted yet) that your bitcoin is somehow endangered? what's the logic here? you think they can grab a canister with their hand and empty the bitcoin inside of it into their physical wallet or something?
Where is the BTC wallets data hosted at when they inevitably wrap the BTC, where is the BTC that gets handled by Smart Contracts going to go besides another BTC wallet, and where would the credentials for this be hosted?
Bloody Basterd! Fuck You. Madarchode. Ok Sir? Good Morning in Hell.
The BTC is always in the BTC blockchain. What ICP canisters will be able to do soon is sign transactions into the BTC blockchain, for this they need a private key, and this is how the private key is generated:
>The solution is to have private keys secretly shared among all node machines (replicas) of a large subnet and create the signature through threshold cryptography. That is, if a threshold of the nodes participates in and completes the signing protocol correctly, the output of this protocol is a valid signature. However, a few nodes that do not meet the threshold cannot sign an unauthorized message themselves.
so no, the fact that hosted content is visible to node operators doesn't change anything, they don't have a private key stored in their canister that they can see.
> With the BTC Integration just two weeks away
It’s been 2 weeks away for 2 months now
Node shuffling. Go read the dev forums
yeah great ideas, we can all say great ideas, but where is it? 2 more weeks away. Always and forever
how can aws shut down your canister? from what i read they can't affect shit.