High-Value

On F-Droid apps and bitcoin donations

The recent post on FOSS android apps and how they can earn money made me curious about their bitcoin donations, so I slapped together a quick script, grabbed the donation addresses from the F-Droid metadata and queried their total received amount.
The result, sorted by total received and valued using some value of today (9366.36 EUR per BTC)

Package address total EUR
net.i2p.android.router 1BPdWwovytfGdBwUDVgqbMZ8omcPQzshpX 100.35295704 939941.92
net.i2p.android 1BPdWwovytfGdBwUDVgqbMZ8omcPQzshpX 100.35295704 939941.92
com.piratebayfree 1KeBs4HBQzkdHC2ou3gpyGHqcL7aKzwTve 76.80127006 719348.34
org.asnelt.derandom 1NZz4TGpJ1VL4Qmqw7aRAurASAT3Cq5S6s 60.84434648 569890.05
com.nononsenseapps.notepad 16DUL1X4yARfM88GN7TV6Y3wQwqrstJs7A 58.40632213 547054.64
ch.blinkenlights.android.vanilla 1adrianERDJusC4c8whyT81zAuiENEqub 52.62216723 492878.16
org.fdroid.fdroid.privileged.ota 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.fdroid.privileged 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.fdroid.ota 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.fdroid 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.basic 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
de.k3b.android.lossless_jpg_crop 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.calyxinstitute.vpn 14wntQ8cBdnhUVfYmDjXz6PbpSSX8nCtkr 17.65221369 165336.99
de.tutao.tutanota 3MDrR5gaMvL8sphuQLX6BvPPKYNArdXsv6 10.30485934 96519.02
net.osmand.plus 1GRgEnKujorJJ9VBa76g8cp3sfoWtQqSs4 8.49212217 79540.27
me.tripsit.tripmobile 1EDqf32gw73tc1WtgdT2FymfmDN4RyC9RN 7.00970601 65655.43
player.efis.pfd 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.mfd 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.zar.aus 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.usa.can 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.sah.jap 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.pan.arg 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.eur.rus 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.cfd 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
com.nutomic.zertman 1NUqm2kyaiRdssFaxYd7CQaWy4og19xH5g 5.0 46831.80
com.nutomic.ensichat 1DmU6QVGSKXGXJU1bqmmStPDNsNnYoMJB4 4.99995 46831.33
com.brentpanther.litecoinwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
com.brentpanther.ethereumwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
com.brentpanther.bitcoinwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
com.brentpanther.bitcoincashwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
im.vector.alpha 1LxowEgsquZ3UPZ68wHf8v2MDZw82dVmAE 3.65680571 34250.96
in.p1x.tanks_of_freedom 18oHovhxpevALZFcjH3mgNKB1yLi3nNFRY 3.59251169 33648.76
com.veken0m.bitcoinium 1yjDmiukhB2i1XyVw5t7hpAK4WXo32d54 3.49440553 32729.86
com.vuze.android.remote 15j7vKgJbixQFZ6AvEFw2BhtA4KG7E14JZ 2.52566983 23656.33
at.bitfire.nophonespam 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.icsdroid 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.gfxtablet 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.davdroid 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.cadroid 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
com.wireguard.android 1ASnTs4UjXKR8tHnLi9yG42n42hbFYV2um 2.36196229 22122.99
net.sourceforge.wifiremoteplay 1LKCFto9SQGqtcvqZxHkqDPqNjSnfMmsow 2.20225896 20627.15
net.sourceforge.opencamera 1LKCFto9SQGqtcvqZxHkqDPqNjSnfMmsow 2.20225896 20627.15
org.witness.sscphase1 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
org.torproject.android 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
org.havenapp.main 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.ripple 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.pixelknot 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.otr.app.im 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.orfox 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.notepadbot 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.locationprivacy 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.lildebi 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.gilga 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.courier 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.checkey 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.cacert 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.browser 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
at.or.at.plugoffairplane 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
sk.baka.aedict 1KJyEutxrm3yL7chvsciMJTvXahXoWE3Pw 2.0 18732.72
byrne.utilities.pasteedroid 1L44pgmZpeMsWsd24WgN6SJjEUARG5eY6G 1.93771879 18149.37
byrne.utilities.hashpass 1L44pgmZpeMsWsd24WgN6SJjEUARG5eY6G 1.93771879 18149.37
byrne.utilities.converter 1L44pgmZpeMsWsd24WgN6SJjEUARG5eY6G 1.93771879 18149.37
com.zoffcc.applications.zanavi 1ZANav18WY8ytM7bhnAEBS3bdrTohsD9p 1.3792561 12918.61
eu.domob.shopt 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
eu.domob.bjtrainer 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
eu.domob.angulo 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
eu.domob.anacam 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
libretasks.app 193Xb3sySr2oEMuJC6bqAov444rSyVczW 1.24689782 11678.89
com.ymber.eleven 12aDckQC6YHEn75zReQWxXFCivBBNXfRjM 1.19375821 11181.17
si.modrajagoda.didi 1FU27EyocpFFhexjoakSe7Hxvf4jD2KmFh 1.05 9834.68
com.nononsenseapps.feeder 1PdmeeGxB2iktvmtkGqwUNmYq7L9tnxjwE 1.02972708 9644.79
org.projectmaxs.transport.xmpp bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.wifichange bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.wifiaccess bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smswrite bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smssend bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smsread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smsnotify bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.shell bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.ringermode bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.phonestateread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.notification bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.nfc bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.misc bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.locationfine bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.filewrite bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.fileread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.contactsread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.clipboard bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.bluetoothadmin bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.bluetooth bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.alarmset bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.main bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
com.eibriel.reddot 1MD8wCtnx5zqGvkY1VYPNqckAyTWDhXKzY 0.923361 8648.53
org.briarproject.briar.android 1NZCKkUCtJV2U2Y9hDb9uq8S7ksFCFGR6K 0.59356774 5559.57
eu.faircode.email 13nUbfsLUzK9Sr7ZJgDRHNR91BJMuDuJnf 0.51806696 4852.40
de.robv.android.xposed.installer 1uAEzZrfJt96UHYQheUUC8gSp2TJdwdw3 0.49531493 4639.30
org.kontalk 14vipppSvCG7VdvoYmbhKZ8DbTfv9U1QfS 0.48859802 4576.38
hashengineering.groestlcoin.wallet_test 3BCeMXVny1HbDc4NK64UZs9oFjKZdajBfx 0.48 4495.85
hashengineering.groestlcoin.wallet 3BCeMXVny1HbDc4NK64UZs9oFjKZdajBfx 0.48 4495.85
org.disrupted.rumble 1PXXMinxQgYUPXzZq6BixZpJTFeiCLqDqD 0.44804797 4196.58
se.manyver 3NNGfHL96UrjggaBVQojF1mnGnXNx1SXv7 0.44135235 4133.86
org.schabi.sharewithnewpipe 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.schabi.openhitboxstreams 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.schabi.newpipelegacy 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.schabi.newpipe 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.mariotaku.twidere 1FHAVAzge7cj1LfCTMfnLL49DgA3mVUCuW 0.33555159 3142.90
de.gabbo.forro_lyrics 1MDjHkXQud77UJk6TqmGkjeyhmz67NfE6g 0.32967373 3087.84
org.disroot.disrootapp 1GNmDSXxpU1zaxEopKCJK2TzLh3dbZAxEA 0.32853919 3077.22
com.dfa.hubzilla_android 1GNmDSXxpU1zaxEopKCJK2TzLh3dbZAxEA 0.32853919 3077.22
com.watabou.pixeldungeon 1LyLJAzxCfieivap1yK3iCpGoUmzAnjdyK 0.30544626 2860.92
ca.pr0ps.xposed.entrustunblocker 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
ca.cmetcalfe.xposed.flatconnectivityicons 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
ca.cmetcalfe.xposed.disablebatterywarnings 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
ca.cmetcalfe.locationshare 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
eu.faircode.netguard 13vtPytVVqCwojmohAqsK61Tk4yGXSWpJK 0.28845628 2701.79
org.totschnig.myexpenses 1GCUGCSfFXzSC81ogHu12KxfUn3cShekMn 0.26904759 2520.00
com.termux.window 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.widget 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.tasker 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.styling 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.boot 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.api 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
se.leap.riseupvpn 1F3KowUJBfvocr1H6DRvwFxfETJ18e8Dp6 0.25404247 2379.45
eu.siacs.conversations.voicerecorder 1AeqNAcg85APAZj9BZfAjdFCC5zesqXp2B 0.25226604 2362.81
eu.siacs.conversations.legacy 1AeqNAcg85APAZj9BZfAjdFCC5zesqXp2B 0.25226604 2362.81
com.morphoss.acal 1C7ChLNbwiQNWS6BLCPNU5TzX3ve7Xup2m 0.24548194 2299.27
com.b44t.messenger 18e3zwis2raitdZVhEhHHT7xG6oXsZte9L 0.24530249 2297.59
com.achep.acdisplay 1GYj49ZnMByKj2f6p7r4f92GQi5pR6BSMz 0.23828669 2231.88
net.alegen.android.netclip 1862EpKxs4BGUM6Td2Gs83QCkVC889Eqja 0.23149008 2168.22
com.simplemobiletools.voicerecorder 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.thankyou 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.smsmessenger 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.notes.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.notes 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.musicplayer 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.gallery.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.gallery 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.flashlight 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.filemanager.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.filemanager 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.draw.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.draw 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.dialer 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.contacts.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.contacts 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.clock 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.camera 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.calendar.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.calendar 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.calculator 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.applauncher 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
cx.hell.android.pdfviewpro 1MLdh6uAPymWVJ4bmRde684uTcLJWwumkK 0.20361036 1907.09
cx.hell.android.pdfview 1MLdh6uAPymWVJ4bmRde684uTcLJWwumkK 0.20361036 1907.09
de.grobox.liberario 12JaQp8zfqRb83JfSwVjH4rZWsZnWRPoyG 0.18405547 1723.93
de.grobox.blitzmail 12JaQp8zfqRb83JfSwVjH4rZWsZnWRPoyG 0.18405547 1723.93
com.todobom.opennotescanner 1H5tqKZoWdqkR54PGe9w67EzBnLXHBFmt9 0.16962324 1588.75
org.libreoffice.impressremote 129jj3HiLfj3zCfqoro3sMTdovizXEdo8A 0.16380002 1534.21
org.eu.exodus_privacy.exodusprivacy 1exodusdyqXD81tS8SkcLhyFj9ioxWsaZ 0.15745937 1474.82
org.openintents.shopping 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.safe 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.notepad 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.flashlight 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.filemanager 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
de.smasi.tickmate 18tub3juj26zyGwdpmGDLgtLEpfFf2Nvhu 0.14452004 1353.63
me.hda.urlhda 1N5czHaoSLukFSTq2ZJujaWGjkmBxv2dT9 0.142 1330.02
com.passcard 1N5czHaoSLukFSTq2ZJujaWGjkmBxv2dT9 0.142 1330.02
org.blokada.alarm 16rJ49uNKCohVhHvWNganP6Y48Ba9BTyKd 0.14151834 1325.51
org.floens.chan 1N7VtcNh8L8u4tF9CJ38GjnPbmxM4Vixi6 0.13177915 1234.29
press.condense.www 325oe18pc8npqHeBGozobnvWfXXe3pujXq 0.12791726 1198.12
org.quantumbadger.redreader 1874wapGxDo2vEp4avisda4gx3SCjsHCQJ 0.12570044 1177.36
wb.receiptspro 3MGikseSB69cGjUkJs4Cqg93s5s8tv38tK 0.12023971 1126.21
be.brunoparmentier.wifikeyshare 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
be.brunoparmentier.openbikesharing.app 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
be.brunoparmentier.dnssetter 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
be.brunoparmentier.apkshare 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
org.smssecure.smssecure 1LoKZXg3bx6kfwAhEFQqS9pgeCE1CFMEJb 0.10927359 1023.50
mobi.boilr.boilr 1PHuSWfuAwR6oz9qV93rTdMVozfM85Qqxx 0.101 946.00
com.morlunk.mountie 1ySD4UzFDtPLq9agRg9eiFtWmz6DJ7bBf 0.09228972 864.42
org.lf_net.pgpunlocker 18ii4wvKxPFvKoGk7MXLngq9yWNsp7ABPd 0.08827862 826.85
com.orpheusdroid.sqliteviewer 1Cbf61y8XNx3BLWvoZB71x4XgBKB7r8BuB 0.07990648 748.43
com.orpheusdroid.screenrecorder 1Cbf61y8XNx3BLWvoZB71x4XgBKB7r8BuB 0.07990648 748.43
com.biglybt.android.client 1BiGLYBT38ttJhvZkjGc5mCw5uKoRHcUmr 0.06538094 612.38
net.gsantner.markor 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
net.gsantner.dandelior 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
io.github.gsantner.memetastic 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
io.github.froodyapp 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
de.live.gdev.timetracker 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
de.live.gdev.cherrymusic 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
com.github.dfa.diaspora_android 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
org.woltage.irssiconnectbot 12Xe9L8Kam2F838RipTstT1BAxWLZjWRxh 0.05900001 552.62
dev.ukanth.ufirewall 1LBUdALwYXDv38wvnUSGvsFjituaWAHvFo 0.05663316 530.45
org.totschnig.sendwithftp 1Dmj6keLGgNHBUD5unsbZz5vnk9wRinRAy 0.05247253 491.48
com.github.yeriomin.yalpstore 14HvYHKe6joHbQjVdAPd1Ha1yXaGS2pVTW 0.05018261 470.03
com.github.yeriomin.smsscheduler 14HvYHKe6joHbQjVdAPd1Ha1yXaGS2pVTW 0.05018261 470.03
com.github.yeriomin.dumbphoneassistant 14HvYHKe6joHbQjVdAPd1Ha1yXaGS2pVTW 0.05018261 470.03
org.ethack.orwall 1Kriu9owRhEsFkj8Lc6Wr5xTv8YTNphhXn 0.04385552 410.77
org.indywidualni.fblite 1JUaZytkub2CP5jhRYQDDY6pibqrUUSp2y 0.04214968 394.79
com.anthony.deepl.openl 3DetrDfft3ChjXMQUsTwQL1ozQvBXwGSsQ 0.04 374.65
org.jamienicol.episodes 149XkMSs84ZyzNMqiQeJLt5DbPru16amwA 0.033 309.09
io.github.powerinside.syncplay 16E1hn96zg9h16VCrxSG6p7b72vyNh64ft 0.03048045 285.49
io.github.powerinside.scrollsocket 16E1hn96zg9h16VCrxSG6p7b72vyNh64ft 0.03048045 285.49
nya.miku.wishmaster 1LaumSD5Y9npHxsq9Cqo3esmWiytqv95QW 0.03 280.99
am.ed.importcontacts 14FPuKQfmV31Fx4uxwXvehmM189nxaQpKB 0.02695857 252.50
am.ed.exportcontacts 14FPuKQfmV31Fx4uxwXvehmM189nxaQpKB 0.02695857 252.50
org.tasks 136mW34jW3cmZKhxuTDn3tHXMRwbbaRU8s 0.02141326 200.56
com.moonpi.tapunlock 1NZGAU1rEs1zBpwdjmnBjiyRsJHfycWhSF 0.02106 197.26
com.moonpi.swiftnotes 1NZGAU1rEs1zBpwdjmnBjiyRsJHfycWhSF 0.02106 197.26
org.telegram.messenger 1McafEgMvqAVujNLtcJumZHxp2UfaNByqs 0.02006732 187.96
eu.faircode.xlua 1GePXhRPgLhwQmBwRHhX1nSCgvfnCY97Gg 0.01687755 158.08
org.decsync.sparss.floss 1JWYoV2MZyu8LYYHCur9jUJgGqE98m566z 0.01598957 149.76
org.decsync.cc 1JWYoV2MZyu8LYYHCur9jUJgGqE98m566z 0.01598957 149.76
org.asdtm.goodweather 1FV8m1MKqZ9ZKB8YNwpsjsuubHTznJSiT8 0.01510861 141.51
org.asdtm.fas 1FV8m1MKqZ9ZKB8YNwpsjsuubHTznJSiT8 0.01510861 141.51
com.nma.util.sdcardtrac 16bxTv1fP8X2QN5SWXc1AcKhhA1tJQKcTa 0.015 140.50
com.kunzisoft.keyboard.switcher 1DSwXCk7Sob24sNsofywNoRQw2f5Qj5t2F 0.01473243 137.99
com.kunzisoft.keepass.libre 1DSwXCk7Sob24sNsofywNoRQw2f5Qj5t2F 0.01473243 137.99
fr.kwiatkowski.ApkTrack 19wFVDUWhrjRe3rPCsokhcf1w9Stj3Sr6K 0.01440284 134.90
com.stripe1.xmouse 17DaqbcEEG3Hn5jBv3sRjPTUUCW1eBp1Wg 0.01358135 127.21
org.nutritionfacts.dailydozen 3GQUrb9sw36MoQeZNJ4g16CCNqgr3Va6bx 0.0118 110.52
com.stoutner.privacybrowser.standard 1Jiooc5L238VnhiWtkdYEkwm7kRNWQspSC 0.01159484 108.60
org.sufficientlysecure.termbot 1LY6Hs6SurATjfxnihzLMDUMUuMxvQ4aEi 0.01151042 107.81
org.sufficientlysecure.keychain 1LY6Hs6SurATjfxnihzLMDUMUuMxvQ4aEi 0.01151042 107.81
com.zeapo.pwdstore 1H1Z1NPTrR5Cej9bKV3Hu4f5WJZYtkbpox 0.01141762 106.94
pk.contender.earmouse 1FdwmPaKhE6pmPRxNHcWh3yFDo3mdtMPy 0.01041024 97.51
im.quicksy.client 3KAD8vew6tPZDjiUJNnZ3YUoUxrCEVNwFL 0.01024848 95.99
eu.siacs.conversations 3KAD8vew6tPZDjiUJNnZ3YUoUxrCEVNwFL 0.01024848 95.99
org.hoi_polloi.android.ringcode 18FLvxn8Vgz5DTgVH1kT4DRJoaANpWhqvP 0.01 93.66
at.linuxtage.companion 1GLTBBirbj8GZ8uY1gwovZ1QEMjfWu3rWT 0.01 93.66
com.jarsilio.android.waveup 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
com.jarsilio.android.scrambledeggsif 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
com.jarsilio.android.pocketup 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
com.jarsilio.android.drowser 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
se.leap.bitmaskclient 1Fze6GLjoxFnwAGNreYLK8ktFdGJdPRxeY 0.00763591 71.52
com.saha.batchuninstaller 3GRYNKRUFsefuvKuTycgbMjB4DFxUXVys4 0.007 65.56
org.sufficientlysecure.viewer.fontpack 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.viewer 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.standalonecalendar 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.localcalendar 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.ical 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.shortcuts 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.ntpsync 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.fastergps 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.birthdayadapter 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
com.moez.QKSMS 3ELLdraJTuJB2CtQACZiAuf1X3udeAsRgP 0.00403494 37.79
org.xposeddownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
org.opengappsdownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
org.basketbuilddownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
org.afhdownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
com.gianlu.aria2app 18rrPNGgz8UkzUYgAnqVye83xEe5fB7XfY 0.00330638 30.97
com.gianlu.aria2android 18rrPNGgz8UkzUYgAnqVye83xEe5fB7XfY 0.00330638 30.97
com.oriondev.moneywallet 1J3APoaFT2jcqRzpb8bEt2rwUn3mDpWE5U 0.00290149 27.18
com.omegavesko.holocounter 19J43UNjckM9Q2M59ZM8ptCW5kA1dWdHdp 0.00277121 25.96
ir.hsn6.turo 1PUJ5sFWxvbx5Np2CjFmhHFnzPe2GPvinj 0.00271154 25.40
com.fr3ts0n.stagefever 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.ecu.gui.androbd 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.androbd.plugin.sensorprovider 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.androbd.plugin.mqtt 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.androbd.plugin.gpsprovider 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
de.tadris.fitness 3BSbGRbJaiSxVg3D6nVRK5C1SZEezhjtK5 0.00214369 20.08
eu.uwot.fabio.altcoinprices 353x3kNMUaAt3i79kQTf3KCJWRAVXSRGpW 0.00213 19.95
ch.bailu.aat 3GK4KLiqKqGg5UQxdkkGXhhDZkdFFicy5T 0.002 18.73
org.elijaxapps.androidxmrigminer 37GpugVZNiof2DzWQX5aivHewc4wZLxATL 0.00189005 17.70
io.oversec.one 16tan5fBNJ6n1QmVxwvvondyvuwgx1W6fE 0.00177442 16.62
com.goltzkiste.guessaday 1Guessas8CtCA9S9ZA9p9fCFAD3VZTE9ey 0.00176227 16.51
net.khertan.forrunners 1s38rpyuJvfvcRFaESZmVSp6EYpVLEDWU 0.00134051 12.56
de.schildbach.oeffi bc1qxm9r8n3pe47r30e04gs2xsalxef55zrfvelvln 0.0012577 11.78
org.gdroid.gdroid 1J2bbhJYksSjeynGGhuSPN9aTEaxiGm4nR 0.001 9.37
com.gitlab.ardash.appleflinger.android 1J2bbhJYksSjeynGGhuSPN9aTEaxiGm4nR 0.001 9.37
org.zamedev.gloomydungeons2.opensource 1BkmsNEeW5A2YketBaa4pDFSAcDwnDuyDp 0.00099 9.27
net.fabiszewski.ulogger bc1qt3uwhze9x8tj6v73c587gprhufg9uur0rzxhvh 0.00097941 9.17
ir.hsn6.trans 1MkJyXh8y3ViXTAFhKUpXfgfECEfnZmLGY 0.00080184 7.51
net.frju.flym 3DprwFMg5bXGz8QimyiaoEE7mmCkj2DGf5 0.00068 6.37
com.zeusln.zeus 3Lbz4vdt15Fsa4wVD3Yk8uGf6ugKKY4zSc 0.0006 5.62
de.schildbach.wallet bc1qedxd9jssgw2fferdmjyyh6fm8jax75q7drfnd4 0.00059521 5.57
com.zoffcc.applications.trifa 1TRifA7eNLHZEcCTj43eYVWHBbLqTuXkS 0.00028782 2.70
com.notecryptpro 1MHEbHt4sBeqGoriwAq1MsXZaZJinoUeLH 0.00027552 2.58
ir.hsn6.defendo 16D7Nroenpx4QDNqfq3Js7sdAVhew2NzGp 0.00018749 1.76
org.proninyaroslav.libretorrent 1Af9DgxtWvVp6bFiYQw2MeWtRzTXshRYpB 0.0001747 1.64
me.shrimadhavuk.numselapp 13csS5SByVR4e3tJ9c4gjC18Lua8dXDp9A 0.00010397 0.97
com.wesaphzt.privatelock 1GCkvAg9oG79niQTbh6EH9rPALQDXKyHKK 5.773e-05 0.54
com.wesaphzt.privatelocation 1GCkvAg9oG79niQTbh6EH9rPALQDXKyHKK 5.773e-05 0.54
ru.glesik.nostrangersms 1DbZjPqe4uaBv32deNqwbWUTrCempo2Wqk 5e-05 0.47
ru.ttyh.neko259.notey 1Lh7a1tx7EREENawQyHhiKoCRF6u6TzVrD 0.0 0.00
re.jcg.playmusicexporter 1NdzpDWPQ53xWT5fraGPZX5F9XrKiPBXjp 0.0 0.00
pl.sanszo.pcis 1PbH84rewi34Ffgr3C5NutMdvEzSQ13wUt 0.0 0.00
pl.net.szafraniec.NFCTagmaker 17E32x5ygXkqf5EWJkryZuarUDUFrb8UqQ 0.0 0.00
pl.net.szafraniec.NFCKey 17E32x5ygXkqf5EWJkryZuarUDUFrb8UqQ 0.0 0.00
org.valos.isolmoa 1LbgYALbkQ2Trgh4yXqdBnbdQosGard5hd 0.0 0.00
org.thecongers.mtpms 1Pg54vVnaLxNsziA6cy9CTefoEG5iAm9Uh 0.0 0.00
org.pacien.tincapp 152t9TEBBhEescQx5gG7T5wHaJVeupAXQm 0.0 0.00
org.opengemara.shiurim 19p5TXDfMksHjUstFEp2PUt383Cy7JdmLa 0.0 0.00
org.nuntius35.wrongpinshutdown 1LSs1BR4ktQcW8DrCjrSrWUvBD6h2rqNJm 0.0 0.00
org.nick.wwwjdic 1DXhWFS9SL78GGyX7Luao9EuP5SxtDiPG1 0.0 0.00
org.miamplayer.autoairplanemode 39RBokXr4V9FPpuF7v1bM6PYcbgRRApp9W 0.0 0.00
org.mbach.lemonde 39RBokXr4V9FPpuF7v1bM6PYcbgRRApp9W 0.0 0.00
org.kost.nmap.android.networkmapper 1588ArbHPcb5VtpZPQgue9iPZ9LiA1eEjF 0.0 0.00
org.kost.externalip 1KbtLnxp6mhkGznFNZZQdcaCUQHmrTtLm4 0.0 0.00
org.kaqui 12bnT7epKmf9ztkAeuM8dHCcoc76r9rgVX 0.0 0.00
org.emunix.unipatcher 16coztryz7xbNNDNhhf98wuHmi3hEintsW 0.0 0.00
org.emunix.insteadlauncher 16coztryz7xbNNDNhhf98wuHmi3hEintsW 0.0 0.00
org.chickenhook.startflagexploit bc1qvll2mp5ndwd4sgycu4ad2ken4clhjac7mdlcaj 0.0 0.00
org.androidpn.client 13MjTPDFQtxv1u1sWURkDduFSw97KbMfsS 0.0 0.00
org.amoradi.syncopoli 1DT8ijBkGUAvW9VZqfCQBJFS62vvw5E7QK 0.0 0.00
net.schueller.peertube 1LoTXo728HzYTtyfbkaf5ewSRvu8ABTDPm 0.0 0.00
net.mabako.steamgifts 1NQBKppWPZiE5PshLxqfFW4pgsnAv9irEu 0.0 0.00
name.gdr.acastus_photon 1NjjuTxXm3ezpnVUGk4VmdEZUcym3SKZ8z 0.0 0.00
me.dbarnett.acastus 1NjjuTxXm3ezpnVUGk4VmdEZUcym3SKZ8z 0.0 0.00
me.danielbarnett.addresstogps 1NjjuTxXm3ezpnVUGk4VmdEZUcym3SKZ8z 0.0 0.00
it.reyboz.screenlock 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.reyboz.minesweeper 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.reyboz.chordshift 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.reyboz.bustorino 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.andreascarpino.hostisdown 1Ph3hFEoQaD4PK6MhL3kBNNh9FZFBfisEH 0.0 0.00
is.zi.huewidgets 1FdGg777eP4cqMrJVMRQiMXEHE2Ee6F62T 0.0 0.00
ir.hsn6.tpb 12SL5VgtjozKTXMgpX7w4MjKvvcFAHbTks 0.0 0.00
ir.hsn6.k2 1iNMJMFqDgYp7iUMd4qkP79CiCLSwLPyp 0.0 0.00
io.github.tjg1.nori 1NHUsSzj3N7TE8rykUYk8rqqLWWSmTVzdp 0.0 0.00
in.shick.lockpatterngenerator 1JscvZEbchRUpCXYX13bJb3aF6U1yT9BwG 0.0 0.00
ga.testapp.testapp 3NUiJXDCkyRTb9Tg7n63yK6Y7CexADtSEh 0.0 0.00
fr.renzo.wikipoff 1BAaxTvK1jkoFKf7qWF2C6M4UX1y86MxaF 0.0 0.00
fr.cph.chicago.foss 13WUmCX1AePEKFGv5U1qRgBockFahsm21o 0.0 0.00
fr.corenting.traficparis 3JmaEkuviReVdCG8fjqCs5LwQkaEGcTMtZ 0.0 0.00
eth.matteljay.mastermindy 14VZcizduTvUTesw4T9yAHZ7GjDDmXZmVs 0.0 0.00
design.codeux.authpass.fdroid 3NcBacCmJbYWpwxj6rWzpM7sx48etMrPtc 0.0 0.00
de.yaacc 1MUvbfNgunNCUtitCkoEEMgmQGZJJg4isj 0.0 0.00
de.vanitasvitae.enigmandroid 1EqhcKs1pZJhEmyCtbH3qtkHT3Y48MCoAT 0.0 0.00
de.schildbach.wallet_test bc1qglkj2svuu3xsktup5xla8u2wjzlu8mfzk6509r 0.0 0.00
de.naturalnet.zahnarztgeraeusche 1EAytSwn1u7tKTZ9sMDVCzDqe2nwVf4Pra 0.0 0.00
de.naturalnet.mirwtfapp 1EAytSwn1u7tKTZ9sMDVCzDqe2nwVf4Pra 0.0 0.00
de.k4ever.k4android 1KiwFPGCunGXF53DBTBf32cNTPXq9FbX5H 0.0 0.00
de.jkliemann.parkendd 1HBFDdz7dJeBE2c3zQmWnzeWCbHoZQ64dd 0.0 0.00
de.Cherubin7th.blackscreenpresentationremote 18QSJmV6Liia7Cau65JnEj2JyxEUCGE2oz 0.0 0.00
com.tritop.androsense2 1Dj4Xkz5KtsarmioEKuuZCBVjahr14dih4 0.0 0.00
com.toxtox.philosopherstonewidget 1KvYjRx1VozqUpiYSCMrEL6mo9LvmpCcNN 0.0 0.00
com.sanskritbasics.memory bc1q3xasvfn2c84dprkk2mxj5g7n6ujwylphu8qsf3 0.0 0.00
com.rockbyte.arxiv 1jokQaTneW1KCbCWsMdVtvPv6oSJ1H3tF 0.0 0.00
com.rigid.birthdroid 1BLEeqwXnJJbpaLHiskZ5WyJJRyEWqCAQZ 0.0 0.00
com.readrops.app bc1qlkzlcsvvtn3y6mek5umv5tc4ln09l64x6y42hr 0.0 0.00
com.onetwofivegames.kungfoobarracuda 1MVNsgRmLqgMoEoQu918ozFFiTaepF8Ti5 0.0 0.00
com.mdroid 18BqyV9mNbFLi5HNNnfUprnPJyJDFP59Xh 0.0 0.00
com.mareksebera.simpledilbert 1FpGN3kcZ3GQsaJgBa8rxGRJjBjJavu78g 0.0 0.00
com.marceljurtz.lifecounter 1HDdKd3uoxdvS8pBKKKxEkjoJqUuBiEjkL 0.0 0.00
com.llamacorp.equate 15KCzAPJvSJLUfjuTQgAgSiSwQu6uLiexC 0.0 0.00
com.kn.paper_foss_theme 1CYiRF6AncdNkxcWTRFf5Mxi7UaFhC3jFG 0.0 0.00
com.ideasfrombrain.search_based_launcher_v2 1NapZs8brWNifGk7QFemqTByczdBAAg9cA 0.0 0.00
com.gmail.anubhavdas54.whatsdeleted bc1qs50wst8x53ud5lr80wukhjcy6l7zpxf5mz5rtm 0.0 0.00
com.github.igrmk.smsq 32JdGEVP42WiVxsADa3Z65qn1xe2K7Yg3S 0.0 0.00
com.genonbeta.TrebleShot 1DBsq8aZjn54hnDYsRY7pTLb3HfsE1mSv8 0.0 0.00
com.example.root.analyticaltranslator 15WVb3LZWCsdZGjkNFBuELwt3U4zpnSgwa 0.0 0.00
com.emmanuelmess.simpleaccounting 1HFhPxH9bqMKvs44nHqXjEEPC2m7z1V8tW 0.0 0.00
com.easwareapps.marbleone_ad_free 1PNwD199whFao1rjMX82Zi5A7M5B6KB7be 0.0 0.00
com.easwareapps.g2l 1PNwD199whFao1rjMX82Zi5A7M5B6KB7be 0.0 0.00
com.easwareapps.f2lflap2lock_adfree 1PNwD199whFao1rjMX82Zi5A7M5B6KB7be 0.0 0.00
com.danhasting.radar 1EwgjPGYiChJ5vyBndt9ugzd963FiVc6gj 0.0 0.00
com.atop 15G2T13emQnJRMvA74Zr6Q71bBcaYBn71v 0.0 0.00
com.aptasystems.dicewarepasswordgenerator 1PbHGv88KH6SXw6d66uSFTUzW2aeqxvQ7V 0.0 0.00
com.andreasgift.totalzero 1Q9TinY9kWoNMWuiToHiGC9uxCk6Vd41Gb 0.0 0.00
com.anddevw.getchromium 188RxvRnSXSZZnjuDdLwNirHDfNusVPobh 0.0 0.00
at.tacticaldevc.panictrigger 1EVr5tm2kugffNy3RWPGFoug6X9v3GTxuJ 0.0 0.00
im.vector.riotx 1LxowEgsquZ3UPZ68wHf8v2MDZw82dVmAEa -1.0 -9366.36
im.vector.app 1LxowEgsquZ3UPZ68wHf8v2MDZw82dVmAEa -1.0 -9366.36
I know this is flawed, I found it interesting nonetheless
The post which inspired this: https://www.reddit.com/fossdroid/comments/hyral2/are_there_fossdroid_apps_that_are_making_money/
submitted by prcrst to fossdroid [link] [comments]

List of CFML Vulnerabilities & Security Issues

This list is updated frequently as we detect more issues, also note that we can’t detect these issues in all cases on all servers, even if the issue has not been patched yet.
Here are some CFML Vulnerabilities & Security Issues that you might have faced-

  1. Jakarta Virtual Directory Exposed – The /jakarta virtual directory (which is required by CF10+ on Tomcat/IIS) is serving files such as isapi_redirect.properties or isapi_redirect.log. The only URI that should be served is /jakarta/isapi_redirect.dll – you can use Request Filtering to block.
  2. Bitcoin Miner Discovered – Found files in /CFIDE that match the signature of a bitcoin miner exploit. Look for /CFIDE/m /CFIDE/m32 /CFIDE/m64 and /CFIDE/updates.cfm among others.
  3. Hotfix APSB11-14 Not Installed – Apply the hotfixes located in Adobe Security Notice apsb11-14.
  4. Railo Security Issue 2635 – Input of Chr(0) to the ReplaceList function can cause infinate loop / crash. Fixed in Version 4.1.1.008
  5. XSS Injection in cfform.js – A document.write call was found in your /CFIDE/scripts/cfform.js file, an attacker may be injecting a javascript, please check your cfform.js file.
  6. Executable found in CFIDE – Found executable file(s) in /CFIDE with one of the following file extensions: dll, exe, bat, sh
  7. Heartbleed Vulnerability Detected – The heartbleed vulnerability is a bug in OpenSSL (the crypto library used by Apache, NGinx, and others) that can allow the leakage of private keys used for TLS/SSL encryption.
  8. OpenBD AdminAPI Exposed to the Public – The /bluedragon/adminapi/ directory is open to the public it should be locked down to prevent exploit.
  9. Security Hotfix APSB12-26 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB12-26 was not found to be installed on your server. This hotfix resolves a sandbox permission issue.
  10. Security Hotfix APSB17-30 Not Installed Or Partailly Installed – The security hotfix referenced in Adobe Security Bulletin APSB17-30 was not found to be fully installed on your server. For the hotfix to be effective you must have Java 8 update 121 or greater installed. This hotfix resolves two critical vulnerabilities CVE-2017-11286 and CVE-2017-11283 / CVE-2017-11284 and one important vulnerability CVE-2017-11285. The issues are resolved in ColdFusion 11 Update 13+ and ColdFusion 2016 Update 5+ with Java 8 update 121 or greater.
  11. ColdFusion Example Applications Installed – The ColdFusion example applications are installed at /cfdocs/exampleapps/ or /CFIDE/gettingstarted/, they should not be installed on a production server.
  12. Svn Hidden Directory Exposed – A request for /.svn/text-base/index.cfm.svn-base appears to resolve to a subversion repository, which could lead to source code disclosure. Please block .svn/
  13. Solr Search Service Exposed – CVE-2010-0185 detected. ColdFusion 9 Apache Solr services are exposed to the public. Any data in solr search collections may be exposed to the public. Follow the instructions in APSB10-04 to remedy, or upgrade to ColdFusion 9.0.1.
  14. TLS Compression Supported – TLS Compression should be disabled due to the CRIME TLS vulnerability.
  15. Security Hotfix APSB11-04 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB11-04 was not found to be installed on your server. This hotfix also contains most prior security hotfixes.
  16. Git Hidden Directory Exposed – A request for /.git/config appears to resolve to a git repository, wouch could lead to source code disclosure. Please block .git/
  17. Cross Site Scripting Vulnerability CVE-2011-4368 – CVE-2011-4368 detected. Apply the hotfix located in Adobe Security Notice apsb11-29.
  18. JVM Vulnerable to Java Null Byte Injection – The JVM that you are running is vulnerable to null byte injections (or null byte poisioning) in java.io file operations. Java 1.7.0_40+ or 1.8+ attempt to mitigate null byte injection attacks.
  19. Java 11 Security Update Available – The JVM that you are running contains security vulnerabilities that could be exploited in server side environments. Update to the latest version of Java 11. Note that Oracle Java 11 requires a commercial license. Adobe CF customers can download Oracle Java 11 from the ColdFusion Downloads Page. You can also use OpenJDK, Amazon Corretto, or other non-oracle JVMs for free.
  20. Security Hotfix APSB19-10 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB19-10 was not found to be installed on your server. This hotfix resolves 2 issues, one important (CVE-2019-7092) and one critical (CVE-2019-7091). The issues are resolved in ColdFusion 11 Update 16+ ColdFusion 2016 Update 8+ and ColdFusion 2018 Update 2+. For all security fixes to be effective you should also have Java 8 update 121 or greater installed.
  21. Cross Site Scripting Vulnerability CVE-2011-0583 – CVE-2011-0583 detected. Apply the hotfixes located in Adobe Security Notice apsb11-04. The detection of this vulnerability also indicates to a high degree of likelihood that the following vulnerabilities may also exist: CVE-2011-0580, CVE-2011-0581, CVE-2011-0582, CVE-2011-0584
  22. Apache 2.2 Security Update Available – The version of Apache you are running does not contain the most recent security fixes.
  23. BlaseDS/AMF External XML Entity Injection – CVE-2009-3960 detected. You must apply the hotfix specified in Adobe Security Bulliten APSB10-05, otherwise an attacker can read any file on the server that ColdFusion has permission to read. You need to do this even if you don’t use BlaseDS or Flash Remoting because it is enabled in CF by default.
  24. SSL Version 2 Enabled – Your Web Server is accepting SSL V2 connections, a weak protocol. For PCI compliance, and strong security you must disable this protocol on your web server.
  25. Missing Strict-Transport-Security Header – This domain supports HTTPS but does not send the HTTP Strict-Transport-Security response header (HSTS) to force HTTPS.
  26. The /CFIDE/scripts directory is in default location. – Consider changing the default location of /CFIDE/scripts/ by changing the value of the Default Script Src setting in the ColdFusion Administrator.
  27. Recalled Hotfix 10.0.3 Installed – You are running ColdFusion 10.0.3 which has been recalled by adobe due to bugs in the release. Please install the latest 10.0 hotfix.
  28. ComponentUtils Exposed to the Public – The /CFIDE/componentutils/ directory is open to the public it should be locked down to prevent exploit.
  29. ColdFusion Update Available – You may not be running the latest version of ColdFusion 8, consider updating to ColdFusion 8.0.1
  30. Security Hotfix APSB13-10 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB13-10 was not found on your server. This hotfix resolves authentication issues that could allow an attacker impersonate a user in your application, or a ColdFusion Administrator.
  31. CVE-2010-2861 Detected – Path Traversal Vulnerability detected (CVE-2010-2861 APSB10-18), this allows an attacker to read any file on the servers file system that ColdFusion has access to (within the same drive on windows).
  32. Security Hotfix APSB13-19 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB13-19 was not found on your server.
  33. Security Hotfix APSB12-15 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB12-15 was not found to be installed on your server. This hotfix resolves a HTTP response splitting vulnerability in the ColdFusion Component Browser CVE-2012-2041.
  34. Security Hotfix APSB16-16 Not Installed – The security hotfix referenced in Adobe Security Bulletin APSB16-16 was not found to be installed on your server. This hotfix addresses a XSS issue, a Java Deserialization Vulnerability and a TLS Hostname verification issue. This issue is fixed in ColdFusion 10 Update 19+, ColdFusion 11 Update 8+, and ColdFusion 2016 Update 1+
  35. Vulnerable PageSpeed Module – The Version of PageSpeed Module you are using may be vulnerable to one or more vulnerabilities. Update your PageSpeed web server module to the latest version to resolve.
  36. TLS 1.2 Is Not Enabled – Configure your server to accept TLS 1.2 connections for optimal HTTPS security. Note for IIS you must be running Windows 2008r2 or greater for TLS 1.2 support. You can use our IIS SSL / TLS configuration tool to toggle protocol support on your server.
  37. Java 13 EOL – Java 13 has reached end of life at the release of Java 14. It is not a LTS (Long Term Support Version), you can use Java 11 for LTS.
  38. Lucee Security Issue 2015-08-06 – Lucee fixed an XSS issue in version 4.5.1.023. This issue remains unpatched in Railo.
submitted by aligatorraid to coldfusion [link] [comments]

The importance of being mindful of security at all times - nearly everyone is one breach away from total disaster

This is a long one - TL;DR at the end!

If you haven't heard yet: BlankMediaGames, makers of Town of Salem, have been breached which resulted in almost 8 million accounts being leaked. For most people, the first reaction is "lol so what it's just a game, why should I really care?" and that is the wrong way to look at it. I'd like to explain why everyone should always care whenever they are part of a breach. I'd also like to talk about some ways game developers - whether they work solo or on a team - can take easy steps to help protect themselves and their customers/players.
First I'd like to state that there is no practical way to achieve 100% solid security to guarantee you'll never be breached or part of a breach. The goal here will be to get as close as possible, or comfortable, so that you can rest easy knowing you can deal with problems when they occur (not if, when).

Why You Should Care About Breaches

The sad reality is most people re-use the same password everywhere. Your email account, your bank account, your steam account, your reddit account, random forums and game websites - you get the idea. If you haven't pieced it together yet the implication is that if anyone gets your one password you use everywhere, it's game over for you - they now own all of your accounts (whether or not they know it yet). Keep in mind that your email account is basically the holy grail of passwords to have. Most websites handle password changes/resets through your email; thus anyone who can login to your email account can get access to pretty much any of your accounts anywhere. Game over, you lose.

But wait, why would anyone want to use my password? I'm nobody!

It doesn't matter, the bad guys sell this information to other bad guys. Bots are used to make as much use of these passwords as possible. If they can get into your bank they might try money transfers. If they get into your Amazon account they might spin up $80,000 worth of servers to mine Bitcoin (or whatever coin is popular at the time). They don't care who you are; it's all automated.
By the way, according to this post (which looks believable enough to be real) this is pretty much how they got into the BMG servers initially. They checked for usernames/emails of admins on the BMG website(s) in previous breach dumps (of which there are many) and found at least one that used the same password on other sites - for their admin account!
If you want to see how many of your accounts are already breached check out Have I Been Pwned - I recommend registering all of your email addresses as well so you get notified of future breaches. This is how I found out about the Town of Salem breach, myself.

How You Can Protect Yourself

Before I go into all the steps you can (and should) take to protect yourself I should note that security is in a constant tug of war with convenience. What this means is that the more security measures you apply the more inconvenienced you become for many tasks. It's up to you to decide how much is too much either way.
First of all I strongly recommend registering your email(s) on https://haveibeenpwned.com/ - this is especially important if your email address is associated to important things like AWS, Steam developer account, bank accounts, social media, etc. You want to know ASAP when an account of yours is compromised so you can take steps to prevent or undo damage. Note that the bad guys have a head start on this!

Passwords

You probably need to have better password hygiene. If you don't already, you need to make sure every account you have uses a different, unique, secure password. You should change these passwords at least once a year. Depending on how many accounts you have and how good your memory is, this is your first big security vs convenience trade-off battle. That's easily solved, though, by using a password manager. You can find a list of password managers on Wikipedia here or you can search around for some comparison articles.
Some notable choices to consider:
Regardless of which one you choose, any of them is 100x better than not using one at all.

Multi-Factor Authentication / Two-Factor Authentication (aka MFA / 2FA)

The problem with all these passwords is that someone can still use them if they are found in a breach. Your passwords are only as strong as the website you use them on. In the case of the BMG breach mentioned above - all passwords were stored in an ancient format which has been insecure for years. It's likely that every single password in the breach can be reversed/cracked, or already have been. The next step you need to take is to make it harder for someone else to login with your password. This is done using Multi-Factor Authentication (or Two-Factor Authentication).
Unfortunately not every website/service supports MFA/2FA, but you should still use it on every single one that does support it. You can check which sites support MFA/2FA here or dig around in account options on any particular site. You should setup MFA/2FA on your email account ASAP! If it's not supported, you need to switch to a provider that does support it. This is more important than your bank account! All of the big email providers support it: GMail, Outlook.com, Yahoo Mail, etc.
The type of MFA/2FA you use depends on what is supported by each site/service, but there is a common approach that is compatible on many of them. Most of them involve phone apps because a phone is the most common and convenient "thing you have" that bad guys (or anyone, really) can't access easily. Time-based One-time Password or TOTP is probably the most commonly used method because it's easy to implement and can be used with many different apps. Google Authenticator was the first popular one, but it has some limitations which continue the security vs convenience battle - namely that getting a new phone is a super huge chore (no backup/restore option - you have to disable and setup each site all over again). Many alternatives support cloud backup which is really convenient, though obviously less secure by some measure.
Notable choices to consider:
Some sites/services use their own app, like Blizzard (battle.net) and Steam, and don't allow you to use other ones. You will probably have a few apps on your phone when all your accounts are setup, but it's worth it. You'll definitely want to enable it on your password manager as well if you chose a cloud-based one.
Don't forget to save backup codes in an actual secure location! If you lose your backup codes and your auth app/physical key you will be locked out of accounts. It's really not fun recovering in that situation. Most recommendations are to print them and put in a fireproof safe, but using some other secure encrypted storage is fine.
There is such a thing as bad MFA/2FA! However, anything is at least better than nothing. A lot of places still use SMS (text messaging) or e-mail for their MFA/2FA implementation. The e-mail one has the most obvious flaw: If someone gets into your email account they have defeated that security measure. The SMS flaws are less obvious and much less likely to affect you, but still a risk: SMS is trivial to intercept (capture data over the air (literally), clone your SIM card data, and some other methods). Still, if you're not a person of interest already, it's still better than nothing.

What Does This Have To Do With GameDev?

Yeah, I do know which subreddit I'm posting in! Here's the section that gets more into things specific to game development (or software development in general).

Secure Your Code

Securing your code actually has multiple meanings here: Securing access to your code, and ensuring your code itself is secure against exploitation. Let's start with access since that's the easier topic to cover!
If you're not already using some form of Source Control Management (SCM) you really need to get on board! I'm not going to go in depth on that as it's a whole other topic to itself, but I'll assume you are using Git or Mercurial (hg) already and hosting it on one of these sites (or a similar one):
First, ensure that you have locked down who can access this code already. If you are using private repositories you need to make sure that the only people who have access are the people who need access (i.e. yourself and your team). Second, everyone should have strong passwords and MFA/2FA enabled on their accounts. If 1 person on the team does not follow good security practices it puts your whole project at risk! So make sure everyone on the team is following along. You can also look into tools to do some auditing and even automate it so that if anyone's account becomes less secure over time (say they turned off MFA one day) they would automatically lose their access.
Additionally you should never commit secrets (passwords, API keys, tokens, social security numbers, etc) to your code repository. Probably 90% of cases where people have their AWS/Google Cloud/Azure accounts compromised and racking up huge bills for bitcoin mining is due to having their passwords/keys stored in their git repo. They either accidentally made it public or someone got access to the private repo through a compromised account. Never store sensitive information in your code repository!
Next topic: Securing your code from vulnerabilities. This one is harder to talk about for game dev as most engines/frameworks are not as susceptible (for lack of a better word) to these situations as others. In a nutshell, you need to keep track of the following:
A lot of these things cannot be solved automatically, unfortunately, but some of it can. If you are using Javascript for your game you likely will be using packages from npm - luckily they (recently) added security auditing for packages. For other languages you can look at tools like Snyk or some other alternatives to audit the libraries you use in your project. Unfortunately none that I know of are aimed at game dev in particular, but it's still important to use these tools when you can. In general, be aware of all of your code dependencies and what impact they can have on your game or your customers if there are security bugs. Impact can range from "can cheat in multiplayer" to "can get IP addresses of all players in the world" or even "can get all information I ever put on my server", etc.
In general you'll want to look into Secure Software Development Lifecycle (commonly SDLC) practices. Microsoft has some information on how they do it.

Secure Your Computer

I'm not going to go in depth on this one because at this point everyone should have a handle on this; if not there are limitless articles, blogs, and videos about the how/what/why. In summary: Keep everything updated, and don't open suspicious links.

Secure Your Website

I will have to add more to this later probably, but again there are tons of good articles, blogs, and videos on these topics. Hopefully the information in this section is enough to get you on the right track - if not feel free to ask for more info. Lots of guides can be found on Digital Ocean's site and they are relevant even if you don't use DO for your servers.
A lot of this will apply to your game servers as well - really any kind of server you expect to setup.

That's it, for now

I ran out of steam while typing this all up after a couple hours, but I may revisit it later to add more info. Feel free to ask any questions about any of these topics and I'll do my best to answer them all.

TL;DR (y u words so much??)

... in general... in general... in general... I sure wrote those 2 words a lot.

Why Should I Trust This Post?

Hopefully I have provided enough information and good links in this post that you can trust the contents to be accurate (or mostly accurate). There is certainly enough information to do some searches on your own to find out how right or wrong I might be about these things.
If you want my appeal to authority answer: I've been working at a major (network/computer) security company for almost 7 years as a software developer, and I've had to put up with pretty much every inconvenience brought on by security. I've also witnessed the aftermath of nearly every type of security failure covered in this post, via customers and the industry at large. None of the links I used are related to my employer or its products.
Edit: Fixed some typos and added some more links
More edit: added a few more points and links
submitted by exoplasm to gamedev [link] [comments]

I literally have tens of thousands of dollars in top-shelf hardware, looking to repurpose some before selling on eBay to build a NAS system, possibly a dedicated firewall device as well. o_O

Q1) What will you be doing with this PC? Be as specific as possible, and include specific games or programs you will be using.**

A1) This will be a dedicated NAS system for my home network. As such, I'm looking to have it:

- Host ##TB's of 720, 1080 & up resolution Movies and TV Shows I'm about to begin ripping from a MASSIVE DVD & Blueray collection I have.

- My kids are big on Minecraft. I understand it's possible to host your own "worlds" (or whatever they call the maps you can build) on your own "server". I think it would be pretty neat to offer them (& their friends - if can be done 'safely/securely') their own partition on one of my NAS HDD's.

- I also have accounts with a couple diff VPN companies... I understand it's possible (?) to sync said VPN's with a NAS, this might be a more relative topic on the next point/purpose...

- I'd like to be able to remotely link to this NAS for when I travel overseas and want to stream at my temp location from my house/this NAS.
______________________
Q2) What is your maximum budget before rebates/shipping/taxes?**

* A2) Here's where I make matters more complicated than most others would... I've been an advocate for Bitcoin and crypto-currencies in general since 2013. I invested in a small mining outfit back in 2014 (strictly Bitcoin/ASIC's). One of my buddies is the President of a large-scale mining operation (foreign and domestic) and he convinced me to dabble in the GPU mining-space. I made my first hardware purchase in Q4, 2017 and launched a small-scale GPU-Farm in my house since then. I had the rigs mining up until Q3 of 2018 (not cost-efficient to keep on, especially living in SoFlo) and since then, the hardware's been collecting dust (& pissing off my family members since they lost access to 3X rooms in the house - I won't let anyone go near my gear). One of my New Years Resolutions for 2019 was to clear out the house of all my mining equipment so that's all about to go up on eBay. So "budget" is relative to whatever I "MUST" spend if I can't repurpose any of the parts I already have on hand for this build... (Anyone having something I "need" and is looking to barter for one of the items I'll list later on in here, LMK).
______________________
Q3) When do you plan on building/buying the PC? Note: beyond a week or two from today means any build you receive will be out of date when you want to buy.**

A3) IMMEDIATELY! :)
______________________
Q4) What, exactly, do you need included in the budget? (ToweOS/monitokeyboard/mouse/etc\)**

A4) Well I had a half-assed idea approximately 1 year ago that it might be wise to build a bunch of 'gaming rigs' to sell on eBay with my intended repurposed mining hardware so I went on a shopping spree for like 6 months. That said; I've got a plethora of various other components that aren't even unboxed yet. 90% of the items I've purchased for this additional project were items that were marked down via MIR (mail-in-rebates) & what-not...
AFAIK, there are only 3X items I absolutely do not have which I 'MUST' find. Those would be - 1) Motherboard which accepts "ECC RAM". 2) CPU for said MOBO. 3) Said "ECC RAM".\* 
______________________
Q5) Which country (and state/province) will you be purchasing the parts in? If you're in US, do you have access to a Microcenter location?**

A5) I'm located in Southwest Florida. No Microcenter's here. Best Buy is pretty much my only option although I am a member of Newegg, Amazon & Costco if that makes any difference?
______________________
Q6) If reusing any parts (including monitor(s)/keyboard/mouse/etc), what parts will you be reusing? Brands and models are appreciated.**

A6) In an attempt to better clean up this Q&A, I'm going to list the items I have on-hand at the end of this questionnaire in-case passers-by feel like this might be a TLDR.* (Scroll to the bottom & you'll see what I mean).
______________________
Q7) Will you be overclocking? If yes, are you interested in overclocking right away, or down the line? CPU and/or GPU?**

A7) I don't think that's necessary for my intended purpose although - I'm not against it if that helps & FWIW, I'm pretty skilled @ this task already (it's not rocket science).
______________________
Q8) Are there any specific features or items you want/need in the build? (ex: SSD, large amount of storage or a RAID setup, CUDA or OpenCL support, etc)**

A8) As stated in A4; ECC RAM is non-negotiable... RAID seems like a logical application here as well.

- This will predominantly be receiving commands from MacOS computers. I don't think that matters really but figured it couldn't hurt to let you guys know.\*

- I'd also be quite fond of implementing "PFSENSE" (or something of that caliber) applied to this system so I could give my Netgear Nighthawks less stress in that arena, plus my limited understanding of PFSENSE is that it's ability to act as a firewall runs circles around anything that comes with consumer-grade Wi-Fi routers (like my Nighthawks). Just the same, I'm open to building a second rig just for the firewall.\*

- Another desirable feature would be that it draws as little electricity from the wall as possible. (I'm EXTREMELY skilled in this arena. I have "Kill-A-Watts" to test/gauge on, as well as an intimate understanding of the differences between Silver, Gold, Platinum and Titanium rated PSU's. As well as having already measured each of the PSU's I have on-hand and taken note of the 'target TDP draw' ("Peak Power Efficiency Draw") each one offers when primed with X amount of GPU's when I used them for their original purpose.\*

- Last, but not least, sound (as in noise created from the rig). I'd like to prop this device up on my entertainment center in the living room. I've (almost) all of the top-shelf consumer grade products one could dream of regarding fans and other thermal-related artifacts.

- Almost forgot; this will be hosting to devices on the KODI platform (unless you guys have better alternative suggestions?)
______________________
Q9) Do you have any specific case preferences (Size like ITX/microATX/mid-towefull-tower, styles, colors, window or not, LED lighting, etc), or a particular color theme preference for the components?**

A9) Definitely! Desired theme would be WHITE. If that doesn't work for whatever reason, black or gray would suffice. Regarding "Case Size". Nah, that's not too important although I don't foresee a mini-ITX build making sense if I'm going to be cramming double digit amounts of TB in the system, Internal HDD's sounds better than a bunch of externals plugged in all the USB ports.
______________________
Q10) Do you need a copy of Windows included in the budget? If you do need one included, do you have a preference?**

A10) I don't know. If I do need a copy of Windows, I don't have one so that's something I'll have to consider I guess. I doubt that's a necessity though.
______________________
______________________
______________________
**Extra info or particulars:*\*

AND NOW TO THE FUN-STUFF... Here's a list of everything (PARTS PARTS PARTS) I have on-hand and ready to deploy into the wild &/or negotiate a trade/barter with:

CASES -
Corsair Carbide Series Air 540 Arctic White (Model# Crypto-Currency-9011048-WW) - (Probably my top pick for this build).
Cooler Master HAF XB EVO (This is probably my top 1st or 2nd pick for this build, the thing is a monster!).
Cooler Master Elite 130 - Mini ITX - Black
Cooler Master MasterBox 5 MID-Tower - Black & White
Raidmax Sigma-TWS - ATX - White
MasterBox Lite 5 - ATX - Black w/ diff. Colored accent attachments (included with purchase)
NZXT S340 Elite Matte White Steel/Tempered Glass Edition
EVGA DG-76 Alpine White - Mid Tower w/ window
EVGA DG-73 Black - Mid Tower w/ window (I have like 3 of these)

______________________
CPU's -
***7TH GEN OR BELOW INTEL's ("Code Name Class mentioned next to each one)**\*
Pentium G4400 (Skylake @54W TDP) - Intel ARK states is "ECC CAPABLE"
Celeron G3930 (Kaby Lake @ 51W TDP) - Intel ARK states is "ECC CAPABLE" :)
i5 6402P (Skylake @65W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(
i5 6600k (Skylake @ 91W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(
i7 6700 (Skylake @ 65W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(
i7 7700k (Kaby Lake @ 95W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(


***8TH GEN INTEL's **\*
i3-8350K (Coffee Lake @91W TDP) - Intel ARK states is "ECC FRIENDLY" :)
I5-8600K (Coffee Lake @95W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(


***AMD RYZEN's **\*
Ryzen 3 2200G
Ryzen 5 1600
Ryzen 7 1700X

______________________
MOTHERBOARDS -

***7TH GEN AND BELOW INTEL BASED MOBO'S - **\*
MSI Z170A-SLI
ASUS PRIME Z270-A
ASUS PRIME Z270-P
ASUS PRIME Z270-K
EVGA Z270 Stinger
GIGABYTE GA-Z270XP-SLI
MSI B150M ARCTIC
MSI B250M MICRO ATX (PRO OPT. BOOST EDITION)

***8TH GEN INTEL BASED MOBO'S - **\*
EVGA Z370 FTW
GIGABYTE Z370XP SLI (Rev. 1.0)
MSI Z370 SLI PLUS


***AMD RYZEN BASED MOBO'S - **\*
ASUS ROG STRIX B350-F GAMING
MSI B350 TOMAHAWK
MSI X370 GAMING PRO
ASROCK AB350M PRO4
______________________


RAM -

Way too many to list, nothing but 4 & 8GB DDR4 sticks and unfortunately, none are ECC so it's not even worth mentioning/listing these unless someone reading this is willing to barter. At which time I'd be obliged to send an itemized list or see if I have what they're/you're specifically looking for.\*
______________________
THERMAL APPLICATIONS/FANS -
JUST FANS -
BeQuiet -
Pure Wings 2 (80mm)
Pure Wings 2 (120mm)
Pure Wings 2 (140mm)
Silent Wings 3 PWM (120mm)

NOCTUA -
PoopBrown - NF-A20 PWM (200mm) Specifically for the BIG "CoolerMaster HAF XB EVO" Case
GREY - NF-P12 Redux - 1700RPM (120mm) PWM
Corsair -
Air Series AF120LED (120mm)

CPU COOLING SYSTEMS -
NOCTUA -
NT-HH 1.4ml Thermal Compound
NH-D15 6 Heatpipe system (this thing is the tits)

EVGA (Extremely crappy coding in the software here, I'm like 99.99% these will be problematic if I were to try and use in any OS outside of Windows, because they barely ever work in the intended Windows as it is).
CLC 240 (240mm Water-cooled system
CRYORIG -
Cryorig C7 Cu (Low-Profile Copper Edition*)

A few other oversized CPU cooling systems I forget off the top of my head but a CPU cooler is a CPU cooler after comparing to the previous 3 models I mentioned.
I almost exclusively am using these amazing "Innovation Cooling Graphite Thermal Pads" as an alternative to thermal paste for my CPU's. They're not cheap but they literally last forever.

NZXT - Sentry Mesh Fan Controller
______________________
POWER SUPPLIES (PSU's) -
BeQuiet 550W Straight Power 11 (GOLD)

EVGA -
750P2 (750W, Platinum)
850P2 (850W, Platinum)
750T2 (750W, TITANIUM - yeah baby, yeah)

ROSEWILL -
Quark 750W Platinum
Quark 650W Platinum

SEASONIC -
Focus 750W Platinum
______________________
STORAGE -
HGST Ultrastar 3TB - 64mb Cache - 7200RPM Sata III (3.5)
4X Samsung 860 EVO 500GB SSD's
2X Team Group L5 LITE 3D 2.5" SSD's 480GB
2X WD 10TB Essential EXT (I'm cool with shucking)
+ 6X various other external HDD's (from 4-8TB) - (Seagate, WD & G-Drives)
______________________

Other accessories worth mentioning -
PCI-E to 4X USB hub-adapter (I have a dozen or so of these - might not be sufficient enough &/or needed but again, 'worth mentioning' in case I somehow ever run out of SATA & USB ports and have extra external USB HDD's. Although, I'm sure there would be better suited components if I get to that point that probably won't cost all that much).
______________________
______________________
______________________
Needless to say, I have at least 1X of everything mentioned above. In most all cases, I have multiples of these items but obviously won't be needing 2X CPU's, Cases, etc...

Naturally, I have GPU's. Specifically;

At least 1X of every. Single. NVIDIA GTX 1070 TI (Yes, I have every variation of the 1070 ti made by MSI, EVGA and Zotac. The only brand I don't have is the Gigabyte line. My partners have terrible experience with those so I didn't even bother. I'm clearly not going to be needing a GPU for this build but again, I'm cool with discussing the idea of a barter if anyone reading this is in the market for one.

I also have some GTX 1080 TI's but those are already spoken for, sorry.

It's my understanding that select CPU's I have on this list are ECC Friendly and AFAIK, only 1 of my MOBO's claims to be ECC Friendly (The ASROCK AB350M PRO4), but for the life of me, I can't find any corresponding forums that confirm this and/or direct me to a listing where I can buy compatible RAM. Just the same, if I go w/ the ASROCK MOBO, that means I'd be using one of the Ryzens. Those are DEF. power hungry little buggers. Not a deal-breaker, just hoping to find something a little more conservative in terms of TDP.


In closing, I don't really need someone to hold my hand with the build part as much as figuring out which motherboard, CPU and RAM to get. Then I'm DEFINITELY going to need some guidance on what OS is best for my desired purpose. If building 2X Rigs makes sense, I'm totally open to that as well...
Rig 1 = EPIC NAS SYSTEM
Rig 2 = EPIC PFSENSE (or the like) DEDICATED FIREWALL

Oh, I almost forgot... The current routers I'm using are...
1X Netgear Nighthawk 6900P (Modem + Router)
1X Netgear Nighthawk X6S (AC 4000 I believe - Router dedicated towards my personal devices - no IoT &/or Guests allowed on this one)
1X TP-Link Archer C5 (Router). Total overkill after implementing the Nighthawks but this old beast somehow has the best range, plus it has 2X USB ports so for now, it's dedicated towards my IoT devices.
---- I also have a few other Wi-Fi routers (Apple Airport Extreme & some inferior Netgear's but I can only allocate so many WiFi Routers to so many WiFi channels w/out pissing off my neighbors) On that note, I have managed to convince my neighbors to let me in their house/WiFi configuration so we all have our hardware locked on specific, non-competing frequencies/channels so everyone's happy. :)


Please spare me the insults as I insulted myself throughout this entire venture. Part of why I did this was because when I was a kid, I used to fantasize about building a 'DREAM PC' but could never afford such. To compensate for this deficiency, I would actually print out the latest and greatest hardware components on a word document, print the lists up & tape to wall (for motivation). I was C++ certified at the age of 14 and built my first PC when I was 7. At the age of 15 I abandoned all hope in the sector and moved on to other aspirations. This entire ordeal was largely based off me finally fulfilling a childhood fantasy. On that note = mission accomplished. Now if I'm actually able to fulfill my desires on this post, I'm definitely going to feel less shitty about blowing so much money on all this stuff over the last couple years.

TIA for assisting in any way possible. Gotta love the internets!


THE END.
:)

EDIT/UPDATE (5 hours after OP) - My inbox is being inundated with various people asking for prices and other reasonable questions about my hardware being up for sale. Not to be redundant but rather to expound on my previous remarks about 'being interested in a bartetrade' with any of you here...

I did say I was going to sell my gear on eBay in the near future, I also said I wanted to trade/barter for anything relative to helping me accomplish my OP's mission(s). I'm not desperate for the $$$ but I'm also not one of those people that likes to rip other people off. That said; I value my time and money invested in this hardware and I'm only willing to unload it all once I've established I have ZERO need for any of it here in my home first. Hence my writing this lengthy thread in an attempt to repurpose at least a grand or two I've already spent.

One of the most commonly asked questions I anticipate receiving from interested bodies is going to be "How hard were you on your hardware?" Contrary to what anyone else would have probably done in my scenario which is say they were light on it whether they were or weren't, I documented my handling of the hardware, and have no problem sharing such documentation with verified, interested buyers (WHEN THE TIME COMES) to offer you guys peace of mind.

I have photo's and video's of the venture from A-Z. I am also obliged to provide (redacted) electricity bill statements where you can correlate my photo's (power draw on each rig), and also accurately deduct the excess power my house consumed with our other household appliances. Even taking into consideration how much (more) I spent in electricity from keeping my house at a constant, cool 70-72F year-round (via my Nest thermostat). Even without the rigs, I keep my AC @ 70 when I'm home and for the last 1.5-2 years, I just so happened to spend 85% of my time here at my house. When I would travel, I'd keep it at 72 for my wife & kids.
Additionally; I had each GPU 'custom' oveunderclocke'd (MSI Afterburner for all GPU's but the EVGA's).*
I doubt everyone reading this is aware so this is for those that don't.... EVGA had the brilliant idea of implementing what they call "ICX technology" in their latest NVIDIA GTX GPU's. The short(est) explanation of this "feature" goes as follows:

EVGA GPU's w/ "ICX 9 & above" have EXTRA HEAT/THERMAL SENSORS. Unlike every other GTX 1070 ti on the market, the one's with this feature actually have each of 2/2 on-board fans connected to individual thermal sensors. Which means - if you were to use the MSI Afterburner program on one of these EVGA's and create a custom fan curve for it, you'd only be able to get 1/2 of the fans to function the way intended. The other fan simply would not engage as the MSI Afterburner software wasn't designed/coded to recognize/ communicate with an added sensor (let alone sensor'S). This, in-turn, would likely result in whoever's using it the unintended way having a GPU defect on them within the first few months I'd imagine... Perhaps if they had the TDP power settings dumbed down as much as I did (60-63%), they might get a year or two out of it since it wouldn't run as near as hot, but I doubt any longer than that since cutting off 50% of the cooling system on one of these can't be ignored too long, surely capacitors would start to blow and who knows what else...
(Warning = RANT) Another interesting side-note about the EVGA's and their "Precision-X" OveUnderclocking software is that it's designed to only recognize 4X GPU's on a single system. For miners, that's just not cool. My favorite builds had 8X and for the motherboards that weren't capable of maintaining stable sessions on 8, I set up with 6X. Only my EVGA Rigs had 3 or 4X GPU's dedicated to a single motherboard. Furthermore, and as stated in an earlier paragraph, (& this is just my opinion) = EVGA SOFTWARE SUCKS! Precision X wasn't friendly with every motherboard/CPU I threw at it and their extension software for the CLC Close-Loop-Cooling/ CPU water-coolers simply didn't work on anything, even integrating into their own Precision-X software. The amount of time it took me to finally find compatible matches with that stuff was beyond maddening. (END RANT).
Which leads me to my other comments on the matter. That's what I had every single 1070 ti set at for TDP = 60-63%. Dropping the power load that much allowed me to bring down (on average) each 1070 ti to a constant 110-115W (mind you, this is only possible w/ "Titanium" rated PSU's, Platinum comes pretty damn close to the Titanium though) while mining Ethereum and was still able to maintain a bottom of 30 MH/s and a ceiling of 32 MH/s. Increasing the TDP to 80, 90, 100% or more only increased my hashrates (yields) negligibly, like 35-36 MH/s TOPS, which also meant each one was not only pulling 160-180W+ (Vs. the aforementioned 115'ish range), it also meant my rigs were creating a significantly greater amount of heat! Fortunately for the GPU's and my own personal habits, I live in South Florida where it's hot as balls typically, last winter was nothing like this one. Increasing my yields by 10-15% didn't justify increasing the heat production in my house by >30%, nor the added electricity costs from subjecting my AC handlers to that much of an extra work-load. For anyone reading this that doesn't know/understand what I'm talking about - after spending no less than 2-3 hours with each. and. every. one. I didn't play with the settings on just one and universally apply the settings to the rest. I found the 'prime' settings and documented them with a label-maker and notepad. Here's the math in a more transparent manner:

*** I NEVER LET MY GPU's BREACH 61C, EVER. Only my 8X GPU rigs saw 60-61 & it was the ones I had in the center of the build (naturally). I have REALLY high power fans (used on BTC ASIC MINERS) that were sucking air from those GPU's which was the only way I was able to obtain such stellar results while mining with them. **\*
Mining at "acceptable" heat temps (not acceptable to me, but most of the internet would disagree = 70C) and overclocking accordingly brings in X amount of yields per unit. =
'Tweaking' (underclocking) the GPU's to my parameters reduced my yield per unit from -10-15%, but it SAVED me well over 30-35% in direct electricity consumption, and an unknown amount of passive electricity consumption via creating approximately 20%+ less heat for my AC handler to combat.

I say all this extra stuff not just for anyone interested in mining with their GPU's, but really to answer (in-depth) the apparent questions you people are asking me in PM's. Something else that should help justify my claims of being so conservative should be the fact I only have/used "Platinum and Titanium" rated PSU's. Heat production, power efficiency and longevity of the hardware were ALWAYS my top priority.* . I truly thought Crypto would continue to gain and/or recover and bounce back faster than it did. If this project had maintained positive income for 12 months+, I'd have expanded one of our sites to also cater to GPU mining on a gnarly scale.

Once I have my NAS (& possibly 2nd rig for the firewall) successfully built, I'll be willing/able to entertain selling you guys some/all of the remaining hardware prior to launching on eBay. If there's something you're specifically looking for that I listed having, feel free to PM me with that/those specific item(s). Don't count on an immediate response but what you can count on is me honoring my word in offering whoever asks first right of refusal when the time comes for me to sell this stuff. Fortunately for me, PM's are time-stamped so that's how I'll gauge everyone's place in line. I hope this extra edit answers most of the questions you guys wanted to have answered and if not, sorry I guess. I'll do my best to bring light to anything I've missed out on after I realize whatever that error was/is. The only way anyone is getting first dibs on my hardware otherwise is if they either offer compelling insight into my original questions, or have something I need to trade w/.

THE END (Round#2)


submitted by Im-Ne-wHere to buildapcforme [link] [comments]

A story from a cloaky camper and an attempt to build a beast mode multi-boxing server.

21/04/2018
Hello Nerds!
 
Some of you may know me, some may not. Those that do will know I offer cloaky camping services over new eden. I do camping contracts / extort renters and focus my time hunting botters when the contracts are quiet. I offer PvP entities access to my cyno network to get dank kills and big escalations. From super carriers to Rattlesnakes.
 
The thing that got me into camping was hunting bots back in the dronelands a few years ago. I realised the most effective way to hurt them was to camp them 23/7, follow them around using locator agents. Eventually they had to rat with me in system. When they did I setup bubble traps etc and dropped blops and cleaned them up.
 
The 2nd thing I love about cloaky camping is the ability to counter Alliances (i feel its overpowered) intel channels / networks. Think about it. They have multiple intel toons dotted around the entrances to their pipes reporting hunters coming into the pipe allowing the PvE players to warp off and safe up. They even use external programs to collect this intel and give audible alerts. Cloaky camping is just the polar opposite. Dotting toons in their ratting pocket and giving me intel on whats going on in their system. As long as local chat exists so will cloaky camping. I'm pretty confident CCP share the same thought.
 
People probably think cloaky camping is easy. You are wrong. The prep work and behind the scenes work that goes into it is pretty immense. You are about to find out.
 
The hardware i'm currently running the 60 clients on is as follows:
 
Camper1: Screenshot of 30 Clients Layout
Camper2:
 
How do you pay for 60 toons
I started with 10 campers and made ISK by other means. When I made new campers I invested ISK and started to Skill extract and plexing the toons. I also make a decent amount from people who pay me to camp others.
 
The Setup  
I manage the clients window positions and CPU allocation with ISBOXER. Its legal to use as long as you don't use input broadcasting. I boot up the clients with ISBOXER EVE Launcher. I copy the window positions / chat channels etc over using garpaui. I use remote desktop to manage the clients light cynos etc.
Example here
 
On both motherboards I had to under clock the processors as they were drawing too much power from the motherboard and causing the chipset to overheat. I think these motherboards are not beefy enough to support these 8 core processors. It caused the CPU to throttle reducing the clock speeds to 1.3Ghz and causing lag issues. I solved this problem by reducing the clock speed from 4Ghz to 3.6Ghz and reducing the CPU voltage. This reduced the heat by a really good amount and stopped the problems.
 
However, Me being me I wanted to expand and the camping pcs were running at full chat. So I needed a better piece of hardware to host these 60+ clients. So, while at Fanfest, I bidded on this R820 Server on ebay and won!
 
Specs:
 
The hardware should be able to support multiple clients. However i'm not too sure how eve is going to behave when I try and open 60 instances all in one OS. I have set myself up for a hell of a challenge! However, I feel like I got a pretty good deal on the server and DELL hold their value. I'm sure I can re sell it if the project fails.
 
Things to work out:
 
Things I will teach you guys
 
I'm learning too so your help input would be awesome! First question. Shall I just update this reddit post each time or create some sort of blog?
Old AMD FX Rigs
New Kit / with various bits I gathered to get started
 
Update 23/04/18
I have made some decent progress on this crazy project. I will give some breif updates here. I will get a blog up and running to post full details with how to's etc. Its probably way to long for reddit.
 
I have successfully installed some GPU's into the R810 AMD R9 280x and Nvidia GTX 970. I soldered some PCI-E cables to the PDB and it worked fine. The GTX sits nicely in the chassis however, the R9 280X is external atm using a PCIE x1 to x16 riser (from my bitcoin mining). Also I have managed to enable and use them both with passthrough in ESXI 6.5. Yes the GPU works with a x1 adaptor. WTF!
 
Freezing Problem with a single os install
If I try and run more than 40 clients in a single OS I the system freezes when loading up client 41. I have tried the following:
I cannot see why it is freezing. Is there any way to gather logs for the client? It doesn't appear to be a resource problem. Plenty of RAM / CPU and HDD isn't going crazy.
 
Here are some pics of the current progress:
submitted by Mar5hy to Eve [link] [comments]

Threadripper KVM GPU Passthru: Testers needed

TL;DR: Check update 8 at the bottom of this post for a fix if you don't care about the history of this issue.
For a while now it has been apparent that PCI GPU passthrough using VFIO-PCI and KVM on Threadripper is a bit broken.
This manifests itself in a number of ways: When starting a VM with a passthru GPU it will either crash or run extremely slowly without the GPU ever actually working inside the VM. Also, once a VM has been booted the output of lspci on the host changes from one kind of output to another. Finally the output of dmesg suggests an issue bringing the GPU up from D0 to D3 power state.
An example of this lspci before and after VM start, as well as dmesg kernel buffer output is included here for the 7800GTX:
08:00.0 VGA compatible controller: NVIDIA Corporation G70 [GeForce 7800 GTX] (rev a1) (prog-if 00 [VGA controller]) [ 121.409329] virbr0: port 1(vnet0) entered blocking state [ 121.409331] virbr0: port 1(vnet0) entered disabled state [ 121.409506] device vnet0 entered promiscuous mode [ 121.409872] virbr0: port 1(vnet0) entered blocking state [ 121.409874] virbr0: port 1(vnet0) entered listening state [ 122.522782] vfio-pci 0000:08:00.0: enabling device (0000 -> 0003) [ 123.613290] virbr0: port 1(vnet0) entered learning state [ 123.795760] vfio_bar_restore: 0000:08:00.0 reset recovery - restoring bars ... [ 129.534332] vfio-pci 0000:08:00.0: Refused to change power state, currently in D3 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation G70 [GeForce 7800 GTX] [10de:0091] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: vfio-pci 
Notice that lspci reports revision FF and can no longer read the header type correctly. Testing revealed that pretty much all graphics cards except Vega would exhibit this behavior, and indeed the output is very similar to the above.
Reddit user wendelltron and others suggested that the D0->D3 transition was to blame. After having gone through a brute-force exhaustive search of the BIOS, kernel and vfio-pci settings for power state transitions it is safe to assume that this is probably not the case since none of it helped.
AMD representative AMD_Robert suggested that only GPUs with EFI-compatible BIOS should be able to be used for passthru in an EFI environment, however, testing with a modern 1080GTX with EFI bios support failed in a similar way:
42:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1) and then 42:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev ff) (prog-if ff) !!! Unknown header type 7f 
Common to all the cards was that they would be unavailable in any way until the host system had been restarted. Any attempt at reading any register or configuration from the card would result in all-1 bits (or FF bytes). The bitmask used for the headers may in fact be what is causing the 7f header type (and not an actual header being read from the card). Not even physically unplugging and re-plugging the card, rescanning the PCIe bus (with /sys/bus/pci/rescan) would trigger any hotplug events or update the card info. Similarly, starting the system without the card and plugging it in would not be reflected in the PCIe bus enumeration. Some cards, once crashed, would show spurious PCIe ACS/AER errors, suggesting an issue with the PCIe controller and/or the card itself. Furthermore, the host OS would be unable to properly shut down or reboot as the kernel would hang when everything else was shut down.
A complete dissection of the vfio-pci kernel module allowed further insight into the issue. Stepping through VM initialization one line at a time (yes this took a while) it became clear that the D3 power issue may be a product of the FF register issue and that the actual instruction that kills the card may have happened earlier in the process. Specifically, the function drivers/vfio/pci/vfio_pci.c:vfio_pci_ioctl, which handles requests from userspace, has entries for VFIO_DEVICE_GET_PCI_HOT_RESET_INFO and VFIO_DEVICE_PCI_HOT_RESET and the following line of code is exactly where the cards go from active to "disconnected" states:
if (!ret) /* User has access, do the reset */ ret = slot ? pci_try_reset_slot(vdev->pdev->slot) : pci_try_reset_bus(vdev->pdev->bus); 
Commenting out this line allows the VM to boot and the GPU driver to install. Unfortunately for the nVidia cards my testing stopped here as the driver would report the well known error 43/48 for which they should be ashamed and shunned by the community. For AMD cards a R9 270 was acquired for further testing.
The reason this line is in vfio-pci is because VMs do not like getting an already initialized GPU during boot. This is a well-known problem with a number of other solutions available. By disabling the line it is neccessary to use one of the other solutions when restarting a VM. For Windows you can disable the device in Device Manager before reboot/shutdown and re-enable it again after the restart - or use login/logoff scripts to have the OS do it automatically.
Unfortunately another issue surfaced which made it clear that the VMs could only be stopped once even though they could now be rebooted many times. Once they were shut down the cards would again go into the all FF "disconnect" state. Further dissection of vfio-pci revealed another instance where an attempt to reset the slot that the GPU is in was made: in drivers/vfio/pci/vfio_pci.c:vfio_pci_try_bus_reset
if (needs_reset) ret = slot ? pci_try_reset_slot(vdev->pdev->slot) : pci_try_reset_bus(vdev->pdev->bus); 
When this line is instead skipped, a VM that has had its GPU properly disabled via Device Manager and has been properly shutdown is able to be re-launched or have another VM using the same GPU launched and works as expected.
I do not understand the underlying cause of the actual issue but the workaround seems to work with no issues except the annoyance of having to disable/re-enable the GPU from within the guest (like in ye olde days). Only speculation can be given to the real reason of this fault; the hot-reset info gathered by the ioctl may be wrong, but the ACS/AER errors suggest that the issue may be deeper in the system - perhaps the PCIe controller does not properly re-initialize the link after hot-reset just as it (or the kernel?) doesn't seem to detect hot-plug events properly even though acpihp supposedly should do that in this setup.
Here is a "screenshot" of Windows 10 running the Unigine Valley benchmark inside a VM with a Linux Mint host using KVM on Threadripper 1950x and an R9 270 passed through on an Asrock X399 Taichi with 1080GTX as host GPU:
https://imgur.com/a/0HggN
This is the culmination of many weeks of debugging. It is interesting to hear if anyone else is able to reproduce the workaround and can confirm the results. If more people can confirm this then we are one step closer to fixing the actual issue.
If you are interested in buying me a pizza, you can do so by throwing some Bitcoin in this direction: 1KToxJns2ohhX7AMTRrNtvzZJsRtwvsppx
Also, English is not my native language so feel free to ask if something was unclear or did not make any sense.
Update 1 - 2017-12-05:
Expanded search to non-gpu cards and deeper into the system. Taking memory snapshots of pcie bus for each step and comparing to expected values. Seem to have found something that may be the root cause of the issue. Working on getting documentation and creating a test to see if this is indeed the main problem and to figure out if it is a "feature" or a bug. Not allowing myself to be optimistic yet but it looks interesting, it looks fixable at multiple levels.
Update 2 - 2017-12-07:
Getting a bit closer to the real issue. The issue seems to be that KVM performs a bus reset on the secondary side of the pcie bridge above the GPU being passed through. When this happens there is an unintended side effect that the bridge changes its state somehow. It does not return in a useful configuration as you would expect and any attempt to access the GPU below it results in errors.
Manually storing the bridge 4k configuration space before the bus reset and restoring it immediately after the bus reset seems to magically bring the bridge into the expected configuration and passthru works.
The issue could probably be fixed in firmware but I'm trying to find out what part of the configuration space is fixing the issue and causing the bridge to start working again. With that information it will be possible to write a targeted patch for this quirk.
Update 3 - 2017-12-10:
Begun further isolation of what particular registers in the config space are affected unintentionally by the secondary bus reset on the bridge. This is difficult work because the changes are seemingly invisible to the kernel, they happen only in the hardware.
So far at least registers 0x19 (secondary bus number) and 0x1a (subordinate bus number) are out of sync with the values in the config space. When a bridge is in faulty mode, writing their already existing value back to them brings the bridge back into working mode.
Update 4 - 2017-12-11 ("the ugly patch"):
After looking at the config space and trying to figure out what bytes to restore from before the reset and what bytes to set to something new it became clear that this would be very difficult without knowing more about the bridge.
Instead a different strategy was followed: Ask the bridge about its current config after reset and then set its current config to what it already is; byte by byte. This brings the config space and the bridge back in sync and everything, including reset/reboot/shutdown/relaunch without scripts inside the VM, now seems to work with the cards acquired for testing. Here is the ugly patch for the brave souls who want to help test it.
Please, if you already tested the workaround: revert your changes and confirm that the bug still exists before testing this new ugly patch:
In /drivers/pci/pci.c, replace the function pci_reset_secondary_bus with this alternate version that adds the ugly patch and two variables required for it to work:
void pci_reset_secondary_bus(struct pci_dev *dev) { u16 ctrl; int i; u8 mem; pci_read_config_word(dev, PCI_BRIDGE_CONTROL, &ctrl); ctrl |= PCI_BRIDGE_CTL_BUS_RESET; pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl); /* * PCI spec v3.0 7.6.4.2 requires minimum Trst of 1ms. Double * this to 2ms to ensure that we meet the minimum requirement. */ msleep(2); ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET; pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl); // The ugly patch for (i = 0; i < 4096; i++){ pci_read_config_byte(dev, i, &mem); pci_write_config_byte(dev, i, mem); } /* * Trhfa for conventional PCI is 2^25 clock cycles. * Assuming a minimum 33MHz clock this results in a 1s * delay before we can consider subordinate devices to * be re-initialized. PCIe has some ways to shorten this, * but we don't make use of them yet. */ ssleep(1); } 
The idea is to confirm that this ugly patch works and then beautify it, have it accepted into the kernel and to also deliver technical details to AMD to have it fixed in BIOS firmware.
Update 5 - 2017-12-20:
Not dead yet!
Primarily working on communicating the issue to AMD. This is slowed by the holiday season setting in. Their feedback could potentially help make the patch a lot more acceptable and a lot less ugly.
Update 6 - 2018-01-03 ("the java hack"):
AMD has gone into some kind of ninja mode and has not provided any feedback on the issue yet.
Due to popular demand a userland fix that does not require recompiling the kernel was made. It is a small program that runs as any user with read/write access to sysfs (this small guide assumes "root"). The program monitors any PCIe device that is connected to VFIO-PCI when the program starts, if the device disconnects due to the issues described in this post then the program tries to re-connect the device by rewriting the bridge configuration.
This program pokes bytes into the PCIe bus. Run this at your own risk!
Guide on how to get the program:
If you have any PCI devices using VFIO-PCI the program will output something along the lines of this:
------------------------------------------- Zen PCIe-Bridge BAConfig Recovery Tool, rev 1, 2018, HyenaCheeseHeads ------------------------------------------- Wed Jan 03 21:40:30 CET 2018: Detecting VFIO-PCI devices Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:40/0000:40:01.3/0000:42:00.0 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:40/0000:40:01.3 Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.1 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:00/0000:00:01.3 Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:40/0000:40:01.3/0000:42:00.1 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:40/0000:40:01.3 Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.0 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:00/0000:00:01.3 Wed Jan 03 21:40:30 CET 2018: Monitoring 4 device(s)... 
And upon detecting a bridge failure it will look like this:
Wed Jan 03 21:40:40 CET 2018: Lost contact with /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.1 Wed Jan 03 21:40:40 CET 2018: Recovering 512 bytes Wed Jan 03 21:40:40 CET 2018: Bridge config write complete Wed Jan 03 21:40:40 CET 2018: Recovered bridge secondary bus Wed Jan 03 21:40:40 CET 2018: Re-acquired contact with /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.1 
This is not a perfect solution but it is a stopgap measure that should allow people who do not like compiling kernels to experiment with passthru on Threadripper until AMD reacts in some way. Please report back your experience, I'll try to update the program if there are any issues with it.
Update 7 - 2018-07-10 ("the real BIOS fix"):
Along with the upcoming A.G.E.S.A. update aptly named "ThreadRipperPI-SP3r2 1.0.0.6" comes a very welcome change to the on-die PCIe controller firmware. Some board vendors have already released BETA BIOS updates with it and it will be generally available fairly soon it seems.
Initial tests on a Linux 4.15.0-22 kernel now show PCIe passthru working phenomenally!
With this change it should no longer be necessary to use any of the ugly hacks from previous updates of this thread, although they will be left here for archival reasons.
Update 8 - 2018-07-25 ("Solved for everyone?"):
Most board vendors are now pushing out official (non-BETA) BIOS updates with AGESA "ThreadRipperPI-SP3r2 1.1.0.0" including the proper fix for this issue. After updating you no longer need to use any of the temporary fixes from this thread. The BIOS updates comes as part of the preparations for supporting the Threadripper 2 CPUs which are due to be released in a few weeks from now.
Many boards support updating over the internet directly from BIOS, but in case you are a bit old-fashioned here are the links (please double-check that I linked you the right place before flashing):
Vendor Board Update Link
Asrock X399 Taichi Update to 2.3, then 3.1
Asrock X399M Taichi Update to 1.10 then 3.1
Asrock X399 Fatality Profesional Gaming Update to 2.1 then 3.1
Gigabyte X399 AURUS Gaming 7 r1 Update to F10
Gigabyte X399 DESIGNARE EX r1 Update to F10
Asus PRIME X399-A Possibly fixed in 0601 (TR2 support and sure fix inbound soon)
Asus X399 RoG Zenith Extreme Possibly fixed in 0601 (TR2 support and sure fix inbound soon)
Asus RoG Strix X399-E Gaming Possibly fixed in 0601 (TR2 support and sure fix inbound soon)
MSI X399 Gaming Pro Carbon AC Update to Beta BIOS 7B09v186 (TR2 update inbound soon)
MSI X399 SLI plus Update to Beta BIOS 7B09vA35 (TR2 update inbound soon)
submitted by HyenaCheeseHeads to Amd [link] [comments]

[META] New to PC Building? - September 2018 Edition

Intro

You've heard from all your gaming friends/family or co-workers that custom PCs are the way to go. Or maybe you've been fed up with your HP, Dell, Acer, Gateway, Lenovo, etc. pre-builts or Macs and want some more quality and value in your next PC purchase. Or maybe you haven't built a PC in a long time and want to get back into the game. Well, here's a good place to start.

Instructions

  1. Make a budget for your PC (e.g., $800, $1000, $1250, $1500, etc.).
  2. Decide what you will use your PC for.
    • For gaming, decide what games and at what resolution and FPS you want to play at.
    • For productivity, decide what software you'll need and find the recommended specs to use those apps.
    • For a bit of both, your PC build should be built on the HIGHEST specs recommended for your applications (e.g., if you only play FortNite and need CPU power for CFD simulations, use specs recommended for CFD).
    Here are some rough estimates for builds with entirely NEW parts:
    1080p 60FPS ultra-settings modern AAA gaming: ~$1,200
    1440p 60FPS high/ultra-settings modern AAA gaming: ~$1,600
    1080p 144FPS ultra-settings modern AAA gaming: $2,000
    4K 50FPS medium/high-settings modern AAA gaming: > $2,400
    It's noted that some compromises (e.g., lower settings and/or resolution) can be made to achieve the same or slightly lower gaming experience within ±15% of the above prices. It's also noted that you can still get higher FPS on older or used PCs by lowering settings and/or resolution AND/OR buying new/used parts to upgrade your system. Make a new topic about it if you're interested.
    Also note that AAA gaming is different from e-sport games like CSGO, DOTA2, FortNite, HOTS, LoL, Overwatch, R6S, etc. Those games have lower requirements and can make do with smaller budgets.
  3. Revise your budget AND/OR resolution and FPS until both are compatible. Compare this to the recommended requirements of the most demanding game on your list. For older games, you might be able to lower your budget. For others, you might have to increase your budget.
    It helps to watch gaming benchmarks on Youtube. A good example of what you're looking for is something like this (https://www.youtube.com/watch?v=9eLxSOoSdjY). Take note of the resolution, settings, FPS, and the specs in the video title/description; ask yourself if the better gaming experience is worth increasing your budget OR if you're okay with lower settings and lowering your budget. Note that you won't be able to see FPS higher than 60FPS for Youtube videos; something like this would have to be seen in-person at a computer shop.
  4. Make a build on https://ca.pcpartpicker.com/. If you still have no idea how to put together parts, start here (http://www.logicalincrements.com/) to get an understanding of PC part tiers. If you want more info about part explanations and brief buying tips, see the next section below.
  5. Click on the Reddit logo button next to Markup, copy and paste the generated text (in markup mode if using new Reddit), and share your build for review!
  6. Consider which retailer to buy your parts from. Here's a table comparing different retailers: https://docs.google.com/spreadsheets/d/1L8uijxuoJH4mjKCjwkJbCrKprCiU8CtM15mvOXxzV1s/edit?usp=sharing
  7. Buy your parts! Use PCPP above to send you e-mail alerts on price drops or subscribe to /bapcsalescanada for deals.
    You can get parts from the following PC retailers in alphabetical order:
  8. After procuring your parts, it's time to build. Use a good Youtube tutorial like this (https://www.youtube.com/watch?v=IhX0fOUYd8Q) that teach BAPC fundamentals, but always refer to your product manuals or other Youtube tutorials for part-specific instructions like CPU mounting, radiator mounting, CMOS resetting, etc. If it everything still seems overwhelming, you can always pay a computer shop or a friend/family member to build it for you.
    It might also be smart to look up some first-time building mistakes to avoid:
  9. Share your experience with us.
  10. If you have any other questions, use the search bar first. If it's not there, make a topic.

BAPC News (Last Updated - 2018/09/20)

CPU

https://www.tomshardware.com/news/intel-9000-series-cpu-faq,37743.html
Intel 9000 CPUs (Coffee Lake Refresh) will be coming out in Q4. With the exception of i9 (8-core, 12 threads) flagship CPUs, the i3, i5, and i7 lineups are almost identical to their Intel 8000 (Coffee Lake) series, but slightly clocked faster. If you are wondering if you should upgrade to the newer CPU on the same tier (e.g., i5-8400 to i5-9400), I don't recommend that you do as you will only see marginal performance increases.

Mobo

https://www.anandtech.com/show/13135/more-details-on-intels-z390-chipset-exposed
Z370s will now be phased out for Z390s boards, which will natively support Intel 9000 CPUs (preferably i5-9600K, i7-9700K, and i9-9900K).

GPU

https://www.youtube.com/watch?v=WDrpsv0QIR0
RTX 2080 and 2080 Ti benchmarks are out; they provide ~10 and ~20 frames better than the 1080 Ti and also feature ray tracing (superior lighting and shadow effects) which is featured in only ~30 games so far (i.e., not supported a lot); effectively, they provide +25% more performance for +70% increased cost. My recommendation is NOT to buy them unless you need it for work or have lots of disposable income. GTX 1000 Pascal series are still relevant in today's gaming specs.

Part Explanations

CPU

The calculator part. More GHz is analogous to fast fingers number crunching in the calculator. More cores is analogous to having more calculators. More threads is analogous to having more filing clerks piling more work for the calculator to do. Microarchitectures (core design) is analogous to how the internal circuit inside the calculator is designed (e.g., AMD FX series are slower than Intel equivalents even with higher OC'd GHz speeds because the core design is subpar). All three are important in determining CPU speed.
In general, higher GHz is more important for gaming now whereas # cores and threads are more important for multitasking like streaming, video editing, and advanced scientific/engineering computations. Core designs from both AMD and Intel in their most recent products are very good now, but something to keep in mind.

Overclocking

The basic concept of overclocking (OCing) is to feed your CPU more power through voltage and hoping it does calculations faster. Whether your parts are good overclockers depends on the manufacturing process of your specific part and slight variations in materials and manufacturing process will result in different overclocking capability ("silicon lottery"). The downside to this is that you can void your warranties because doing this will produce excess heat that will decrease the lifespan of your parts AND that there is a trial-and-error process to finding OC settings that are stable. Unstable OC settings result in computer freezes or random shut-offs from excess heat. OCing will give you extra performance often for free or by investing in a CPU cooler to control your temperatures so that the excess heat will not decrease your parts' lifespans as much. If you don't know how to OC, don't do it.

Current Products

Intel CPUs have higher GHz than AMD CPUs, which make them better for gaming purposes. However, AMD Ryzen CPUs have more cores and threads than their Intel equivalents. The new parts are AMD Ryzen 3, 5, or 7 2000 series or Intel i3, i5, or i7 8000 series (Coffee Lake). Everything else is outdated.
If you want to overclock on an AMD system, know that you can get some moderate OC on a B350/B450 with all CPUs. X370/X470 mobos usually come with better VRMs meant for OCing 2600X, 2700, and 2700X. If you don't know how to OC, know that the -X AMD CPUs have the ability to OC themselves automatically without manually settings. For Intel systems, you cannot OC unless the CPU is an unlocked -K chip (e.g., i3-8350K, i5-8600K, i7-8700K, etc.) AND the motherboard is a Z370 mobo. In general, it is not worth getting a Z370 mobo UNLESS you are getting an i5-8600K and i7-8700K.

CPU and Mobo Compatibility

Note about Ryzen 2000 CPUs on B350 mobos: yes, you CAN pair them up since they use the same socket. You might get an error message on PCPP that says that they might not be compatible. Call the retailer and ask if the mobo you're planning on buying has a "Ryzen 2000 Series Ready" sticker on the box. This SHOULD NOT be a problem with any mobos manufactured after February 2018.
Note about Intel 9000 CPUs on B360 / Z370 mobos: same as above with Ryzen 2000 CPUs on B350 or X370 boards.

CPU Cooler (Air / Liquid)

Air or liquid cooling for your CPU. This is mostly optional unless heavy OCing on AMD Ryzen CPUs and/or on Intel -K and i7-8700 CPUs.
For more information about air and liquid cooling comparisons, see here:

Motherboard/mobo

Part that lets all the parts talk to each other. Comes in different sizes from small to big: mITX, mATX, ATX, and eATX. For most people, mATX is cost-effective and does the job perfectly. If you need more features like extra USB slots, go for an ATX. mITX is for those who want a really small form factor and are willing to pay a premium for it. eATX mobos are like ATX mobos except that they have more features and are bigger - meant for super PC enthusiasts who need the features.
If you are NOT OCing, pick whatever is cheap and meets your specs. I recommend ASUS or MSI because they have RMA centres in Canada in case it breaks whereas other parts are outside of Canada like in the US. If you are OCing, then you need to look at the quality of the VRMs because those will greatly influence the stability and lifespan of your parts.

Memory/RAM

Part that keeps Windows and your software active. Currently runs on the DDR4 platform for new builds. Go for dual channel whenever possible. Here's a breakdown of how much RAM you need:
AMD Ryzen CPUs get extra FPS for faster RAM speeds (ideally 3200MHz) in gaming when paired with powerful video cards like the GTX 1070. Intel Coffee Lake CPUs use up a max of 2667MHz for B360 mobos. Higher end Z370 mobos can support 4000 - 4333MHz RAM depending on the mobo, so make sure you shop carefully!
It's noted that RAM prices are highly inflated because of the smartphone industry and possibly artificial supply shortages. For more information: https://www.extremetech.com/computing/263031-ram-prices-roof-stuck-way

Storage

Part that store your files in the form of SSDs and HDDs.

Solid State Drives (SSDs)

SSDs are incredibly quick, but are expensive per TB; they are good for booting up Windows and for reducing loading times for gaming. For an old OEM pre-built, upgrading the PC with an SSD is the single greatest speed booster you can do to your system. For most people, you want to make sure the SSD you get is NOT DRAM-less as these SSDs do not last as long as their DRAM counterparts (https://www.youtube.com/watch?v=ybIXsrLCgdM). It is also noted that the bigger the capacity of the SSD, the faster they are. SSDs come in four forms:
The 2.5" SATA form is cheaper, but it is the old format with speeds up to 550MB/s. M.2 SATA SSDs have the same transfer speeds as 2.5" SATA SSDs since they use the SATA interface, but connect directly to the mobo without a cable. It's better for cable management to get an M.2 SATA SSD over a 2.5" SATA III SSD. M.2 PCI-e SSDs are the newest SSD format and transfer up to 4GB/s depending on the PCI-e lanes they use (e.g., 1x, 2x, 4x, etc.). They're great for moving large files (e.g., 4K video production). For more info about U.2 drives, see this post (https://www.reddit.com/bapccanada/comments/8jxfqs/meta_new_to_pc_building_may_2018_edition/dzqj5ks/). Currently more common for enterprise builds, but could see some usage in consumer builds.

Hard Disk Drives (HDDs)

HDDs are slow with transfer speeds of ~100MB/s, but are cheap per TB compared to SSDs. We are now at SATA III speeds, which have a max theoretical transfer rate of 600MB/s. They also come in 5400RPM and 7200RPM forms. 5400RPM uses slightly less power and are cheaper, but aren't as fast at dealing with a large number of small files as 7200RPM HDDs. When dealing with a small number of large files, they have roughly equivalent performance. It is noted that even a 10,000RPM HDD will still be slower than an average 2.5" SATA III SSD.

Others

SSHDs are hybrids of SSDs and HDDs. Although they seem like a good combination, it's much better in all cases to get a dedicated SSD and a dedicated HDD instead. This is because the $/speed better for SSDs and the $/TB is better for HDDs. The same can be said for Intel Optane. They both have their uses, but for most users, aren't worth it.

Overall

I recommend a 2.5" or M.2 SATA ≥ 250GB DRAM SSD and a 1TB or 2TB 7200RPM HDD configuration for most users for a balance of speed and storage capacity.

Video Card/GPU

Part that runs complex calculations in games and outputs to your monitor and is usually the most expensive part of the budget. The GPU you pick is dictated by the gaming resolution and FPS you want to play at.
In general, all video cards of the same product name have almost the same non-OC'd performance (e.g., Asus Dual-GTX1060-06G has the same performance as the EVGA 06G-P4-6163-KR SC GAMING). The different sizes and # fans DO affect GPU OCing capability, however. The most important thing here is to get an open-air video card, NOT a blower video card (https://www.youtube.com/watch?v=0domMRFG1Rw). The blower card is meant for upgrading pre-builts where case airflow is limited.
For cost-performance, go for the NVIDIA GTX cards because of the cryptomining industry that has inflated AMD RX cards. Bitcoin has taken a -20% hit since January's $10,000+ as of recently, but the cryptomining industry is still ongoing. Luckily, this means prices have nearly corrected itself to original MSRP in 2016.
In general:
Note that if your monitor has FreeSync technology, get an AMD card. If your monitor has G-Sync, get a NVIDIA card. Both technologies allow for smooth FPS gameplay. If you don't have either, it doesn't really matter which brand you get.
For AMD RX cards, visit https://www.pcworld.com/article/3197885/components-graphics/every-amd-radeon-rx-graphics-card-you-can-buy-for-pc-gaming.html

New NVIDIA GeForce RTX Series

New NVIDIA 2000 RTX series have been recently announced and will be carried in stores in Q3 and Q4. Until all of the products have been fully vetted and reviewed, we cannot recommend those yet as I cannot say if they are worth what NVIDIA has marketed them as. But they will be faster than their previous equivalents and will require more wattage to use. The 2070, 2080, and 2080 Ti will feature ray tracing, which is a new feature seen in modern CG movies that greatly enhances lighting and shadow effects. At this time, < 30 games will use ray tracing (https://www.pcgamer.com/21-games-will-support-nvidias-real-time-ray-tracing-here-are-demos-of-tomb-raider-and-control/). It's also noted that the 2080 Ti is the Titan XP equivalent, which is why it's so expensive. (https://www.youtube.com/watch?v=Irs8jyEmmPQ) The community's general recommendation is NOT to pre-order them until we see some reviews and benchmarks from reviewers first.
Looks like a couple of benchmarks are out. While keeping other parts equal the following results were obtained(https://videocardz.com/77983/nvidia-geforce-rtx-2080-ti-and-rtx-2080-official-performance-unveiled). So the 2080 and 2080 Ti are better than last generation's 1080 Ti by ~10 and ~20 frames respectively.

Case

Part that houses your parts and protects them from its environment. Should often be the last part you choose because the selection is big enough to be compatible with any build you choose as long as the case is equal to or bigger than the mobo form factor.
Things to consider: aesthetics, case airflow, cable management, material, cooling options (radiators or # of fan spaces), # fans included, # drive bays, toolless installation, power supply shroud, GPU clearance length, window if applicable (e.g., acrylic, tempered glass), etc.
It is recommended to watch or read case reviews on Youtube to get an idea of a case's performance in your setup.

Power Supply/PSU

Part that runs your PC from the wall socket. Never go with an non-reputable/cheap brand out on these parts as low-quality parts could damage your other parts. Recommended branded PSUs are Corsair, EVGA, Seasonic, and Thermaltake, generally. For a tier list, see here (https://linustechtips.com/main/topic/631048-psu-tier-list-updated/).

Wattage

Wattage depends on the video card chosen, if you plan to OC, and/or if you plan to upgrade to a more powerful PSU in the future. Here's a rule of thumb for non-OC wattages that meet NVIDIA's recommendations:
There are also PSU wattage calculators that you can use to estimate your wattage. How much wattage you used is based on your PC parts, how much OCing you're doing, your peripherals (e.g., gaming mouse and keyboard), and how long you plan to leave your computer running, etc. It is noted that these calculators use conservative estimates, so use the outputted wattage as a baseline of how much you need. Here are the calculators (thanks, VitaminDeity).
Pick ONE calculator to use and use the recommended wattage, NOT recommended product, as a baseline of what wattage you need for your build. Note that Cooler Master and Seasonic use the exact calculator as Outervision. For more details about wattage, here are some reference videos:

Modularity

You might also see some info about modularity (non-modular, semi-modular, or fully-modular). These describe if the cables will come connected to the PSU or can be separated of your own choosing. Non-modular PSUs have ALL of the cable connections attached to the PSU with no option to remove unneeded cables. Semi-modular PSUs have separate cables for HDDs/SSDs and PCI-e connectors, but will have CPU and mobo cables attached. Modular PSUs have all of their cables separate from each other, allowing you to fully control over cable management. It is noted that with decent cooling and airflow in your case, cable management has little effect on your temperatures (https://www.youtube.com/watch?v=YDCMMf-_ASE).

80+ Efficiency Ratings

As for ratings (80+, 80+ bronze, 80+ gold, 80+ platinum), these are the efficiencies of your PSU. Please see here for more information. If you look purely on electricity costs, the 80+ gold PSUs will be more expensive than 80+ bronze PSUs for the average Canadian user until a breakeven point of 6 years (assuming 8 hours/day usage), but often the better performance, longer warranty periods, durable build quality, and extra features like fanless cooling is worth the extra premium. In general, the rule of thumb is 80+ bronze for entry-level office PCs and 80+ gold for mid-tier or higher gaming/workstation builds. If the price difference between a 80+ bronze PSU and 80+ gold PSU is < 20%, get the 80+ gold PSU!

Warranties

Warranties should also be looked at when shopping for PSUs. In general, longer warranties also have better PSU build quality. In general, for 80+ bronze and gold PSU units from reputable brands:
Any discrepancies are based on varied wattages (i.e., higher wattages have longer warranties) or updated warranty periods. Please refer to the specific product's warranty page for the correct information. For EVGA PSUs, see here (https://www.evga.com/support/warranty/power-supplies/). For Seasonic PSUs, see here (https://seasonic.com/support#period). For Corsair PSUs, see here (https://www.corsair.com/ca/en/warranty).
For all other PSU inquiries, look up the following review sites for the PSUs you're interested in buying:
These guys are engineering experts who take apart PSUs, analyze the quality of each product, and provide an evaluation of the product. Another great website is http://www.orionpsudb.com/, which shows which PSUs are manufactured by different OEMs.

Operating System (OS)

Windows 10

The most common OS. You can download the ISO here (https://www.microsoft.com/en-ca/software-download/windows10). For instructions on how to install the ISO from a USB drive, see here (https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/install-windows-from-a-usb-flash-drive) or watch a video here (https://www.youtube.com/watch?v=gLfnuE1unS8). For most users, go with the 64-bit version.
If you purchase a Windows 10 retail key (i.e., you buy it from a retailer or from Microsoft directly), keep in mind that you are able to transfer it between builds. So if you're building another PC for the 2nd, 3rd, etc. time, you can reuse the key for those builds PROVIDED that you deactivate your key before installing it on your new PC. These keys are ~$120.
However, if you have an OEM key (e.g., pre-builts), that key is tied specifically to your mobo. If you ever decide to upgrade your mobo on that pre-built PC, you might have to buy a new Windows 10 license. For more information, see this post (https://www.techadvisor.co.uk/feature/windows/windows-10-oem-or-retail-3665849/). The cheaper Windows 10 keys you can find on Kinguin are OEM keys; activating and deactivating these keys may require phoning an automated Microsoft activation line. Most of these keys are legitimate and cost ~$35, although Microsoft does not intend for home users to obtain this version of it. Buyer beware.
The last type of key is a volume licensing key. They are licensed in large volumes to corporate or commercial usage. You can find lots of these keys on eBay for ~$10, but if the IT department who manages these keys audit who is using these keys or if the number of activations have exceeded the number allotted on that one key, Microsoft could block that key and invalidate your license. Buyer beware.
For more information on differentiating between all three types of keys, see this page (https://www.tenforums.com/tutorials/49586-determine-if-windows-license-type-oem-retail-volume.html).
If money is tight, you can get Windows 10 from Microsoft and use a trial version of it indefinitely. However, there will be a watermark in the bottom-right of your screen until you activate your Windows key.

MacOS

If you're interested in using MacOS, look into Hackintosh builds. This will allow you to run MacOS to run on PC parts, saving you lots of money. These builds are pretty picky about part compatibility, so you might run into some headaches trying to go through with this. For more information, see the following links:

Linux

If you're interested in a free open-source OS, see the following links:
For more information, go to /linux, /linuxquestions, and /linux4noobs.

Peripherals

Monitors

Keyboards and Mice

Overall

Please note that the cost-performance builds will change daily because PC part prices change often! Some builds will have excellent cost-performance one day and then have terrible cost-performance the next. If you want to optimize cost-performance, it is your responsibility to do this if you go down this route!
Also, DO NOT PM me with PC build requests! It is in your best interests to make your own topic so you can get multiple suggestions and input from the community rather than just my own. Thanks again.

Sample Builds

Here are some sample builds that are reliable, but may not be cost-optimized builds. These builds were created on September 9, 2018; feel free to "edit this part list" and create your own builds.

Links

Helpful links to common problems below:

Contributors

Thanks to:

Housekeeping

2019/09/22
2019/09/18
Updates:
2019/09/09
Updates:
Sorry for the lack of updates. I recently got a new job where I work 12 hours/day for 7 days at a time out of the city. What little spare time I have is spent on grad school and the gym instead of gaming. So I've been pretty behind on the news and some might not be up-to-date as my standards would have been with less commitments. If I've made any mistakes, please understand it might take a while for me to correct them. Thank you!
submitted by BlackRiot to bapccanada [link] [comments]

How to mine $1,000,000 of Bitcoin using just a laptop ... How Much Can You Make Mining Bitcoin With 6X 1080 Ti ... BITCOIN HASHRATE PLUMMETS! YOU WON'T BELIEVE WHAT BTC PRICE DID LAST TIME Free bitcoin mining and withdraw without fee - YouTube How to get a Bitcoin Wallet Address - FREE & in under a ...

PCI/DSS compliance. we made it easy : Three steps to buy bitcoin & litecoin with us. 1. REGISTER . Enter email, create a strong password, protect your wallet with the PIN code and you are all set! 2. VERIFY. ID Verification. Today is not possible to buy bitcoin without KYC (Know your Customer). We made it simple though. Be prepared to provide us your ID and personal details. 3. BUY CRYPTO. Buy ... PCI to BTC Exchange Rate - 1 Pay Coin in Bitcoin. 0.00002107 . BTC 0.000021; Vol [24h] $69 059,6937 . pci to btc converter . Exchange Pair Price 24h volume ; Upbit : PCI/BTC : $0,2183 ... Ultimately, the value of a bitcoin is determined by what people will pay for it. In this way, there's a similarity to how stocks are priced. In this way, there's a similarity to how stocks are priced. View live PIMCO DYNAMIC CREDIT & MTG INC FUND chart to track its stock's price action. Find market predictions, PCI financials and market news. Explore the top 50 cryptocurrencies with Coinbase, including cryptocurrency price charts, crypto descriptions, and the latest price of Bitcoin and Ethereum.

[index] [13046] [27933] [34541] [33751] [13801] [48926] [48805] [6982] [23813] [761]

How to mine $1,000,000 of Bitcoin using just a laptop ...

With low mining difficulty and high potential returns choosing the best cryptocurrency to mine was a no-brainer. Discover our algorithm's undervalued coins l... Mining Bitcoin is as easy as installing the mining software on the PC you already own and clicking start. Anyone can do this and see the money start rolling ... #bitcoin price history #how much is a bitcoin #bitcoin current value #btc value #btc price usd #bitcoin worth #bitcoin stock price #btc to usd converter #buy bitcoin with credit card #1 bitcoin to ... Last time bitcoin hash rate took a nosedive to a new low, bitcoin price turned bullish. This is what btc price charts tell us! #Bitcoin #btc Headlines: https... Buy Raspberry Pi 4 Model B 4GB: https://amzn.to/2tlBfGW How to Setup a Raspberry Pi 4 Bitcoin Mining Rig w/ Bitmain AntMiner U3: https://youtu.be/dPWTSytzN7g...

#