Wallets Recovery VS parity-ethereum

It works when it works, and sometimes not https://walletsrecovery.org/

I dojt know what this is for, if its technical or not. Maybe ask a language ai model to elabotate some stuff. If walletsrecovery.org

https://walletsrecovery.org look for list of wallets that support BIP-39.

Yesn't In addition to your seed phrase, you need the script type and derivation path (assuming you're not backing up from the wallet you generated the seed from) https://walletsrecovery.org/ <-literally just a list of derivation paths per wallet

You can find your derivation path here: https://walletsrecovery.org/

See https://walletsrecovery.org/ for a partial survey of compatibility and incompatibility

You can check which derivation path your wallet uses here: https://walletsrecovery.org (this is literally just a list of derivation paths)

https://walletsrecovery.org check this

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).