BitCore BTX - Your Coin, Your Money

PDQ Deploy packs v71.0.0 (2020-06-12)

Background

This is v71.0.0 (v70.0.0, v69.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.25 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v20.009.20063
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.387 (Chrome)
  • Adobe Flash Player v32.0.0.387 (Firefox)
  • Adobe Flash Player v32.0.0.387 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • FileZilla Client v3.48.1
  • Gimp v2.10.20 (x86)
  • Google Chrome Enterprise v83.0.4103.97
  • Google Chrome Enterprise v83.0.4103.97 (x86)
  • Google Earth Pro v7.3.3
  • Java Development Kit 8 Update 241
  • Java Development Kit 8 Update 241 (x86)
  • Java Development Kit 11.0.7
  • Java Runtime 8 update 241
  • Java Runtime 8 update 241 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.4.4
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v77.0.1
  • Mozilla Firefox v77.0.1 (x86)
  • Mozilla Firefox ESR v68.9.0
  • Mozilla Firefox ESR v68.9.0 (x86)
  • Mozilla Thunderbird v68.9.0 (x86) (customized; read notes)
  • Notepad++ v7.8.7 (x86)
  • Pale Moon v28.10.0
  • Pale Moon v28.10.0 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.4.0 (x86)
  • VLC media player v3.0.10 -- ! NOTE: Switched to x64 only (dropped x86 package)
  • WinSCP v5.17.6 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (empty recycle bin to empty for every user on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to sysadmin [link] [comments]

Review and Prospect of Crypto Economy-Development and Evolution of Consensus Mechanism (2)

Review and Prospect of Crypto Economy-Development and Evolution of Consensus Mechanism (2)

https://preview.redd.it/a51zsja94db51.png?width=567&format=png&auto=webp&s=99e8080c9e9b1fb5e11cbd70f915f9cb37188f81
Foreword
The consensus mechanism is one of the important elements of the blockchain and the core rule of the normal operation of the distributed ledger. It is mainly used to solve the trust problem between people and determine who is responsible for generating new blocks and maintaining the effective unification of the system in the blockchain system. Thus, it has become an everlasting research hot topic in blockchain.
This article starts with the concept and role of the consensus mechanism. First, it enables the reader to have a preliminary understanding of the consensus mechanism as a whole; then starting with the two armies and the Byzantine general problem, the evolution of the consensus mechanism is introduced in the order of the time when the consensus mechanism is proposed; Then, it briefly introduces the current mainstream consensus mechanism from three aspects of concept, working principle and representative project, and compares the advantages and disadvantages of the mainstream consensus mechanism; finally, it gives suggestions on how to choose a consensus mechanism for blockchain projects and pointed out the possibility of the future development of the consensus mechanism.
Contents
First, concept and function of the consensus mechanism
1.1 Concept: The core rules for the normal operation of distributed ledgers
1.2 Role: Solve the trust problem and decide the generation and maintenance of new blocks
1.2.1 Used to solve the trust problem between people
1.2.2 Used to decide who is responsible for generating new blocks and maintaining effective unity in the blockchain system
1.3 Mainstream model of consensus algorithm
Second, the origin of the consensus mechanism
2.1 The two armies and the Byzantine generals
2.1.1 The two armies problem
2.1.2 The Byzantine generals problem
2.2 Development history of consensus mechanism
2.2.1 Classification of consensus mechanism
2.2.2 Development frontier of consensus mechanism
Third, Common Consensus System
Fourth, Selection of consensus mechanism and summary of current situation
4.1 How to choose a consensus mechanism that suits you
4.1.1 Determine whether the final result is important
4.1.2 Determine how fast the application process needs to be
4.1.2 Determining the degree to which the application requires for decentralization
4.1.3 Determine whether the system can be terminated
4.1.4 Select a suitable consensus algorithm after weighing the advantages and disadvantages
4.2 Future development of consensus mechanism
Last lecture review: Chapter 1 Concept and Function of Consensus Mechanism plus Chapter 2 Origin of Consensus Mechanism
Chapter 3 Common Consensus Mechanisms (Part 1)
Figure 6 Summary of relatively mainstream consensus mechanisms
📷
https://preview.redd.it/9r7q3xra4db51.png?width=567&format=png&auto=webp&s=bae5554a596feaac948fae22dffafee98c4318a7
Source: Hasib Anwar, "Consensus Algorithms: The Root Of The Blockchain Technology"
The picture above shows 14 relatively mainstream consensus mechanisms summarized by a geek Hasib Anwar, including PoW (Proof of Work), PoS (Proof of Stake), DPoS (Delegated Proof of Stake), LPoS (Lease Proof of Stake), PoET ( Proof of Elapsed Time), PBFT (Practical Byzantine Fault Tolerance), SBFT (Simple Byzantine Fault Tolerance), DBFT (Delegated Byzantine Fault Tolerance), DAG (Directed Acyclic Graph), Proof-of-Activity (Proof of Activity), Proof-of- Importance (Proof of Importance), Proof-of-Capacity (Proof of Capacity), Proof-of-Burn ( Proof of Burn), Proof-of-Weight (Proof of Weight).
Next, we will mainly introduce and analyze the top ten consensus mechanisms of the current blockchain.
》POW
-Concept:
Work proof mechanism. That is, the proof of work means that it takes a certain amount of computer time to confirm the work.
-Principle:
Figure 7 PoW work proof principle
📷
https://preview.redd.it/xupacdfc4db51.png?width=554&format=png&auto=webp&s=3b6994641f5890804d93dfed9ecfd29308c8e0cc
The PoW represented by Bitcoin uses the SHA-256 algorithm function, which is a 256-bit hash algorithm in the password hash function family:
Proof of work output = SHA256 (SHA256 (block header));
if (output of proof of work if (output of proof of work >= target value), change the random number, recursive i logic, continue to compare with the target value.
New difficulty value = old difficulty value* (time spent by last 2016 blocks /20160 minutes)
Target value = maximum target value / difficulty value
The maximum target value is a fixed number. If the last 2016 blocks took less than 20160 minutes, then this coefficient will be small, and the target value will be adjusted bigger, if not, the target value will be adjusted smaller. Bitcoin mining difficulty and block generation speed will be inversely proportional to the appropriate adjustment of block generation speed.
-Representative applications: BTC, etc.
》POS
-Concept:
Proof of stake. That is, a mechanism for reaching consensus based on the holding currency. The longer the currency is held, the greater the probability of getting a reward.
-Principle:
PoS implementation algorithm formula: hash(block_header) = Coin age calculation formula: coinage = number of coins * remaining usage time of coins
Among them, coinage means coin age, which means that the older the coin age, the easier it is to get answers. The calculation of the coin age is obtained by multiplying the coins owned by the miner by the remaining usage time of each coin, which also means that the more coins you have, the easier it is to get answers. In this way, pos solves the problem of wasting resources in pow, and miners cannot own 51% coins from the entire network, so it also solves the problem of 51% attacks.
-Representative applications: ETH, etc.
》DPoS
-Concept:
Delegated proof of stake. That is, currency holding investors select super nodes by voting to operate the entire network , similar to the people's congress system.
-Principle:
The DPOS algorithm is divided into two parts. Elect a group of block producers and schedule production.
Election: Only permanent nodes with the right to be elected can be elected, and ultimately only the top N witnesses can be elected. These N individuals must obtain more than 50% of the votes to be successfully elected. In addition, this list will be re-elected at regular intervals.
Scheduled production: Under normal circumstances, block producers take turns to generate a block every 3 seconds. Assuming that no producer misses his order, then the chain they produce is bound to be the longest chain. When a witness produces a block, a block needs to be generated every 2s. If the specified time is exceeded, the current witness will lose the right to produce and the right will be transferred to the next witness. Then the witness is not only unpaid, but also may lose his identity.
-Representative applications: EOS, etc.
》DPoW
-Concept:
Delayed proof of work. A new-generation consensus mechanism based on PoB and DPoS. Miners use their own computing power, through the hash algorithm, and finally prove their work, get the corresponding wood, wood is not tradable. After the wood has accumulated to a certain amount, you can go to the burning site to burn the wood. This can achieve a balance between computing power and mining rights.
-Principle:
In the DPoW-based blockchain, miners are no longer rewarded tokens, but "wood" that can be burned, burning wood. Miners use their own computing power, through the hash algorithm, and finally prove their work, get the corresponding wood, wood is not tradable. After the wood has accumulated to a certain amount, you can go to the burning site to burn the wood. Through a set of algorithms, people who burn more wood or BP or a group of BP can obtain the right to generate blocks in the next event segment, and get rewards (tokens) after successful block generation. Since more than one person may burn wood in a time period, the probability of producing blocks in the next time period is determined by the amount of wood burned by oneself. The more it is burned, the higher the probability of obtaining block rights in the next period.
Two node types: notary node and normal node.
The 64 notary nodes are elected by the stakeholders of the dPoW blockchain, and the notarized confirmed blocks can be added from the dPoW blockchain to the attached PoW blockchain. Once a block is added, the hash value of the block will be added to the Bitcoin transaction signed by 33 notary nodes, and a hash will be created to the dPow block record of the Bitcoin blockchain. This record has been notarized by most notary nodes in the network. In order to avoid wars on mining between notary nodes, and thereby reduce the efficiency of the network, Komodo designed a mining method that uses a polling mechanism. This method has two operating modes. In the "No Notary" (No Notary) mode, all network nodes can participate in mining, which is similar to the traditional PoW consensus mechanism. In the "Notaries Active" mode, network notaries use a significantly reduced network difficulty rate to mine. In the "Notary Public Activation" mode, each notary public is allowed to mine a block with its current difficulty, while other notary public nodes must use 10 times the difficulty of mining, and all normal nodes use 100 times the difficulty of the notary public node.
Figure 8 DPoW operation process without a notary node
📷
https://preview.redd.it/3yuzpemd4db51.png?width=500&format=png&auto=webp&s=f3bc2a1c97b13cb861414d3eb23a312b42ea6547
-Representative applications: CelesOS, Komodo, etc.
CelesOS Research Institute丨DPoW consensus mechanism-combustible mining and voting
》PBFT
-Concept:
Practical Byzantine fault tolerance algorithm. That is, the complexity of the algorithm is reduced from exponential to polynomial level, making the Byzantine fault-tolerant algorithm feasible in practical system applications.
-Principle:
Figure 9 PBFT algorithm principle
📷
https://preview.redd.it/8as7rgre4db51.png?width=567&format=png&auto=webp&s=372be730af428f991375146efedd5315926af1ca
First, the client sends a request to the master node to call the service operation, and then the master node broadcasts other copies of the request. All copies execute the request and send the result back to the client. The client needs to wait for f+1 different replica nodes to return the same result as the final result of the entire operation.
Two qualifications: 1. All nodes must be deterministic. That is to say, the results of the operation must be the same under the same conditions and parameters. 2. All nodes must start from the same status. Under these two limited qualifications, even if there are failed replica nodes, the PBFT algorithm agrees on the total order of execution of all non-failed replica nodes, thereby ensuring security.
-Representative applications: Tendermint Consensus, etc.
Next Lecture: Chapter 3 Common Consensus Mechanisms (Part 2) + Chapter 4 Consensus Mechanism Selection and Status Summary
CelesOS
As the first DPOW financial blockchain operating system, CelesOS adopts consensus mechanism 3.0 to break through the "impossible triangle", which can provide high TPS while also allowing for decentralization. Committed to creating a financial blockchain operating system that embraces supervision, providing services for financial institutions and the development of applications on the supervision chain, and formulating a role and consensus ecological supervision layer agreement for supervision.
The CelesOS team is dedicated to building a bridge between blockchain and regulatory agencies/financial industry. We believe that only blockchain technology that cooperates with regulators will have a real future. We believe in and contribute to achieving this goal.

📷Website
https://www.celesos.com/
📷 Telegram
https://t.me/celeschain
📷 Twitter
https://twitter.com/CelesChain
📷 Reddit
https://www.reddit.com/useCelesOS
📷 Medium
https://medium.com/@celesos
📷 Facebook
https://www.facebook.com/CelesOS1
📷 Youtube
https://www.youtube.com/channel/UC1Xsd8wU957D-R8RQVZPfGA
submitted by CelesOS to u/CelesOS [link] [comments]

PDQ Deploy packs v71.0.0 (2020-06-12)

Background

This is v71.0.0 (v70.0.0, v69.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.25 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v20.009.20063
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.387 (Chrome)
  • Adobe Flash Player v32.0.0.387 (Firefox)
  • Adobe Flash Player v32.0.0.387 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • FileZilla Client v3.48.1
  • Gimp v2.10.20 (x86)
  • Google Chrome Enterprise v83.0.4103.97
  • Google Chrome Enterprise v83.0.4103.97 (x86)
  • Google Earth Pro v7.3.3
  • Java Development Kit 8 Update 241
  • Java Development Kit 8 Update 241 (x86)
  • Java Development Kit 11.0.7
  • Java Runtime 8 update 241
  • Java Runtime 8 update 241 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.4.4
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v77.0.1
  • Mozilla Firefox v77.0.1 (x86)
  • Mozilla Firefox ESR v68.9.0
  • Mozilla Firefox ESR v68.9.0 (x86)
  • Mozilla Thunderbird v68.9.0 (x86) (customized; read notes)
  • Notepad++ v7.8.7 (x86)
  • Pale Moon v28.10.0
  • Pale Moon v28.10.0 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.4.0 (x86)
  • VLC media player v3.0.10 -- ! NOTE: Switched to x64 only (dropped x86 package)
  • WinSCP v5.17.6 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to pdq [link] [comments]

PDQ Deploy packs v70.0.0 (2020-03-31)

Background

This is v70.0.0 (v69.0.0, v68.0.0, v67.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.15 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v20.006.20042
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.344 (Chrome)
  • Adobe Flash Player v32.0.0.344 (Firefox)
  • Adobe Flash Player v32.0.0.344 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • FileZilla Client v3.47.2.1
  • Gimp v2.10.18 (x86)
  • Google Chrome Enterprise v80.0.3987.149
  • Google Chrome Enterprise v80.0.3987.149 (x86)
  • Google Earth Pro v7.3.2
  • Java Development Kit 8 Update 241
  • Java Development Kit 8 Update 241 (x86)
  • Java Development Kit 11.0.6
  • Java Runtime 8 update 241
  • Java Runtime 8 update 241 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.4.2
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v74.0.0
  • Mozilla Firefox v74.0.0 (x86)
  • Mozilla Firefox ESR v68.6.0
  • Mozilla Firefox ESR v68.6.0 (x86)
  • Mozilla Thunderbird v68.6.0 (x86) (customized; read notes)
  • Notepad++ v7.8.5 (x86)
  • Pale Moon v28.9.0.2
  • Pale Moon v28.9.0.2 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.4.0 (x86)
  • VLC media player v3.0.8 (x86)
  • WinSCP v5.17.2 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source, although donations are of course appreciated since all work done on them is in my spare time for free. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to pdq [link] [comments]

PDQ Deploy packs v69.0.0 (2020-02-06)

Background

This is v69.0.0 (v68.0.0, v67.0.0, v66.0.0, v65.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.15 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v19.021.20058
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.321 (Chrome)
  • Adobe Flash Player v32.0.0.321 (Firefox)
  • Adobe Flash Player v32.0.0.321 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • CutePDF v3.0 (PDF printer) (x86) // REMOVED; Since Windows natively supports PDF printing now there's no reason to keep this in the pack
  • FileZilla Client v3.46.3
  • Gimp v2.10.14 (x86)
  • Google Chrome Enterprise v80.0.3987.87
  • Google Chrome Enterprise v80.0.3987.87 (x86)
  • Google Earth Pro v7.3.2
  • Java Development Kit 8 Update 231
  • Java Development Kit 8 Update 231 (x86)
  • Java Development Kit 11.0.6
  • Java Runtime 8 update 231
  • Java Runtime 8 update 231 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.4.0
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v72.0.2
  • Mozilla Firefox v72.0.2 (x86)
  • Mozilla Firefox ESR v68.4.2
  • Mozilla Firefox ESR v68.4.2 (x86)
  • Mozilla Thunderbird v68.4.2 (x86) (customized; read notes)
  • Notepad++ v7.8.4 (x86)
  • Pale Moon v28.8.2.1
  • Pale Moon v28.8.2.1 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.2.4 (x86)
  • VLC media player v3.0.8 (x86)
  • WinSCP v5.15.9 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source, although donations are of course appreciated since all work done on them is in my spare time for free. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to sysadmin [link] [comments]

PDQ Deploy packs v68.0.0 (2020-01-11)

Background

This is v68.0.0 (v67.0.0, v66.0.0, v65.0.0, v64.0.0, v63.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.15 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v19.021.20058
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.303 (Chrome)
  • Adobe Flash Player v32.0.0.303 (Firefox)
  • Adobe Flash Player v32.0.0.303 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • CutePDF v3.0 (PDF printer) (x86)
  • FileZilla Client v3.46.3
  • Gimp v2.10.14 (x86)
  • Google Chrome Enterprise v79.0.3945.117
  • Google Chrome Enterprise v77.0.3945.117 (x86)
  • Google Earth Pro v7.3.2
  • Java Development Kit 8 Update 231
  • Java Development Kit 8 Update 231 (x86)
  • Java Development Kit 11.0.5
  • Java Runtime 8 update 231
  • Java Runtime 8 update 231 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.3.4
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v72.0.1
  • Mozilla Firefox v72.0.1 (x86)
  • Mozilla Firefox ESR v68.4.1
  • Mozilla Firefox ESR v68.4.1 (x86)
  • Mozilla Thunderbird v68.4.1 (x86) (customized; read notes)
  • Notepad++ v7.8.2 (x86)
  • Pale Moon v28.8.1
  • Pale Moon v28.8.1 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.2.4 (x86)
  • VLC media player v3.0.8 (x86)
  • WinSCP v5.15.9 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source, although donations are of course appreciated since all work done on them is in my spare time for free. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to sysadmin [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

PDQ Deploy packs v67.0.0 (2019-10-22)

Background

This is v67.0.0 (v66.0.0, v65.0.0, v64.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.15 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Package list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v19.008.20071
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.270 (Chrome)
  • Adobe Flash Player v32.0.0.270 (Firefox)
  • Adobe Flash Player v32.0.0.270 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7042
  • CutePDF v3.0 (PDF printer) (x86)
  • FileZilla Client v3.45.1
  • Gimp v2.10.12 (x86)
  • Google Chrome Enterprise v77.0.3865.120
  • Google Chrome Enterprise v77.0.3865.1205 (x86)
  • Google Earth Pro v7.3.2
  • Java Development Kit 8 Update 231
  • Java Development Kit 8 Update 231 (x86)
  • Java Development Kit 11.0.5
  • Java Runtime 8 update 231
  • Java Runtime 8 update 231 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.2.7 ! -- NEW
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Microsoft Silverlight v5.1.50901.0 (x86) ! -- REMOVED
  • Mozilla Firefox v69.0.3
  • Mozilla Firefox v69.0.3 (x86)
  • Mozilla Firefox ESR v68.1.0
  • Mozilla Firefox ESR v68.1.0 (x86)
  • Mozilla Thunderbird v68.1.2 (x86) (customized; read notes)
  • Notepad++ v7.8.0 (x86)
  • Pale Moon v28.7.1.0
  • Pale Moon v28.7.1.0 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.23
  • TightVNC v2.8.23 (x86)
  • UltraVNC v1.2.2.4 (x86)
  • VLC media player v3.0.8 (x86)
  • WinSCP v5.15.5 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CDROMs, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Developer Contact & Pack Integrity

If you find a bug or glitch, PM me, post it here, or you can reach me anytime on Keybase. Advice and comments are welcome and appreciated.
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.

Donations

These packs will always be free and open-source, although donations are of course appreciated since all work done on them is in my spare time for free. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to sysadmin [link] [comments]

PDQ Deploy packs v69.0.0 (2020-02-06)

Background

This is v69.0.0 (v68.0.0, v67.0.0, v66.0.0, v65.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.15 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v19.021.20058
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.321 (Chrome)
  • Adobe Flash Player v32.0.0.321 (Firefox)
  • Adobe Flash Player v32.0.0.321 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • CutePDF v3.0 (PDF printer) (x86) // REMOVED; Since Windows natively supports PDF printing now there's no reason to keep this in the pack
  • FileZilla Client v3.46.3
  • Gimp v2.10.14 (x86)
  • Google Chrome Enterprise v80.0.3987.87
  • Google Chrome Enterprise v80.0.3987.87 (x86)
  • Google Earth Pro v7.3.2
  • Java Development Kit 8 Update 231
  • Java Development Kit 8 Update 231 (x86)
  • Java Development Kit 11.0.6
  • Java Runtime 8 update 231
  • Java Runtime 8 update 231 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.4.0
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v72.0.2
  • Mozilla Firefox v72.0.2 (x86)
  • Mozilla Firefox ESR v68.4.2
  • Mozilla Firefox ESR v68.4.2 (x86)
  • Mozilla Thunderbird v68.4.2 (x86) (customized; read notes)
  • Notepad++ v7.8.4 (x86)
  • Pale Moon v28.8.2.1
  • Pale Moon v28.8.2.1 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.2.4 (x86)
  • VLC media player v3.0.8 (x86)
  • WinSCP v5.15.9 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source, although donations are of course appreciated since all work done on them is in my spare time for free. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to pdq [link] [comments]

PDQ Deploy packs v68.0.0 (2020-01-11)

Background

This is v68.0.0 (v67.0.0, v66.0.0, v65.0.0, v64.0.0, v63.0.0, etc...) of our PDQ installers and includes all installers from the previous package with old versions removed.
All packages:
  1. ...install silently and don't place desktop or quicklaunch shortcuts
  2. ...disable all auto-update, nag popup and stat-collection/telemetry "features" possible
  3. ...work with the free or paid version of PDQ Deploy but do not require it - each package can run standalone (e.g. from a thumb drive) or pushed with SCCM/GPO/etc if desired. PM me if you need assistance setting something like that up

Download

Primary:
Download the torrent.
Secondary: Download the self-extracting archive from one of the repos:
Mirror HTTPS HTTP Location Host
Official link link US-NY SGC-Hosting
#1 link link FR mxmod
Tertiary:
Plug one of these keys into Resilio Sync (formerly called "BT Sync") to pull down that repository:
- BTRSRPF7Y3VWFRBG64VUDGP7WIIVNTR4Q (Installer Packages, ~2.15 GB) - BMHHALGV7WLNSAPIPYDP5DU3NDNSM5XNC (WSUS Offline updates, ~12.00 GB) 
Make sure the settings for your Sync folder look like this (or this if you're on v1.3.x). Specifically you need to enable DHT.
Quaternary: (source code)
The Github page contains all scripts and wrapper files used in the pack. Check it out if you want to see the code without downloading the full binary pack, or just steal them for your own use. Note that downloading from Github directly won't work - you need either this provided pack or go manually fetch all the binaries yourself in order to just plug them in and start working.

Pack list

Installers:
(Updates in bold. All installers are 64-bit unless otherwise marked)
  • 7-Zip v19.00
  • 7-Zip v19.00 (x86)
  • Adobe Acrobat Reader DC v19.021.20058
  • Adobe AIR v32.0.0.125
  • Adobe Flash Player v32.0.0.303 (Chrome)
  • Adobe Flash Player v32.0.0.303 (Firefox)
  • Adobe Flash Player v32.0.0.303 (IE / ActiveX)
  • Apple iTunes v12.5.1.21
  • CDBurnerXP v4.5.8.7128
  • CutePDF v3.0 (PDF printer) (x86)
  • FileZilla Client v3.46.3
  • Gimp v2.10.14 (x86)
  • Google Chrome Enterprise v79.0.3945.117
  • Google Chrome Enterprise v77.0.3945.117 (x86)
  • Google Earth Pro v7.3.2
  • Java Development Kit 8 Update 231
  • Java Development Kit 8 Update 231 (x86)
  • Java Development Kit 11.0.5
  • Java Runtime 8 update 231
  • Java Runtime 8 update 231 (x86)
  • Java Runtime 10.0.2
  • KTS KypM Telnet/SSH Server v1.19c (x86)
  • LibreOffice v6.3.4
  • Microsoft .NET Framework v3.5.1 SP1 (x86)
  • Microsoft Silverlight v5.1.50918.0
  • Mozilla Firefox v72.0.1
  • Mozilla Firefox v72.0.1 (x86)
  • Mozilla Firefox ESR v68.4.1
  • Mozilla Firefox ESR v68.4.1 (x86)
  • Mozilla Thunderbird v68.4.1 (x86) (customized; read notes)
  • Notepad++ v7.8.2 (x86)
  • Pale Moon v28.8.1
  • Pale Moon v28.8.1 (x86)
  • Spark v2.8.3 (x86)
  • TightVNC v2.8.27
  • TightVNC v2.8.27 (x86)
  • UltraVNC v1.2.2.4 (x86)
  • VLC media player v3.0.8 (x86)
  • WinSCP v5.15.9 (x86)
Utilities:
  • Clean Up ALL Printers (purge all printers from target)
  • Clean Up Orphaned Printers (remove non-existent printers from the spooler)
  • Empty All Recycle Bins (force all recycle bins to empty on target)
  • Enable Remote Desktop
  • Install PKI Certificates
  • Reboot (force target reboot in 15 seconds)
  • Remove Adobe Flash Player (removes all versions)
  • Remove Java Runtime (removes JRE versions 3-11 using all means necessary)
  • Remove Microsoft Silverlight (removes all versions of Silverlight)
  • Temp File Cleanup
  • USB Device Cleanup. Uninstalls non-present USB hubs, USB storage devices and their storage volumes, Disks, CD-ROM's, Floppies, WPD devices and deletes their registry items. Devices will re-initialize at next connection

Instructions

  1. Import all .XML files from the \job files directory into PDQ deploy (it should look roughly like this after you've imported them).
  2. Copy all files from the \repository directory to wherever your repository is.
  3. All jobs reference PDQ's $(Repository) variable, so make sure it's set in preferences.

Package Notes

  1. Read the notes in the PDQ interface for each package, they explain exactly what that installer does. Basically, most packages use a .bat file to accomplish multi-step installs with the free version of PDQ. You can edit the batch files to see what they do; most just delete "All Users" desktop shortcuts and things like that. changelog-v##-updated-.txt has version and release history in addition to random notes where I complain about things like Reader DC and how much of a pain it is to build packages for.
  2. Thunderbird:
    • Thunderbird is configured to use a global config file stored on a network share. This allows for settings changes en masse. By default it's set to check for config updates every 120 minutes.
    • You can change the config location, update frequency, OR disable this behavior entirely by editing thunderbird-custom-settings.js.
    • A copy of the config file is in the Thunderbird directory and is called thunderbird-global-settings.js
    • If you don't want any customizations, just edit Thunderbird's .bat file and comment out or delete all the lines mentioning the custom config files.
  3. Microsoft Offline Updates - built using the excellent WSUS Offline tool. Please donate to them if you can, their team does excellent work.

Integrity

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.
If you find a bug or glitch, PM me or post it here. Advice and comments are welcome and appreciated.

Donations

These packs will always be free and open-source, although donations are of course appreciated since all work done on them is in my spare time for free. If you feel like giving away your hard-earned cash to random strangers on the internet you may do so here:
Patreon
Bitcoin: 1Bfxpo1WqTGwRXZKrwYZV2zvJ4ggyj9GE1
Monero (preferred):
46ZUK4VDLLz3zapDw62UaS71ZfFBjH9uwhc8FeyocPhUHHsuxj5zfvpZpZcZFHWpxoXD99MVt6PnR9QfftXDV8s6CFAnPSo
"Do not withhold good from those to whom it is due, when it is in your power to act."
submitted by vocatus to pdq [link] [comments]

Transcript of discussion between an ASIC designer and several proof-of-work designers from #monero-pow channel on Freenode this morning

[08:07:01] lukminer contains precompiled cn/r math sequences for some blocks: https://lukminer.org/2019/03/09/oh-kay-v4r-here-we-come/
[08:07:11] try that with RandomX :P
[08:09:00] tevador: are you ready for some RandomX feedback? it looks like the CNv4 is slowly stabilizing, hashrate comes down...
[08:09:07] how does it even make sense to precompile it?
[08:09:14] mine 1% faster for 2 minutes?
[08:09:35] naturally we think the entire asic-resistance strategy is doomed to fail :) but that's a high-level thing, who knows. people may think it's great.
[08:09:49] about RandomX: looks like the cache size was chosen to make it GPU-hard
[08:09:56] looking forward to more docs
[08:11:38] after initial skimming, I would think it's possible to make a 10x asic for RandomX. But at least for us, we will only make an ASIC if there is not a total ASIC hostility there in the first place. That's better for the secret miners then.
[08:13:12] What I propose is this: we are working on an Ethash ASIC right now, and once we have that working, we would invite tevador or whoever wants to come to HK/Shenzhen and we walk you guys through how we would make a RandomX ASIC. You can then process this input in any way you like. Something like that.
[08:13:49] unless asics (or other accelerators) re-emerge on XMR faster than expected, it looks like there is a little bit of time before RandomX rollout
[08:14:22] 10x in what measure? $/hash or watt/hash?
[08:14:46] watt/hash
[08:15:19] so you can make 10 times more efficient double precisio FPU?
[08:16:02] like I said let's try to be productive. You are having me here, let's work together!
[08:16:15] continue with RandomX, publish more docs. that's always helpful.
[08:16:37] I'm trying to understand how it's possible at all. Why AMD/Intel are so inefficient at running FP calculations?
[08:18:05] midipoet (uid316937[email protected]/web/irccloud.com/x-vszshqqxwybvtsjm) has joined #monero-pow
[08:18:17] hardware development works the other way round. We start with 1) math then 2) optimization priority 3) hw/sw boundary 4) IP selection 5) physical implementation
[08:22:32] This still doesn't explain at which point you get 10x
[08:23:07] Weren't you the ones claiming "We can accelerate ProgPoW by a factor of 3x to 8x." ? I find it hard to believe too.
[08:30:20] sure
[08:30:26] so my idea: first we finish our current chip
[08:30:35] from simulation to silicon :)
[08:30:40] we love this stuff... we do it anyway
[08:30:59] now we have a communication channel, and we don't call each other names immediately anymore: big progress!
[08:31:06] you know, we russians have a saying "it was smooth on paper, but they forgot about ravines"
[08:31:12] So I need a bit more details
[08:31:16] ha ha. good!
[08:31:31] that's why I want to avoid to just make claims
[08:31:34] let's work
[08:31:40] RandomX comes in Sep/Oct, right?
[08:31:45] Maybe
[08:32:20] We need to audit it first
[08:32:31] ok
[08:32:59] we don't make chips to prove sw devs that their assumptions about hardware are wrong. especially not if these guys then promptly hardfork and move to the next wrong assumption :)
[08:33:10] from the outside, this only means that hw & sw are devaluing each other
[08:33:24] neither of us should do this
[08:33:47] we are making chips that can hopefully accelerate more crypto ops in the future
[08:33:52] signing, verifying, proving, etc.
[08:34:02] PoW is just a feature like others
[08:34:18] sech1: is it easy for you to come to Hong Kong? (visa-wise)
[08:34:20] or difficult?
[08:34:33] or are you there sometimes?
[08:34:41] It's kind of far away
[08:35:13] we are looking forward to more RandomX docs. that's the first step.
[08:35:31] I want to avoid that we have some meme "Linzhi says they can accelerate XYZ by factor x" .... "ha ha ha"
[08:35:37] right? we don't want that :)
[08:35:39] doc is almost finished
[08:35:40] What docs do you need? It's described pretty good
[08:35:41] so I better say nothing now
[08:35:50] we focus on our Ethash chip
[08:36:05] then based on that, we are happy to walk interested people through the design and what else it can do
[08:36:22] that's a better approach from my view than making claims that are laughed away (rightfully so, because no silicon...)
[08:36:37] ethash ASIC is basically a glorified memory controller
[08:36:39] sech1: tevador said something more is coming (he just did it again)
[08:37:03] yes, some parts of RandomX are not described well
[08:37:10] like dataset access logic
[08:37:37] RandomX looks like progpow for CPU
[08:37:54] yes
[08:38:03] it is designed to reflect CPU
[08:38:34] so any ASIC for it = CPU in essence
[08:39:04] of course there are still some things in regular CPU that can be thrown away for RandomX
[08:40:20] uncore parts are not used, but those will use very little power
[08:40:37] except for memory controller
[08:41:09] I'm just surprised sometimes, ok? let me ask: have you designed or taped out an asic before? isn't it risky to make assumptions about things that are largely unknown?
[08:41:23] I would worry
[08:41:31] that I get something wrong...
[08:41:44] but I also worry like crazy that CNv4 will blow up, where you guys seem to be relaxed
[08:42:06] I didn't want to bring up anything RandomX because CNv4 is such a nailbiter... :)
[08:42:15] how do you guys know you don't have asics in a week or two?
[08:42:38] we don't have experience with ASIC design, but RandomX is simply designed to exactly fit CPU capabilities, which is the best you can do anyways
[08:43:09] similar as ProgPoW did with GPUs
[08:43:14] some people say they want to do asic-resistance only until the vast majority of coins has been issued
[08:43:21] that's at least reasonable
[08:43:43] yeah but progpow totally will not work as advertised :)
[08:44:08] yeah, I've seen that comment about progpow a few times already
[08:44:11] which is no surprise if you know it's just a random sales story to sell a few more GPUs
[08:44:13] RandomX is not permanent, we are expecting to switch to ASIC friendly in a few years if possible
[08:44:18] yes
[08:44:21] that makes sense
[08:44:40] linzhi-sonia: how so? will it break or will it be asic-able with decent performance gains?
[08:44:41] are you happy with CNv4 so far?
[08:45:10] ah, long story. progpow is a masterpiece of deception, let's not get into it here.
[08:45:21] if you know chip marketing it makes more sense
[08:45:24] linzhi-sonia: So far? lol! a bit early to tell, don't you think?
[08:45:35] the diff is coming down
[08:45:41] first few hours looked scary
[08:45:43] I remain skeptical: I only see ASICs being reasonable if they are already as ubiquitous as smartphones
[08:45:46] yes, so far so good
[08:46:01] we kbew the diff would not come down ubtil affter block 75
[08:46:10] yes
[08:46:22] but first few hours it looks like only 5% hashrate left
[08:46:27] looked
[08:46:29] now it's better
[08:46:51] the next worry is: when will "unexplainable" hashrate come back?
[08:47:00] you hope 2-3 months? more?
[08:47:05] so give it another couple of days. will probably overshoot to the downside, and then rise a bit as miners get updated and return
[08:47:22] 3 months minimum turnaround, yes
[08:47:28] nah
[08:47:36] don't underestimate asicmakers :)
[08:47:54] you guys don't get #1 priority on chip fabs
[08:47:56] 3 months = 90 days. do you know what is happening in those 90 days exactly? I'm pretty sure you don't. same thing as before.
[08:48:13] we don't do any secret chips btw
[08:48:21] 3 months assumes they had a complete design ready to go, and added the last minute change in 1 day
[08:48:24] do you know who is behind the hashrate that is now bricked?
[08:48:27] innosilicon?
[08:48:34] hyc: no no, and no. :)
[08:48:44] hyc: have you designed or taped out a chip before?
[08:48:51] yes, many years ago
[08:49:10] then you should know that 90 days is not a fixed number
[08:49:35] sure, but like I said, other makers have greater demand
[08:49:35] especially not if you can prepare, if you just have to modify something, or you have more programmability in the chip than some people assume
[08:50:07] we are chipmakers, we would never dare to do what you guys are doing with CNv4 :) but maybe that just means you are cooler!
[08:50:07] and yes, programmability makes some aspect of turnaround easier
[08:50:10] all fine
[08:50:10] I hope it works!
[08:50:28] do you know who is behind the hashrate that is now bricked?
[08:50:29] inno?
[08:50:41] we suspect so, but have no evidence
[08:50:44] maybe we can try to find them, but we cannot spend too much time on this
[08:50:53] it's probably not so much of a secret
[08:51:01] why should it be, right?
[08:51:10] devs want this cat-and-mouse game? devs get it...
[08:51:35] there was one leak saying it's innosilicon
[08:51:36] so you think 3 months, ok
[08:51:43] inno is cool
[08:51:46] good team
[08:51:49] IP design house
[08:51:54] in Wuhan
[08:52:06] they send their people to conferences with fake biz cards :)
[08:52:19] pretending to be other companies?
[08:52:26] sure
[08:52:28] ha ha
[08:52:39] so when we see them, we look at whatever card they carry and laugh :)
[08:52:52] they are perfectly suited for secret mining games
[08:52:59] they made at most $6 million in 2 months of mining, so I wonder if it was worth it
[08:53:10] yeah. no way to know
[08:53:15] but it's good that you calculate!
[08:53:24] this is all about cost/benefit
[08:53:25] then you also understand - imagine the value of XMR goes up 5x, 10x
[08:53:34] that whole "asic resistance" thing will come down like a house of cards
[08:53:41] I would imagine they sell immediately
[08:53:53] the investor may fully understand the risk
[08:53:57] the buyer
[08:54:13] it's not healthy, but that's another discussion
[08:54:23] so mid-June
[08:54:27] let's see
[08:54:49] I would be susprised if CNv4 ASICs show up at all
[08:54:56] surprised*
[08:54:56] why?
[08:55:05] is only an economic question
[08:55:12] yeah should be interesting. FPGAs will be near their limits as well
[08:55:16] unless XMR goes up a lot
[08:55:19] no, not *only*. it's also a technology question
[08:55:44] you believe CNv4 is "asic resistant"? which feature?
[08:55:53] it's not
[08:55:59] cnv4 = Rabdomx ?
[08:56:03] no
[08:56:07] cnv4=cryptinight/r
[08:56:11] ah
[08:56:18] CNv4 is the one we have now, I think
[08:56:21] since yesterday
[08:56:30] it's plenty enough resistant for current XMR price
[08:56:45] that may be, yes!
[08:56:55] I look at daily payouts. XMR = ca. 100k USD / day
[08:57:03] it can hold until October, but it's not asic resistant
[08:57:23] well, last 24h only 22,442 USD :)
[08:57:32] I think 80 h/s per watt ASICs are possible for CNv4
[08:57:38] linzhi-sonia where do you produce your chips? TSMC?
[08:57:44] I'm cruious how you would expect to build a randomX ASIC that outperforms ARM cores for efficiency, or Intel cores for raw speed
[08:57:48] curious
[08:58:01] yes, tsmc
[08:58:21] Our team did the world's first bitcoin asic, Avalon
[08:58:25] and upcoming 2nd gen Ryzens (64-core EPYC) will be a blast at RandomX
[08:58:28] designed and manufactured
[08:58:53] still being marketed?
[08:59:03] linzhi-sonia: do you understand what xmr wants to achieve, community-wise?
[08:59:14] Avalon? as part of Canaan Creative, yes I think so.
[08:59:25] there's not much interesting oing on in SHA256
[08:59:29] Inge-: I would think so, but please speak
[08:59:32] hyc: yes
[09:00:28] linzhi-sonia: i am curious to hear your thoughts. I am fairly new to this space myself...
[09:00:51] oh
[09:00:56] we are grandpas, and grandmas
[09:01:36] yet I have no problem understanding why ASICS are currently reviled.
[09:01:48] xmr's main differentiators to, let's say btc, are anonymity and fungibility
[09:01:58] I find the client terribly slow btw
[09:02:21] and I think the asic-forking since last may is wrong, doesn't create value and doesn't help with the project objectives
[09:02:25] which "the client" ?
[09:02:52] Monero GUI client maybe
[09:03:12] MacOS, yes
[09:03:28] What exactly is slow?
[09:03:30] linzhi-sonia: I run my own node, and use the CLI and Monerujo. Have not had issues.
[09:03:49] staying in sync
[09:03:49] linzhi-sonia: decentralization is also a key principle
[09:03:56] one that Bitcoin has failed to maintain
[09:04:39] hmm
[09:05:00] looks fairly decentralized to me. decentralization is the result of 3 goals imo: resilient, trustless, permissionless
[09:05:28] don't ask a hardware maker about physical decentralization. that's too ideological. we focus on logical decentralization.
[09:06:11] physical decentralization is important. with bulk of bitnoin mining centered on Chinese hydroelectric dams
[09:06:19] have you thought about including block data in the PoW?
[09:06:41] yes, of course.
[09:07:39] is that already in an algo?
[09:08:10] hyc: about "centered on chinese hydro" - what is your source? the best paper I know is this: https://coinshares.co.uk/wp-content/uploads/2018/11/Mining-Whitepaper-Final.pdf
[09:09:01] linzhi-sonia: do you mine on your ASICs before you sell them?
[09:09:13] besides testing of course
[09:09:45] that paper puts Chinese btc miners at 60% max
[09:10:05] tevador: I think everybody learned that that is not healthy long-term!
[09:10:16] because it gives the chipmaker a cost advantage over its own customers
[09:10:33] and cost advantage leads to centralization (physical and logical)
[09:10:51] you guys should know who finances progpow and why :)
[09:11:05] but let's not get into this, ha ha. want to keep the channel civilized. right OhGodAGirl ? :)
[09:11:34] tevador: so the answer is no! 100% and definitely no
[09:11:54] that "self-mining" disease was one of the problems we have now with asics, and their bad reputation (rightfully so)
[09:13:08] I plan to write a nice short 2-page paper or so on our chip design process. maybe it's interesting to some people here.
[09:13:15] basically the 5 steps I mentioned before, from math to physical
[09:13:32] linzhi-sonia: the paper you linked puts 48% of bitcoin mining in Sichuan. the total in China is much more than 60%
[09:13:38] need to run it by a few people to fix bugs, will post it here when published
[09:14:06] hyc: ok! I am just sharing the "best" document I know today. it definitely may be wrong and there may be a better one now.
[09:14:18] hyc: if you see some reports, please share
[09:14:51] hey I am really curious about this: where is a PoW algo that puts block data into the PoW?
[09:15:02] the previous paper I read is from here http://hackingdistributed.com/2018/01/15/decentralization-bitcoin-ethereum/
[09:15:38] hyc: you said that already exists? (block data in PoW)
[09:15:45] it would make verification harder
[09:15:49] linzhi-sonia: https://the-eye.eu/public/Books/campdivision.com/PDF/Computers%20General/Privacy/bitcoin/meh/hashimoto.pdf
[09:15:51] but for chips it would be interesting
[09:15:52] we discussed the possibility about a year ago https://www.reddit.com/Monero/comments/8bshrx/what_we_need_to_know_about_proof_of_work_pow/
[09:16:05] oh good links! thanks! need to read...
[09:16:06] I think that paper by dryja was original
[09:17:53] since we have a nice flow - second question I'm very curious about: has anyone thought about in-protocol rewards for other functions?
[09:18:55] we've discussed micropayments for wallets to use remote nodes
[09:18:55] you know there is a lot of work in other coins about STARK provers, zero-knowledge, etc. many of those things very compute intense, or need to be outsourced to a service (zether). For chipmakers, in-protocol rewards create an economic incentive to accelerate those things.
[09:19:50] whenever there is an in-protocol reward, you may get the power of ASICs doing something you actually want to happen
[09:19:52] it would be nice if there was some economic reward for running a fullnode, but no one has come up with much more than that afaik
[09:19:54] instead of fighting them off
[09:20:29] you need to use asics, not fight them. that's an obvious thing to say for an asicmaker...
[09:20:41] in-protocol rewards can be very powerful
[09:20:50] like I said before - unless the ASICs are so useful they're embedded in every smartphone, I dont see them being a positive for decentralization
[09:21:17] if they're a separate product, the average consumer is not going to buy them
[09:21:20] now I was talking about speedup of verifying, signing, proving, etc.
[09:21:23] they won't even know what they are
[09:22:07] if anybody wants to talk about or design in-protocol rewards, please come talk to us
[09:22:08] the average consumer also doesn't use general purpose hardware to secure blockchains either
[09:22:14] not just for PoW, in fact *NOT* for PoW
[09:22:32] it requires sw/hw co-design
[09:23:10] we are in long-term discussions/collaboration over this with Ethereum, Bitcoin Cash. just talk right now.
[09:23:16] this was recently published though suggesting more uptake though I guess https://btcmanager.com/college-students-are-the-second-biggest-miners-of-cryptocurrency/
[09:23:29] I find it pretty hard to believe their numbers
[09:24:03] well
[09:24:09] sorry, original article: https://www.pcmag.com/news/366952/college-kids-are-using-campus-electricity-to-mine-crypto
[09:24:11] just talk, no? rumors
[09:24:18] college students are already more educated than the average consumer
[09:24:29] we are not seeing many such customers anymore
[09:24:30] it's data from cisco monitoring network traffic
[09:24:33] and they're always looking for free money
[09:24:48] of course anyone with "free" electricity is inclined to do it
[09:24:57] but look at the rates, cannot make much money
[09:26:06] Ethereum is a bloated collection of bugs wrapped in a UI. I suppose they need all the help they can get
[09:26:29] Bitcoin Cash ... just another get rich quick scheme
[09:26:38] hmm :)
[09:26:51] I'll give it back to you, ok? ha ha. arrogance comes before the fall...
[09:27:17] maye we should have a little fun with CNv4 mining :)
[09:27:25] ;)
[09:27:38] come on. anyone who has watched their track record... $75M lost in ETH at DAO hack
[09:27:50] every smart contract that comes along is just waiting for another hack
[09:27:58] I just wanted to throw out the "in-protocol reward" thing, maybe someone sees the idea and wants to cowork. maybe not. maybe it's a stupid idea.
[09:29:18] linzhi-sonia: any thoughts on CN-GPU?
[09:29:55] CN-GPU has one positive aspect - it wastes chip area to implement all 18 hash algorithms
[09:30:19] you will always hear roughly the same feedback from me:
[09:30:52] "This algorithm very different, it heavy use floating point operations to hurt FPGAs and general purpose CPUs"
[09:30:56] the problem is, if it's profitable for people to buy ASIC miners and mine, it's always more profitable for the manufacturer to not sell and mine themselves
[09:31:02] "hurt"
[09:31:07] what is the point of this?
[09:31:15] it totally doesn't work
[09:31:24] you are hurting noone, just demonstrating lack of ability to think
[09:31:41] what is better: algo designed for chip, or chip designed for algo?
[09:31:43] fireice does it on daily basis, CN-GPU is a joke
[09:31:53] tevador: that's not really true, especially in a market with such large price fluctuations as cryptocurrency
[09:32:12] it's far less risky to sell miners than mine with them and pray that price doesn't crash for next six months
[09:32:14] I think it's great that crypto has a nice group of asicmakers now, hw & sw will cowork well
[09:32:36] jwinterm yes, that's why they premine them and sell after
[09:32:41] PoW is about being thermodynamically and cryptographically provable
[09:32:45] premining with them is taking on that risk
[09:32:49] not "fork when we think there are asics"
[09:32:51] business is about risk minimization
[09:32:54] that's just fear-driven
[09:33:05] Inge-: that's roughly the feedback
[09:33:24] I'm not saying it hasn't happened, but I think it's not so simple as saying "it always happens"
[09:34:00] jwinterm: it has certainly happened on BTC. and also on XMR.
[09:34:19] ironically, please think about it: these kinds of algos indeed prove the limits of the chips they were designed for. but they don't prove that you cannot implement the same algo differently! cannot!
[09:34:26] Risk minimization is not starting a business at all.
[09:34:34] proof-of-gpu-limit. proof-of-cpu-limit.
[09:34:37] imagine you have a money printing machine, would you sell it?
[09:34:39] proves nothing for an ASIC :)
[09:35:05] linzhi-sonia: thanks. I dont think anyone believes you can't make a more efficient cn-gpu asic than a gpu - but that it would not be orders of magnitude faster...
[09:35:24] ok
[09:35:44] like I say. these algos are, that's really ironic, designed to prove the limitatios of a particular chip in mind of the designer
[09:35:50] exactly the wrong way round :)
[09:36:16] like the cache size in RandomX :)
[09:36:18] beautiful
[09:36:29] someone looked at GPU designs
[09:37:31] linzhi-sonia can you elaborate? Cache size in RandomX was selected to fit CPU cache
[09:37:52] yes
[09:38:03] too large for GPU
[09:38:11] as I said, we are designing the algorithm to exactly fit CPU capabilities, I do not claim an ASIC cannot be more efficient
[09:38:16] ok!
[09:38:29] when will you do the audit?
[09:38:35] will the results be published in a document or so?
[09:38:37] I claim that single-chip ASIC is not viable, though
[09:39:06] you guys are brave, noone disputes that. 3 anti-asic hardforks now!
[09:39:18] 4th one coming
[09:39:31] 3 forks were done not only for this
[09:39:38] they had scheduled updates in the first place
[09:48:10] Monero is the #1 anti-asic fighter
[09:48:25] Monero is #1 for a lot of reasons ;)
[09:48:40] It's the coin with the most hycs.
[09:48:55] mooooo
[09:59:06] sneaky integer overflow, bug squished
[10:38:00] p0nziph0ne ([email protected]/vpn/privateinternetaccess/p0nziph0ne) has joined #monero-pow
[11:10:53] The convo here is wild
[11:12:29] it's like geo-politics at the intersection of software and hardware manufacturing for thermoeconomic value.
[11:13:05] ..and on a Sunday.
[11:15:43] midipoet: hw and sw should work together and stop silly games to devalue each other. to outsiders this is totally not attractive.
[11:16:07] I appreciate the positive energy here to try to listen, learn, understand.
[11:16:10] that's a start
[11:16:48] <-- p0nziph0ne ([email protected]/vpn/privateinternetaccess/p0nziph0ne) has quit (Quit: Leaving)
[11:16:54] we won't do silly mining against xmr "community" wishes, but not because we couldn'd do it, but because it's the wrong direction in the long run, for both sides
[11:18:57] linzhi-sonia: I agree to some extent. Though, in reality, there will always be divergence between social worlds. Not every body has the same vision of the future. Reaching societal consensus on reality tomorrow is not always easy
[11:20:25] absolutely. especially at a time when there is so much profit to be made from divisiveness.
[11:20:37] someone will want to make that profit, for sure
[11:24:32] Yes. Money distorts.
[11:24:47] Or wealth...one of the two
[11:26:35] Too much physical money will distort rays of light passing close to it indeed.
submitted by jwinterm to Monero [link] [comments]

Bitcoin Wallet - Download, Encrypt, Backup, & Use The Only Guide to Getting started - Bitcoin - Bitcoin.org How To Use Bitcoin Testnet - Getting Free Testcoins Chatting with an Expert on Bitcoin HALVING PUMP CAN BE ON THE WAY! (Bitcoin Cash Altcoin Can Pump With BCH Halving?)

Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ BitCore BTX was born as a response to the concerns of the Bitcoin community and has been growing and providing many more solutions to the community BitCore BTX - Your Coin, Your Money BitCore has one of the lowest transaction fees on the market while possibly providing the best on-chain scaling solution in the entire crypto-sphere. About us. Bitcoin Core is an open source project which maintains and releases Bitcoin client software called “Bitcoin Core”.. It is a direct descendant of the original Bitcoin software client released by Satoshi Nakamoto after he published the famous Bitcoin whitepaper.. Bitcoin Core consists of both “full-node” software for fully validating the blockchain as well as a bitcoin wallet. In the output produced by the above command, you can safely ignore any warnings and failures, but you must ensure the output lists "OK" after the name of the release file you downloaded. For example: bitcoin-0.20.0-x86_64-linux-gnu.tar.gz: OK. Obtain a copy of the release signing key by running the following command: Building Bitcoin Core on Windows is slightly more complicated since Bitcoin Core is mostly developed on Linux-based or other Unix-like operating systems. Below is a summary of build-windows.md to build Bitcoin Core on Windows 64-bit. Enable Windows Subsystem for Linux (WSL) Install a Linux distribution (e.g. Ubuntu) Install dependencies

[index] [25554] [1634] [20130] [6931] [30696] [24399] [25385] [3798] [15691] [24755]

Bitcoin Wallet - Download, Encrypt, Backup, & Use

How to Trade Bitcoin, Ether and Ripple Trading the Crypto Currencies thru CoreSpreads. In this video we look into the cryptocurrencies that you can trade via CoreSpreads. Satoshi developed the source code mostly himself up until mid-2010, when he handed it off to the open-source community. It is now maintained under the project called Bitcoin Core. This video is unavailable. Watch Queue Queue. Watch Queue Queue For Bitcoin Core Client updates: https://bitcoincore.org @bitcoincoreorg in Twitter Linux terminal commands: sha256sum, tar, cp, sudo, rm, exit, less * All other commands have been covered in ... #BITCOIN #ALTCOIN I'm Eren Caner , Bitcoin Cash , altcoin halving can pump with BCH halving? Bitcoin Cash pump can be on the way. Here the why and how. You also find out Bitcoin , BCH halving ...

Flag Counter