Bitcoin Forum
August 14, 2018, 09:45:27 AM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
  Home Help Search Donate Login Register  
  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 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 ... 86 »
121  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 11, 2016, 12:40:06 AM
Also, source code for anyone who wants it: https://github.com/Vorksholk/PascalCoin-CUDA/blob/master/kernel.cu

And if people just want to download the new miner binaries without grabbing the whole PascalCoin package from filedropper: https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.00/CUDA_Pascal_v1.00.zip
122  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 11, 2016, 12:35:00 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3

 Is this the unneutered version of your software or have you not released it yet?


He released the unmetred one last night to support the network. Vorsholk is solid and a great person.

Actually totally spaced this, here's an unneutered version with the memory leak fix: http://www.filedropper.com/pascalcudav4
123  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 10, 2016, 11:17:00 PM
To answer a few questions about the GPU miner I've seen pop up:

Is the GPU miner compatible with 1.0.7?
Not currently, although I plan to make a GPU miner for 1.0.7 sometime soon (this weekend?).

Is there a memory leak in the current GPU miner?
Yup, leaks about a megabyte-ish a minute. I'm pretty sure I found the problem, testing the new version now to make sure it still performs as expected.

Do I need to use different users in Windows to mine with multiple GPUs?
Probably--each GPU will be essentially duplicating the work of the other GPUs if they're fed the same mining data, since they run deterministically (no 'random' nonce generation, though the number of threads running on the GPU do affect the nonce range explored).

Can the different GPU miners all run from the same folder?
No, you need to run a separate instance of PascalCoin from a separate folder for each GPU on the same machine.

Why do I need to use different users for multiple GPUs?
You need to run multiple instances of PascalCoin either with a different public key you mine with, or with a different miner name in order to make sure the GPUs aren't duplicating each other's work.

Will I be able to mine with multiple GPUs to a single wallet in the future?
Yes. The version that supports 1.0.7 and it's RPC functionality will allow you to specify a different miner name for each GPU. As long as you let each GPU use a different miner name, they won't duplicate any work between them (because the miner name is part of what gets hashed when producing a block).

Does it still make sense to CPU mine?
If you have free electric or just want to play around, sure. Unless you have free electric, it isn't going to be profitable.
124  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 10, 2016, 06:34:22 PM
@VorkSholk,
The miner is slowly draining the RAM , until its full of capacity and the PC stops responding...

Watched the miner a bit, certainly seems to slowly absorb memory over time... I probably missed something to dealloc.
125  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 10, 2016, 02:24:10 AM
Hi,

I'm getting this error "missing MSVCR120.dll", when trying to run gpu miner.

Windows 10 x64 build. Repair, uninstall, reinstalled  Microsoft Visual C++ 2013 Redistributable (x64) and restarted my PC - but still getting the same error.

help, please...

Try installing the 32-bit redistributable Smiley

Hello,

I download the cudaminer, and started the PascalCoinCUDA_sm61.exe

I dont need to make a .bat file do assing my wallet? I see that on pascalcoinwallet shows that im mining at 0,4Kh/s, but i don't see my sharerate, earning, nothing related to usual mining


Nope, don't need a .bat file. You can benchmark your card's performance using the binaries in the benchmark folder, but when you run the regular miner you have to wait a while to see any kind of result (sort of like a share).
126  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 10, 2016, 12:26:49 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3
127  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 10, 2016, 12:08:10 AM
Still not enough hashing power on the network, I'm gonna release the unneutered miner sometime in the next few hours.
128  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 10, 2016, 12:05:41 AM

Which wallet should be used with the GPU miner?

I've loaded up both, the one that comes with the miner
is version 1.0 and shows a hashrate of 0 using one cpu
core. The version 1.06 shows a hashrate for 1 core. The
GPU miner reports 'found nonce' using either wallet.



Gotta use the one that shows 1.0.0.0 (that comes in the pascalcuda zip file). The hashrate of 0 is because the CPU miner isn't doing any actual mining, just ferrying data back and forth to let the GPU miner do its work Smiley The GPU miner 'found nonce' isn't necessarily a block solution, it's a nonce which would be a valid solution at a difficulty target of 20000000 (basically the resultant hash starts with 32 zeroes, since 20 in hex is 32 in decimal), so it gives you some ability to see hashrate/"progress." With the current target of 265xxxxx, about one in 80-ish of those 'found nonce' will actually be a block Smiley.  You can think of the 'found nonce' sort of like shares pool mining, except you only get paid when you get a high-enough difficulty share.
129  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 09:53:52 PM
i use only 1 miner thread but running three istances of pascal coin (1 for each card) and cpu usage is big...

Ahh, I'll see what I can do Smiley
Made a build of the PascalWallet that uses 0% CPU while running for a GPU miner, testing it to make sure it can still mine a block, and then I'll publish it!
130  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 09:48:49 PM
i use only 1 miner thread but running three istances of pascal coin (1 for each card) and cpu usage is big...

Ahh, I'll see what I can do Smiley
131  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 09:42:03 PM
vorksholk you think this coin can mine also with compute capability 1.3 ? (have some testla card s1070 laying around) more over i see HUGE cpu usage ... should i disable mining in the pascal coin wallet and use only cuda exe ?


These cards are being sold super cheap right now on Ebay, and it looks like there are a lot of them around.  Another user here in a thread I just posted on the cards said they were essentially worthless for mining except to play with, but I'm a bit of an optimist.  Maybe also while the coin is still young they would be ok.  What are your experience with them?  I have the new thread maybe you could chime in there. 



As far as I'm aware, recent CUDA dev tools don't even support computing for things <compute 2.0.
132  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 09:33:39 PM
vorksholk you think this coin can mine also with compute capability 1.3 ? (have some testla card s1070 laying around) more over i see HUGE cpu usage ... should i disable mining in the pascal coin wallet and use only cuda exe ?

My code isn't compatible with cc1.3 unfortunately, sorry!

The CPU usage should only be, at most, one core pegged. Make sure you have one (and exactly one) mining thread in the PascalCoin wallet.
133  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 09:32:35 PM
sooo when sha asics can mine too

More than likely a new ASIC would have to be developed (due to differences in the way PascalCoin is mined, despite being SHA-256), although I can't speak for certain.
134  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 09:02:07 PM
have some wallet for donation ?

I might stick a donation address in the final miner, but for now I'm getting my benefit from having the faster miner instead Smiley Thanks though!

If Vorksholk doesn't want some donations make sure you donate directly to the Pascal developer to stimulate his development.

Yup, good idea!
135  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 08:55:26 PM
Seems people are fine with the 50% neutered miner for a week, and then full open-source release of the miner, and that's my favorite option since people can start mining today, so that's what we're going to do!

First thing's first, the download link: http://www.filedropper.com/pascalcuda

There are some incredibly important instructions though, since it's not obvious how to use, and there are a lot of caveats to the miner:
1. You must already have PascalCoin installed. If you don't have it, download it from sourceforge here: https://sourceforge.net/projects/pascalcoin/. Once it is installed, run the PascalCoinWallet.exe provided in the download.
2. You must be using a 256-bit secp256k1 key. This is the default behavior of the PascalCoin wallet.
3. Your miner name must be exactly 10 characters long. The miner expects that the input is exactly 176 total bytes (which is achieved by using a secp256k1 key and a 10-character name)
4. You must have one (and only one) active mining thread in the PascalCoin wallet. This mining thread is constantly loading solutions from datain.txt and attempting to mine a block with them.
5. You must run the GPU miner from the same directory as PascalCoinWallet.exe. If you run PascalCoinWallet.exe from the extracted PascalCuda.zip file and the PascalCoinCUDA_smXX.exe miner from the same location, it will work.

You can mine with multiple GPUs, however it might take a bit of cleverness. The miner accepts a single argument, a number, which determines which device the miner mines on. However, mining with multiple GPUs to one instance of a PascalCoin wallet will create duplicate work. A future version of the miner could avoid this by allowing each miner to use a different miner name, or something. Work in progress. Probably the easiest way to mine with multiple GPUs is to run separate copies of the PascalCoin wallet under different Windows users (and have each with either a different miner name, or a different private key being used for mining), and use a different GPU for each one.

There are a lot of different versions of the miner, compiled for different compute architectures (3.0 through 6.1). To find out which one your NVidia card supports, see: https://en.wikipedia.org/wiki/CUDA#Version_features_and_specifications

You may find that a version with a lower compute version than your card's compute version performs better for whatever reason. The only restriction is that you can't run a version with a higher compute capability than your card supports.

You will see a folder called 'Benchmarks' with a bunch of .exe files in it. This contains a standard headerout.txt file that will never change (unless you change it) that you can run all of the different smXX versions against to find out which is the fastest on your system. The benchmarker doesn't do full mining, but the performance of the benchmarker should be the same as the regular program. The benchmarker basically uses 'low-difficulty' shares to get a more accurate picture of hashrate. The benchmarker and standard miner are both neutered in the exact same fashion, so the benchmarkers should be accurate indicators of actual mining performance.

You will see that the benchmarker (and occasionally regular miner) will report the same nonce twice or more. This means there is duplicate work, an issue I'm still tracking down in my code.

Each time the actual miner (not the benchmarker) prints out a hash and a "Found nonce: ..." line, it found a solution that would work for a difficulty-20 block (AKA target = 20000000). On average, it would take 16 of these 'shares' to crack a block at a target of 25000000, or slightly less than 32 of these 'shares' to crack a block at the current target (256E5937).

If you find a way to compromise the neutering of the miner and make it run at full speed, congrats! It's probably not too difficult, and you're more than free to try.

Current forum time is October 09, 2016 8-ish PM. I will release the unneutered version and complete source-code sometime before October 16, 2016 8-ish PM.

Also since some people are complaining about this reducing the value of the coin: GPU miners are a natural progression of virtually every PoW cryptocurrency. By not making one, we're leaving the coin completely vulnerable to someone who does (and who could then freeze the network, strand it on a crazy difficulty, constantly fork it, etc.) By having someone like me make a GPU miner and releasing a 50% speed miner within about 5 hours of initial GPU mining and a full-speed miner a week later, the network is protected against a bad actor making a private GPU miner and harming the network. If anything, having a GPU miner should increase the value of the coin since it will soon be ~20x more secure (the GPU miner is roughly 20x more cost effective than equivalent CPUs). Also, this opens up the potential for a pool to be developed, and for an even faster OpenCL version to be created.

CAn you please release a version for gtx 460 cuda 2.1 version.It says cuda driver version is insufficient for CUDA runtime version.CUDA version 7.1

Here's a new zip file with a sm20 version too: http://www.filedropper.com/pascalcudav2
But it might not work for your card, since you only have CUDA 7.1 installed, and I don't have older versions of CUDA installed to build on. Sad
136  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 08:44:37 PM
have some wallet for donation ?

I might stick a donation address in the final miner, but for now I'm getting my benefit from having the faster miner instead Smiley Thanks though!
137  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 08:40:05 PM
I also haven't tested it, but I believe a shorter miner name would work if you just pad it with whitespace (so if you want your name to be 'Pascal' you could probably enter 'Pascal    ' (note the 4 spaces) into the miner name field, assuming that the wallet doesn't do any kind of trimming).
138  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 08:38:08 PM
ok stupid me didnt read abt arguments . i tried to issue a /? but no result sooooooooooooooooooooo need to read better stupid idiot... anyway great job first block found !

Congrats! I don't have much more time to work on this in the coming week, but I'll try to make it a bit more user friendly for the full launch! Smiley
139  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 08:37:36 PM
Seems people are fine with the 50% neutered miner for a week, and then full open-source release of the miner, and that's my favorite option since people can start mining today, so that's what we're going to do!

First thing's first, the download link: http://www.filedropper.com/pascalcuda

There are some incredibly important instructions though, since it's not obvious how to use, and there are a lot of caveats to the miner:
1. You must already have PascalCoin installed. If you don't have it, download it from sourceforge here: https://sourceforge.net/projects/pascalcoin/. Once it is installed, run the PascalCoinWallet.exe provided in the download.
2. You must be using a 256-bit secp256k1 key. This is the default behavior of the PascalCoin wallet.
3. Your miner name must be exactly 10 characters long. The miner expects that the input is exactly 176 total bytes (which is achieved by using a secp256k1 key and a 10-character name)
4. You must have one (and only one) active mining thread in the PascalCoin wallet. This mining thread is constantly loading solutions from datain.txt and attempting to mine a block with them.
5. You must run the GPU miner from the same directory as PascalCoinWallet.exe. If you run PascalCoinWallet.exe from the extracted PascalCuda.zip file and the PascalCoinCUDA_smXX.exe miner from the same location, it will work.

You can mine with multiple GPUs, however it might take a bit of cleverness. The miner accepts a single argument, a number, which determines which device the miner mines on. However, mining with multiple GPUs to one instance of a PascalCoin wallet will create duplicate work. A future version of the miner could avoid this by allowing each miner to use a different miner name, or something. Work in progress. Probably the easiest way to mine with multiple GPUs is to run separate copies of the PascalCoin wallet under different Windows users (and have each with either a different miner name, or a different private key being used for mining), and use a different GPU for each one.

There are a lot of different versions of the miner, compiled for different compute architectures (3.0 through 6.1). To find out which one your NVidia card supports, see: https://en.wikipedia.org/wiki/CUDA#Version_features_and_specifications

You may find that a version with a lower compute version than your card's compute version performs better for whatever reason. The only restriction is that you can't run a version with a higher compute capability than your card supports.

You will see a folder called 'Benchmarks' with a bunch of .exe files in it. This contains a standard headerout.txt file that will never change (unless you change it) that you can run all of the different smXX versions against to find out which is the fastest on your system. The benchmarker doesn't do full mining, but the performance of the benchmarker should be the same as the regular program. The benchmarker basically uses 'low-difficulty' shares to get a more accurate picture of hashrate. The benchmarker and standard miner are both neutered in the exact same fashion, so the benchmarkers should be accurate indicators of actual mining performance.

You will see that the benchmarker (and occasionally regular miner) will report the same nonce twice or more. This means there is duplicate work, an issue I'm still tracking down in my code.

Each time the actual miner (not the benchmarker) prints out a hash and a "Found nonce: ..." line, it found a solution that would work for a difficulty-20 block (AKA target = 20000000). On average, it would take 16 of these 'shares' to crack a block at a target of 25000000, or slightly less than 32 of these 'shares' to crack a block at the current target (256E5937).

If you find a way to compromise the neutering of the miner and make it run at full speed, congrats! It's probably not too difficult, and you're more than free to try.

Current forum time is October 09, 2016 8-ish PM. I will release the unneutered version and complete source-code sometime before October 16, 2016 8-ish PM.

Also since some people are complaining about this reducing the value of the coin: GPU miners are a natural progression of virtually every PoW cryptocurrency. By not making one, we're leaving the coin completely vulnerable to someone who does (and who could then freeze the network, strand it on a crazy difficulty, constantly fork it, etc.) By having someone like me make a GPU miner and releasing a 50% speed miner within about 5 hours of initial GPU mining and a full-speed miner a week later, the network is protected against a bad actor making a private GPU miner and harming the network. If anything, having a GPU miner should increase the value of the coin since it will soon be ~20x more secure (the GPU miner is roughly 20x more cost effective than equivalent CPUs). Also, this opens up the potential for a pool to be developed, and for an even faster OpenCL version to be created.

Thanks so much Vorksholk, I would really like to support a pool creation and we can develop other services for pascal from there.

A pool would be awesome! I unfortunately don't have the time to develop a pool myself (at least not for a while, got a bunch of other stuff to work on), but if anyone is interested in developing a pool I'd be more than happy to provide some tips. It basically boils down to this: the current modified PascalCoin wallet shoves out a 176-byte-long chunk of mining data, which is exactly what is hashed to solve a block. The last 4 bytes are the nonce, and the 2nd-to-last-4 bytes are the timestamp (unix epoch). Additionally, somewhere in that jumble is the miner name. Since the nonce is a 4-byte field, it only has 2^32 possible values, which could be exhausted in a few seconds by a fast GPU miner. Updating the timestamp is one way to get around this, but this would still mean you could only mine at about 4.294 GH/s. However, changing the miner name gives you another 10 bytes to fiddle with (2^80), which could be easily expanded to 14 bytes. Going to 18 bytes would require the calculation of an additional SHA256 expansion/compression round for the midstate, but that's no big deal with a miner build to take advantage of midstates anyhow. So a pool would probably have each worker use a different miner name. Your pool would grab the 176 bytes of data from the file, and serve it out to anyone with a miner connected to your pool. The mining software itself would alter the timestamp, nonce, and worker name, but they'd still be mining with the pool's public key. Shares work just like before, except server-side you have to build the block header using the worker name to validate their nonce/timestamp combo. Should be smooth sailing from there.

So it boils down to:
-->Mining software needs to be altered to support changing the miner name and potentially be more flexible with the midstate (and also needs to be networked instead of reading data from a file)
-->PascalCoin wallet needs an additional modification to allow the mining thread to also change the miner name

And then all of the bookkeeping/backend that's standard for a pool. Smiley
140  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Pascal Coin: P2P cryptocurrency without need of historical operations on: October 09, 2016, 08:21:48 PM
Seems people are fine with the 50% neutered miner for a week, and then full open-source release of the miner, and that's my favorite option since people can start mining today, so that's what we're going to do!

NOTICE: Someone ran a VirusTotal scan which came up with some positive results. I'm trying to figure out why, but to be on the safe side, don't download this until I figure it out! Sad

First thing's first, the download link: https://www.filedropper.com/pascalcudav4 EDIT: Update to v4, new PascalCoin wallet doesn't chew up CPU, GPU miner is now unneutered (2x performance from previous version), memory leak in GPU miner fixed!

Also, the miner is now open-source:
https://github.com/Vorksholk/PascalCoin-CUDA/blob/master/kernel.cu  Cheesy

There are some incredibly important instructions though, since it's not obvious how to use, and there are a lot of caveats to the miner:
1. You must already have PascalCoin installed. If you don't have it, download it from sourceforge here: https://sourceforge.net/projects/pascalcoin/. Once it is installed, run the PascalCoinWallet.exe provided in the download.
2. You must be using a 256-bit secp256k1 key. This is the default behavior of the PascalCoin wallet.
3. Your miner name must be exactly 10 characters long. The miner expects that the input is exactly 176 total bytes (which is achieved by using a secp256k1 key and a 10-character name)
4. You must have one (and only one) active mining thread in the PascalCoin wallet. This mining thread is constantly loading solutions from datain.txt and attempting to mine a block with them.
5. You must run the GPU miner from the same directory as PascalCoinWallet.exe. If you run PascalCoinWallet.exe from the extracted PascalCuda.zip file and the PascalCoinCUDA_smXX.exe miner from the same location, it will work.

You can mine with multiple GPUs, however it might take a bit of cleverness. The miner accepts a single argument, a number, which determines which device the miner mines on. However, mining with multiple GPUs to one instance of a PascalCoin wallet will create duplicate work. A future version of the miner could avoid this by allowing each miner to use a different miner name, or something. Work in progress. Probably the easiest way to mine with multiple GPUs is to run separate copies of the PascalCoin wallet under different Windows users (and have each with either a different miner name, or a different private key being used for mining), and use a different GPU for each one.

There are a lot of different versions of the miner, compiled for different compute architectures (3.0 through 6.1). To find out which one your NVidia card supports, see: https://en.wikipedia.org/wiki/CUDA#Version_features_and_specifications

You may find that a version with a lower compute version than your card's compute version performs better for whatever reason. The only restriction is that you can't run a version with a higher compute capability than your card supports.

You will see a folder called 'Benchmarks' with a bunch of .exe files in it. This contains a standard headerout.txt file that will never change (unless you change it) that you can run all of the different smXX versions against to find out which is the fastest on your system. The benchmarker doesn't do full mining, but the performance of the benchmarker should be the same as the regular program. The benchmarker basically uses 'low-difficulty' shares to get a more accurate picture of hashrate. The benchmarker and standard miner are both neutered in the exact same fashion, so the benchmarkers should be accurate indicators of actual mining performance.

You will see that the benchmarker (and occasionally regular miner) will report the same nonce twice or more. This means there is duplicate work, an issue I'm still tracking down in my code.

Each time the actual miner (not the benchmarker) prints out a hash and a "Found nonce: ..." line, it found a solution that would work for a difficulty-20 block (AKA target = 20000000). On average, it would take 2 of these 'shares' to crack a block at a target of 21000000, 16 of these 'shares' to crack a block at a target of 25000000, etc.

Current forum time is October 09, 2016 8-ish PM. I will release the unneutered version and complete source-code sometime before October 16, 2016 8-ish PM.
Released unneutered version about 6 days early.

Also since some people are complaining about this reducing the value of the coin: GPU miners are a natural progression of virtually every PoW cryptocurrency. By not making one, we're leaving the coin completely vulnerable to someone who does (and who could then freeze the network, strand it on a crazy difficulty, constantly fork it, etc.) By having someone like me make a GPU miner and releasing a 50% speed miner within about 5 hours of initial GPU mining and a full-speed miner a week later Edit: a day-ish later, the network is protected against a bad actor making a private GPU miner and harming the network. If anything, having a GPU miner should increase the value of the coin since it will soon be ~20x more secure (the GPU miner is roughly 20x more cost effective than equivalent CPUs). Also, this opens up the potential for a pool to be developed, and for an even faster OpenCL version to be created.
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 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 ... 86 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!