List of all Bitcoin addresses with a balance

[albert0bsd]

I just try to download the lastest file and sadly the server is down, reading the recent messages i think i wil put a mirror ot the files as soon i can get a copy of them.

@LoyceV I will let you know when my mirror is ready.

[LoyceV]

i think i wil put a mirror ot the files as soon i can get a copy of them.

I can rsync them to you the second I update them if you want. I've only killed Apache2, my server and updates are still running.

[albert0bsd]

I can rsync them to you the second I update them if you want.

Yes, absolutely. That would be great.

I can set up a dedicated account/SSH key with access only to the mirror directory, so you can rsync the files whenever you update them.

Let me know what you need from my side. Send me a DM if you like

[albert0bsd]

Thank you loyceV for the rsync

Here is my mirror:

Code:

https://addresses.albertobsd.dev/

I remove LATEST symlink file to avoid people trying to update it each 3 minutes, All other files will be there.

[LoyceV]

Here is my mirror:

Code:

https://addresses.albertobsd.dev/

Suggestion: sort the files by date instead of alphabet.
Enjoy your burned bandwidth
Updates are scheduled, they start right after my update finishes.

I remove LATEST symlink file to avoid people trying to update it each 3 minutes, All other files will be there.

I've excluded it from rsync. It should also remove older files.

It occurred to me....
What if I provide uncompressed text-files? Would that work with rsync? I've never used rsync to a public location. It would save so much bandwidth if only the removed/added addresses have to be downloaded each day!
Alternatively: what if I provide only a list of changes, that users can easily add on their own each day? It could even be a daily list of changes from the past week, so downloading once a week is enough to be up to date again.
Thoughts?

[pbies]

It occurred to me....
What if I provide uncompressed text-files? Would that work with rsync? I've never used rsync to a public location. It would save so much bandwidth if only the removed/added addresses have to be downloaded each day!
Alternatively: what if I provide only a list of changes, that users can easily add on their own each day? It could even be a daily list of changes from the past week, so downloading once a week is enough to be up to date again.
Thoughts?

You would need to host "diff" files. Much work on client side to update the file.

Also .txt goes full size thru Internet (can be even packed in the air but still bandwidth takes whole file) so loss of bandwidth.

I don't like neither of these solutions. My own opinion.

@albert0bsd HTTPS will kill your server fast when there will be few downloads at the same time. Maybe plain HTTP?

[LoyceV]

You would need to host "diff" files. Much work on client side to update the file.

I've never created diff files, but shouldn't it take only seconds to process from a script? I doubt it's slower than downloading and decompressing gz.

Also .txt goes full size thru Internet (can be even packed in the air but still bandwidth takes whole file) so loss of bandwidth.

Rsync can take care of that. Let's test it:
1. I've uncompressed Bitcoin_addresses_August_29_2026.txt.gz on my server to "test", and downloaded it through compressed rsync:

Code:

sent 43 bytes  received 1,75G bytes  1,07M bytes/sec
total size is 2,81G  speedup is 1,60

2. I've uncompressed Bitcoin_addresses_August_30_2026.txt.gz on my server to "test", and downloaded it through compressed rsync:

sent 424,24K bytes  received 1,54G bytes  1,03M bytes/sec
total size is 2,81G  speedup is 1,83

This is disappointing. I had higher hopes for rsync being smart enough to handle this with much less bandwidth.

I don't like neither of these solutions. My own opinion.

Thanks. I'm just looking for an option to keep it online.

@albert0bsd: are updates working on your mirror? Your listing was last updated yesterday, and files that should be deleted are still shown.

I don't know why downloads from this server are now sooooooo slow! It used to be much faster:

I also tested Bitcoin addresses with a balance:

Code:

-                    41%[=======>            ] 561.19M  55.5MB/s    eta 11s

This is a different server. Much smaller, but fast disk.

[pbies]

Diff files are short, but to make changes to whole addresses file is at least to once copy it (in the same folder) and apply the changes.
He would need to search in the file (so read it line by line) for single lines and apply the patch. Always it is at least to go once thru file line by line and make at least one copy of the whole file (the changed one beside the source file being in the same folder).

[albert0bsd]

@albert0bsd HTTPS will kill your server fast when there will be few downloads at the same time. Maybe plain HTTP?

Thank you for the recommendation, I will monitor the CPU usage, right now is 3% usage, for the moment is OK.

The problem is all .dev top-level domains are built into the HSTS preload list, which forces all web browsers to connect via HTTPS only.
For scripts I can redirect HTTP but for browsers I cannot do anything.

@albert0bsd: are updates working on your mirror? Your listing was last updated yesterday, and files that should be deleted are still shown.

The rsync directory and the web root directory are different (sorry for that this is because the directory user permissions are different between your user and the apache user)

I just add a hourly cron job to update new files into the web directory. I will add some script later to work with the deleted files.