Oooh, I see! I'm Moroccan, which is why I was curious Hope you had a great time there

Are you Moroccan?

deal 🤝

thanks @Imyourfed

But this doesn't change the fact that P2PKH isn’t secure against quantum threats as it is today

Yaa but I think breaking hash functions (SHA-256) is fundamentally different from breaking ECC or RSA.

I still have a question that I don't have an answer to: if ECC and RSA could be broken with the advent of quantum computers, what makes hash functions remain secure?

For context: https://crypto.stackexchange.com/questions/44386/are-cryptographic-hash-functions-quantum-secure

Glad to hear that! thanks

Thank you @Bit_Alb

I think I might need to make a separate illustration for policy rules if that’s something you’re interested in

The bitcoind client has a -maxconnections configuration option. Setting -maxconnections=N specifies the total number of connections, including both incoming and ourbound connections (the default is 125, 8 outbound and 117 inbound)

Nodes are identified by their IP addresses. If a node misbehaves => it gets added to its "ban list" => so it won’t listen to that node anymore (The more people that "ban" that node, the less effect it has on the network)

Misbehaving includes things like spamming mempool messages, relaying invalid transactions, and broadcasting invalid blocks (Reference: https://bitcoin.stackexchange.com/questions/48834#48835)

Thanks for the context! I’ll put together an explainer on this later this week

🙏🙏

If you're struggling to come up with a solution for the coding exercise, lmk I can help

@DarthCoin posting it as markdown looks even better 😁✨