Bitcoin Forum
November 22, 2026, 02:25:11 AM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: Will you support Gavin's new block size limit hard fork of 8MB by January 1, 2016 then doubling every 2 years?
1.  yes
2.  no

Pages: « 1 ... 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 [1366] 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 ... 1557 »
  Print  
Author Topic: Gold collapsing. Bitcoin UP.  (Read 2032359 times)
NewLiberty
Legendary
*
Offline

Activity: 1204
Merit: 1002


Gresham's Lawyer


View Profile WWW
June 24, 2015, 03:43:02 PM
 #27301

(sorry for the OT)

if memory serves somewhere in the last few dozens of pages there was a debate
involving climate change,  I've just found this interesting article titled
"What's really warming the world"

http://www.bloomberg.com/graphics/2015-whats-warming-the-world/


There are other threads on this topic here already.  Why pollute this one?  Wink

FREE MONEY1 Bitcoin for Silver and Gold NewLibertyDollar.com and now BITCOIN SPECIE (silver 1 ozt) shows value by QR
Bulk premiums as low as .0012 BTC "BETTER, MORE COLLECTIBLE, AND CHEAPER THAN SILVER EAGLES" 1Free of Government
sickpig
Legendary
*
Offline

Activity: 1260
Merit: 1014


View Profile
June 24, 2015, 03:52:31 PM
 #27302

(sorry for the OT)

if memory serves somewhere in the last few dozens of pages there was a debate
involving climate change,  I've just found this interesting article titled
"What's really warming the world"

http://www.bloomberg.com/graphics/2015-whats-warming-the-world/


There are other threads on this topic here already.  Why pollute this one?  Wink

You're absolutely right.

Again sorry for being off topic.

Bitcoin is a participatory system which ought to respect the right of self determinism of all of its users - Gregory Maxwell.
sickpig
Legendary
*
Offline

Activity: 1260
Merit: 1014


View Profile
June 24, 2015, 04:24:00 PM
 #27303

EU Banks Forced to Report Bitcoin-Linked Accounts Transacting Over €1,000

http://www.xbt.money/eu-banks-forced-to-report-bitcoin-linked-accounts-transacting-over-e1000/

Quote
An anonymous Dutch bank employee has revealed that major banks in the EU are applying new rules forcing banks to report, monitor or investigate accounts receiving or sending over €1,000 connected to bitcoin.

Bitcoin is a participatory system which ought to respect the right of self determinism of all of its users - Gregory Maxwell.
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 24, 2015, 04:28:52 PM
 #27304

Tsipras taking to Twitter!

http://blogs.wsj.com/moneybeat/2015/06/24/equities-turn-red-as-greek-optimism-fades-tsipras-vents-on-twitter/
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 24, 2015, 04:36:13 PM
 #27305

another person who sees problems with block size voting.  i haven't analyzed the attack; just posting here from bitcoin-dev:

On Tue, Jun 23, 2015 at 8:05 PM, William Madden <will.madden@novauri.com> wrote:

    Here are refutations of the approach in BIP-100 here:
    http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf

    To recap BIP-100:

    1) Hard form to remove static 1MB block size limit
    2) Add new floating block size limit set to 1MB
    3) Historical 32MB message limit remains
    4) Hard form on testnet 9/1/2015
    5) Hard form on main 1/11/2016
    6) 1MB limit changed via one-way lock in upgrade with a 12,000 block
    threshold by 90% of blocks
    7) Limit increase or decrease may not exceed 2x in any one step
    Cool Miners vote by encoding 'BV'+BlockSizeRequestValue into coinbase
    scriptSig, e.g. "/BV8000000/" to vote for 8M.
    9) Votes are evaluated by dropping bottom 20% and top 20%, and then the
    most common floor (minimum) is chosen.

    8MB limits doubling just under every 2 years makes a static value grow
    in a predictable manner.

    BIP-100 makes a static value grow (or more importantly potentially
    shrink) in an unpredictable manner based on voting mechanics that are
    untested in this capacity in the bitcoin network.  Introducing a highly
    variable and untested dynamic into an already complex system is
    unnecessarily risky.

    For example, the largely arbitrary voting rules listed in 9 above can be
    gamed.  If I control pools or have affiliates involved in pools that
    mine slightly more than 20% of blocks, I could wait until block sizes
    are 10MB, and then suddenly vote "/BV5000000/" for 20% of blocks and
    "/BV5000001/" for the remaining 10%.  If others don't consistently vote
    for the same "/BV#/" value, vote too consistently and have their value
    thrown out as the top 20%, I could win the resize to half capacity
    "/BV5000001/" because it was the lowest repeated value not in the bottom
    20%.

    I could use this to force an exodus to my sidechain/alt coin, or to
    choke out the bitcoin network.  A first improvement would be to only let
    BIP-100 raise the cap and not lower it, but if I can think of a
    vulnerability off the top of my head, there will be others on the other
    side of the equation that have not been thought of.  Why bother
    introducing a rube goldberg machine like voting when a simple 8mb cap
    with predictable growth gets the job done, potentially permanently?

NewLiberty
Legendary
*
Offline

Activity: 1204
Merit: 1002


Gresham's Lawyer


View Profile WWW
June 24, 2015, 04:57:51 PM
 #27306

another person who sees problems with block size voting.  i haven't analyzed the attack; just posting here from bitcoin-dev:

On Tue, Jun 23, 2015 at 8:05 PM, William Madden <will.madden@novauri.com> wrote:

    Here are refutations of the approach in BIP-100 here:
    http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf

    To recap BIP-100:

    1) Hard form to remove static 1MB block size limit
    2) Add new floating block size limit set to 1MB
    3) Historical 32MB message limit remains
    4) Hard form on testnet 9/1/2015
    5) Hard form on main 1/11/2016
    6) 1MB limit changed via one-way lock in upgrade with a 12,000 block
    threshold by 90% of blocks
    7) Limit increase or decrease may not exceed 2x in any one step
    Cool Miners vote by encoding 'BV'+BlockSizeRequestValue into coinbase
    scriptSig, e.g. "/BV8000000/" to vote for 8M.
    9) Votes are evaluated by dropping bottom 20% and top 20%, and then the
    most common floor (minimum) is chosen.

    8MB limits doubling just under every 2 years makes a static value grow
    in a predictable manner.

    BIP-100 makes a static value grow (or more importantly potentially
    shrink) in an unpredictable manner based on voting mechanics that are
    untested in this capacity in the bitcoin network.  Introducing a highly
    variable and untested dynamic into an already complex system is
    unnecessarily risky.

    For example, the largely arbitrary voting rules listed in 9 above can be
    gamed.  If I control pools or have affiliates involved in pools that
    mine slightly more than 20% of blocks, I could wait until block sizes
    are 10MB, and then suddenly vote "/BV5000000/" for 20% of blocks and
    "/BV5000001/" for the remaining 10%.  If others don't consistently vote
    for the same "/BV#/" value, vote too consistently and have their value
    thrown out as the top 20%, I could win the resize to half capacity
    "/BV5000001/" because it was the lowest repeated value not in the bottom
    20%.

    I could use this to force an exodus to my sidechain/alt coin, or to
    choke out the bitcoin network.  A first improvement would be to only let
    BIP-100 raise the cap and not lower it, but if I can think of a
    vulnerability off the top of my head, there will be others on the other
    side of the equation that have not been thought of.  Why bother
    introducing a rube goldberg machine like voting when a simple 8mb cap
    with predictable growth gets the job done, potentially permanently?



Is it meant to be humorous that voting is described as arbitrary when compared to a single person picking a number out of his head?

FREE MONEY1 Bitcoin for Silver and Gold NewLibertyDollar.com and now BITCOIN SPECIE (silver 1 ozt) shows value by QR
Bulk premiums as low as .0012 BTC "BETTER, MORE COLLECTIBLE, AND CHEAPER THAN SILVER EAGLES" 1Free of Government
Adrian-x
Legendary
*
Offline

Activity: 1372
Merit: 1000



View Profile
June 24, 2015, 05:08:48 PM
Last edit: June 24, 2015, 05:31:40 PM by Adrian-x
 #27307

I've come to see a single core as being the single greatest threat to Bitcoin out of all of this. A better situation to me would be a bitcoin P2P network with several separately developed cores that adhere to a common set of rules. The upgrade path is then always put to a vote. Any one core could then propose a change simply by implementing it (with a rule that after x% of blocks back the change it becomes active).

Then if people like the change, more will move to that core. This in turn would cause the other core to adopt the change or lose their users, and that is how consensus is achieved. If a majority did not like the change, they would not move to that core, and the change would never be accepted.

At no point in this do any set of gatekeepers get to dictate terms. Since no core has a majority of users captured, change would always have to come through user acceptance and adoption, and developers would simply be proposers of options.

You just reinvented pegged side chains.
I think you're just starting to understand Bitcoin. No need to fork to SC's?

Thank me in Bits 12MwnzxtprG2mHm3rKdgi7NmJKCypsMMQw
thezerg
Legendary
*
Offline

Activity: 1246
Merit: 1018


View Profile
June 24, 2015, 05:15:21 PM
 #27308

yes the voting has issues.  

The biggest issue is the role the block size cap should have in the network.  

Satoshi, Gavin, et al. see it as a "sanity check".  In software this is essentially an exceptional condition -- a value that the system should *never* exceed.  In this perspective, miners can individually produce smaller blocks (regardless of pending txn count) so why create a mechanism that essentially forces a cartel (collective behavior)?  The only reason would be to maximize miner profitability by manipulating the supply curve.  Closely tracking evolving network and disk capacity is not necessary for a "sanity check" because most miners will simply start mining smaller blocks (than the limit) if network and disk stop following moore's law.

Others want the max block size to be an entity that can be used to actively manage the network.  Presumably if miners are noticing a lot of "spam", but a "misbehaving" miner is mining it, they could vote to reduce block capacity to eliminate this spam.  Also, voting lets the limit more closely track the evolution of network and disk capacity.
Zangelbert Bingledack
Legendary
*
Offline

Activity: 1036
Merit: 1000


View Profile
June 24, 2015, 05:37:57 PM
 #27309

Is it meant to be humorous that voting is described as arbitrary when compared to a single person picking a number out of his head?

A single person picking a number out of their head is voting, because all the person can do is make a suggestion. Every suggestion is voted on, by investors.

Superimposing a second voting mechanism, and more complexity with it, seems redundant. That is, unless you think "hard forks are dangerous." I say, get comfortable with the fork, make it so that it is easy to do with predictable results, and then use it whenever necessary. Whatever its dangers may be, the dynamics of that voting mechanism are far superior.
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 24, 2015, 05:43:34 PM
 #27310

yes the voting has issues.  

The biggest issue is the role the block size cap should have in the network.  

Satoshi, Gavin, et al. see it as a "sanity check".  In software this is essentially an exceptional condition -- a value that the system should *never* exceed.  In this perspective, miners can individually produce smaller blocks (regardless of pending txn count) so why create a mechanism that essentially forces a cartel (collective behavior)?  The only reason would be to maximize miner profitability by manipulating the supply curve.  Closely tracking evolving network and disk capacity is not necessary for a "sanity check" because most miners will simply start mining smaller blocks (than the limit) if network and disk stop following moore's law.

Others want the max block size to be an entity that can be used to actively manage the network.  Presumably if miners are noticing a lot of "spam", but a "misbehaving" miner is mining it, they could vote to reduce block capacity to eliminate this spam.  Also, voting lets the limit more closely track the evolution of network and disk capacity.

Let's assume a spam attacking misbehaving miner ala the large miner, large block attack against small miners that was initially a huge FUD advanced by Wiulle and others that you don't hear anything about anymore. Simple defense, just mine a 0 TX header only block during the time of your large block processing. This is the practical defense that Wang Chun told us they do and that we've witnessed they do during stress tests. And this defense can be done  irrespective of whether as a miner you are connected to Corallo's relay network or not which those Fudsters love to go on about.

Point being miners can and should be encouraged to track TX's and fees and construct blocks appropriately based on their own internal metrics and profitability. Core devs can't possibly do this.

Yes, you could accuse Gavin of trying to be a one man predictor for network growth at this point but his proposal is based on sound growth projections with the larger point being that he is trying to automate out as much human intervention, voting manipulation  and need for future forks as much as  possible.

thezerg
Legendary
*
Offline

Activity: 1246
Merit: 1018


View Profile
June 24, 2015, 05:49:20 PM
 #27311

yes the voting has issues.  

The biggest issue is the role the block size cap should have in the network.  

Satoshi, Gavin, et al. see it as a "sanity check".  In software this is essentially an exceptional condition -- a value that the system should *never* exceed.  In this perspective, miners can individually produce smaller blocks (regardless of pending txn count) so why create a mechanism that essentially forces a cartel (collective behavior)?  The only reason would be to maximize miner profitability by manipulating the supply curve.  Closely tracking evolving network and disk capacity is not necessary for a "sanity check" because most miners will simply start mining smaller blocks (than the limit) if network and disk stop following moore's law.

Others want the max block size to be an entity that can be used to actively manage the network.  Presumably if miners are noticing a lot of "spam", but a "misbehaving" miner is mining it, they could vote to reduce block capacity to eliminate this spam.  Also, voting lets the limit more closely track the evolution of network and disk capacity.

Let's assume a spam attacking misbehaving miner ala the large miner, large block attack against small miners that was initially a huge FUD advanced by Wiulle and others that you don't hear anything about anymore. Simple defense, just mine a 0 TX header only block during the time of your large block processing. This is the practical defense that Wang Chun told us they do and that we've witnessed they do during stress tests. And this defense can be done  irrespective of whether as a miner you are connected to Corallo's relay network or not which those Fudsters love to go on about.

Point being miners can and should be encouraged to track TX's and fees and construct blocks appropriately based on their own internal metrics and profitability. Cite devs can't possibly do this.

Yes, you could accuse Gavin of trying to be a one man predictor for network growth at this point but his proposal is based on sound growth projections with the larger point being that he is trying to automate out as much human intervention and need for future forks as much as  possible.

Miners are

yes the key thing to understand is that he's not trying to hit a bullseye here.  It is not necessary.  He is just trying to define an extreme condition to let coders allocate memory, size embedded hardware, etc based on these maximums.  Individual miners are welcome to mine smaller blocks.
tvbcof
Legendary
*
Offline

Activity: 5390
Merit: 1370


View Profile
June 24, 2015, 06:21:37 PM
Last edit: June 24, 2015, 06:34:47 PM by tvbcof
 #27312

I'm less interested in rushing the hard fork than I was, now that it seems less likely that Bitcoin breaks due to full blocks.

I sent transactions Monday during the test, I just picked some older outputs from the bottom of the wallet, and they confirmed after 1 block.

The full block 'problem' was overplayed for propaganda reasons.  It's the same principle as making loud noises to get a herd of animals to do what you want them to do.

Someone made some graph with his guess at simplistic future predictions which did not (because they can not) make any allowance for future developments.  His genius was to put pretty colors on it which were even more arbitrary.  Since people like shiny and colorful things (a throw-back to our simian ancestry where identifying ripe fruit was important) it was a wildly successful bit of propaganda with many observers.  That does not make it particularly meaningful in reality though.

In point of fact there is a large mostly synthetic utilization of transaction availability even at the 1MB derived rate.  This from people who would not be there if it were not for the fact that BTC transactions are subsidized to the level of being nearly free.  Sloughing off these freeloaders will not threaten the system at all and may be helpful.  This would buy us at least a lot of time.  If/When an actual problem with capacity occurs everyone that I know of (except perhaps MP) is perfectly amenable to increasing capacity through simplistic block size increase methods.  In that case, unlike today, it will be much more easy to gain the 'consensus' that Bitcoin needs.


sig spam anywhere and self-moderated threads on the pol&soc board are for losers.
tvbcof
Legendary
*
Offline

Activity: 5390
Merit: 1370


View Profile
June 24, 2015, 06:49:16 PM
 #27313

(sorry for the OT)

if memory serves somewhere in the last few dozens of pages there was a debate
involving climate change,  I've just found this interesting article titled
"What's really warming the world"

http://www.bloomberg.com/graphics/2015-whats-warming-the-world/


There are other threads on this topic here already.  Why pollute this one?  Wink

You're absolutely right.

Again sorry for being off topic.

Just for reference, those of us who's interests include the global climate change issue/scam (if they have a range of interests at all) have a lot of fun on another epic thread here:  https://bitcointalk.org/index.php?topic=374873.0  All are welcome and a lot of scammer minions have fallen.  Most of the time it only takes a few days.


sig spam anywhere and self-moderated threads on the pol&soc board are for losers.
polyclef
Newbie
*
Offline

Activity: 10
Merit: 1


View Profile
June 24, 2015, 07:09:45 PM
 #27314

No. No hostile forks.
justusranvier
Legendary
*
Offline

Activity: 1400
Merit: 1069



View Profile
June 24, 2015, 07:20:13 PM
 #27315

No. No hostile forks.
if 75% of the network wants to go with large blocks and 25% want to force smaller blocks, which fork is the hostile one?
tvbcof
Legendary
*
Offline

Activity: 5390
Merit: 1370


View Profile
June 24, 2015, 07:45:32 PM
 #27316

No. No hostile forks.
if 75% of the network wants to go with large blocks and 25% want to force smaller blocks, which fork is the hostile one?

I suppose by that argument the Russian revolution (to use one of countless examples)  was, by definition, not a 'hostile' fork since it was democratic.

In any conflict, once the first shot is fired all involved parties are are appropriately labeled 'belligerents'.  As to who 'started it', that is left to the history books and these are, as they say, 'written by the victors.'


sig spam anywhere and self-moderated threads on the pol&soc board are for losers.
justusranvier
Legendary
*
Offline

Activity: 1400
Merit: 1069



View Profile
June 24, 2015, 08:25:16 PM
 #27317

I suppose by that argument the Russian revolution (to use one of countless examples)  was, by definition, not a 'hostile' fork since it was democratic.

In any conflict, once the first shot is fired all involved parties are are appropriately labeled 'belligerents'.  As to who 'started it', that is left to the history books and these are, as they say, 'written by the victors.'
The fundemental error here is failing to recognize the voluntary nature of currency adoption.

Gavin proposed a change to Bitcoin that users are free to accept or decline.

That some developers interpreted this as a threat and turned it into a battle only shows the weakness of their position.

The proper response would have been to convince people to not choose the change by explaning why they would be better of by doing so.

Instead, they acted with outrage over the idea that somebody proposed something without their permission and was doing a better job of convincing people that they'd benefit from his proposal instead of theirs.

This is not a sustainable position for them. Money is only as valuable as there are other people willing to accept it, and nobody is in a position to force anybody to accept Bitcoin.

People who act on the expectation that their opinions are right by default because they were there first and so aren't subject to continual validation in the marketplace of ideas are going to end up losing everything.
Zangelbert Bingledack
Legendary
*
Offline

Activity: 1036
Merit: 1000


View Profile
June 24, 2015, 08:30:41 PM
Last edit: June 24, 2015, 08:42:25 PM by Zangelbert Bingledack
 #27318

If/When an actual problem with capacity occurs everyone that I know of (except perhaps MP) is perfectly amenable to increasing capacity through simplistic block size increase methods.  In that case, unlike today, it will be much more easy to gain the 'consensus' that Bitcoin needs.

If so, then people can all take a chill pill and stop with the scaremongering on both sides. We're probably a lot closer to consensus than we think if the FUD is all cleared away.

I expect we are far from 1MB being stifling, as long as the fee market works properly, and conversely I also suspect that the cap isn't really needed at all. But for the sake of conservatism and consensus, we should just keep moving up the cap modestly so that it stays similar to its usual position well above where it would be actually functioning as much of a cap. If problems arise on either the "fees too high" or "blocks too big" (or "spammers just use up all the extra space") side, we can make the necessary adjustments by either increasing the cap or getting the fee market working better. If we get both problems, we'll actually be in a double pinch and have to innovate our way out, but I don't think we're anywhere close to that even being a possibility yet.

The debate now, assuming the FUD is wiped away, seems to come down to, "Is it better to hit too-high fees first, or too-big blocks first?" I can see the argument from an optimization perspective that too-high fees is smoother and results in more economization and innovation, but on the other hand if it starts to hinder adoption that would be self-defeating and could even reduce decentralization because people who otherwise would have adopted and run full nodes will turn away.

I think from looking at how everyone is acting and reacting in this debate that it is clear people's opinions (even of most devs) will generally move away from any pain that develops, so I see no danger of Bitcoin being "stuck" or stonewalled into a position that is painful for anyone, at least until we get to the "double pinch" scenario above, where both full blocks and high fees are a problem, but again that should be way far in the future, where we really can likely rely on things like Lightning Network and whatever other alien tech exists then.

TL;DR: Not worried.
Odalv
Legendary
*
Offline

Activity: 1414
Merit: 1000



View Profile
June 24, 2015, 08:35:18 PM
 #27319

I suppose by that argument the Russian revolution (to use one of countless examples)  was, by definition, not a 'hostile' fork since it was democratic.

In any conflict, once the first shot is fired all involved parties are are appropriately labeled 'belligerents'.  As to who 'started it', that is left to the history books and these are, as they say, 'written by the victors.'
The fundemental error here is failing to recognize the voluntary nature of currency adoption.

Gavin proposed a change to Bitcoin that users are free to accept or decline.

That some developers interpreted this as a threat and turned it into a battle only shows the weakness of their position.

The proper response would have been to convince people to not choose the change by explaning why they would be better of by doing so.

Instead, they acted with outrage over the idea that somebody proposed something without their permission and was doing a better job of convincing people that they'd benefit from his proposal instead of theirs.

This is not a sustainable position for them. Money is only as valuable as there are other people willing to accept it, and nobody is in a position to force anybody to accept Bitcoin.

People who act on the expectation that their opinions are right by default because they were there first and so aren't subject to continual validation in the marketplace of ideas are going to end up losing everything.

Maybe it would be fine if 8 GB block-size supporters spin-of their own XT-coin sidechain.  :-) (My advice is to use 2wp so you can go back later.)
TPTB_need_war
Sr. Member
****
Offline

Activity: 420
Merit: 262


View Profile
June 24, 2015, 08:40:36 PM
Last edit: June 24, 2015, 08:54:26 PM by TPTB_need_war
 #27320

I'm more of the opinion that Bitcoin will succeed, provided that it does not fail, and that a misstep can easily be worse than doing nothing.
Intelligent people may disagree with this.

The question is, what more qualifies as "doing nothing":

  • Letting Bitcoin operate with constantly full blocks, which has never been done before, or
  • Continuing to let Bitcoin operate with non-full blocks, effectively uncapped,* as it always has

   ?


*Of course a large part of the debate is over whether the current hard cap is actually doing anything. So the appeal to conservatism implied by "doing nothing" just pushes the question back.

Your question presumes omniscience thus it is not falsifiable. Junk science.

For example, it may be the case that the vulture capital is waiting for the exponential block size scaling before they unload the masses into Bitcoin via Paypal, Coinbase, Circle, Facebook, 21 Inc, etc.. With the intent of forcing out ephemeral miners and achieving distributed centralization and KYC regulation every where.

Actually that outcome is the one I think is nearly assured no matter which direction we go, because one could speculate that they've also invested in pegged side chains as an alternative where those entities can push the masses into a side chain which extracts the BTC value out of Core, and then they cut loose the hashrate on Core (and any other merged mind side chains) and send it off into nowhere, nowhere land.

Then again, I am onto their plans and working on the antidote.

Pages: « 1 ... 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 [1366] 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 ... 1557 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!