testdisk VS bips

One would be Roadkil's app: https://www.roadkil.net/program.php?ProgramID=29 Another would be TestDisk over at CGSecurity: https://www.cgsecurity.org/

Photorec

Thu Feb 16 16:13:36 2023 Command line: TestDisk TestDisk 7.2-WIP, Data Recovery Utility, February 2023 Christophe GRENIER https://www.cgsecurity.org OS: Windows 8 (9200) Compiler: GCC 11.2, Cygwin 3001.4 ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=1000204886016 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=250059350016 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=4000787030016 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=4000787029504 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=249482384896 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=4000768327680 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=10735345664 filewin32_getfilesize(\\.\F:) GetFileSize err Fonction incorrecte. filewin32_setfilepointer(\\.\F:) SetFilePointer err Fonction incorrecte. Warning: can't get size for \\.\F: disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=989469508096 disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=4000650887168 Hard disk list Disk \\.\PhysicalDrive0 - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - HGST HTS721010A9E630, S/N:JR10006P0GLHBF, FW:JB0OA3J0 Disk \\.\PhysicalDrive1 - 250 GB / 232 GiB - CHS 30401 255 63, sector size=512 - Samsung SSD 850 EVO mSATA 250GB, S/N:S248NX0H404264F, FW:EMT41B6Q Disk \\.\PhysicalDrive2 - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - USB3.0 , S/N:0123456789ABCDEF, FW:0203 Disk \\.\PhysicalDrive3 - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - Seagate M3 Portable, S/N:NM14GJTZ, FW:9300 Partition table type (auto): EFI GPT Disk \\.\PhysicalDrive2 - 4000 GB / 3726 GiB - USB3.0 Partition table type: EFI GPT Analyse Disk \\.\PhysicalDrive2 - 4000 GB / 3726 GiB - CHS 486401 255 63 hdr_size=92 hdr_lba_self=1 hdr_lba_alt=7814037167 (expected 7814037167) hdr_lba_start=34 hdr_lba_end=7814037134 hdr_lba_table=2 hdr_entries=128 hdr_entsz=128 check_part_gpt failed for partition 1 P MS Reserved 34 32767 32734 [Microsoft reserved partition] Current partition structure: No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker 1 P MS Reserved 34 32767 32734 [Microsoft reserved partition] 1 P MS Reserved 34 32767 32734 [Microsoft reserved partition] 2 P MS Data 32768 7814033407 7814000640 [Basic data partition] [sauvegarde2] search_part() Disk \\.\PhysicalDrive2 - 4000 GB / 3726 GiB - CHS 486401 255 63 NTFS at 2/10/9 filesystem size 7814000640 sectors_per_cluster 8 mft_lcn 786432 mftmirr_lcn 2 clusters_per_mft_record -10 clusters_per_index_record 1 NTFS part_offset=16777216, part_size=4000768327680, sector_size=512 NTFS partition cannot be added (part_offset

Go to https://www.cgsecurity.org/. Read the docs and find out.

If your files were recently deleted you might be able to get them back by using some disk recovery tools. https://github.com/cgsecurity/testdisk

You can scan his disks with PhotoRec from https://www.cgsecurity.org/.

https://www.cgsecurity.org/ See their wiki page for file recovery on your laptop.

Try something from this page https://www.cgsecurity.org/

Christophe Grenier's https://www.cgsecurity.org/ is probably the oldest and most respected. It has gathered years of information to do the recovery yourself.

Modern bitcoin addresses use a base-32 character set that leaves out some of the most ambiguous pairs and also permutes the address ordering so that the most visually similar remaining characters produce single bit errors which are better handled by the addresses error detecting (and potentially correcting) code.

https://github.com/bitcoin/bips/blob/master/bip-0173.mediawi...

Context: Bitcoin miners have just adopted a 50% pay cut for themselves. This pay cut was baked into Bitcoin protocol at the launch of the network (mostly, see "BIP 42" [1]). The OP link gives information about the block in which this pay cut was made.

I get that HN comments tend to dismiss Bitcoin. But the fact that for the fourth time this pay cut has happened without a hitch speaks volumes to what makes Bitcoin interesting: It's a rare combination of economic incentives and technology that keeps chugging. Nobody can stop it. And it's extremely resistant to change. It requires no governmental approval. All attempts at subversion or interference have failed. There aren't many things that come close to that kind of record.

[1] https://github.com/bitcoin/bips/blob/master/bip-0042.mediawi...

Bitcoin transactions involve locking funds in scripts, which can only be spent if those locking conditions are met. The part of the script that expresses these locking conditions are called ScriptPubKeys. On the other hand, the part that provides unlocking scripts to satisfy the locking conditions is referred to as ScriptSig for legacy transactions, and ScriptWitness for SegWit Transactions. These scripts are evaluated by a stack-based language called Script. This article will mainly focus on ScriptPubKeys.

Here’s the reference https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

There are 5 271 537 971 301 488 476 000 309 317 528 177 868 800 possible permutations of the bip39 wordlist found here: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt when using 12 word seeds. You probably have better change to win the lottery every week for the rest of your life than cracking a 12 word seed in correct order

No one controls Bitcoin, because it's a protocol. Bitcoin Core is the reference implementation, but there are others, and anyone can create new implementations if they wish. Also, the Bitcoin Core maintainers can't just change something on a whim, because users would then switch to another fork. Maintainers (or miners or other groups) can't force their changes on users, because everyone can decide on their own which version they want to use.

The protocol development happens through BIPs (Bitcoin improvement proposals): https://github.com/bitcoin/bips

BIPs are discussed for years, before (and if) they are implemented, and basically everyone needs to agree on them, because no one wants to fork the blockchain, which could be devastating.

All the seeds generated from the CoolWallet (Number / Word) adhere to the BIP-39 protocol.