Bitcoin Forum
December 18, 2017, 05:06:52 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Poll
Question: I will be posting the DNET Price on the twitter at a set interval. Please vote for the frequency I will post it, I Want to lessen the complains of over activity.. Smiley
every 15 min - 45 (13.2%)
every 30 min - 19 (5.6%)
every hour - 63 (18.5%)
every 2 hours - 29 (8.5%)
every 4 hours - 184 (54.1%)
Total Voters: 340

Pages: « 1 ... 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 [196] 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 ... 480 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - POS 2.0 - ZEROCOIN PROTOCOL  (Read 692662 times)
Tecem
Newbie
*
Offline Offline

Activity: 18


View Profile
August 22, 2016, 11:10:46 AM
 #3901

My masternode wallet isn't syncing. It stays at 8 hours behind. Now I restarted and its 9 hours behind. Looks like its stuck at block 264538. When I check http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html I see there are new blocks. On my pc I did a full new resent but it crashes all the time.
1513616812
Hero Member
*
Offline Offline

Posts: 1513616812

View Profile Personal Message (Offline)

Ignore
1513616812
Reply with quote  #2

1513616812
Report to moderator
1513616812
Hero Member
*
Offline Offline

Posts: 1513616812

View Profile Personal Message (Offline)

Ignore
1513616812
Reply with quote  #2

1513616812
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513616812
Hero Member
*
Offline Offline

Posts: 1513616812

View Profile Personal Message (Offline)

Ignore
1513616812
Reply with quote  #2

1513616812
Report to moderator
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
August 22, 2016, 11:34:31 AM
 #3902

windows and linux node wallets crashing.


this is the debug for when it freezes in windows turning a node on.

2016-08-22 11:42:35 CActiveMasternode::Register() - RelayElectionEntry vin = CTxIn(COutPoint(670b2c66f7c3085aed0a316dfdb913bddd9265d362ca497a3e0ec8ca396d2516, 1), scriptSig=)
2016-08-22 11:42:37 CActiveMasternode::Register() - Adding to Masternode list
    service: 192.99.217.120:51472
    vin: CTxIn(COutPoint(028daa3945a7f9e3aca085aa128d9fc405584c8f78afaeea44d30958aeb602a6, 0), scriptSig=)
2016-08-22 11:42:37 CActiveMasternode::Register() - RelayElectionEntry vin = CTxIn(COutPoint(028daa3945a7f9e3aca085aa128d9fc405584c8f78afaeea44d30958aeb602a6, 0), scriptSig=)
2016-08-22 11:42:37 CMasternodePaymentWinner::IsValid - Unknown Masternode 6eeb8cff42f2d7376c14f929278295a4490e8246e7a0df5b533380be29a0ea19-1
2016-08-22 11:42:37 CMasternodePaymentWinner::IsValid - Unknown Masternode 6eeb8cff42f2d7376c14f929278295a4490e8246e7a0df5b533380be29a0ea19-1
2016-08-22 11:42:37 CMasternodePaymentWinner::IsValid - Unknown Masternode d1f39c09081d46039c34c0199ffe5430038547079d284e028f408ce8a75b9422-1
2016-08-22 11:42:37 CMasternodePaymentWinner::IsValid - Unknown Masternode 1ed36b70363e123c7725e8dc1fa33c28c9b825cdaac5b8edfbb86897da394324-1
2016-08-22 11:42:37 CMasternodePaymentWinner::IsValid - Unknown Masternode d327397aa5bf79e097a26f47b0749d5f1eecd81444f056170102268fdfc45fd5-0
2016-08-22 11:42:37 CMasternodePaymentWinner::IsValid - Unknown Masternode 1ed36b70363e123c7725e8dc1fa33c28c9b825cdaac5b8edfbb86897da394324-1
2016-08-22 11:42:38 CMasternodePaymentWinner::IsValid - Unknown Masternode d327397aa5bf79e097a26f47b0749d5f1eecd81444f056170102268fdfc45fd5-0
jakiman
Legendary
*
Offline Offline

Activity: 1064


jakiman is back!


View Profile
August 22, 2016, 11:53:28 AM
 #3903

Okay. I may have fixed my main controller/stake windows wallet from crashing.
Well, it's running the longest so far today. Over 15mins without a crash! Shocked

Basically, it's due to a corrupt or incorrect wallet.dat it seems.

What I did was get a known good wallet.dat backup and a known good blockchain backup then starting it with -zapwallettxes. (which keeps the labels)
After this, I ended up with a different number of coins compared to initiating the zapwallettxes after starting up the wallet via tools - repair wallet.
(if you don't have a blockchain backup, I guess you'll have to resync from scratch)

For the first time today, my wallet is able to go into "Staking Active" state as well.
With the same block hash as MN info page. So far so good!

You can follow me on Twitter for the latest PIVX news & updates: https://twitter.com/jakimanboy
DRPD
Legendary
*
Offline Offline

Activity: 868


View Profile
August 22, 2016, 12:49:58 PM
 #3904


no way to fix crashing mn's atm.

i just deleted all files incl. wallet.dat. -> complete new install -> sync from scratch on all mn's -> running/syncing for maybe ~3 hrs -> crash all down now.

waiting for a new version .....
muchoman
Sr. Member
****
Offline Offline

Activity: 461


View Profile
August 22, 2016, 01:11:09 PM
 #3905


no way to fix crashing mn's atm.

i just deleted all files incl. wallet.dat. -> complete new install -> sync from scratch on all mn's -> running/syncing for maybe ~3 hrs -> crash all down now.

waiting for a new version .....

Sad but true.
q327K091
Legendary
*
Offline Offline

Activity: 1218


View Profile
August 22, 2016, 01:42:58 PM
 #3906

is this windows specific issue ? have 47 nodes 0 problem (linux)

new upcoming awesome coin

the Gulden Coin: GKWHEPx3rQyPnbgQUSHu8gtgoRCgpqed1j
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
August 22, 2016, 02:03:15 PM
 #3907

is this windows specific issue ? have 47 nodes 0 problem (linux)

Nope my nodes on mphosting are doing it as well. Not all of them tho.
B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 420



View Profile WWW
August 22, 2016, 04:36:44 PM
 #3908

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

https://slack.pivx.org/ PIVX https://www.pivx.org PIVX https://forum.pivx.org/ PIVX https://github.com/PIVX-Project
Decentralized governance ✔ Privacy (Zerocoin protocol) ✔ Instant Tx✔ No Instamine ✔ POS✔decreasing inflation ✔
jamcrypt
Jr. Member
*
Offline Offline

Activity: 58


View Profile WWW
August 22, 2016, 04:57:00 PM
 #3909

So, why did this flop?

TXN44vKu7DuuDodL1Seky9rvt2mmXtqaMV
Tweeting handle @TrumpCoinG
TrumpCoin.com
#MakeCryptoGreatAgain
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
August 22, 2016, 05:33:17 PM
 #3910

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.
B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 420



View Profile WWW
August 22, 2016, 05:37:35 PM
 #3911

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.

I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new?

https://slack.pivx.org/ PIVX https://www.pivx.org PIVX https://forum.pivx.org/ PIVX https://github.com/PIVX-Project
Decentralized governance ✔ Privacy (Zerocoin protocol) ✔ Instant Tx✔ No Instamine ✔ POS✔decreasing inflation ✔
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
August 22, 2016, 05:47:19 PM
 #3912

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.

I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new?

Yep plenty of resources. Mp hosting nodes crashing to. Not just me as well. Some of them are fine but others arnt.
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
August 22, 2016, 07:12:38 PM
 #3913

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.

I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new?

test my crash problem on yours.

in debug

masternode start-alias mn1 YOURPASSWORD

and work you way up your nodes pressing up to bring up

masternode start-alias mn1 YOURPASSWORD

then just change the number. normal happens after activating about 5-6

might be that you just dont have enough nodes to see this crash and are only using limited functions in the wallet...

If it crashes it will not say the masternode has been activated but you can still go through the menus.

the mphosting/linux masternode is another problem in its own as that is just fresh install, new wallet, only things saved were conf file.
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064


View Profile WWW
August 22, 2016, 08:12:24 PM
 #3914

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.

I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new?

test my crash problem on yours.

in debug

masternode start-alias mn1 YOURPASSWORD

and work you way up your nodes pressing up to bring up

masternode start-alias mn1 YOURPASSWORD

then just change the number. normal happens after activating about 5-6

might be that you just dont have enough nodes to see this crash and are only using limited functions in the wallet...

If it crashes it will not say the masternode has been activated but you can still go through the menus.

the mphosting/linux masternode is another problem in its own as that is just fresh install, new wallet, only things saved were conf file.

I have tried to tell you before, that u need to use walletpassphrase <your pass phrase> 12000

Then do the masternode start-alias <masternode name>

The repeat, one line at a time. Will work much better than doing masternode start-alias <masternode name> <wallet passphrase>

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
mikegi
Full Member
***
Offline Offline

Activity: 165


View Profile
August 22, 2016, 08:21:29 PM
 #3915

I haven't had problems with the exception of the chain being stuck... once. (Same block
as everyone else...) My masternodes didn't need to be restarted for this. I started my
controller with a pre-PoS wallet.dat backup and masternodes with new wallet files. I can't say for
sure, but I don't I have had to restart masternodes with this version.
(Darknet Core Daemon version v2.1.2.0-ef94980). The wallet, I have restarted... usually due to
rebooting.

With all the restarting due to new versions, being stuck on forks,  it's likely all the remaining
wallets in the backup dir could all be corrupted... cause problems... since the default
number of backups to keep is 10.

$ darknetd -? |grep backup
  -createwalletbackups=<n> Number of automatic wallet backups (default: 10)


Corrupted is proably not be the best word, as it's likely that all the keys can be extracted, but
anyway, having something that causes problem for the dnet software or berkeley database
library.

Backing up the backup wallet directory every now and then would be prudent.
(As well as  keeping track of the versions of Berkeley DB used... if you don't use version 4.8 )

Note, that the Berkeley DB version, should not be a concern to most. To use a different version
one would need to compile darknetd oneself and specify that you are not using 4.8 with
./configure --with-incompatible-bdb.

I am far from being an expert in wallet.dat files and databases, but when I have run into syncing
trouble or wallet database problems in the past with other coins. It has often been something
to do with a mismatched DB library version or with a the database not being shut down cleanly
(software crash, system crash, ungraceful shutdown).

I suspect there will not be any new fix for those who are still having problems in the next darknet version.

Out of curiosity, has anyone tried "-salvagewallet"  (please back up first).  
mikegi
Full Member
***
Offline Offline

Activity: 165


View Profile
August 22, 2016, 08:34:58 PM
 #3916

We are trying to research the issue with corrupting and crashing wallets.

Is anyone having issues with Wallets crashing, that is NOT using that wallet to run a masternode (either local or remote masternodes). Just staking??

My wallet is running great, it only crashed on that wallet version that was corrupting wallet.dats. but I'm not running any masternodes and I haven't staked once but that's probly because my stake weight is in the negative, I have managed to get back 431 coins though lol! I just spent several hours trying to recover my coins, pretty sure they got orphaned during one of the forks. Since the wallet is defaulted to back itself up alot I had probly 40 back ups, I checked the dates on Bittrex then found all of the back ups from the day before, the day of, and the day after the transactions went out, imported a shit ton of .dats in hopes that one of them would have the private key for one of the address that I was using to withdraw but no deal, how that one address is the only one I don't have the key to and all of my small test transactions came through on another address but none of the big transfers is puzzling. So I have issues with 2 addresses, one that shows up on the block explorer but the private keys are mia and another that the big transfers aren't on the Explorer, only record is on my Bittrex account. So anyhow got the wallet completely rebuilt, all of the labels sorted out and sent a few coins from Bittrex, finally at least everything's working, but I'm not going to get too comfortable because it was all working before and confirmed in my wallet then poof got all forked up


         08/10/2016   DNET 4732.27123882   Completed
.       Address: DPAeb34bEZ9FfBh8Qt391UmHNhZWdzL27q
        TxId: b1a48c0214460ab94b5e46d2ef1e411a35213eab9277ee090d20841a4f9ab8c0

 That's the one that only the small txs stuck, if someone has an urge to do some Scooby-Doo business there you go
If anybody has any ideas I'm open for suggestions, ive literally tried everything I'm pretty sure. For now I gotta chill for a bit, that was exhausting

These might be a good start... ( it may be a bit of work to find the right numbers to modify this for DNET, and could depend on the format of the wallet but when you do you can extract all the keys, from wallet, used and unused). Could someone who knows more comment please?

https://gist.github.com/msm595/7595164

https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
August 22, 2016, 08:35:26 PM
 #3917

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.

I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new?

test my crash problem on yours.

in debug

masternode start-alias mn1 YOURPASSWORD

and work you way up your nodes pressing up to bring up

masternode start-alias mn1 YOURPASSWORD

then just change the number. normal happens after activating about 5-6

might be that you just dont have enough nodes to see this crash and are only using limited functions in the wallet...

If it crashes it will not say the masternode has been activated but you can still go through the menus.

the mphosting/linux masternode is another problem in its own as that is just fresh install, new wallet, only things saved were conf file.

I have tried to tell you before, that u need to use walletpassphrase <your pass phrase> 12000

Then do the masternode start-alias <masternode name>

The repeat, one line at a time. Will work much better than doing masternode start-alias <masternode name> <wallet passphrase>

Will try that next time. Doesn't explain the Linux/node crashing tho
mxnsch
Sr. Member
****
Offline Offline

Activity: 455


Miner, Firmware Tinkerer, Whisky Drinker


View Profile
August 22, 2016, 09:02:45 PM
 #3918

is this windows specific issue ? have 47 nodes 0 problem (linux)
No, the controller wallet seems to be the mostly affected component. OSX and Windows at least. Masternodes itself are working for me most of the time.

██  ███  masternode ninja ██  ███
EcoChavCrypto
Sr. Member
****
Offline Offline

Activity: 364


★Jetwin.com★


View Profile
August 22, 2016, 09:07:28 PM
 #3919

Contrary to you guys on my side everything is working perfectly. I have no problems, no crash. yesterday I started with fresh brand new wallet, wired coins, launch masternode... I am just waiting the first payement to be certain. However I have no crashes what's so ever win7 64 & debian 32...

Did you really use a wallet from before the switch to POS? maybe you should create a brand new clean wallet.dat and send your coins there from your current one... just and idea.

I hope your issues will be resolved.

Fresh resync. New wallet on nodes, controller is a wallet from may. Nothing to do with files it's the exe.

I don't know what to tell you... win10? because on my side as I told you, it's crash proof. Do you have enough cpu and ram resources? others programs running? maybe it's the old wallet controller? everything full new?

test my crash problem on yours.

in debug

masternode start-alias mn1 YOURPASSWORD

and work you way up your nodes pressing up to bring up

masternode start-alias mn1 YOURPASSWORD

then just change the number. normal happens after activating about 5-6

might be that you just dont have enough nodes to see this crash and are only using limited functions in the wallet...

If it crashes it will not say the masternode has been activated but you can still go through the menus.

the mphosting/linux masternode is another problem in its own as that is just fresh install, new wallet, only things saved were conf file.

I have tried to tell you before, that u need to use walletpassphrase <your pass phrase> 12000

Then do the masternode start-alias <masternode name>

The repeat, one line at a time. Will work much better than doing masternode start-alias <masternode name> <wallet passphrase>

I have been doing this technique for a few days now.  My win 64 wallet seems fine with no crashing. its just the nodes that keep crashing and getting corrupt blockchain errors.  Its becoming a bit sporadic now.  Majority of my nodes resynced ok but one got corrupted.


▄▄▄████████▄▄▄
▄▄███▀▀▀ ▄  ▄ ▀▀▀███▄▄
▄██▀▀ ▄▄████  ████▄▄ ▀▀██▄
▄██▀ ▄███████    ███████▄ ▀██▄
██▀ ▄████████▀    ▀████████▄ ▀██
██▀ ██████████      ██████████ ▀██
██▀ ██████████        ██████████ ▀██
▄██                                ██▄
██ ▄                              ▄ ██
██ ███▄                        ▄███ ██
██ ██████▄                  ▄██████ ██
██ ▀████████              ████████▀ ██
▀██ ███████                ███████ ██▀
██▄ █████▀                ▀█████ ▄██
██▄ ████        ▄▄        ████ ▄██
██▄ ▀█      ▄▄████▄▄      █▀ ▄██
██▄    ▄▄██████████▄▄    ▄██▀
▀██▄▄ ▀▀██████████▀▀ ▄▄██▀
▀▀███▄▄▄ ▀▀▀▀ ▄▄▄███▀▀
▀▀▀████████▀▀▀
 

    [    ]
tylerderden
Hero Member
*****
Offline Offline

Activity: 952


View Profile
August 22, 2016, 11:03:15 PM
 #3920

We are trying to research the issue with corrupting and crashing wallets.

Is anyone having issues with Wallets crashing, that is NOT using that wallet to run a masternode (either local or remote masternodes). Just staking??

My wallet is running great, it only crashed on that wallet version that was corrupting wallet.dats. but I'm not running any masternodes and I haven't staked once but that's probly because my stake weight is in the negative, I have managed to get back 431 coins though lol! I just spent several hours trying to recover my coins, pretty sure they got orphaned during one of the forks. Since the wallet is defaulted to back itself up alot I had probly 40 back ups, I checked the dates on Bittrex then found all of the back ups from the day before, the day of, and the day after the transactions went out, imported a shit ton of .dats in hopes that one of them would have the private key for one of the address that I was using to withdraw but no deal, how that one address is the only one I don't have the key to and all of my small test transactions came through on another address but none of the big transfers is puzzling. So I have issues with 2 addresses, one that shows up on the block explorer but the private keys are mia and another that the big transfers aren't on the Explorer, only record is on my Bittrex account. So anyhow got the wallet completely rebuilt, all of the labels sorted out and sent a few coins from Bittrex, finally at least everything's working, but I'm not going to get too comfortable because it was all working before and confirmed in my wallet then poof got all forked up


         08/10/2016   DNET 4732.27123882   Completed
.       Address: DPAeb34bEZ9FfBh8Qt391UmHNhZWdzL27q
        TxId: b1a48c0214460ab94b5e46d2ef1e411a35213eab9277ee090d20841a4f9ab8c0

 That's the one that only the small txs stuck, if someone has an urge to do some Scooby-Doo business there you go
If anybody has any ideas I'm open for suggestions, ive literally tried everything I'm pretty sure. For now I gotta chill for a bit, that was exhausting

These might be a good start... ( it may be a bit of work to find the right numbers to modify this for DNET, and could depend on the format of the wallet but when you do you can extract all the keys, from wallet, used and unused). Could someone who knows more comment please?

https://gist.github.com/msm595/7595164

https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings


Oh sure...lemme just open this can of worms real quick hahaa,  thanks for the links though seriously. Im not even that concerned about it working now,  I think digging into all of that will be cool regardless of the end result.

I did try salvage wallet also,  unfortunately it didn't work. Wallet had a salvaged title or some thing.
Pages: « 1 ... 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 [196] 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 ... 480 »
  Print  
 
Jump to:  

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!