Latest posts of: bigvito19

Show Posts
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 »

101

Bitcoin / Project Development / Re: Large Bitcoin Collider Thread 2.0

on: June 18, 2021, 05:25:55 PM

Quote from: crypto-dev on June 18, 2021, 02:48:02 PM Is there any status update about till which bit have you reached rico666? Also, is it possible for you to share the database of private keys and their corresponding public keys? The public keys that are exposed and left to solve: #120 ( 17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT ) 800000000000000000000000000000 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 02CEB6CBBCDBDF5EF7150682150F4CE2C6F4807B349827DCDBDD1F2EFA885A2630 #125 ( 1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5 ) 10000000000000000000000000000000 1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 0233709EB11E0D4439A729F21C2C443DEDB727528229713F0065721BA8FA46F00E #130 ( 1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua ) 200000000000000000000000000000000 3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 03633CBE3EC02B9401C5EFFA144C5B4D22F87940259634858FC7E59B1C09937852 #135 ( 16RGFo6hjq9ym6Pj7N5H7L1NR1rVPJyw2v ) 4000000000000000000000000000000000 7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 02145D2611C823A396EF6712CE0F712F09B9B4F3135E3E0AA3230FB9B6D08D1E16 #140 ( 1QKBaU6WAeycb3DbKbLBkX7vJiaS8r42Xo ) 80000000000000000000000000000000000 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 031F6A332D3C5C4F2DE2378C012F429CD109BA07D69690C6C701B6BB87860D6640 #145 ( 19GpszRNUej5yYqxXoLnbZWKew3KdVLkXg ) 1000000000000000000000000000000000000 1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 03AFDDA497369E219A2C1C369954A930E4D3740968E5E4352475BCFFCE3140DAE5 #150 ( 1MUJSJYtGPVGkBCTqGspnxyHahpt5Te8jy ) 20000000000000000000000000000000000000 3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 03137807790EA7DC6E97901C2BC87411F45ED74A5629315C4E4B03A0A102250C49 #155 ( 1AoeP37TmHdFh8uN72fu9AqgtLrUwcv2wJ ) 400000000000000000000000000000000000000 7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 035CD1854CAE45391CA4EC428CC7E6C7D9984424B954209A8EEA197B9E364C05F6 #160 ( 1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv ) 8000000000000000000000000000000000000000 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 02E0A8B039282FAF6FE0FD769CFBC4B6B4CF8758BA68220EAC420E32B91DDFA673

102

Alternate cryptocurrencies / Mining (Altcoins) / Re: Obsolete gtx1060-3gb GPUS can find valuable BTC keys 250 MH/Sec, 1000TH

on: June 16, 2021, 09:00:31 PM

Quote from: WanderingPhilospher on June 14, 2021, 03:22:53 PM Just tinkering around with small changes to original VanitySearch, here are some numbers: Code: [ Combination Speed 61864.26 TH/s ][Combinations Checked 2^66.29] [Found 0] So with 5 cards and 39 million addresses (with no bloom filter yet), I am getting almost 62 Petahashes per second. Program is using right at 6.5GB RAM, constant, so here is my question to @btc-room101, with your configuration, how much constant RAM is used? GPUs obviously lost speed with that many addresses. If I only wanted a constant set number of addresses (not update and sync with chain), what would be the easiest most efficient way to set it up with bloom filter? You got a windows version of it?

103

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: June 13, 2021, 02:55:54 PM

How would I calculate how many combinations of 16jY7q would be in 2^64 range?

104

Bitcoin / Development & Technical Discussion / Re: Vanitygen: Vanity bitcoin address generator/miner [v0.22]

on: May 29, 2021, 07:57:58 PM

Quote from: DaveF on April 29, 2019, 02:27:50 PM Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them. I know it's a newer project and Jean_Luc is working VERY VERY hard on it so getting accurate numbers is going to be a moving target. But for now all we can do is look through the thread and see who is running what to get a general idea. So far I have pulled from this thread: GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128) 914.418 MK/s (GPU 896.216 MK/s) GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128) 220.180 MK/s (GPU 220.180 MK/s) GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128) 10.233 MK/s (GPU 7.026 MK/s) GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128) 1535.880 MK/s (GPU 1470.257 MK/s) Added 30-April-2019 GPU: GPU #0 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128) 321.929 MK/s (GPU 321.929 MK/s) GPU: GPU #0 GeForce GTX 1080 (20x128 cores) Grid(160x128) 672.062 MK/s (GPU 672.062 MK/s) Added 1-May-2019 GPU: GPU #0 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) GPU: GPU #3 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) GPU: GPU #2 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) GPU: GPU #1 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) 7260.449 MK/s (GPU 7212.931 MK/s) So 7260 / 4 = 1815 MK/s GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128) 104.960 MK/s (GPU 94.405 MK/s) (2^32.12) Added 3-May-2019 i7-7700K CPU Number of CPU thread: 8 22.092 MK/s (GPU 0.000 MK/s) With -t 7 Number of CPU thread: 7 21.609 MK/s Added 8-May-2019 EVGA RTX 2080 XC ULTRA 1427.967 MK/s (GPU 1424.946 MK/s) Added 23-May-2019 GPU: GPU #0 GeForce GTX 1660 Ti 961.319 MK/s (GPU 961.319 MK/s) GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128) GPU: GPU #1 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128) 5128.213 MK/s (GPU 5128.213 MK/s) So 5128 / 2 = 2564 MK/s Added 8-June-2019 GPU: GPU #0 GeForce GTX 960M (5x128 cores) Grid(40x128) 117.802 MK/s (GPU 117.802 MK/s) Added 23-July-2019 GPU: GPU #0 GeForce GTX 1660 (22x64 cores) Grid(176x128) 839.061 MK/s (GPU 839.061 MK/s) Added 25-July-2019 GPU: GPU #0 GeForce GTX 1650 (14x64 cores) Grid(112x128) 511.906 MK/s (GPU 511.906 MK/s) (2^36.97) Added 21-Nov-2019 GPU: GPU #0 GeForce GTX 970 (13x128 cores) Grid(104x128) 360.322 MK/s (GPU 331.442 MK/s) (2^32.77) Added 25-Nov-2019 GPU: GPU #0 GeForce GTX 980 (16x128 cores) Grid(128x128) 375.384 MK/s (GPU 375.384 MK/s) GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256) [1361.71 Mkey/s][GPU 1361.71 Mkey/s] GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256) [2001.52 Mkey/s][GPU 2001.52 Mkey/s] Anything else? -Dave Last updated 25-Nov-2019. Actually i think especially in regards to the cuda version of bitcrack, the number of cuda cores for the specific card is really important, and there is actually a bunch of older cards with some great numbers here, for ex. the GTX 680 have 1536 cuda cores, which also happends to be the number of cuda cores for the GTX 770. For comparison other cards cuda cores: RTX 2080 TI - 4352 GTX 1080 TI - 3583 RTX 2080 Super - 3072 RTX 2080 Gaming - 2944 GTX 780 TI - 2880 GTX 980 TI - 2816 GTX 2070 TI - 2560 GTX 1080 - 2560 RTX 2070 Gaming - 2304 GTX 780 - 2304 RTX 2060 Super - 2176 GTX 980 - 2048 RTX 2060 - 1920 GTX 1070 - 1920 GTX 1060 1708 GTX 1660 TI - 1536 GTX 770 - 1536 GTX 680 - 1536 GTX 1660 Dual OC - 1408 GTX 670 - 1344 GTX 1660 Armor - 1280 GTX 1060 - 1152 GTX 760 - 1152 GTX 1650 - 896 GTX 1050 TI - 768 GTX 1050 - 640 GTX 580 - 512

105

Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder)

on: May 29, 2021, 07:56:53 PM

Quote from: DaveF on April 29, 2019, 02:27:50 PM Has anyone put together (or started to put together) a list of CPUs / Video Cards & the speed you can get out of them. I know it's a newer project and Jean_Luc is working VERY VERY hard on it so getting accurate numbers is going to be a moving target. But for now all we can do is look through the thread and see who is running what to get a general idea. So far I have pulled from this thread: GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(224x128) 914.418 MK/s (GPU 896.216 MK/s) GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128) 220.180 MK/s (GPU 220.180 MK/s) GPU: GPU #0 GeForce GT 520M (1x48 cores) Grid(8x128) 10.233 MK/s (GPU 7.026 MK/s) GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128) 1535.880 MK/s (GPU 1470.257 MK/s) Added 30-April-2019 GPU: GPU #0 GeForce GTX 1060 3GB (9x128 cores) Grid(72x128) 321.929 MK/s (GPU 321.929 MK/s) GPU: GPU #0 GeForce GTX 1080 (20x128 cores) Grid(160x128) 672.062 MK/s (GPU 672.062 MK/s) Added 1-May-2019 GPU: GPU #0 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) GPU: GPU #3 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) GPU: GPU #2 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) GPU: GPU #1 Tesla V100-SXM2-16GB (80x64 cores) Grid(640x128) 7260.449 MK/s (GPU 7212.931 MK/s) So 7260 / 4 = 1815 MK/s GPU: GPU #0 GeForce GTX 750 (4x128 cores) Grid(32x128) 104.960 MK/s (GPU 94.405 MK/s) (2^32.12) Added 3-May-2019 i7-7700K CPU Number of CPU thread: 8 22.092 MK/s (GPU 0.000 MK/s) With -t 7 Number of CPU thread: 7 21.609 MK/s Added 8-May-2019 EVGA RTX 2080 XC ULTRA 1427.967 MK/s (GPU 1424.946 MK/s) Added 23-May-2019 GPU: GPU #0 GeForce GTX 1660 Ti 961.319 MK/s (GPU 961.319 MK/s) GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128) GPU: GPU #1 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128) 5128.213 MK/s (GPU 5128.213 MK/s) So 5128 / 2 = 2564 MK/s Added 8-June-2019 GPU: GPU #0 GeForce GTX 960M (5x128 cores) Grid(40x128) 117.802 MK/s (GPU 117.802 MK/s) Added 23-July-2019 GPU: GPU #0 GeForce GTX 1660 (22x64 cores) Grid(176x128) 839.061 MK/s (GPU 839.061 MK/s) Added 25-July-2019 GPU: GPU #0 GeForce GTX 1650 (14x64 cores) Grid(112x128) 511.906 MK/s (GPU 511.906 MK/s) (2^36.97) Added 21-Nov-2019 GPU: GPU #0 GeForce GTX 970 (13x128 cores) Grid(104x128) 360.322 MK/s (GPU 331.442 MK/s) (2^32.77) Added 25-Nov-2019 GPU: GPU #0 GeForce GTX 980 (16x128 cores) Grid(128x128) 375.384 MK/s (GPU 375.384 MK/s) GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256) [1361.71 Mkey/s][GPU 1361.71 Mkey/s] GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256) [2001.52 Mkey/s][GPU 2001.52 Mkey/s] Anything else? -Dave Last updated 25-Nov-2019. Actually i think especially in regards to the cuda version of bitcrack, the number of cuda cores for the specific card is really important, and there is actually a bunch of older cards with some great numbers here, for ex. the GTX 680 have 1536 cuda cores, which also happends to be the number of cuda cores for the GTX 770. For comparison other cards cuda cores: RTX 2080 TI - 4352 GTX 1080 TI - 3583 RTX 2080 Super - 3072 RTX 2080 Gaming - 2944 GTX 780 TI - 2880 GTX 980 TI - 2816 GTX 2070 TI - 2560 GTX 1080 - 2560 RTX 2070 Gaming - 2304 GTX 780 - 2304 RTX 2060 Super - 2176 GTX 980 - 2048 RTX 2060 - 1920 GTX 1070 - 1920 GTX 1060 1708 GTX 1660 TI - 1536 GTX 770 - 1536 GTX 680 - 1536 GTX 1660 Dual OC - 1408 GTX 670 - 1344 GTX 1660 Armor - 1280 GTX 1060 - 1152 GTX 760 - 1152 GTX 1650 - 896 GTX 1050 TI - 768 GTX 1050 - 640 GTX 580 - 512

106

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 29, 2021, 11:32:17 AM

I got an RTX 2060 GPU. I was testing it using Jean_Luc's vanitygen and kangaroo. With the vanitygen the speed was at least +900 MKeys and the kangaroo speed was doing between 500 and 600 MKeys. Is this normal or do I have the wrong configuration with kangaroo?

107

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 23, 2021, 11:00:53 PM

So what does 256 bits look like stored in a work file, I need to see an example.

108

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 22, 2021, 01:54:16 AM

Quote from: a.a on May 22, 2021, 01:22:48 AM Expected RAM is 135431276999271530496 MB The Executable is running into OOM (out of memory) and silently fails? So that's why the bits are shaved off that's causing the range to seem like its smaller? It doesn't fail, it does hash. It just the range is smaller.

109

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 22, 2021, 01:53:51 AM

Quote from: fxsniper on May 22, 2021, 01:19:47 AM Quote from: bigvito19 on May 22, 2021, 12:21:32 AM Anybody else see this: What is problem detail? try test compare with binary windows .exe release and you compile version Did both have problem? I can only use the windows.exe, I can't compile because I don't have a gpu. I used 2 different laptops, 1 had reduced range and the other had doubled the range. On top of that I couldn't use my work files with the kangaroo 256.

110

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 22, 2021, 12:21:32 AM

Anybody else see this:

111

Alternate cryptocurrencies / Mining (Altcoins) / Re: Obsolete gtx1060-3gb GPUS can be used to find valuable keys 250 MH/Sec, 1000TH

on: May 22, 2021, 12:21:13 AM

Quote from: btc-room101 on May 21, 2021, 02:35:04 AM Quote from: bigvito19 on May 19, 2021, 03:30:14 PM All talk and no examples of anything, getting tired of all this theory talk. There are dozens of steps & modules in this process, its like cooking gourmet meal for a 1,000 people Your the type of person that wants a GUI, and his hand held going to the bathroom. All my stuff is cmd-line, like any hacking of cryptography its a long and tedious process, I have no intention of automating and black boxxing for morons. I will provide components and explain in detail how to use each component, but I will only do this with people who are not morons. Obviously, if you ain't already got a MS in physics or math, and ain't a python/c++ guru, and if you ain't got 10+ years experience in LINUX, no source on earth is going to help you, nobody helped me get this stuff going I did it on my own, and if smart people want to take this to the next step, that's good with me. If you didn't spend 20+ years as a sw developer doing networking, os, graphics, device-drivers, .. then you aint' going to get any of this ever. What moron 'talk' the entire thing is to teach people to think the right way about hacking bitcoin. GARWIN had a great quote "The hardest thing about dropping a-bomb was that once it was dropped they couldn't deny it existed", same here once everybody know's how easy it is to hack bitcoin, then the mythology is game-over. Garwin was the presidents advisor on atomic physics for 50+ years, he's probably dead now. Theory is way more interesting to me than 'code', you say your tired of 'thinking' you must be a first class un-educated fool. Why are you even posting? Don't you have a computer game to play? Dude you are a scammer, and your programs have malware in it. Those little projects that you just uploaded that probably don't even work cause you was trying to sell those same ones over a year ago. Now they are free, I wonder why.....still talk that same gibberish theory with those crappy programs you got and I don't remember trying to use your programs because you was trying to sell them. Now all of a sudden uploading them for free. Keep talking crazy, your account will be gone. You the one brought up the word moron, I could go on and on about you.

112

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 19, 2021, 08:41:17 PM

Quote from: WanderingPhilospher on May 19, 2021, 08:23:05 PM Quote from: NotATether on May 19, 2021, 07:29:26 PM Quote from: a.a on May 19, 2021, 06:33:05 PM What is the url of the fork? https://github.com/ZenulAbidin/Kangaroo-256 So what exactly does your fork do? Make it able to search in a 256 bit range? Anything else? Yea that's it, just make it able to search in a 256 bit range. That's all he was working on.

113

Alternate cryptocurrencies / Mining (Altcoins) / Re: Obsolete gtx1060-3gb GPUS can be used to find valuable keys 250 MH/Sec, 1000TH

on: May 19, 2021, 05:45:35 PM

Quote from: btc-room101 on May 19, 2021, 04:07:33 PM Quote from: bigvito19 on May 19, 2021, 03:30:14 PM All talk and no examples of anything, getting tired of all this theory talk. You can lead a moron to water, but you can't make them drink, funny how this works. I see I triggered you real good, you know you spam the same thing over and over. You will stop posting for a while and start back. You do it every time.

114

Alternate cryptocurrencies / Mining (Altcoins) / Re: Obsolete gtx1060-3gb GPUS can be used to find valuable keys 250 MH/Sec, 1000TH

on: May 19, 2021, 03:30:14 PM

All talk and no examples of anything, getting tired of all this theory talk.

115

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: May 14, 2021, 12:39:38 PM

Quote from: NotATether on May 14, 2021, 05:27:01 AM Quote from: Desyationer on May 14, 2021, 05:18:43 AM I only have 660 ti and this gives me a speed of 80 raw, 45 both addresses, 25 with tens of millions of addresses loaded. Can I count on anything or wasting my time? I see there are a lot of owners here for 4x3090, etc. You're probably not going to find an address with a large search range using a single 660Ti or even four GPUs. What's the ideal speed to find an address, small and large search range?

116

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2021, 01:02:22 PM

Quote from: fxsniper on May 11, 2021, 07:58:07 AM Quote from: WanderingPhilospher on May 11, 2021, 06:40:56 AM None of what you said makes sense....if you could run one 2^60 keyspace range in 1 second, how many days would it take to run 2^60 ranges?? Random = starting point for each tame and wild then they jump uniformly. You should really stop comparing the two programs, they are different. I just think if still run kangaroo all keyspace 2**120 still can not solve his puzzle I not have power with Tesla V100 or any GTX 30xx I just got new GPU GTX 1080 (not ti) for working graphics 3D render just looing for strategy for small card can do. and can run on some free time if method notworking I change to other method can possible You don't suppose to search all the space of course you won't solved it that way, that's what the DPs is for.

117

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 07, 2021, 09:42:58 AM

Quote from: NotATether on May 07, 2021, 08:33:26 AM Quote from: bigvito19 on May 06, 2021, 09:57:24 PM Quote from: NotATether on May 06, 2021, 05:39:15 PM Quote from: bigvito19 on May 06, 2021, 11:50:22 AM Ok, the 204.56 MK/s and 165.57 MK/s are those 2 speeds are added together to equal 370.13 MK/s? No. The first value on the left is the combined speed of both the CPU and GPU. The second value (165) is measuring the GPU speed only. it means the CPU speed is actually about 39 MK/s. Oh ok then, so what gpu's can go at least or close to 1 billion keys with kangaroo? A single RTX3090 can do 3 or 4 gigakeys/s, so it's not unreasonable to assume the other RTX 30s can search in excess of 1GK/s too. What about the RTX 20s?

118

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 06, 2021, 09:57:24 PM

Quote from: NotATether on May 06, 2021, 05:39:15 PM Quote from: bigvito19 on May 06, 2021, 11:50:22 AM Ok, the 204.56 MK/s and 165.57 MK/s are those 2 speeds are added together to equal 370.13 MK/s? No. The first value on the left is the combined speed of both the CPU and GPU. The second value (165) is measuring the GPU speed only. it means the CPU speed is actually about 39 MK/s. Oh ok then, so what gpu's can go at least or close to 1 billion keys with kangaroo?

119

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 06, 2021, 11:50:22 AM

Quote from: fxsniper on May 06, 2021, 12:25:53 AM Quote from: bigvito19 on May 05, 2021, 01:56:03 PM When you run kangaroo what are the speeds on the GTX 1060 and GTX 1050Ti? I use GTX 1050 not Ti on laptop speed 120-150M [204.56 MK/s][GPU 165.57 MK/s][Count 2^30.02][Dead 0][07s (Avg 01:28)][34.6/68.0MB] GTX 1050 and GTX 1050Ti is difference right GTX 1050Ti may be double speed to high more 50% Ok, the 204.56 MK/s and 165.57 MK/s are those 2 speeds are added together to equal 370.13 MK/s?

120

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 05, 2021, 01:56:03 PM

Quote from: WanderingPhilospher on May 01, 2021, 08:16:24 PM Quote from: NotATether on May 01, 2021, 07:52:23 PM Quote from: WanderingPhilospher on May 01, 2021, 03:46:01 PM I don't know anyone mass buying V100s; it is just the example used to solve #120 because that is the type and number of cards that were used to solve #110 and #115. I feel like #120 is going to be solved by large numbers of older cards lying around in people's garages somewhere, rather than with anything that can be rented with AWS or Vast. Even 100 of any high-end card just seems too expensive for someone with deep pockets to rent in the long run and you can get better results searching with a few thousand of people's Maxwell and Pascal cards (and even Radeons if Kangaroo ever gets ported to OpenCL). Well, it will be me so I can tell you they are all RTX 20xx and 30xx, but I am using 1 GTX 1060 and 1 GTX 1050Ti to do the tedious work. EDIT: I'm not running it full time, just here and there, so anyone really has a chance. When you run kangaroo what are the speeds on the GTX 1060 and GTX 1050Ti?

Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 »