Welcome to this discussion thread. Feel free to ask questions or discuss things related to this section.
I have a question regarding Sybil attacks. @ivan, you mentioned in your video at 1:30 that someone could surround a node. But can someone choose which node they are connecting with? If so, can a node choose how many neighboring nodes it connects to?
Thanks in advance for the additional info!
I wanted to bump my previous question and I also have an additional question:
For Segmentation, you mentioned that whenever that segmentation/barrier goes down, the group that was cut-off will have their blockchain replaced by the outside blockchain.
That being said, we’ve learned in your other courses that “the longest chain wins”. So what happens in a case where a small group of nodes happens to mine blocks at a slightly faster rate than the outside chain? In the case of Segmentation, if the group that’s cut off from the internet maintains a chain that’s slightly longer (due to decreased difficulty and some luck), why would this chain not replace the outside “global” chain?
Edit: The 51% attack video addressed my question above by explaining that you’d need 30-51% of the hashpower to be able to create a longer chain. This makes sense given that network difficulty adjusts every 2016 block (or 2 weeks). By the time it adjusts to this new “fake chain”, the global chain will be much longer and too difficult to catch up to. Even if mining difficulty decreases within this “fake chain” it would only adjust to so that blocks are solved within ~10 minutes on average, so it would never really have the opportunity to catch up to the main chain’s length. Is this the correct response?
Thanks for your insight!
Depends on the Bitcoin daemon sw we are talking about.
Include ‘connect’ and ‘maxconnections’ options to config file or to daemon cli options can be used to control the things you are asking for.
Play with other bitcoin options at: https://jlopp.github.io/bitcoin-core-config-generator/
# Connect only to the specified node(s); can be set multiple times. connect=184.108.40.206 connect=220.127.116.11 connect=18.104.22.168 connect=22.214.171.124 connect=126.96.36.199` # Maintain at most N connections to peers. maxconnections=5
to say “the longest chain wins” is a simplification, “the chain with more work wins” is more like the true statement.
I would expect to find some chapter about generating Bitcoin address and ‘man-in-middle’ attack, or lower or hacked deterministic ‘random-seed’ used in the past at paper-wallet and other online web wallets risks, like example shown in this article: https://www.finder.com.au/did-you-use-walletgenerator-net-you-should-change-your-keys
This hack was fixed meanwhile, but nevertheless it is important to students of this lessons to know that this Bitcoin attack was in place for sometime until someone noticed and warned the ‘public’ about this vulnerability hacked at that ‘legit’ website …
In terms of the ‘Packet Sniffing’ section and the suggestion to use TOR browser to protect from snoopers potentially mapping your IP address to your bitcoin address(es). Wouldn’t a VPN service (that didn’t keep activity logs and with a kill switch to prevent leakage) be equally as good at protecting against such IP to bitcoin address mapping?
Or is there some difference that I’m not seeing?
Hello sir, by using a TOR network, you will add an extra layer of security from snoopers, also if add to that a VPN, you will get another extra layer (so now you have 2 layers of security).
The TOR network will use the network to send your packets through a tunneling system of nodes on that network, also the VPN will add an extra layer since it will “hide” your real address.
Hope this gives you a clear view of the subject, keep learning!
If you have any doubt, please let us know so we can help you!