btcrecover VS CIPs

https://github.com/3rdIteration/btcrecover

Edit: I GOT IT!!!, had to use https://btcrecover.readthedocs.io/. Turns out I had the wrong word. Thank you u/Crypto-Guide, you are a lifesaver. My week just got a whole lot better.

I'm not aware of any such list, and I don't think atomic has even disclosed all of their derivation paths. For example the derivation path to ethereum had to be reverse-engineered, it is possible to get the private key to ethereum address made with atomic using the recovery software btcrecover. However it can be a little painful to get running and the documentation is quite extensive because it caters to so many different wallets.

BTCRecover (https://btcrecover.readthedocs.io/) does this (I maintain the tool), basically something like an M1 Mac can easily check about 200,000 seeds per second.

Also, for anyone without your coding skills, BTCRecover is a free open-source program from /u/Crypto-Guide that traces its origins nearly a decade.

One of the most used and trusted tools for this is btcrecover (current fork of 3rdIteration). It can run offline if you are concerned about security, but it's not the most user-friendly tool.

You can try and go it manually, but if you get fed up with that then you can also use tools like BTCRecover to attempt to speed up checking https://btcrecover.readthedocs.io/ (I also have a bunch of videos about it on my channel)

You need to be sure you have the right seed... The passphrase is easy to mess up, so you can try a bunch of things by hand or use BTCRecover to help test a bunch of seeds very quickly. (https://btcrecover.readthedocs.io/)

BTCRecover can be used for this https://btcrecover.readthedocs.io/

CPS-???? | Governance Security [New Problem]: This problem statement describes security issues to be considered by protocol governance CIPs.

The Lace team is already working with the community on how to find the best way to develop the CIP-72 - DApp Registration & Discovery. If you’re interested in taking part, contribute here

All mobile wallets have some kind of dApp browser, but there are no hard specs for how they should be run that is implemented at the moment. You might be interested in CIP72 if you're interested in standards for this topic more generally: https://github.com/cardano-foundation/CIPs/pull/355

CIP-???? | Extend token metadata for translations [New Proposal]: This proposal defines an addition to CIP-25 | Media NFT Metadata Standard to support more languages than English.

If you wish to add your perspectives to CIP 1694, make sure to share them here. Add your voice as the era of Voltaire rolls out!

Last week, a community-led roundtable took place on the topic of CIP-1694. You can catch the recap and outcome in last week’s newsletter or this Cardano Forum recap here. Worth a read.

Conditions inside a native script (but there is a CIP for changing this here)

Thank you for the information! That is very important. Actually I wrote a specification https://github.com/cardano-foundation/CIPs/pull/442 where I address exactly that issue.