shadowsocks-rust VS parity-ethereum

Maybe with https://shadowsocks.org/

I am also in China right now and sorry to say that ProtonVPN hasn't worked at all for me.I downloaded four different VPN apps before departing from Europe and only Mullvad had worked since they implement a Shadowsocks bridge on some connections.

If the changing por trick work you can try shadowsocks or v2ray.

Use this: https://github.com/shadowsocks/shadowsocks-rust

For shadowsocks, you can download it from here: https://github.com/shadowsocks/shadowsocks-rust/releases/tag/v1.14.3, get the "shadowsocks-v1.14.3.x86_64-unknown-linux-gnu.tar.xz" file, and extract it. You should have the ssclient and you can use that in the terminal to connect with it. This seems to have instructions on how to use it

Fellow sub member /u/zenzebeat reports that https://shadowsocks.org/ still works fine albeit slow.

The library killer's confession contains the bugged contract address, and some post-mortem links.

Not really. If one of the clients interpreted a part of the spec in a different way, event if they are right, they would have change it to follow an officially approved code because that's the consensus.

There are examples like https://github.com/openethereum/parity-ethereum/blob/55c90d4...

$150 Million of ETH gets locked up in Parity multisig contracts after a user "accidentally" kills a referenced library.

Case in point. Here's the line of code that introduced a bug in a contract that was ultimately worth $32M:

https://github.com/openethereum/parity-ethereum/blame/4c3217...

https://blog.openzeppelin.com/on-the-parity-wallet-multisig-...

If you look at the associated pull request, it added over 2K lines of code, and removed almost 1K, spread across 20 different files. 5 files have changed so much, GitHub doesn't even show their diff by default.

It was reviewed by one person in a single day.

for those that don't know, Gavin Wood was responsible for writing the Parity Multi-Sig wallet contract on Ethereum, which was famously killed by mistake due to a bug that was discovered by a developer who was playing around with the contract. This caused 513,743 ETH to be permanently frozen ($1,842,796,141 USD as of today).