Who Broke the SHA1 Algorithm (And What Does It Mean for ...

Bitcoin Cash's hash functions are now available in WebAssembly (SHA-256, SHA-512, SHA-1, and RIPEMD-160)

Bitcoin Cash's hash functions are now available in WebAssembly (SHA-256, SHA-512, SHA-1, and RIPEMD-160) submitted by bitjson to btc [link] [comments]

How Litecoin Cash fork is going on

In the evening of February 18, on the block 1361111 hardfork of Litecoin Cash happened. All LTC holders were promised LCC coins in the ratio 1 LTC = 10 LCC.
The new cryptocurrency works on the Bitcoin SHA-256 hashing algorithm instead of the Scrypt from Litecoin. It will attract owners of obsolete equipment for bitcoin mining. At the same time, developers promise faster transactions than Bitcoin and Bitcoin Cash.
Litecoin Cash is now developing its own QT wallets. Now a new coin is supported by at least one purse - Coinomi.
The project site also reports that the new coin will be traded on crypto-exchangers Yobit, MercatoX, TradeSatoshi, MeanXTrade and CryptoBridge.
At the time of writing this post LCC on the Yobit exchange is worth 0.00031000 BTC, or $ 3.40. The price since the beginning of trading has more than doubled.
Litecoin founder Charlie Lee said that he has nothing to do with the project, and advised not to invest in it.
Join our Telegram channel to be the first to read news of blockchain and crypto industries
submitted by ICOandCryptoNews to ICOandCryptoNews [link] [comments]

Bitcoin Cash's hash functions are now available in WebAssembly (SHA-256, SHA-512, SHA-1, and RIPEMD-160)

Bitcoin Cash's hash functions are now available in WebAssembly (SHA-256, SHA-512, SHA-1, and RIPEMD-160) submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

Mine bitcoin today while it is still surging! Buy Hash/rates starting at $1.20 per 10G/H for SHA-256. Lifetime Contracts and also automatic Payouts! No issues with Payouts! Use my link, to lock-in for 10% off

submitted by C00lGiraff3 to cloudmining [link] [comments]

Why was the RIPEMD-160 hash algorithms chosen before SHA-1? [bitcoin.SE]

Why was the RIPEMD-160 hash algorithms chosen before SHA-1? [bitcoin.SE] submitted by sroose to Bitcoin [link] [comments]

[Draw #58] We have our comments, and soon we’ll have our winner!

Alright.

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in this [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion for Fall and Winter 2020-2021]: https://old.reddit.com/millionairemakersmeta/comments/iw8mse/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will decrease the counter. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the GitHub repository, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #58, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.5 or better and follow the path to the folder labeled: MM58
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #58:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/masteMM58 SHA-256 of Comment IDs: 965c2c672cdcb28ac73f5bd866fc32403b8c7c8c94ffbb5c7e7ab93dccae8b58 SHA-256 of Authors: 62f3f887c55f6b6cffa3c3031c7a29ab25da8a653b327f4367ca914d92c8d866 SHA-256 of DQed Age: a05064a8c85ee95f48a4ac9f8f5b5562005a7dd9057bc8fa72bb7c3bfb785d08 SHA-256 of Multiple Posters: 1972757669a1deea8c21f97b2eed5bd191e75eb31b0cef24428ab4f1eede8649 SHA-256 of Truncated IDs: 1d66d36bb98ed5a8547209b2270bd72caa6d61276469aeb336cd64f628e5dcdc Block Selection: The Third Bitcoin Block After 20 September 2020 - 16:00:00 UTC Total Participants: 7,468 
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

[Draw #57] The comments have been gathered, it is time to see who our winner is!

Let’s hope everything goes smoothly this time!

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in this [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC (12:00 PM EDT), the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion for Spring and Summer 2020]: https://reddit.com/millionairemakersmeta/comments/g3a53t/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will decrease the counter. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the GitHub repository, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #57, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here. Only use the files that are in the GitHub repository.
If you are interested in doing this for yourself, download Python 3.5 or better and follow the path to the folder labeled: MM57
If you decide to pursue this path of verification, DO NOT PREMATURELY ANNOUNCE THE WINNER! In the event of discrepancies, this can make manners complicated and result in difficult decisions. Doing so will result in a 40-day ban for the first offense, and continuing offenses could result in a permanent ban. You are welcome to post your results afterwards, and privately contact the moderation team if desired.
Status Reports:
I will be reporting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #57:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/masteMM57 SHA-256 of Comment IDs: c6fc972ad7a198f92b0c0570abef9e890d18f08c500309c059516fe916fc06e6 SHA-256 of Authors: 384f813e06a08032a948f3b607b30e127490bab87ba34d4212981beb8e830d5c SHA-256 of DQed Age: 9764b033c3c877feb88c169095cd4ff4e09304b18cb9e5722594093cbed2b1ed SHA-256 of Multiple Posters: fecc372c92f1daafed8a6e240a4aae282b2393aa81ece506c68dbc5dc6fd542b SHA-256 of Truncated IDs: e104fca0c44521e334e5e94f952a89ca88db0fd92617fdcf0ae962428be27114 Block Selection: The Third Bitcoin Block After 23 August 2020 - 16:00:00 UTC Total Participants: 7,654 
submitted by lilfruini to millionairemakers [link] [comments]

Use weaker hash from strong hash to reduce size ?

Hello,
I was wondering if it would make sense to use a weaker hash algorithm (e.g. MD5 or SHA-1) on a hash generated by a stronger one (e.g. SHA-2, SHA-3) to reduce the storing size of the hash.Every keys will be hashed 2 times (e.g key -> SHA-2 -> MD5).
I was reading The bitcoin block size limit controversy (link) and was wondering if reducing the hash of Previous Block and Merkel Root could reduce the size of a block.
What are the consequences of doing that?

Edit: thank you for all your explanations!
submitted by LutinRose to crypto [link] [comments]

[Draw #56] The comments have been collected, and the winner will soon be selected!

I’m posting this early so I won’t have to later.

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in this [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion for Spring and Summer 2020]: https://reddit.com/millionairemakersmeta/comments/g3a53t/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will decrease the counter. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the GitHub repository, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #56, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.5 or better and follow the path to the folder labeled: MM56
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #56:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/masteMM56 SHA-256 of Comment IDs: e57ae28b92664cd67bc89c1a707184b460d353347ef7f4b96bc544a3eae3f561 SHA-256 of Authors: dad8b4ce5524db48bd19a719577f6db218329c05c1d08b733d7ee45d39b30523 SHA-256 of DQed Age: 98217fc99f543ed3ac8395c1fba6d054c63af5aadc18b8f894cb8a72f99bf2a7 SHA-256 of Multiple Posters: ff2255ce3934be2c098207232ab91eb460fed516898eef6123b0e17adf537ac0 SHA-256 of Truncated IDs: 7623ea9d10884d7bc50f6d0bc0734b0234d80faefc61439219f6af8fe96f7db2 Block Selection: The Third Bitcoin Block After 19 July 2020 - 16:00:00 UTC Total Participants: 7,738 
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

Your entries have been made, it’s time to pick a winner! [Draw #55]

We’re going to pick someone, and that someone will like it!

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in this [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion for Spring and Summer 2020]: https://reddit.com/millionairemakersmeta/comments/g3a53t/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will decrease the counter. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the GitHub repository, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #55, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.5 or better and follow the path to the folder labeled: MM55
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #55:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/masteMM55 SHA-256 of Comment IDs: d4f1038b8d16a65bd1ec626f8f6770ba9d154141e7ab7933c78ebe70d1f65c12 SHA-256 of Authors: af9bbd1afd93d2fc5e3a94cc5d332cbacab54b9f82b718a5978e7900b039c865 SHA-256 of DQed Age: 99d50004fddd01c05b8686354b29bb782ede5737289fc301a341df048dff038c SHA-256 of Multiple Posters: 683e47f3026ebd45bbefdb2f2c17519b186f1d017b00acf4e2f6aaedce9b3e1f SHA-256 of Truncated IDs: 38761cc450a8ebddd089bbb50789313b1b2f5ca98fc04bfed6032358ef0a9388 Block Selection: The Third Bitcoin Block After 21 June 2020 - 16:00:00 UTC Total Participants: 5,381 
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

Generate bitcoin address with numbers in python

I have been trying to get the code to increment (loop) to other numbers like 2,3,4.... But it stops at the default which is 1... import argparse import hashlib from binascii import hexlify, unhexlify from struct import Struct from utils import g, b58encode, b58decode PACKER = Struct('>QQQQ') def count_leading_zeroes(s): count = 0 for c in s: if c == '\0': count += 1 else: break return count def base58_check_encode(prefix, payload, compressed=False):

Add version byte in front of RIPEMD-160 hash (0x00 for Main Network)

s = prefix + payload if compressed: s = prefix + payload + b'\x01'

Add the 4 checksum bytes at the end of extended RIPEMD-160 hash. This is the 25-byte binary Bitcoin Address.

checksum = hashlib.sha256(hashlib.sha256(s).digest()).digest()[0:4] result = s + checksum return '1' * count_leading_zeroes(result) + b58encode(result).decode() def pub_key_to_addr(s): ripemd160 = hashlib.new('ripemd160') hash_sha256 = hashlib.new('SHA256')

Perform SHA-256 hashing on the public key

hash_sha256.update(bytes.fromhex(s))

Perform RIPEMD-160 hashing on the result of SHA-256

ripemd160.update(hash_sha256.digest()) return base58_check_encode(b'\0', ripemd160.digest()) def int_to_address(number): number0 = number >> 192 number1 = (number >> 128) & 0xffffffffffffffff number2 = (number >> 64) & 0xffffffffffffffff number3 = number & 0xffffffffffffffff private_key = hexlify(PACKER.pack(number0, number1, number2, number3)).decode("utf-8") print('Converting from: ' + str(int(private_key, 16))) compressed_key = base58_check_encode(b'\x80', unhexlify(private_key), True) print('Private key: ' + compressed_key)

address

x, y = str(g * int(private_key, 16)).split() len1 = len(x) len2 = len(y) if len1 != 64: z = 64 - len1 x = '0'z + x if len2 != 64: z = 64 - len2 y = '0'z + y compressed_public_key_with_out_prefix = x + y pk_prefix = '02' if not int(compressed_public_key_with_out_prefix[64:], 16) % 2 == 0: pk_prefix = '03' compressed_public_key = pk_prefix + compressed_public_key_with_out_prefix[:64] print('Public key: ' + compressed_public_key) print('Bitcoin address: ' + pub_key_to_addr(compressed_public_key)) def wif_to_key(wif): slicer = 4 if wif[0] in ['K', 'L']: slicer = 5 return hexlify(b58decode(wif)[1:-slicer]).decode('utf-8') def main(): parser = argparse.ArgumentParser(description='Generates private key, public key and wallet address from number') parser.add_argument('number', type=int, nargs='?', default=1, help='A required integer number argument') args = parser.parse_args() int_to_address(args.number)

int_to_address(12345678900987654321)

if name == "main": main()
Please, how do I make it to increment to other numbers.. The full code is on github https://github.com/PaulGregoBitcoin-Keys-Generatoblob/mastegenerators.py
submitted by Far-Onion-4112 to Bitcoin [link] [comments]

Checker Thread (A list of hacked clients for easy reference)

Community contribution is the only way this thread will be useful. This is a WIP! More clients will be added as time goes on!
Quick note: The vast majority of these are files supplied by the community -- some may not work. The person who sent me 9b9t says it doesn't work, but I have not personally tested. Please let me know if it works or does not work.

Some additional notes:
I am open to community criticism so long as it can actually be used to benefit the thread. Issues with formatting, approach, client choice, etc. are all great things to come talk to me about so I may improve. However, people keep commenting the same things over and over and over — “VirusTotal can’t catch X” is a popular one — and I don’t have time to deal with it. If you have a security concern, you are more than welcome to raise it. HOWEVER, do not make unreasonable requests of me — I work, in addition to that I have a social life, I have responsibilities at home as well. This is a side thing that I do when I have the time. A lot of people have suggested looking through bytecode to determine if a client is malicious. I do not have the time to do this for every client. If you are willing to help and do more than say “you should do more than you already are, even though you have a job and a life outside of an obscure subreddit,” feel free to DM me. People who take the broken record approach and say things that are already covered in the thread, or refuse to offer help and just post complaints, will be blocked and ignored. I’m all down for making this post better, but I’m not gonna waste my time with people who won’t work with me. Thank you for your help!

BIG THANKS TO u/jpie726 FOR HIS MASSIVE CONTRIBUTIONS! WITHOUT HIM THIS LIST WOULD BE SIGNIFICANTLY LESS EXPANSIVE. GO UPVOTE THIS MAN INTO HEAVEN, HE DESERVES IT!

Eventually I would like to make a Python script that takes care of all the necessary tasks to install these clients. Python itself is available through the Windows Store as well as on Python's website, or through various other installers. It will install any additional dependencies via Pip and will use Curl to retrieve the files. Anyone interested in helping with this script is more than welcome to do so, if you wish. The two options for assisting me would be as follows:
1. You can install Visual Studio Code or Atom and work with me directly through those applications (more details soon™)
2. A GitHub page may be made and you could submit pull requests through that and edit the script alone.

#######################################################################
There is a misconception that I am only here for free paid clients.
1. I can't use a paid client unless I have access to a cracked version, an account, and the HWID bound to said account.
2. People are also saying there's a way for clients to track if someone leaks them. While I suppose this is possible if they bothered to put in the absurd amount of effort it would take, it would give them no benefit and it would do no good as I am not running the software on my desktop -- I am sending the software to VirusTotal, grabbing the SHA-256 checksum, and deleting the file.
3. If all you're going to do is post that "VirusTotal can't catch x" or "muh client" do not waste my time, and don't waste yours. You will be ignored in favor of people who will actually help me construct what I hope to be a megathread for this subreddit, FOR YOU GUYS. I mean jeez, someone's trying to help and half the fucking responses are "muh client" like come on. No wonder this fucking subreddit is dead, sheesh. If someone's trying to help you and you just step on their toes that's just not very cool, not everyone is trying to scam you. I do just be trying to help people who come here doe.
4. If you have concerns, raise them respectfully. Do not attack me, you will be ignored or if I feel so inclined I will give you 110% of the shit you give me right back to you. I will answer questions, I will elaborate on my goals, I will take helpful advice. Everything else will be outright ignored, and misinformation will be countered. That is all, thread below.
#######################################################################

I named this the Checker Thread to make it easy to search for in the subreddit. Enjoy.Below will be a list of hacked clients, with VirusTotal links, SHA-256 hashes, direct download links (skipping ad pages) and eventually features for each client. I'd also like to add what servers they do and don't work on, but I need the community to help with that.
The only client I use is Impact, send me additional clients in the comments and they will be added to this list.

Note about SHA-256 hashes:
SHA-256 hashes are a hash of a file produced algorithmically. This type of hash was developed by the United States National Security Agency, and is typically used to verify that files are what they are supposed to be. Widely used in cryptographic applications such as SSH, APT repositories, transactions on websites, verifying files, Bitcoin, and more. It is very common. This type of cryptographic hash has been in use since 2001. An SHA-256 hash will be the exact same for the same file regardless of the source of the file, so if your hash is different from the one listed here you do not have the legitimate installer OR the hash is not up-to-date.

Note about VirusTotal tests:
Several people have pointed out to me something I feel should be brought up in the main thread. VirusTotal is not a catch-all, just as your typical antivirus software is not a catch-all. It will not catch everything. It should be used as a general guideline only. Clean VirusTotal tests do not guarantee your safety, although if the program passes all ~70 or so antivirus engines it's probably safe to use. Any additional malicious activity should be caught by your antivirus program's heuristics. I take no responsibility for anything that is malicious, but I can say in good conscience that I have done everything I can to ensure that everything on this thread is safe. Keep in mind that programs that trip VirusTotal may still be safe to use, antivirus programs often pick up injectors as malware or Trojans because that's how those types of viruses behave in the real world. Use your best judgement. If your best judgement is not good enough, do not use these programs. You have been warned.

----- C --- L --- I --- E --- N --- T--- S ------ C --- L --- I --- E --- N --- T--- S ------ C --- L --- I --- E --- N --- T--- S -----

Impact | 1.11.2 to 1.15.2 | Java Edition
VirusTotal Link for *.exe Installer | VirusTotal Link for *.jar Installer
SHA-256 Hash: 4EAFFB99759FBD949D0FBEF58AE9CEB45CE8CA2B0D7DC22147D4FF0E46F010EC
Impact triggered 0/72 engines on both installers.
Direct Link to Impact's *.exe Installer | Direct Link to Impact's *.jar Installer
------------------------------------------------------------------------------------------------------------------------------------------------

Sigma | 1.8 to 1.16 | Java Edition
VirusTotal Link for *.jar Installer | VirusTotal Link for the *.zip the Installer is Contained In
SHA-256 Hash for the *.zip file: 3FCD397849358522BF0EEEAF117487DBA860919900A904551DF512BE2C34B48C
Sigma's *.zip file triggered 0/59 engines on the *.zip file.
Sigma's *.jar file triggered 0/60 engines on the *.jar file.
Direct Link to Sigma's *.zip File that Contains the Installer
------------------------------------------------------------------------------------------------------------------------------------------------

9b9t | 1.12.2, needs testing | Java Edition | Forge Mod
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: 30E4F2778688D54CE7992AFDE509460A7BDDBDA77800219083D4D12BC696EEA0
9b9t triggered 0/60 engines.
AnonFile link to 9b9t's *.jar Mod
------------------------------------------------------------------------------------------------------------------------------------------------

Ingrosware | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: BD1A0F9079F4C834A251163C3A0ECBFF7DFC28AB00CF1C74008AADD042FAD358
Ingrosware triggered 0/59 engines.
AnonFile link to a pre-built *.jar Mod
Note: Ingrosware is open source, and is available on GitHub. If you want to build it yourself, you can do so here.
------------------------------------------------------------------------------------------------------------------------------------------------

Mercury | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: 70E585A94218149970410ACAE5BE7C1C1B731140F1AF55FE2D1292B1CA74DCB9
Mercury triggered 0/60 engines.
AnonFile link to Mercury's *.jar Mod
------------------------------------------------------------------------------------------------------------------------------------------------

Atlas | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.jar Forge Mod
SHA-256 Hash: 7AEB7220CBD5D7C4E4421A940357F14EC70B18DB905469E288529FE3A2C04D57
Note: The file is called AceHackGold-n3.0-release.jar in VirusTotal. The client is identified as Atlas in the .nfo file it came bundled with.
Atlas triggered 7/59 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.jar Mod
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
Note 2: The file downloaded is called AceHackGold-n3.0-release.jar*, I'm not sure why. This file was community-sourced, but it has been inspected in the same manner as all the others*.
------------------------------------------------------------------------------------------------------------------------------------------------

Atom | 1.12.2 | Java Edition | Forge Mod | Use with extreme caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 3B43F952EB5B14F2B01592057B27E92B0E38B6874EA10B8E893BFCBC71463377
Note: The file is called output.157312297.txt in VirusTotal. In addition, VirusTotal identifies the file type properly (\.zip).*
Atom triggered 9/59 engines.
Note: Upon closer inspection of the VirusTotal scan, the client accesses numerous registry keys, which is a behavior I personally would consider to be unnecessary and incredibly suspicious. You can find more information in the VirusTotal scan. The client also exhibits typical Trojan false-positives.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
Use this client with extreme caution. There are behaviors that I consider to be extremely suspicious, you must determine for yourself if it's safe to use however. This may just be how the client works. I do not know, and I can't be bothered to test it.
------------------------------------------------------------------------------------------------------------------------------------------------

Aurora | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 9A66929B629AB076383340D33E0EF9B8CE221679EF79315240EA6C760651A533
Aurora triggered 0/61 engines.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

CandyCat | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 8CEC2F9F28AA3957504E0CC66BF1516080C7BAC50EADB54DC6DD97E0E6E9C745
CandyCat triggered 9/61 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

DayNightGod | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 9CEEB43476B18149C0DA76B7AE94713AAF60ED4D2BFD2339E863CC46A1808A0D
DayNightGod triggered 1/59 engines.
Note: Upon closer inspection, only one engine was triggered. The client did not trigger the usual false-positives of a Trojan, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

HyperLethal | 1.12.2 | Java Edition | Forge Mod | Use with caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 77FACC1FDB0415438963CCC8DDB4081958563AAA962CE9C024E5063DA32E8FAD
HyperLethal triggered 2/59 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------

LoveClient | 1.12.2 | Java Edition | Forge Mod | Use with extreme caution!
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: C71EC42FF612D75CB7AA21B8400D164A74AAD9BB65D2DFEE232461DAF98034C2
LoveClient triggered 9/61 engines.
Note: Upon closer inspection of the VirusTotal scan, the client accesses numerous registry keys, which is a behavior I personally would consider to be unnecessary and incredibly suspicious. You can find more information in the VirusTotal scan. The client also exhibits typical Trojan false-positives.
AnonFile Link for the *.zip File
Use this client with extreme caution. There are behaviors that I consider to be extremely suspicious, you must determine for yourself if it's safe to use however. This may just be how the client works. I do not know, and I can't be bothered to test it.
------------------------------------------------------------------------------------------------------------------------------------------------

SnowHack | 1.12.2 | Java Edition | Forge Mod
VirusTotal Link for the *.zip the Forge Mod is Contained In
SHA-256 Hash: 7100C8D59CE06B279F7D03D834FC2C361F10BEAE913575FC7EFA74E498167D2C
SnowHack triggered 10/62 engines.
Note: Upon closer inspection of the VirusTotal scan, the client appears to be of the injected flavor. Injectors are commonly a false positive Trojan. The client appears to be safe, and there was nothing particularly noteworthy in the VirusTotal scan that is atypical for an injector. While this makes the file appear to be safe, use with caution.
AnonFile Link for the *.zip File
Note: This is a cracked client! The crack is pre-done, so no additional work is required to use -- just put it in your Forge Mods folder and click play.
------------------------------------------------------------------------------------------------------------------------------------------------
submitted by Daemris to minecraftclients [link] [comments]

Tron v11.1.3 (2020-08-20) // Minor updates; Remove PCHunter due to A/V false positives

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.3 (2020-08-20)
- Removed PCHunter utility (extra utility, Tron never ran PCHunter) due to false positives with many A/V engines
. Minor definition updates

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

You made your comments, it’s time to see who our winners! [Draw #54]

Honestly, with how effective the new source code is, it may be easier to automate this process. Let’s not get ahead of ourselves, we’re picking a winner!

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in this [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion for Spring and Summer 2020]: https://reddit.com/millionairemakersmeta/comments/g3a53t/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will, simple. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the Dropbox folder, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #54, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.5 or better and follow the path to the folder labeled: MM54
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #54:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/masteMM54 SHA-256 of Primary IDs: 573ad4148e79528eb00430cf6a8cdc5255e50c6fdd208c5af2c03cc004f54a1b SHA-256 of Authors: b1cdd5dce2da1d952b5425726f01e531d90829ec2fbc9d9a21f60fa93e50701b SHA-256 of DQed Age: 4022e832bbd3182ceabd631d9f44130d0bdd7fc3d2bb374823b7b388cd0aa095 SHA-256 of Multiple Posters: be7013c9cf7cd26be543a8aa985488df0ea7e66cd57afd189f5c38e3343b4db0 SHA-256 of Truncated IDs: 0a592fe3a3dae7c3c0f5995048874157b7a144999fa9a38a47937999c5ef64ca Block Selection: The Third Bitcoin Block After 17 May 2020 - 16:00:00 UTC Total Participants: 79,960 
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

Let’s not dawdle in picking a winner, come in and see who it could be! [Draw #53]

Ladies and gentlemen, this marks the fastest time from the thread being locked to the following post getting posted!

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in this [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion for Spring and Summer 2020]: https://reddit.com/millionairemakersmeta/comments/g3a53t/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will, simple. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the Dropbox folder, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #53, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.5 or better and follow the path to the folder labeled: MM53
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #53:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/master SHA-256 of Primary IDs: 934bb09c18a3545ac2b1747efedc0d9757fa08b1615bce4859145d682bb6b9f6 SHA-256 of Authors: 3cd8728eda8452e1e38da0c6346683899dd7ba0068d6e885bb9ad91d182d6188 SHA-256 of DQed Age: de0ea9f849968dfcab4c4c38aa7820380977db43913d2a12a50a215a3825c94c SHA-256 of Multiple Posters: 779cef3ecc9e2e4085b10906ee6b7bd2a4677234235580d6f94a1af7f79df699 SHA-256 of Truncated IDs: 10473d69c0344db168a6ee9243ce683d57401a76d60d2727ad033a6387eabe4d Block Selection: The Third Bitcoin Block After 19 April 2020 - 16:00:00 UTC Total Participants: 9,515 
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

Tron v11.1.2 (2020-07-13) // Fix screen rotation bug caused by O&OSU10; escape some references to %USERNAME%; minor definition updates

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.2 (2020-07-13)
! bugfix: Wrap missed reference to %TEMP% in quotes. Thanks to u/TheDarkThought
- Minor definition updates

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

Premining SHA-256 hashes

Could someone explain how SHA-256 works in bitcoin and specifically how hashes are generated and what qualities a hash must have to be considered valid? Im trying to understand more of the technical side of bitcoin, and I think I have a misunderstanding. Is the only requirement for the next hash to be smaller than the hash of the previous block? And if thats the case would someone not be able to "premine" obvious smaller hashes and then just add them to the blockchain to make their chain the longest?
Thanks you for any and all help!
submitted by UBCStudent9929 to Bitcoin [link] [comments]

Why I think blockchain voting is a terrible idea.


Recently, some news popped up on “blockchain voting” that promises the “security of the blockchain”.
What. The. Hell.
Disclaimer I did not read all 100 paragraphs of their patent (most of it describing implementations and technicalities) so what I write here may or may not be accurate to what they plan on doing. I will revise as I see new information.
Pre-foreword: Vocabulary
Asymmetrical encryption: Assymentrical encryption is where encryption and decryption require two different “keys”. Typically, there is the public key and private key. The private key is never shared, but the public key is shown to everyone in the world. In asymmetrical encryption, only the Private key can decrypt ciphertext encrypted with the Public key, and vice versa.
Nonce: a cryptographic element which is just a random bunch of text at variable length.
Hash: a cryptographic hash. Read: SHA
Foreword: What’s blockchain? (This assumes USPS implements similar to the bitcoin paper)
Blockchain is a system of a distributed ledger. Each entry contains information on a transaction. The “sender” of the money encrypts the transaction with their private asymmetrical encryption key. This means people with the public key can verify they sent it.
Every “block” contains a set amount of entries, which are then hashed (in bitcoin- with a special nonce which is found by “mining”) and passed onto the next block in the chain. Every block is hashed with the previous block’s hash.
Another part of blockchain is that whichever chain of blocks is longest is the correct chain- so long as the entries are valid. Shorter chains are discarded (this is how the Etherium 51% attacks that got 5.6 million worked).
Why this sucks.
As I understand it, the blockchain system works like so:
Voter A adds their name to the ledger on the “I voted” chain. Voter A anonymously adds their vote onto the “Who I voted for” chain.
Ok, cool. A did everything right. But if this is all that’s going on here...?
The problems.
Ok, so what works?
There are a BILLION other ways to do voting that are more secure and more anonymous than a damn blockchain. Here are some:
Epilogue
As far as I understand, voting by blockchain is a bad idea and I will need to see some very good arguments defending it on the USPS side before I trust it. Distributed, public computing models should not be used in voting.

It takes a lot of money to make Blockchain secure.

submitted by Mooshua to CryptoCurrency [link] [comments]

We’re picking our winner, no need to comment! Just sit back and enjoy the ride! [Draw #52]

Brace yourselves.

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in the [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 16:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.5, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Survey Results:
The results are in! PayPal is one of the most important services of payment, so feedback here was critical.
With that being said, we will continue to offer our alternatives, including cryptocurrencies and other payment services. Thank you for your time!
Results: https://imgur.com/gallery/tnIZTFP
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries. (Currently, the discussion thread is also being used for #52. I will look to make a seasonal thread.)
[Discussion #51]: https://www.reddit.com/millionairemakersmeta/comments/f8g5fo/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 16:00 UTC) to select the winner.
If a block is discovered by 15:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 16:00:00 UTC, then it will, simple. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the Dropbox folder, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #52, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.5 and follow the path to the folder labeled: MM52
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 1:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you will be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #52:
GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/master SHA-256 of Primary IDs: a8735f7dacabd6bd279ed096587f49ecaf2225508b7484bdea1739faf4d21949 SHA-256 of Authors: 3cd8728eda8452e1e38da0c6346683899dd7ba0068d6e885bb9ad91d182d6188 SHA-256 of DQed Age: de0ea9f849968dfcab4c4c38aa7820380977db43913d2a12a50a215a3825c94c SHA-256 of Multiple Posters: 779cef3ecc9e2e4085b10906ee6b7bd2a4677234235580d6f94a1af7f79df699 SHA-256 of Truncated IDs: 10473d69c0344db168a6ee9243ce683d57401a76d60d2727ad033a6387eabe4d Block Selection: The Third Bitcoin Block After 22 March 2020 - 16:00:00 UTC Total Participants: 75,102 
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

The comments on our post were so much, it broke our script twice! We're going to delay the Draw, and pick our winner starting at 22:00 UTC. If you're a programmer, your help will be greatly appreciated. Anyone else, come in and see the plan! [Draw #49]

Honestly, you all are amazing.

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in either [Drawing Thread] posts, you are entered in the drawing and don't need to do anything else. By 22:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.7, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk near the time passed since its creation. The winner will be announced in a stickied comment.
The Problem:
So, there were so many comments that our script broke! In case you haven't seen the original thread, the comments overwhelmed the PRAW package that it just stopped both times.
Here's the video for your interest: https://youtu.be/7UBLBU92dmI
The Solution:
Alright, so I'm no programmer. The most I've ever done to a piece of code is adding "/nHash: 'Hash'", and that's nothing.
If you're a programmer, your help will be greatly appreciated. Please leave a comment or directly PM lilfruini. Thanks to TyrSniper for the help in letting me know what to do.
The Schedule:
19:00 UTC (2:00 PM ET) - Comment retrieval will be done as through Draw #38, and the two different post retrievals will attempt to be performed at the same time.
19:30 UTC (2:30 PM ET) - If they weren't able to be performed simultaneously, a retrieval of Part 2 will be performed.
20:00 UTC (3:00 PM ET) - A different version of the comment ID text will be created, with the SHA-256 hash inserted in the first line. These will combine Part 1 and Part 2.
22:00 UTC (5:00 PM ET) - Drawing Information will be stickied in the comments (most likely before), and the wait for the Bitcoin hash begins
Thank you.
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

Tron v11.1.1 (2020-05-25) // Fix -pmb switch behavior; remove deprecated telemetry-removal tasks; prevent CCleaner from wiping Taskbar Jump Lists

Background

Tron is a script that "fights for the User."
It aims to automate ~87% of the tedious work in getting a badly-running Windows system back on its feet (clicking "next" in a/v scan windows, etc); with much left to the discretion of the tech.
It is built with heavy reliance on community input and updated regularly.
It is NOT a system optimization or "baseline" script.
Read the instructions.

Sequence of operation

Prep > Tempclean > De-bloat > Disinfect > Repair > Patch > Optimize > Wrap-up | Manual tools
Saves a log to C:\logs\tron\tron.log (configurable).
screenshots of Tron in action

Changelog

(significant changes in bold; full changelog on Github)
v11.1.1 (2020-05-25)
! Fix -pmb switch behavior
* CCleaner: Disable clearing of Taskbar Jump Lists. Thanks to u/D00shene
- Telemetry removal: Remove outdated job that used to uninstall "bad" updates
- Remove post-run restore point creation

Download

  1. Primary method: Download the .torrent.
  2. Secondary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-DC u/SGC-Hosting
    #1 link link US-NY u/danodemano
    #3 link link DE u/bodrino
    #4 link link US/EU u/mxmod
    #5 link --- US-MI u/ajcutshall
    #6 link --- AU u/agent-squirrel
    #7 link --- GB-LND u/FreezerMoosh
    #8 link --- US-MO u/OlderGeeks
    #9 link --- Amazon CDN u/helpdesktv
    #10 link --- Global CDN Softpedia
  3. Tertiary: Connect to the Syncthing repo (instructions) to get fixes/updates immediately. This method has some risks and you should only use it if you understand them.
  4. Quaternary: Source code
    Source code is available on Github (Note: this doesn't include many of the utilities Tron relies on to function). If you want to view the code without downloading a ~600MB package, Github is a good place to do it.

Command-Line Support

Tron has full command-line support. Switches are optional, can be used simultaneously, and override their respective default when used. See here for a list of command-line switches.

Pack Integrity

SHA-256 hashes are in \tron\integrity_verification\checksums.txt and are signed with my PGP key; included. Use this to verify pack integrity.

Donations

Tron will always be free and open-source. If you'd like to buy me a beer or more importantly ... scotch ... you can do so here:
  • Patreon
  • Bitcoin: 1Biw8gx2kD7mZf66ZdNgB9tG1pE9YA3kEd
  • Bitcoin Cash: 18sXTTrAViPZVQtm63zBK6aCK3XfJpEThk
  • Monero (preferred): 4GG9KsJhwcW3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6HbYdDuZEDZ947uiEje
These addresses go directly to u/vocatus. If you wish to support another volunteer (e.g. the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please look here first for a list of common issues (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to TronScript and myself or one of the community members will look at the issue. Additionally, you can reach me 24/7 on Keybase.
\integrity verification contains checksums.txt and is signed with my PGP key (0x07d1490f82a211a2, pubkey included). Use this to verify the pack.
"Do not withhold good from those to whom it is due, when it is in your power to act." -p3:27
submitted by vocatus to TronScript [link] [comments]

We had some difficulties, but it's not stopping us! The winner will be picked tonight, I'll explain what happened in the post! [Draw #51]

Sorry for being so late, thanks for waiting.

TL;DR - This post is for the sole purpose of choosing a winner. If you commented in the [Drawing Thread], you are entered in the drawing and don't need to do anything else. By 22:00 UTC, the winner will be selected. The Bitcoin (BTC) blockchain will be used to pick this winner. This can be verified at any device running Python 3.8, and you do not need to own Bitcoin in order to participate.
Additionally, all information to replicate the Drawing at home is available on Dropbox and GitHub, scroll down for more information.
Importantly, this post WILL NOT BE EDITED in order to keep the integrity of the Drawing. To verify this, there will not be an asterisk during the time passed since its creation. The winner will be announced in a stickied comment.
The Problem
Alright, so three things happened:
First, I overslept. I fell asleep at midnight, and woke up around 8 o'clock. When I noticed this, I gathered the comments at 9 AM ET, which is pretty close to the deadline.
Second, I haven't used a PC, Mac, or any other reasonable piece of desktop hardware to run a Python script in years. If it's not through Repl.it on my iPad, it's through Pydroid 3 on my LG V30. I couldn't figure out a way to efficiently run the scripts on Repl.it on my iPad, and as for my phone, it didn't want to parse through the authors. Also, the software I used is Python 3.7, while leroy627 stated it required the use of Python 3.8.
In other words, I wasn't able to fully follow through the process of running the scripts due to hardware restraints and lack of the necessary software. I received this error when running getAuthors.py, but I'm not having it stop us.
Third, it's just a culmination of real-life conflicts. I honestly hate having to delay the [Draw] post, but otherwise, I hope everything is fine.
What does this mean for you all?
What happens is that the process of picking the winner is delayed, but not for much longer than what is standard. Also, potential winners will be manually disqualified after an unsuccessful vetting of their account, rather than having it be done automatically, if it comes to that.
The Solution
The comments have already been collected, we're just going to go through the process that has been established in [Draw #49] and [Draw #39], just with the software usable that's on GitHub (save for getAuthors.py and removeInvalids.py, unless if a fix is possible). The winner will be picked on 22:00 UTC (epoch timestamp: 1582495200) today.
DISCLAIMER: Some of the information may be unrevised, but procedures are the same as prior draws. Thank you.
Off Topic:
The [Discussion] Thread at /millionairemakersmeta is open. All comments are welcome there for any inquiries.
[Discussion #51]: https://www.reddit.com/millionairemakersmeta/comments/f8g5fo/_/
Explanation!
The Bitcoin (BTC) blockchain will be used to choose a winner. Once the time listed has passed, there will be an active check to determine the blockchain's winning hash. Like before, this subreddit will wait for the 3rd Block after the time (being 22:00 UTC) to select the winner.
If a block is discovered by 21:59 UTC, it will not be counted towards the counter of three blocks. If it's discovered by 22:00:00 UTC, then it will, simple. This can be checked by seeing the timestamp given to it by blockchain explorers.
You are able to see how this subreddit will verify the winner by checking the Dropbox folder, which also includes a back-up plan in case of an emergency.
Standard Protocol:
This post will not be edited! This is to prevent tampering of the hash or files by any of the moderators. To prove this, look for the lack of an asterisk near the time since creation.
To verify if a hash for a file is that of Draw #51, upload the file of choice to a SHA-256 generator, and match it with its respective hash output. The result you receive should be the same as what is listed here.
If you are interested in doing this for yourself, download Python 3.8 and follow the path to the text file here: MM51\OfficialMM51IDs.txt
Status Reports:
I will be commenting on the progress of the drawing via the comments, so other users can keep track of the progress. These comments will be pinned at the top of the post and be distinguished. Most likely, after 6:00 PM ET, the pinned comment will be announcing the winner.
If you can run Python yourself and follow the instructions, you should also be able to find the winner. Make sure the hash released from the blockchain and the total number of participants match with what is described below. In addition, thank you for your patience.
Information Used For Draw #51:
Dropbox Folder: https://www.dropbox.com/sh/ot6hok3e5zt5enl/AACqBWoCAgikuGsdVs6Z5frta?dl=0 GitHub Repository: https://github.com/lilfruini/CommentGathering-MillionaireMakers/tree/master
SHA-256 of Primary IDs: a8735f7dacabd6bd279ed096587f49ecaf2225508b7484bdea1739faf4d21949
Block Selection: The Third Bitcoin Block After 23 February 2020 - 22:00:00 UTC Total Participants: 7,860
submitted by MakerOfMillionaires to millionairemakers [link] [comments]

What is a Bitcoin hash and SHA-256 - YouTube Don't Get Scammed! *Part 1* How To Check the SHA256 Hash-Monero's Compromised Binaries-Coin Stealer SHA256 Hashing Using Java - Backbone of any Blockchain or a Cryptocurrency Bitcoin - Hash Pointers and Data Structures Que es SHA-256 y el HASH en Bitcoin!!!!?

As well as SHA1, Todd has placed similar bounties on the RIPE MD160 and SHA256 hash functions – both of which are necessary for the integrity of the bitcoin standard, and would therefore be ... By comparison bitcoin network does 62-bits (including +1 for double hash) every 10-minutes and is 537,000 times more powerful than deepcrack, or could if it were focused on DES rather than SHA256 crack a DES key in 9 seconds to deepcracks 56 hours. Miner privacy Bitcoin’s blockchain uses SHA-256 (Secure Hash Algorithm). In 2001, SHA-256 was developed by the National Security Agency (NSA) in the USA. Bitcoin’s proof of work algorithm is based on SHA-256. Using this, Bitcoin miners solve computationally difficult math problems to add blocks into the blockchain. Bitcoin blocks are added by verifying ... In early 2005, Rijmen and Oswald published an attack on a reduced version of SHA-1 — 53 out of 80 rounds — which finds collisions with a computational effort of fewer than 2 80 operations. In February 2005, an attack by Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu was announced. The authors have presented a collision for 58-round SHA-1, found with 2 33 hash operations. SHA-256 Cryptographic Hash Algorithm. SHA-256 is one of the successor hash functions to SHA-1 (collectively referred to as SHA-2), and is one of the strongest hash functions available. SHA-256 is not much more complex to code than SHA-1, and has not yet been compromised in any way. The 256-bit key makes it a good partner-function for AES.

[index] [24859] [23889] [16692] [15401] [22669] [32397] [6504] [23671] [18131] [26725]

What is a Bitcoin hash and SHA-256 - YouTube

Hola amigos les dejo un video explicando lo que es el algoritmo de encriptado SHA-256 y también en que se utiliza en la red Bitcoin. Además les dejo una explicación de lo que es el HASH en Bitcoin. Learn more advanced front-end and full-stack development at: https://www.fullstackacademy.com SHA-1 stands for Secure Hash Algorithm 1, a cryptographic hash ... Cryptographic Hash functions - how your passwords and other credentials are stored in databases - Duration: 22:25. Hacks And Security - Concepts of Technology 66,525 views 22:25 Secure Hashing Algorithm (SHA1) explained. Dr Mike Pound explains how files are used to generate seemingly random hash strings. EXTRA BITS: https://youtu.be/... Hash Pointers and Data Structures - Bitcoin and Cryptocurrency Technologies Part 1 - Introduction to Crypto and Cryptocurrencies Learn about cryptographic building blocks ("primitives") and reason ...

#