SHA-256 - BitcoinWiki

Devcoin: ethically inspired cryptocurrency

A community based around the Devcoin cryptocurrency, an ethically inspired project created to help fund FOSS developers, artists, musicians, writers and more.
[link]

Myriad - A coin for everyone.

Myriad (XMY) is a Multi-PoW consensus protocol secured by 5 mining algorithms. Each one suits different hardware.
[link]

The Wallet Import Format on the Bitcoin wiki has different hash results for their SHA-256 hashes than I'm getting…

On the Wallet Import Format page on the Bitcoin wiki (https://en.bitcoin.it/wiki/Wallet_import_format) it has a hexadecimal string
800C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D 
And it says that the SHA-256 hash of this is
8147786C4D15106333BF278D71DADAF1079EF2D2440A4DDE37D747DED5403592 
I'm not getting that. I've tried both an online hasher, and Python's hashlib, and I'm not getting that hash. Perhaps is the wiki incorrect? Or perhaps are they using a different hash algorithm than SHA-256?
EDIT:
For clarification, I keep getting
e2e4146a36e9c455cf95a4f259f162c353cd419cc3fd0e69ae36d7d1b6cd2c09 
as the SHA-256 hash.
submitted by Plazmotech to Bitcoin [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]

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]

Tron v11.1.0 (2020-04-25) // Remove Malwarebytes installation by default (-pmb to preserve); French language fix; definition and de-bloat 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.0 (2020-04-25)
/ Change REMOVE_MALWAREBYTES to PRESERVE_MALWAREBYTES (-pmb) as the new default behavior is to remove it at the end of the script
* Fix for Internet connection check on French language systems
* Minor definition updates for sub-tools and A/V engines

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]

How are Ethereum addresses created?

This says that an Ethereum address is basically a Keccak-256 (SHA-3) with some truncation, basically 20 bytes.
https://cryptoticker.io/en/ethereum-addresses-generation/
Bitcoin by comparison has this nice article: https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses
I also found the EIP for checksum addresses, but that of course needs an address to be constructed first: https://eips.ethereum.org/EIPS/eip-55
submitted by Zamicol to ethdev [link] [comments]

Tron v11.0.1 (2020-03-31) // Ultra Mega Coronavirus Edition; 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.0.1 (2020-03-31)
* Minor definition updates for sub-tools and A/V engines
v11.0.0 (2020-02-05)
+ Add switch REMOVE_MALWAREBYTES (-rmb) to have Tron automatically uninstall Malwarebytes at the end of the run
+ Add switch SKIP_COOKIE_CLEANUP (-scc) to have Tron preserve ALL browser cookies. This is NOT generally recommended as Tron now automatically preserves the most common login cookies (chase.com, spotify.com, gmail.com, etc) and wiping other tracking cookies is still good for user privacy and security. You can see the list of cookies Tron preserves in this file. Thanks to tbr:sebastian.
- Remove BleachBit. This is despite the fact that I prefer BleachBit over CCleaner. Reason 1) It performs the same function as CCleaner. Reason 2) It doesn't support excluding certain cookie domains from wiping (the main reason). Once BleachBit supports cookie whitelisting, we will switch over to it exclusively and remove CCleaner from Tron
* Stage 1: Temp file cleanup: Streamline user profile cleanup code, removing a redundant code block
! Stage 5: Patch: Suppress Windows Defender update output unless running in verbose mode
* Update all sub-tools and definition files

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]

Tron v11.0.0 (2020-02-05) // Automatically preserve login cookies for common sites (chase.com, gmail.com, etc); Add REMOVE_MALWAREBYTES and SKIP_COOKIE_CLEANUP switches; Improve Windows Disk Cleanup, Remove BleachBit (see notes); streamline user profile cleanup

Background

Tron is a script that "fights for the User." Think of it as a tech on a thumb drive that automates ~87% of the tedious work in cleaning a Windows system, with some things left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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.0.0 (2020-02-05)
+ Add switch REMOVE_MALWAREBYTES (-rmb) to have Tron automatically uninstall Malwarebytes at the end of the run
+ Add switch SKIP_COOKIE_CLEANUP (-scc) to have Tron preserve ALL browser cookies. This is NOT generally recommended as Tron now automatically preserves the most common login cookies (chase.com, spotify.com, gmail.com, etc) and wiping other tracking cookies is still good for user privacy and security. You can see the list of cookies Tron preserves in this file. Thanks to tbr:sebastian.
- Remove BleachBit. This is despite the fact that I prefer BleachBit over CCleaner. Reason 1) It performs the same function as CCleaner. Reason 2) It doesn't support excluding certain cookie domains from wiping (the main reason). Once BleachBit supports cookie whitelisting, we will switch over to it exclusively and retire CCleaner from Tron
* Stage 1: Temp file cleanup: Streamline user profile cleanup code, removing a redundant code block
! Stage 5: Patch: Suppress Windows Defender update output unless running in verbose mode
* Update all sub-tools and definition files

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]

Mining and Dogecoin - Some FAQs

Hey shibes,
I see a lot of posts about mining lately and questions about the core wallet and how to mine with it, so here are some facts!
Feel free to add information to that thread or correct me if I did any mistake.

You downloaded the core wallet

Great! After a decade it probably synced and now you are wondering how to get coins? Bad news: You don't get coins by running your wallet, even running it as a full node. Check what a full node is here.
Maybe you thought so, because you saw a very old screenshot of a wallet, like this (Version 1.2). This version had a "Dig" tab where you can enter your mining configuration. The current version doesn't have this anymore, probably because it doesn't make sense anymore.

You downloaded a GPU/CPU miner

Nice! You did it, even your antivirus system probably went postal and you started covering all your webcams... But here is the bad news again: Since people are using ASIC miners, you just can't compete with your CPU hardware anymore. Even with your more advanced GPU you will have a hard time. The hashrate is too high for a desktop PC to compete with them. The blocks should be mined every 1 minute (or so) and that's causing the difficulty to go up - and we are out... So definitly check what is your hashrate while you are mining, you would need about 1.5 MH/s to make 1 Doge in 24 hours!

Mining Doge

Let us start with a quote:
"Dogecoin Core 1.8 introduces AuxPoW from block 371,337. AuxPoW is a technology which enables miners to submit work done while mining other coins, as work on the Dogecoin block chain."
- langerhans
What does this mean? You could waste your hashrate only on the Dogecoin chain, probably find never a block, but when, you only receive about 10.000 Dogecoins, currently worth about $25. Or you could apply your hashrate to LTC and Doge (and probably even more) at the same time. Your change of solving the block (finding the nonce) is your hashrate divided by the hashrat in sum - and this is about the same for Doge and LTC. This means you will always want to submit your work to all chains available!

Mining solo versus pool

So let's face it - mining solo won't get you anywhere, so let's mine on a pool! If you have a really bad Hashrate, please consider that: Often you need about $1 or $2 worth of crypto to receive a payout (without fees). This means, you have to get there. With 100 MH/s on prohashing, it takes about 6 days, running 24/7 to get to that threshold. Now you can do the math... 1 MH/s = 1000 KH/s, if you are below 1 MH/s, you probably won't have fun.

Buying an ASIC

You found an old BTC USB-miner with 24 GH/s (1 GH/s = 1000 MH/s) for $80 bucks - next stop lambo!? Sorry, bad news again, this hashrate is for SHA-256! If you want to mine LTC/Doge you will need a miner using scrypt with quite lower numbers on the hashrate per second, so don't fall for that. Often when you have a big miner (= also loud), you get more Hashrate per $ spent on the miner, but most will still run on a operational loss, because the electricity is too expensive and the miners will be outdated soon again. Leading me to my next point...

Making profit

You won't make money running your miner. Just do the math: What if you would have bougth a miner 1 year ago? Substract costs for electricity and then compare to: What if you just have bought coins. In most cases you would have a greater profit by just buying coins, maybe even with a "stable" coin like Doges.

Cloud Mining

Okay, this was a lot of text and you are still on the hook? Maybe you are desperated enough to invest in some cloud mining contract... But this isn't a good idea either, because most of such contracts are scams based on a ponzi scheme. You often can spot them easy, because they guarantee way to high profits, or they fake payouts that never happened, etc.
Just a thought: If someone in a subway says to you: Give me $1 and lets meet in one year, right here and I give you $54,211,841, you wouldn't trust him and if some mining contract says they will give you 5% a day it is basically the same.
Also rember the merged mining part. Nobody would offer you to mine Doges, they would offer you to buy a hashrate for scrypt that will apply on multiple chains.

Alternative coins

Maybe try to mine a coin where you don't have ASICs yet, like Monero and exchange them to Doge. If somebody already tried this - feel free to add your thoughts!

Folding at Home (Doge)

Some people say folding at home (FAH - https://www.dogecoinfah.com/) still the best. I just installed the tool and it says I would make 69.852 points a day, running on medium power what equates to 8 Doges. It is easy, it was fun, but it isn't much.
Thanks for reading
_nformant
submitted by _nformant to dogecoin [link] [comments]

05-24 00:54 - 'Topic: [Quantum computing] Reason: [SHA-256 encryption breaking]' (self.Bitcoin) by /u/Xyopsi removed from /r/Bitcoin within 42-52min

'''
After the years of successful advancements of quantum computing, I have been worrying about Bitcoin and it's future. I've done research about quantum computing and it's capabilities and it's not looking too good for our beloved cryptocurrency because it might have a security flaw. With quantum computing the SHA-256 (that secures Bitcoin) algorithm can be broken later in the future with the advancements with quantum computing. I'm not saying it's going to happen tomorrow but there is a chance that cryptography protocols are going to have to change to ensure the integrity of bitcoin and it's future. This is hypothetical though, not to fear monger or troll but this needs to be a discussion on which people can share opinions about this topic and come up solutions to prevent keys to be solved by in which the government or tech companies like Google, Amazon, etc can crack. I feel that this is important to discuss about and I care about the future of bitcoin and other cryptocurrencies and it's contributers and holders.
Sources used: [link]1
[link]2
[link]3
[link]4
[link]5
Edit: Thanks u/jenny82ishere for fact checking me. The SHA-256 algorithm is not encryption.
'''
Topic: [Quantum computing] Reason: [SHA-256 encryption breaking]
Go1dfish undelete link
unreddit undelete link
Author: Xyopsi
1: b*oc**hainhub.net/bl**/*lo*/cryptogra*hy-**ockc**in-b*tc**n/ 2: www.sci***edai*y.com/news/*a**er*energy/qu*ntum_co****i*g/ 3: www.*oogle.**m/a*p/s/ww*.science*ews.org/ar**cl*/n**-***nt****om*u*ers-can-*pe*ate**ig**r-temperatures/amp 4: en.m.wik*ped**.or*/wiki/**A-* 5: en.bitco*n**t*wi*i/Wall*t_en*ryp*io*
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

Tron v10.9.2 (2020-01-19) // bugfixes; improved network detection code

Background

Tron is a script that "fights for the User." Think of it as a tech on a thumb drive that automates ~87% of the tedious work in cleaning a Windows system, with some things left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.9.2 (2020-01-19)
! MBAM bugfixes in Stage 3
* Improved network detection code in initialize_environment.bat, thanks to u/McGanondorf

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]

Tron v10.8.9 (2020-01-11) // Fix Internet Connectivity Check bug; fix obscure MBAM launch bug; fix SIV crash on Win10 Insider builds

Background

Tron is a script that "fights for the User." Think of it as a Tech on a thumb drive that automates ~85% of the tedious work in cleaning a Windows system, with some things left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.9.0 (2020-01-13)
! Fix script-breaking syntax bug in Stage 3
v10.8.9 (2020-01-11)
! Fix bluescreen/greenscreen crash on Win10 insider builds when pulling system information using siv.exe. Thanks to u/iamzacharyrs
! Fix error where we'd attempt to launch %MBAM% but the variable was empty. Thanks to u/thementallydeceased
! Fix bug where we were inadvertently disabling the Internet Connectivity Check, which makes Office 365 unhappy. Thanks to u/shadenoah
* Definition and sub-tool 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-TX 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 contained 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 waste money here:
and I guarantee it will go to waste
  • 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]

Tron v10.9.1 (2020-01-16) // Stage 3 bugfixes

Background

Tron is a script that "fights for the User." Think of it as a tech on a thumb drive that automates ~87% of the tedious work in cleaning a Windows system, with some things left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.9.1 (2020-01-16)
! More bugfixes in Stage 3

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-TX 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]

How to Create Your Own Cryptocurrency Using Python 2020

A blockchain is a public database that irreversibly documents and authenticates the possession and transmission of digital assets. Digital currencies, like Bitcoin and Ethereum, are based on this concept. Blockchain is an exciting technology that you can use to transform the capabilities of your applications.
Of late, we’ve been seeing governments, organizations, and individuals using the blockchain technology to create their own cryptocurrencies—and avoid being left behind. Notably, when Facebook proposed its own cryptocurrency, called Libra, the announcement stirred many waters across the world.

What if you could also follow suit and create your own version of a cryptocurrency?

I thought about this and decided to develop an algorithm that creates a crypto.
I decided to call the cryptocurrency fccCoin.
In this tutorial, I’m going to illustrate the step-by-step process I used to build the digital currency (I used the object-oriented concepts of the Python programming language).
Here is the basic blueprint of the blockchain algorithm for creating the fccCoin:
class Block: def __init__(): #first block class pass def calculate_hash(): #calculates the cryptographic hash of every block class BlockChain: def __init__(self): # constructor method pass def construct_genesis(self): # constructs the initial block pass def construct_block(self, proof_no, prev_hash): # constructs a new block and adds it to the chain pass u/staticmethod def check_validity(): # checks whether the blockchain is valid pass def new_data(self, sender, recipient, quantity): # adds a new transaction to the data of the transactions pass u/staticmethod def construct_proof_of_work(prev_proof): # protects the blockchain from attack pass u/property def last_block(self): # returns the last block in the chain return self.chain[-1]
Now, let me explain what is taking place…
1. Building the first Block class A blockchain comprises of several blocks that are joined to each other (that sounds familiar, right?).
The chaining of blocks takes place such that if one block is tampered with, the rest of the chain becomes invalid.
In applying the above concept, I created the following initial block class
import hashlib import time class Block: def __init__(self, index, proof_no, prev_hash, data, timestamp=None): self.index = index self.proof_no = proof_no self.prev_hash = prev_hash self.data = data self.timestamp = timestamp or time.time() u/property def calculate_hash(self): block_of_string = “{}{}{}{}{}”.format(self.index, self.proof_no, self.prev_hash, self.data, self.timestamp) return hashlib.sha256(block_of_string.encode()).hexdigest() def __repr__(self): return “{} – {} – {} – {} – {}”.format(self.index, self.proof_no, self.prev_hash, self.data, self.timestamp)
As you can see from the code above, I defined the __init__() function, which will be executed when the Block class is being initiated, just like in any other Python class.
I provided the following parameters to the initiation function:
self—this refers to the instance of the Block class, making it possible to access the methods and attributes associated with the class; index—this keeps track of the position of the block within the blockchain; proof_no—this is the number produced during the creation of a new block (called mining); prev_hash—this refers to the hash of the previous block within the chain; data—this gives a record of all transactions completed, such as the quantity bought; timestamp—this places a timestamp for the transactions. The second method in the class, calculate_hash, will generate the hash of the blocks using the above values. The SHA-256 module is imported into the project to assist in obtaining the hashes of the blocks.
After the values have been inputted into the cryptographic hash algorithm, the function will return a 256-bit string representing the contents of the block.
This is how security is achieved in blockchains—every block will have a hash and that hash will rely on the hash of the previous block.
As such, if someone tries to compromise any block in the chain, the other blocks will have invalid hashes, leading to disruption of the entire blockchain network.
Ultimately, a block will look like this:
{ “index”: 2, “proof”: 21, “prev_hash”: “6e27587e8a27d6fe376d4fd9b4edc96c8890346579e5cbf558252b24a8257823”, “transactions”: [ {‘sender’: ‘0’, ‘recipient’: ‘Quincy Larson’, ‘quantity’: 1} ], “timestamp”: 1521646442.4096143 }
2. Building the Blockchain class The main idea of a blockchain, just as the name implies, involves “chaining” several blocks to one another.
Therefore, I’m going to construct a Blockchain class that will be useful in managing the workings of the whole chain. This is where most of the action is going to take place.
The Blockchain class will have various helper methods for completing various tasks in the blockchain.
Let me explain the role of each of the methods in the class.
a. Constructor method This method ensures the blockchain is instantiated.
class BlockChain: def __init__(self): self.chain = [] self.current_data = [] self.nodes = set() self.construct_genesis()
Here are the roles of its attributes:
b. Constructing the genesis block The blockchain requires a construct_genesis method to build the initial block in the chain. In the blockchain convention, this block is special because it symbolizes the start of the blockchain.
In this case, let’s construct it by simply passing some default values to the construct_block method.
I gave both proof_no and prev_hash a value of zero, although you can provide any value you want.
def construct_genesis(self): self.construct_block(proof_no=0, prev_hash=0) def construct_block(self, proof_no, prev_hash): block = Block( index=len(self.chain), proof_no=proof_no, prev_hash=prev_hash, data=self.current_data) self.current_data = [] self.chain.append(block) return block
c. Constructing new blocks
The construct_block method is used for creating new blocks in the blockchain.
Here is what is taking place with the various attributes of this method:
d. Checking validity
The check_validity method is important in assessing the integrity of the blockchain and ensuring anomalies are absent.
As mentioned earlier, hashes are essential for the security of the blockchain as even the slightest change in the object will lead to the generation of a completely new hash.
Therefore, this check_validity method uses if statements to check whether the hash of every block is correct.
It also verifies if every block points to the right previous block, through comparing the value of their hashes. If everything is correct, it returns true; otherwise, it returns false.
u/staticmethod def check_validity(block, prev_block): if prev_block.index + 1 != block.index: return False elif prev_block.calculate_hash != block.prev_hash: return False elif not BlockChain.verifying_proof(block.proof_no, prev_block.proof_no): return False elif block.timestamp <= prev_block.timestamp: return False return True
e. Adding data of transactions
The new_data method is used for adding the data of transactions to a block. It’s a very simple method: it accepts three parameters (sender’s details, receiver’s details, and quantity) and append the transaction data to self.current_data list.
Anytime a new block is created, this list is allocated to that block and reset once more as explained in the construct_block method.
Once the transaction data has been added to the list, the index of the next block to be created is returned.
This index is calculated by adding 1 to the index of the current block (which is the last in the blockchain). The data will assist a user in submitting the transaction in future.
def new_data(self, sender, recipient, quantity): self.current_data.append({ ‘sender’: sender, ‘recipient’: recipient, ‘quantity’: quantity }) return True
f. Adding proof of work
Proof of work is a concept that prevents the blockchain from abuse. Simply, its objective is to identify a number that solves a problem after a certain amount of computing work is done.
If the difficulty level of identifying the number is high, it discourages spamming and tampering with the blockchain.
In this case, we’ll use a simple algorithm that discourages people from mining blocks or creating blocks easily.
u/staticmethod def proof_of_work(last_proof): ”’this simple algorithm identifies a number f’ such that hash(ff’) contain 4 leading zeroes f is the previous f’ f’ is the new proof ”’ proof_no = 0 while BlockChain.verifying_proof(proof_no, last_proof) is False: proof_no += 1 return proof_no u/staticmethod def verifying_proof(last_proof, proof): #verifying the proof: does hash(last_proof, proof) contain 4 leading zeroes? guess = f'{last_proof}{proof}’.encode() guess_hash = hashlib.sha256(guess).hexdigest() return guess_hash[:4] == “0000”
g. Getting the last block
Lastly, the latest_block method is a helper method that assists in obtaining the last block in the blockchain. Remember that the last block is actually the current block in the chain.
u/property def latest_block(self): return self.chain[-1]
Let’s sum everything together
Here is the entire code for creating the fccCoin cryptocurrency.
You can also get the code on this GitHub repository.
import hashlib import time class Block: def __init__(self, index, proof_no, prev_hash, data, timestamp=None): self.index = index self.proof_no = proof_no self.prev_hash = prev_hash self.data = data self.timestamp = timestamp or time.time() u/property def calculate_hash(self): block_of_string = “{}{}{}{}{}”.format(self.index, self.proof_no, self.prev_hash, self.data, self.timestamp) return hashlib.sha256(block_of_string.encode()).hexdigest() def __repr__(self): return “{} – {} – {} – {} – {}”.format(self.index, self.proof_no, self.prev_hash, self.data, self.timestamp) class BlockChain: def __init__(self): self.chain = [] self.current_data = [] self.nodes = set() self.construct_genesis() def construct_genesis(self): self.construct_block(proof_no=0, prev_hash=0) def construct_block(self, proof_no, prev_hash): block = Block( index=len(self.chain), proof_no=proof_no, prev_hash=prev_hash, data=self.current_data) self.current_data = [] self.chain.append(block) return block u/staticmethod def check_validity(block, prev_block): if prev_block.index + 1 != block.index: return False elif prev_block.calculate_hash != block.prev_hash: return False elif not BlockChain.verifying_proof(block.proof_no, prev_block.proof_no): return False elif block.timestamp <= prev_block.timestamp: return False return True def new_data(self, sender, recipient, quantity): self.current_data.append({ ‘sender’: sender, ‘recipient’: recipient, ‘quantity’: quantity }) return True u/staticmethod def proof_of_work(last_proof): ”’this simple algorithm identifies a number f’ such that hash(ff’) contain 4 leading zeroes f is the previous f’ f’ is the new proof ”’ proof_no = 0 while BlockChain.verifying_proof(proof_no, last_proof) is False: proof_no += 1 return proof_no u/staticmethod def verifying_proof(last_proof, proof): #verifying the proof: does hash(last_proof, proof) contain 4 leading zeroes? guess = f'{last_proof}{proof}’.encode() guess_hash = hashlib.sha256(guess).hexdigest() return guess_hash[:4] == “0000” u/property def latest_block(self): return self.chain[-1] def block_mining(self, details_miner): self.new_data( sender=”0″, #it implies that this node has created a new block receiver=details_miner, quantity= 1, #creating a new block (or identifying the proof number) is awarded with 1 ) last_block = self.latest_block last_proof_no = last_block.proof_no proof_no = self.proof_of_work(last_proof_no) last_hash = last_block.calculate_hash block = self.construct_block(proof_no, last_hash) return vars(block) def create_node(self, address): self.nodes.add(address) return True u/staticmethod def obtain_block_object(block_data): #obtains block object from the block data return Block( block_data[‘index’], block_data[‘proof_no’], block_data[‘prev_hash’], block_data[‘data’], timestamp=block_data[‘timestamp’])
Now, let’s test our code to see if it works.
blockchain = BlockChain() print(“***Mining fccCoin about to start***”) print(blockchain.chain) last_block = blockchain.latest_block last_proof_no = last_block.proof_no proof_no = blockchain.proof_of_work(last_proof_no) blockchain.new_data( sender=”0″, #it implies that this node has created a new block recipient=”Quincy Larson”, #let’s send Quincy some coins! quantity= 1, #creating a new block (or identifying the proof number) is awarded with 1 ) last_hash = last_block.calculate_hash block = blockchain.construct_block(proof_no, last_hash) print(“***Mining fccCoin has been successful***”) print(blockchain.chain)
It worked!
Here is the output of the mining process:
***Mining fccCoin about to start*** [0 – 0 – 0 – [] – 1566930640.2707076] ***Mining fccCoin has been successful*** [0 – 0 – 0 – [] – 1566930640.2707076, 1 – 88914 – a8d45cb77cddeac750a9439d629f394da442672e56edfe05827b5e41f4ba0138 – [{‘sender’: ‘0’, ‘recipient’: ‘Quincy Larson’, ‘quantity’: 1}] – 1566930640.5363243]
Conclusion
There you have it!
That’s how you could create your own blockchain using Python.
Let me say that this tutorial just demonstrates the basic concepts for getting your feet wet in the innovative blockchain technology.
If this coin were deployed as-is, it could not meet the present market demands for a stable, secure, and easy-to-use cryptocurrency.
Therefore, it can still be improved by adding additional features to enhance its capabilities for mining and sending financial transactions.
Nonetheless, it’s a good starting point if you decide to make your name known in the amazing world of cryptos.
If you have any comments or questions, please post them below.
Happy (crypto) coding!
Source: Cryptoors
submitted by djkloud to CryptoTechnology [link] [comments]

Tron v10.8.8 (2019-12-14) // Possible fix for "pinned items" clearing; disable clearing of "Recently Opened Documents"; update all definition files and sub-tools

Background

Tron is a script that "fights for the User." Think of it as a Tech on a thumb drive that automates ~85% of the tedious work in cleaning a Windows system, with some things left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.8.8 (2019-11-03)
! Possible fix for clearing of "pinned items"
* Disable clearing of "Recently Opened Documents"
* Definition and sub-tool 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-TX 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 contained 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 waste money here:
and I guarantee it will go to waste
  • 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 anytime 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]

Tron v10.8.7 (2019-11-03) // Run Windows Disk Cleanup; remove cached NVIDIA drivers; fix "some settings are managed by your organization" bug

Background

Tron is a script that "fights for the User." Think of it as a Tech on a thumb drive that automates ~85% of the tedious work in cleaning a Windows system, with the understanding that some things are better left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.8.7 (2019-11-03)
+ Add running of built-in Windows Disk Cleanup. Thanks to u/thementallydeceased
- Skip Bleachbit on Windows XP since as of v3 Bleachbit dropped support for XP
+ Add removal of cached NVIDIA driver installers. Thanks to u/strifethe9tailedfox
- Remove deletion of built-in Windows wallpaper images. On modern systems the space use is negligible
- Remove "activate deferring of updates" due to community request
* Update all sub-tools, SSD drive identifiers, definition files and de-bloat lists

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-TX 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 ~500MB 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

\tron\integrity_verification\checksums.txt contains SHA-256 hashes and is 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 waste money here:
and I guarantee it will go to waste
  • 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 anytime 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]

Tron v10.8.6 (2019-10-09) // Run SFC /scannow prior to DISM repair; skip MBAM install & run directly if already installed

Background

Tron is a script that "fights for the User." Think of it as a tech-on-a-thumb-drive that aims to automate ~85% of the tedious work in cleaning a Windows system, with the understanding that some things are better left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.8.6 (2019-10-09)
* improvement: Run DISM repair prior to SFC /scannow, per MS best practices. Thanks to u/b_sen
* mbam: Skip install of MBAM and directly launch if it already exists. Thanks to u/RedBaron2
* Update all sub-tools, definition files and de-bloat lists

Download

  1. Primary method: Download the .torrent.
  2. Primary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-TX 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-TX u/RB14060 (XygenHosting)
    #6 link --- US-MI u/ajcutshall
    #7 link --- AU u/agent-squirrel
    #8 link --- Amazon CDN u/helpdesktv
    #9 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
    Tron 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 ~550MB package, Github is a good place to do it.

Command-Line Support

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

Integrity

\tron\integrity_verification\checksums.txt contains SHA-256 checksums for every file and is signed with my PGP key; included. You can use this to verify pack integrity.

Donations

Tron will always be free and open-source, though of course donations are appreciated since the work done on the project is in my spare time for free. If you feel overly charitable you can donate using one of these methods:
  • 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. mirror operator like the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

Please first look here for a list of common (Tron appearing to be stalled, etc). If it doesn't answer your issue, make a top-level post to the /TronScript subreddit and myself or one of the community members will take a look at the issue. Additionally, you can reach me anytime on Keybase.
In the folder \integrity verification the file checksums.txt is signed with my PGP key (0x07d1490f82a211a2, pubkey included). You can use this to verify package integrity.
"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]

Bitcoin’s Security and Hash Rate Explained

Bitcoin’s Security and Hash Rate Explained
As the Bitcoin hash rate reaches new all-time highs, there’s never been a better time to discuss blockchain security and its relation to the hashing power and the Proof of Work (PoW) that feed the network. The Bitcoin system is based on a form of decentralized trust, heavily relying on cryptography. This makes its blockchain highly secure and able to be used for financial transactions and other operations requiring a trustless ledger.
Far from popular belief, cryptography dates back to thousands of years ago. The same root of the word encryption — crypt — comes from the Greek word ‘kryptos’, meaning hidden or secret. Indeed, humans have always wanted to keep some information private. The Assyrians, the Chinese, the Romans, and the Greeks, they all tried over the centuries to conceal some information like trade deals or manufacturing secrets by using symbols or ciphers carved in stone or leather. In 1900 BC, Egyptians used hieroglyphics and experts often refer to them as the first example of cryptography.
Back to our days, Bitcoin uses cryptographic technologies such as:
  1. Cryptographic hash functions (i.e. SHA-256 and RIPEMD-160)
  2. Public Key Cryptography (i.e. ECDSA — the Elliptic Curve Digital Signature Algorithm)
While Public Key Cryptography, bitcoin addresses, and digital signatures are used to provide ownership of bitcoins, the SHA-256 hash function is used to verify data and block integrity and to establish the chronological order of the blockchain. A cryptographic hash function is a mathematical function that verifies the integrity of data by transforming it into a unique unidentifiable code.
Here is a graphic example to make things more clear:

– Extract from the MOOC (Massive Open Online Course) in Digital Currencies at the University of Nicosia.
Furthermore, hash functions are used as part of the PoW algorithm, which is a prominent part of the Bitcoin mining algorithm and this is what is of more interest to understand the security of the network. Mining creates new bitcoins in each block, almost like a central bank printing new money and creates trust by ensuring that transactions are confirmed only when enough computational power is devoted to the block that contains them. More blocks mean more computation, which means more trust.
With PoW, miners compete against each other to complete transactions on the network and get rewarded. Basically they need to solve a complicated mathematical puzzle and a possibility to easily prove the solution. The more hashing power, the higher the chance to resolve the puzzle and therefore perform the proof of work. In more simple words, bitcoins exist thanks to a peer to peer network that helps validate transactions in the ledger and provides enough trust to avoid that a third party is involved in the process. It also exists because miners give it life by resolving that computational puzzle, through the mining reward incentive they are receiving.
For more info, contact Block.co directly or email at [email protected].
Tel +357 70007828
Get the latest from Block.co, like and follow us on social media:
✔️Facebook
✔️LinkedIn
✔️Twitter
✔️YouTube
✔️Medium
✔️Instagram
✔️Telegram
✔️Reddit
✔️GitHub
submitted by BlockDotCo to u/BlockDotCo [link] [comments]

Waltonchain adds GNU General Public License details to code - BUT does the code contain this?

Waltonchain adds GNU General Public License details to code - BUT does the code contain this?
Dear Crypto community,
Yesterday we saw Waltonchain release their Open Source code which resulted in huge criticism regarding the oversight of removing the original copyright to the original codebase, Ethereum Go, on which it is based.
Following this, the team have now updated the code to show the original copyright:
Image from Github
Source: https://github.com/WaltonChain/WaltonChain_Gwtc_Src/blob/mastep2p/rlpx.go?utm_source=share&utm_medium=ios_app
Github: https://github.com/WaltonChain?tab=repositories

I'd like to say thank you to the community for having such strong opinion on this matter, and for all the subreddit admins that assisted in creating clarity toward this. As a global community we should hold every blockchain up to the same standards, and I am grateful that this was shown in regard to the GNU General Public License.

Now that the issue is resolved, and since Waltonchain is currently a hot topic, I implore all the coders and devs out there to delve deep into the code to see exactly what Waltonchain have released. Not just the modification to the eth codebase, but the additional code. What does the code allow?

What we've been told as a community is that the Waltonchain source code has changes that allows for:
  • Security - DASH X11 - Most cryptographic algorithms used in cryptocurrencies use only one hash function for calculation. There are 11 of them in X11, which provides a higher degree of protection against hackers and scams. Waltonchain has customised the DASH X11 hashing algorithm to fit their purpose.
  • More secure than Bitcoin. The Bitcoin algorithm is SHA-256 is based on a previous secure hash algorithm family of standards, namely SHA-2, the hash functions within the X11 algorithm all successfully made it into the second-round in search for a new, more secure standard — SHA-3. Keccak, the function which won the competition and is therefore the new standard on which SHA-3 is based on, can at the very least be considered more secure that SHA-256.
  • Efficiency — Waltonchain have produced ASICs with the equivalent hashing power of 200GPUs (32–40kW) whilst using only 135W, thus helping the parent chain become decentralised
  • PoS aspect works in tandem with PoW, in that it adds a reduced difficulty based on number of coins held and time between blocks. Effectively the longer coins are held and the longer the time between blocks, the lower the difficulty for mining blocks. This again enhances the power efficiency of the network in its entirety.
  • Fast cross-chain searching via Proof of Labour —PoL enables hash values or indices from sub-chains (child chains) to be synced with the parent chain in a ‘cross chain index mechanism’ to enable fast searches for data via the parent chain.
  • Scalibility — Unlimited scalibility due to child chains; each CC is an independent blockchain (or DAG) using its own consensus mechanism (PoS, PoA, PoW, PoeT, etc) and can store data within itself. The parent chain by nature therefore cannot become bloated.
  • Atomic Swaps — PoL by nature ensures a record of every inter-chain transaction is held, and allows the function of atomic swaps between currencies.

Also to note is that the code has been audited by Knownsec, the same company that audited projects like HPB and NANO.

Lets have an open dialogue and talk about these features of the code - but firstly, do they exist? Hopefully people will approach this with the same enthusiasm as they did yesterday.

EDIT 1st June: A user on the Waltonchain sub has done an analysis which by the looks of it, disproves the initial assessment by many of the 'blockchain experts' in cc that have said the open source code is simply a copy and paste . https://www.reddit.com/waltonchain/comments/bveqea/changeset_goethereum_v171_to_gwtc_v110/
It is interesting to see just how much people love to hate Waltonchain that they spread misinformation either intentionally, or unintentionally, and that it gets the most attention out of any announcement.

For reference:
Block explorer: www.Waltonchain.pro (all wallets, mining wallet, documentation etc is available via that link)
submitted by Yayowam to CryptoCurrency [link] [comments]

Tron v10.8.5 (2019-09-09) // Fix Sophos bug; Fix Xbox service disabling bug; definition updates

Background

Tron is a script that "fights for the User." Think of it as a tech-on-a-thumb-drive that aims to automate ~85% of the tedious work in cleaning a Windows system, with the understanding that some things are better left to the discretion of the tech. It is built with heavy reliance on community input and updated regularly.

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)
v10.8.5 (2019-09-08)
! ! Fix (rare) bug where Sophos would fail to delete its service after running. Thanks to u/Nightfoxsd420
! Switch Xbox service startup status to "manual" vs. "disabled". Thanks to u/EnderProGaming
* Update all sub-tools, definition files and de-bloat lists

Download

  1. Primary method: Download the .torrent.
  2. Primary: Download a self-extracting .exe pack from one of the mirrors:
    Mirror HTTPS HTTP Location Host
    Official link link US-TX 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-TX u/RB14060 (XygenHosting)
    #6 link --- US-MI u/ajcutshall
    #7 link --- AU u/agent-squirrel
    #8 link --- Amazon CDN u/helpdesktv
    #9 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
    Tron 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 ~550MB package, Github is a good place to do it.

Command-Line Support

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

Integrity

\tron\integrity_verification\checksums.txt contains SHA-256 checksums for every file and is signed with my PGP key; included. You can use this to verify pack integrity.

Donations

Tron will always be free and open-source, though of course donations are appreciated since the work done on the project is in my spare time for free. If you feel overly charitable you can donate using one of these methods:
  • 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. mirror operator like the incredibly generous u/SGC-Hosting) please contact them directly.

Problems and Support

If you have an issue with Tron, please first look here for a list of common issues and solutions (Tron appearing to be stalled, etc). If it doesn't answer your issue, please make a top-level post to the /TronScript subreddit and myself or one of the community members will take a look at the issue. Please report bugs so that we can fix them!
"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]

CODE FUD: Resolved.

Dear Waltonchain community,
Yesterday we saw Waltonchain release their Open Source code which resulted in huge criticism regarding the oversight of removing the original copyright to the original codebase, Ethereum Go, on which it is based.
Following this, the team have now updated the code to show the original copyright:
Source: https://github.com/WaltonChain/WaltonChain_Gwtc_Src/blob/mastep2p/rlpx.go?utm_source=share&utm_medium=ios_app
Github: https://github.com/WaltonChain?tab=repositories

I'd like to say thank you to the community for having such strong opinion on this matter, and for all the subreddit admins that assisted in creating clarity toward this. As a global community we should hold every blockchain up to the same standards, and I am grateful that this was shown in regard to the GNU General Public License.

Now that the issue is resolved, and since Waltonchain is currently a hot topic, I implore all the coders and devs out there to delve deep into the code to see exactly what Waltonchain have released. Not just the modification to the eth codebase, but the additional code. What does the code allow?

What we've been told as a community is that the Waltonchain source code has changes that allows for:

Also to note is that the code has been audited by Knownsec, the same company that audited projects like HPB and NANO.

Lets have an open dialogue and talk about these features of the code - but firstly, do they exist? Hopefully people will approach this with the same enthusiasm as they did yesterday.

For reference:
Block explorer: www.Waltonchain.pro (all wallets, mining wallet, documentation etc is available via that link)
submitted by Yayowam to waltonchain [link] [comments]

Looking back 18 months.

I was going through old emails today and came across this one I sent out to family on January 4, 2018. It was a reflection on the 2017 crypto bull market and where I saw it heading, as well as some general advice on crypto, investment, and being safe about how you handle yourself in cryptoland.
I feel that we are on the cusp of a new bull market right now, so I thought that I would put this out for at least a few people to see *before* the next bull run, not after. While the details have changed, I don't see a thing in this email that I fundamentally wouldn't say again, although I'd also probably insist that people get a Yubikey and use that for all 2FA where it is supported.
Happy reading, and sorry for some of the formatting weirdness -- I cleaned it up pretty well from the original email formatting, but I love lists and indents and Reddit has limitations... :-/
Also, don't laught at my token picks from January 2018! It was a long time ago and (luckliy) I took my own advice about moving a bunch into USD shortly after I sent this. I didn't hit the top, and I came back in too early in the summer of 2018, but I got lucky in many respects.
----------------------------------------------------------------------- Jan-4, 2018
Hey all!
I woke up this morning to ETH at a solid $1000 and decided to put some thoughts together on what I think crypto has done and what I think it will do. *******, if you could share this to your kids I’d appreciate it -- I don’t have e-mail addresses, and it’s a bit unwieldy for FB Messenger… Hopefully they’ll at least find it thought-provoking. If not, they can use it as further evidence that I’m a nutjob. 😉
Some history before I head into the future.
I first mined some BTC in 2011 or 2012 (Can’t remember exactly, but it was around the Christmas holidays when I started because I had time off from work to get it set up and running.) I kept it up through the start of summer in 2012, but stopped because it made my PC run hot and as it was no longer winter, ********** didn’t appreciate the sound of the fans blowing that hot air into the room any more. I’ve always said that the first BTC I mined was at $1, but looking back at it now, that’s not true – It was around $2. Here’s a link to BTC price history.
In the summer of 2013 I got a new PC and moved my programs and files over before scrapping the old one. I hadn’t touched my BTC mining folder for a year then, and I didn’t even think about salvaging those wallet files. They are now gone forever, including the 9-10BTC that were in them. While I can intellectually justify the loss, it was sloppy and underlines a key thing about cryptocurrency that I believe will limit its widespread adoption by the general public until it is addressed and solved: In cryptoland, you are your own bank, and if you lose your password or account number, there is no person or organization that can help you reset it so that you can get access back. Your money is gone forever.
On April 12, 2014 I bought my first BTC through Coinbase. BTC had spiked to $1000 and been in the news, at least in Japan. This made me remember my old wallet and freak out for a couple of months trying to find it and reclaim the coins. I then FOMO’d (Fear Of Missing Out”) and bought $100 worth of BTC. I was actually very lucky in my timing and bought at around $430. Even so, except for a brief 50% swing up almost immediately afterwards that made me check prices 5 times a day, BTC fell below my purchase price by the end of September and I didn’t get back to even until the end of 2015.
In May 2015 I bought my first ETH at around $1. I sent some guy on bitcointalk ~$100 worth of BTC and he sent me 100 ETH – all on trust because the amounts were small and this was a small group of people. BTC was down in the $250 range at that point, so I had lost 30-40% of my initial investment. This was of the $100 invested, so not that much in real terms, but huge in percentages. It also meant that I had to buy another $100 of BTC on Coinbase to send to this guy. A few months after I purchased my ETH, BTC had doubled and ETH had gone down to $0.50, halving the value of my ETH holdings. I was even on the first BTC purchase finally, but was now down 50% on the ETH I had bought.
The good news was that this made me start to look at things more seriously. Where I had skimmed white papers and gotten a superficial understanding of the technology before FOMO’ing, I started to act as an investor, not a speculator. Let me define how I see those two different types of activity:
So what has been my experience as an investor? After sitting out the rest of 2015 because I needed to understand the market better, I bought into ETH quite heavily, with my initial big purchases being in March-April of 2016. Those purchases were in the $11-$14 range. ETH, of course, dropped immediately to under $10, then came back and bounced around my purchase range for a while until December of 2016, when I purchased a lot more at around $8.
I also purchased my first ICO in August of 2016, HEAT. I bought 25ETH worth. Those tokens are now worth about half of their ICO price, so about 12.5ETH or $12500 instead of the $25000 they would be worth if I had just kept ETH. There are some other things with HEAT that mean I’ve done quite a bit better than those numbers would suggest, but the fact is that the single best thing I could have done is to hold ETH and not spend the effort/time/cost of working with HEAT. That holds true for about every top-25 token on the market when compared to ETH. It certainly holds true for the many, many tokens I tried to trade in Q1-Q2 of 2017. In almost every single case I would have done better and slept better had I just held ETH instead of trying to be smarter than Mr. Market.
But, I made money on all of them except one because the crypto market went up more in USD terms than any individual coin went down in ETH or BTC terms. This underlines something that I read somewhere and that I take to heart: A rising market makes everyone seem like a genius. A monkey throwing darts at a list of the top 100 cryptocurrencies last year would have doubled his money. Here’s a chart from September that shows 2017 year-to-date returns for the top 10 cryptocurrencies, and all of them went up a *lot* more between then and December. A monkey throwing darts at this list there would have quintupled his money.
When evaluating performance, then, you have to beat the monkey, and preferably you should try to beat a Wall Street monkey. I couldn’t, so I stopped trying around July 2017. My benchmark was the BLX, a DAA (Digital Asset Array – think fund like a Fidelity fund) created by ICONOMI. I wasn’t even close to beating the BLX returns, so I did several things.
  1. I went from holding about 25 different tokens to holding 10 now. More on that in a bit.
  2. I used those funds to buy ETH and BLX. ETH has done crazy-good since then and BLX has beaten BTC handily, although it hasn’t done as well as ETH.
  3. I used some of those funds to set up an arbitrage operation.
The arbitrage operation is why I kept the 11 tokens that I have now. All but a couple are used in an ETH/token pair for arbitrage, and each one of them except for one special case is part of BLX. Why did I do that? I did that because ICONOMI did a better job of picking long-term holds than I did, and in arbitrage the only speculative thing you must do is pick the pairs to trade. My pairs are (No particular order):
I also hold PLU, PLBT, and ART. These two are multi-year holds for me. I have not purchased BTC once since my initial $200, except for a few cases where BTC was the only way to go to/from an altcoin that didn’t trade against ETH yet. Right now I hold about the same 0.3BTC that I held after my first $100 purchase, so I don’t really count it.
Looking forward to this year, I am positioning myself as follows:
Looking at my notes, I have two other things that I wanted to work into this email that I didn’t get to, so here they are:
  1. Just like with free apps and other software, if you are getting something of value and you didn’t pay anything for it, you need to ask why this is. With apps, the phrase is “If you didn’t pay for the product, you are the product”, and this works for things such as pump groups, tips, and even technical analysis. Here’s how I see it.
    1. People don’t give tips on stocks or crypto that they don’t already own that stock or token. Why would they, since if they convince anyone to buy it, the price only goes up as a result, making it more expensive for them to buy in? Sure, you will have friends and family that may do this, but people in a crypto club, your local cryptocurrency meetup, or online are generally not your friends. They are there to make money, and if they can get you to help them make money, they will do it. Pump groups are the worst of these, and no matter how enticing it may look, stay as far away as possible from these scams. I even go so far as to report them when I see them advertise on FB or Twitter, because they are violating the terms of use.
    2. Technical analysis (TA) is something that has been argued about for longer than I’ve been alive, but I think that it falls into the same boat. In short, TA argues that there are patterns in trading that can be read and acted upon to signal when one must buy or sell. It has been used forever in the stock and foreign exchange markets, and people use it in crypto as well. Let’s break down these assumptions a bit.
i. First, if crypto were like the stock or forex markets we’d all be happy with 5-7% gains per year rather than easily seeing that in a day. For TA to work the same way in crypto as it does in stocks and foreign exchange, the signals would have to be *much* stronger and faster-reacting than they work in the traditional market, but people use them in exactly the same way.
ii. Another area where crypto is very different than the stock and forex markets centers around market efficiency theory. This theory says that markets are efficient and that the price reflects all the available information at any given time. This is why gold in New York is similar in price to gold in London or Shanghai, and why arbitrage margins are easily <0.1% in those markets compared to cryptoland where I can easily get 10x that. Crypto simply has too much speculation and not enough professional traders in it yet to operate as an efficient market. That fundamentally changes the way that the market behaves and should make any TA patterns from traditional markets irrelevant in crypto.
iii. There are services, both free and paid that claim to put out signals based on TA for when one should buy and sell. If you think for even a second that they are not front-running (Placing orders ahead of yours to profit.) you and the other people using the service, you’re naïve.
iv. Likewise, if you don’t think that there are people that have but together computerized systems to get ahead of people doing manual TA, you’re naïve. The guys that I have programming my arbitrage bots have offered to build me a TA bot and set up a service to sell signals once our position is taken. I said no, but I am sure that they will do it themselves or sell that to someone else. Basically they look at TA as a tip machine where when a certain pattern is seen, people act on that “tip”. They use software to see that “tip” faster and take a position on it so that when slower participants come in they either have to sell lower or buy higher than the TA bot did. Remember, if you are getting a tip for free, you’re the product. In TA I see a system when people are all acting on free preset “tips” and getting played by the more sophisticated market participants. Again, you have to beat that Wall Street monkey.
  1. If you still don’t agree that TA is bogus, think about it this way: If TA was real, Wall Street would have figured it out decades ago and we would have TA funds that would be beating the market. We don’t.
  2. If you still don’t agree that TA is bogus and that its real and well, proven, then you must think that all smart traders use them. Now follow that logic forward and think about what would happen if every smart trader pushing big money followed TA. The signals would only last for a split second and would then be overwhelmed by people acting on them, making them impossible to leverage. This is essentially what the efficient market theory postulates for all information, including TA.
OK, the one last item. Read this weekly newsletter – You can sign up at the bottom. It is free, so they’re selling something, right? 😉 From what I can tell, though, Evan is a straight-up guy who posts links and almost zero editorial comments.
Happy 2018.
submitted by uetani to CryptoCurrency [link] [comments]

Is Crypto Currency truly at risk due to Quantum Computers, and what can you do about it?

Is Crypto Currency truly at risk due to Quantum Computers, and what can you do about it?

There is no denying that the Quantum revolution is coming. Security protocols for the internet, banking, telecommunications, etc... are all at risk, and your Bitcoins (and alt-cryptos) are next!
This article is not really about quantum computers[i], but, rather, how they will affect the future of cryptocurrency, and what steps a smart investor will take. Since this is a complicated subject, my intention is to provide just enough relevant information without being too “techy.”

The Quantum Evolution

In 1982, Nobel winning physicist, Richard Feynman, hypothesized how quantum computers[ii] would be used in modern life.
Just one year later, Apple released the “Apple Lisa”[iii] – a home computer with a 7.89MHz processor and a whopping 5MB hard drive, and, if you enjoy nostalgia, it used 5.25in floppy disks.
Today, we walk around with portable devices that are thousands of times more powerful, and, yet, our modern day computers still work in a simple manner, with simple math, and simple operators[iv]. They now just do it so fast and efficient that we forget what’s happening behind the scenes.
No doubt, the human race is accelerating at a remarkable speed, and we’ve become obsessed with quantifying everything - from the everyday details of life to the entire universe[v]. Not only do we know how to precisely measure elementary particles, we also know how to control their actions!
Yet, even with all this advancement, modern computers cannot “crack” cryptocurrencies without the use of a great deal more computing power, and since it’s more than the planet can currently supply, it could take millions, if not billions, of years.
However, what current computers can’t do, quantum computers can!
So, how can something that was conceptualized in the 1980’s, and, as of yet, has no practical application, compromise cryptocurrencies and take over Bitcoin?
To best answer this question, let’s begin by looking at a bitcoin address.

What exactly is a Bitcoin address?

Well, in layman terms, a Bitcoin address is used to send and receive Bitcoins, and looking a bit closer (excuse the pun), it has two parts:[vi]
A public key that is openly shared with the world to accept payments. A public key that is derived from the private key. The private key is made up of 256 bits of information in a (hopefully) random order. This 256 bit code is 64 characters long (in the range of 0-9/a-f) and further compressed into a 52 character code (using RIPEMD-160).
NOTE: Although many people talk about Bitcoin encryption, Bitcoin does not use Encryption. Instead, Bitcoin uses a hashing algorithm (for more info, please see endnote below[vii]).
Now, back to understanding the private key:
The Bitcoin address “1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm” translates to a private key of “5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf” which further translates to a 256 bit private key of “0000000000000000000000000000000000000000000000000000000000000001” (this should go without saying, but do not use this address/private key because it was compromised long ago.) Although there are a few more calculations that go behind the scenes, these are the most relevant details.
Now, to access a Bitcoin address, you first need the private key, and from this private key, the public key is derived. With current computers, it’s classically impractical to attempt to find a private key based on a public key. Simply put, you need the private key to know the public key.
However, it has already been theorized (and technically proven) that due to private key compression, multiple private keys can be used to access the same public key (aka address). This means that your Bitcoin address has multiple private keys associated with it, and, if someone accidentally discovers or “cracks” any one of those private keys, they have access to all the funds in that specific address.
There is even a pool of a few dedicated people hunting for these potential overlaps[viii], and they are, in fact, getting very efficient at it. The creator of the pool also has a website listing every possible Bitcoin private key/address in existence[ix], and, as of this writing, the pool averages 204 trillion keys per day!
But wait! Before you get scared and start panic selling, the probability of finding a Bitcoin address containing funds (or even being used) is highly unlikely – nevertheless, still possible!
However, the more Bitcoin users, the more likely a “collision” (finding overlapping private/public key pairs)! You see, the security of a Bitcoin address is simply based on large numbers! How large? Well, according to my math, 1.157920892373x1077 potential private keys exist (that number represents over 9,500 digits in length! For some perspective, this entire article contains just over 14,000 characters. Therefore, the total number of Bitcoin addresses is so great that the probability of finding an active address with funds is infinitesimal.

So, how do Quantum Computers present a threat?

At this point, you might be thinking, “How can a quantum computer defeat this overwhelming number of possibilities?” Well, to put it simple; Superposition and Entanglement[x].
Superposition allows a quantum bit (qbit) to be in multiple states at the same time. Entanglement allows an observer to know the measurement of a particle in any location in the universe. If you have ever heard Einstein’s quote, “Spooky Action at a Distance,” he was talking about Entanglement!
To give you an idea of how this works, imagine how efficient you would be if you could make your coffee, drive your car, and walk your dog all at the same time, while also knowing the temperature of your coffee before drinking, the current maintenance requirements for your car, and even what your dog is thinking! In a nutshell, quantum computers have the ability to process and analyze countless bits of information simultaneously – and so fast, and in such a different way, that no human mind can comprehend!
At this stage, it is estimated that the Bitcoin address hash algorithm will be defeated by quantum computers before 2028 (and quite possibly much sooner)! The NSA has even stated that the SHA256 hash algorithm (the same hash algorithm that Bitcoin uses) is no longer considered secure, and, as a result, the NSA has now moved to new hashing techniques, and that was in 2016! Prior to that, in 2014, the NSA also invested a large amount of money in a research program called “Penetrating Hard Targets project”[xi] which was used for further Quantum Computer study and how to break “strong encryption and hashing algorithms.” Does NSA know something they’re not saying or are they just preemptively preparing?
Nonetheless, before long, we will be in a post-quantum cryptography world where quantum computers can crack crypto addresses and take all the funds in any wallet.

What are Bitcoin core developers doing about this threat?

Well, as of now, absolutely nothing. Quantum computers are not considered a threat by Bitcoin developers nor by most of the crypto-community. I’m sure when the time comes, Bitcoin core developers will implement a new cryptographic algorithm that all future addresses/transactions will utilize. However, will this happen before post-quantum cryptography[xii]?
Moreover, even after new cryptographic implementation, what about all the old addresses? Well, if your address has been actively used on the network (sending funds), it will be in imminent danger of a quantum attack. Therefore, everyone who is holding funds in an old address will need to send their funds to a new address (using a quantum safe crypto-format). If you think network congestion is a problem now, just wait…
Additionally, there is the potential that the transition to a new hashing algorithm will require a hard fork (a soft fork may also suffice), and this could result in a serious problem because there should not be multiple copies of the same blockchain/ledger. If one fork gets attacked, the address on the other fork is also compromised. As a side-note, the blockchain Nebulas[xiii] will have the ability to modify the base blockchain software without any forks. This includes adding new and more secure hashing algorithms over time! Nebulas is due to be released in 2018.

Who would want to attack Bitcoin?

Bitcoin and cryptocurrency represent a threat to the controlling financial system of our modern economy. Entire countries have outright banned cryptocurrency[xiv] and even arrested people[xv], and while discrediting it, some countries are copying cryptocurrency to use (and control) in their economy[xvi]!
Furthermore, Visa[xvii], Mastercard[xviii], Discover[xix], and most banks act like they want nothing to do with cryptocurrency, all the while seeing the potential of blockchain technology and developing their own[xx]. Just like any disruptive technology, Bitcoin and cryptocurrencies have their fair share of enemies!
As of now, quantum computers are being developed by some of the largest companies in the world, as well as private government agencies.
No doubt, we will see a post-quantum cryptography world sooner than most realize. By that point, who knows how long “3 letter agencies” will have been using quantum technology - and what they’ll be capable of!

What can we do to protect ourselves today?

Of course, the best option is to start looking at how Bitcoin can implement new cryptographic features immediately, but it will take time, and we have seen how slow the process can be just for scaling[xxi].
The other thing we can do is use a Bitcoin address only once for outgoing transactions. When quantum computers attack Bitcoin (and other crypto currencies), their first target will be addresses that have outgoing transactions on the blockchain that contain funds.
This is due to the fact that when computers first attempt to crack a Bitcoin address, the starting point is when a transaction becomes public. In other words, when the transaction is first signed – a signed transaction is a digital signature derived from the private key, and it validates the transaction on the network. Compared to classical computers, quantum computers can exponentially extrapolate this information.
Initially, Bitcoin Core Software might provide some level of protection because it only uses an address once, and then sends the remaining balance (if any) to another address in your keypool. However, third party Bitcoin wallets can and do use an address multiple times for outgoing transactions. For instance, this could be a big problem for users that accept donations (if they don’t update their donation address every time they remove funds). The biggest downside to Bitcoin Core Software is the amount of hard-drive space required, as well as diligently retaining an up-to-date copy of the entire blockchain ledger.
Nonetheless, as quantum computers evolve, they will inevitably render SHA256 vulnerable, and although this will be one of the first hash algorithms cracked by quantum computers, it won’t be the last!

Are any cryptocurrencies planning for the post-quantum cryptography world?

Yes, indeed, there are! Here is a short list of ones you may want to know more about:

Full disclosure:

Although I am in no way associated with any project listed above, I do hold coins in all as well as Bitcoin, Litecoin and many others.
The thoughts above are based on my personal research, but I make no claims to being a quantum scientist or cryptographer. So, don’t take my word for anything. Instead, do your own research and draw your own conclusions. I’ve included many references below, but there are many more to explore.
In conclusion, the intention of this article is not to create fear or panic, nor any other negative effects. It is simply to educate. If you see an error in any of my statements, please, politely, let me know, and I will do my best to update the error.
Thanks for reading!

References

[i] https://www.youtube.com/watch?v=JhHMJCUmq28 – A great video explaining quantum computers.
[ii] https://www.doc.ic.ac.uk/~nd/surprise_97/journal/vol4/spb3/ - A brief history of quantum computing.
[iii] https://en.wikipedia.org/wiki/Apple_Lisa - More than you would ever want to know about the Apple Lisa.
[iv] https://www.youtube.com/watch?v=tpIctyqH29Q&list=PL8dPuuaLjXtNlUrzyH5r6jN9ulIgZBpdo - Want to learn more about computer science? Here is a great crash course for it!
[v] https://www.collinsdictionary.com/dictionary/english/quantify - What does quantify mean?
[vi] https://en.bitcoin.it/wiki/Private_key - More info about Bitcoin private keys.
[vii] https://www.securityinnovationeurope.com/blog/page/whats-the-difference-between-hashing-and-encrypting - A good example of the deference between Hash and Encryption
[viii] https://lbc.cryptoguru.org/stats - The Large Bitcoin Collider.
[ix] http://directory.io/ - A list of every possible Bitcoin private key. This website is a clever way of converting the 64 character uncompressed key to the private key 128 at a time. Since it is impossible to save all this data in a database and search, it is not considered a threat! It’s equated with looking for a single needle on the entire planet.
[x] https://uwaterloo.ca/institute-for-quantum-computing/quantum-computing-101#Superposition-and-entanglement – Brief overview of Superposition and Entanglement.
[xi] https://www.washingtonpost.com/world/national-security/nsa-seeks-to-build-quantum-computer-that-could-crack-most-types-of-encryption/2014/01/02/8fff297e-7195-11e3-8def-a33011492df2_story.html?utm_term=.e05a9dfb6333 – A review of the Penetrating Hard Targets project.
[xii] https://en.wikipedia.org/wiki/Post-quantum_cryptography - Explains post-quantum cryptography.
[xiii] https://www.nebulas.io/ - The nebulas project has some amazing technology planned in their roadmap. They are currently in testnet stage with initial launch expected taking place in a few weeks. If you don’t know about Nebulas, you should check them out. [xiv] https://en.wikipedia.org/wiki/Legality_of_bitcoin_by_country_or_territory - Country’s stance on crypto currencies.
[xv] https://www.cnbc.com/2017/08/30/venezuela-is-one-of-the-worlds-most-dangerous-places-to-mine-bitcoin.html - Don’t be a miner in Venezuela!
[xvi] http://www.newsweek.com/russia-bitcoin-avoid-us-sanctions-cryptocurrency-768742 - Russia’s plan for their own crypto currency.
[xvii] http://www.telegraph.co.uk/technology/2018/01/05/visa-locks-bitcoin-payment-cards-crackdown-card-issue - Recent attack from visa against crypto currency.
[xviii] https://www.ccn.com/non-government-digital-currency-junk-says-mastercard-ceo-rejecting-bitcoin/ - Mastercards position about Bitcoin.
[xix] http://www.livebitcoinnews.com/discover-joins-visa-mastercard-barring-bitcoin-support/ - Discovers position about Bitcoin.
[xx] http://fortune.com/2017/10/20/mastercard-blockchain-bitcoin/ - Mastercard is making their own blockchain.
[xxi] https://bitcoincore.org/en/2015/12/21/capacity-increase/ - News about Bitcoin capacity. Not a lot of news…
[xxii] https://learn.iota.org/faq/what-makes-iota-quantum-secure - IOTA and quantum encryption.
[xxiii] https://eprint.iacr.org/2011/191.pdf - The whitepaper of Winternitz One-Time Signature Scheme
[xxiv] https://cardanoroadmap.com/ - The Cardano project roadmap.
[xxv] https://eprint.iacr.org/2017/490 - More about the BLISS hash system.
[xxvi] https://www.ethereum.org/ - Home of the Ethereum project.
[xxvii] https://en.wikipedia.org/wiki/SHA-3#Security_against_quantum_attacks – SHA3 hash algorithm vs quantum computers.
[xxviii] https://en.wikipedia.org/wiki/Lamport_signature - Lamport signature information.
[xxix] https://theqrl.org/ - Home of the Quantum Resistant Ledger project.
submitted by satoshibytes to CryptoCurrency [link] [comments]

Instructions for Solving the SHA-265 Cryptographic Hash Function 1 Introduction Oneway ,SHA256, and Merkle Tree - Merkle Tree Miningcompany.ltd - New Free Bitcoin Cloud Mining Site 2020 - Signup Bonus 100 Gh/s Quantenrechner = Untergang des Bitcoin? But how does bitcoin actually work?

SHA-256, der Nachfolger von SHA-1 wurde, trägt einen anderen Namen-SHA-2. Es ist nicht viel schwieriger zu codieren als SHA-1, und der 256-Bit-Schlüssel wurde bisher noch nie kompromittiert. Die sichere Kommunikation für Websites und Webdienste basiert auf Dateien, die als Zertifikate bezeichnet werden. Что такое sha-256? sha-256 一 криптографическая хэш-функция, разработанная Агенством SHA-256 is a member of the SHA-2 cryptographic hash functions designed by the NSA. SHA stands for Secure Hash Algorithm. Cryptographic hash functions are mathematical operations run on digital data; by comparing the computed "hash" (the output from execution of the algorithm) to a known and expected hash value, a person can determine the data's integrity. So with all the extra attention SHA-256 gets, it is now more likely that flaws are found rather sooner than later. However, SHA-2 is a very widely used algorithm as it is, regardless of its use in Bitcoin. If there were any great and obvious flaws, they would have been found already. The following is a list of cryptocurrencies (both current and dead) that use the SHA-256 hashing algorithm. 21Coin <!-- https://coinmarketcap. The following is a list of cryptocurrencies (both current and dead) that use the SHA-256 hashing algorithm. 21Coin <!-- https://coinmarketcap Bitcoin (BTC) Bitcoin Cash (BCC) BitToken (BXT

[index] [13626] [9726] [3965] [12234] [3687] [9956] [28762] [21908] [1688] [21422]

Instructions for Solving the SHA-265 Cryptographic Hash Function

However, unlike Bitcoin which uses a single mining algorithm - Digibyte uses five separate algorithms that are equally weighted. The five algorithms used on the Digibyte blockchain are SHA256 ... I Bought An ABANDONED "Pimp My Ride" Minivan For $850 And It's WORSE Than You Think - Duration: 23:55. Tavarish Recommended for you Secure Hashing Algorithm (SHA1) explained. Dr Mike Pound explains how files are used to generate seemingly random hash strings. EXTRA BITS: https://youtu.be/... Java Tutorial - Hash functions (MD2, MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512) - Duration: 12:33. Zoran Davidović 17,260 views About: Wiki Online is the channel where you can find all the latest videos related to earning tutorials, best app reviews, bitcoin earning, cryptocurrency updates, digital cloud mining and more ...

Flag Counter