Wall Observer BTC/USD - Bitcoin price movement tracking & discussion

[surfer43]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

[windjc]

huge dump on stamp

huge being 100 in half hour?

Close to 400 in a few minutes.

[chessnut]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

lol aaaaaaannnddd it's gone.

[Ivanhoe]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

500 is not huge, but it was more like 300 or something.

[MinermanNC]

huge dump on stamp

huge being 100 in half hour?

Close to 400 in a few minutes.

This is to be expected, there will be many waiting in line to buy it up now while cheap.

[EuroTrash]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

lol aaaaaaannnddd it's gone.

Yay! Fuck off you bears! Weeeee!

[surfer43]

huge dump on stamp

huge being 100 in half hour?

Close to 400 in a few minutes.

This is to be expected, there will be many waiting in line to buy it up now while cheap.

I'm in 

[adamstgBit]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

500 is not huge, but it was more like 300 or something.

in the last 15mins 410BTC was traded on stamps.

most of it came in the last 10 mins and it was a flat out DUMP with no shame.

[EuroTrash]

That bottle of champagne wine has been sitting in the fridge for too long, so fuck this I'm gonna open it anyway.

Cheers from some AmeriTrash!

Cheers  

[thefunkybits]

If we have really hit bottom, it WILL be a rocky road up

[surfer43]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

500 is not huge, but it was more like 300 or something.

in the last 15mins 410BTC was traded on stamps.

Yeah but 5 minutes ago close to 600 BTC was traded in the last 15 mins..

[Ivanhoe]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

500 is not huge, but it was more like 300 or something.

in the last 15mins 410BTC was traded on stamps.

most of it came in the last 10 mins and it was a flat out DUMP with no shame.

Yes, but not all was dumped.

edit: Don't edit your posts Adam

[MinermanNC]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

500 is not huge, but it was more like 300 or something.

in the last 15mins 410BTC was traded on stamps.

I think we're in for a bit of a roller-coaster ride lol but with a happy ending

[surfer43]

huge dump on stamp

huge being 100 in half hour?

being 500+ in 5 minutes

500 is not huge, but it was more like 300 or something.

in the last 15mins 410BTC was traded on stamps.

I think were in for a bit of a roller-coaster ride lol but with a happy ending

All this was was one guy exiting, over a few minutes to cause panic..

[cbutters]

someone was really scared of that budding rally from taking off... can only mean they want your coins.

[mmitech]

Guys did you read what Pieter Wuille  Bitcoin dev wrote ?  I have no intention to make any fud but Bitcoin generation maybe not limited to 21 million as sopposed to be, they still dont know how the client will behave when they reach the last Block reward, and they think it will start over from 50 BTC....


https://github.com/bitcoin/bips/blob/master/bip-0042.mediawiki

Although it is widely believed that Satoshi was an inflation-hating goldbug he never said this, and in fact programmed Bitcoin's money supply to grow indefinitely, forever. He modeled the monetary supply as 4 gold mines being discovered per mibillenium (1024 years), with equal intervals between them, each one being depleted over the course of 140 years.

This poses obvious problems, however. Prominent among them is the discussion on what to call 1 billion Bitcoin, which symbol color to use for it, and when wallet clients should switch to it by default.

To combat this, this document proposes a controversial change: making Bitcoin's monetary supply finite.

Details

As is well known, Satoshi was a master programmer whose knowledge of C++ was surpassed only by his knowledge of Japanese culture. The code below:

    int64_t nSubsidy = 50 * COIN;
    // Subsidy is cut in half every 210,000 blocks
    // which will occur approximately every 4 years.
    nSubsidy >>= (nHeight / 210000);
is carefully written to rely on undefined behaviour in the C++ specification - perhaps so it can be hardware accelerated in future.

The block number is divided by 210000 (the "apparent" subsidy halving interval in blocks), and the result is used as input for a binary shift, applied to the original payout (50 BTC), expressed in base units. Thanks to the new-goldmine interval being exactly 64 times the halving interval, and 64 being the size in bits of the currency datatype, the cycle repeats itself every 64 halvings on all currently supported platforms.

Despite the nice showoff of underhanded programming skills - we want Bitcoin to be well-specified. Otherwise, we're clearly in for a bumpy ride

[adamstgBit]

Guys did you read what Pieter Wuille  Bitcoin dev wrote ?  I have no intention to make any fud but Bitcoin generation maybe not limited to 21 million as sopposed to be, they still dont know how the client will behave when they reach the last Block reward, and they think it will start over from 50 BTC....
https://github.com/bitcoin/bips/blob/master/bip-0042.mediawiki

Although it is widely believed that Satoshi was an inflation-hating goldbug he never said this, and in fact programmed Bitcoin's money supply to grow indefinitely, forever. He modeled the monetary supply as 4 gold mines being discovered per mibillenium (1024 years), with equal intervals between them, each one being depleted over the course of 140 years.

This poses obvious problems, however. Prominent among them is the discussion on what to call 1 billion Bitcoin, which symbol color to use for it, and when wallet clients should switch to it by default.

To combat this, this document proposes a controversial change: making Bitcoin's monetary supply finite.

Details

As is well known, Satoshi was a master programmer whose knowledge of C++ was surpassed only by his knowledge of Japanese culture. The code below:

    int64_t nSubsidy = 50 * COIN;
    // Subsidy is cut in half every 210,000 blocks
    // which will occur approximately every 4 years.
    nSubsidy >>= (nHeight / 210000);
is carefully written to rely on undefined behaviour in the C++ specification - perhaps so it can be hardware accelerated in future.

The block number is divided by 210000 (the "apparent" subsidy halving interval in blocks), and the result is used as input for a binary shift, applied to the original payout (50 BTC), expressed in base units. Thanks to the new-goldmine interval being exactly 64 times the halving interval, and 64 being the size in bits of the currency datatype, the cycle repeats itself every 64 halvings on all currently supported platforms.

Despite the nice showoff of underhanded programming skills - we want Bitcoin to be well-specified. Otherwise, we're clearly in for a bumpy ride

ya and the Y2K bug will crash the planet.

[fonzie]

Guys did you read what Pieter Wuille  Bitcoin dev wrote ?  I have no intention to make any fud but Bitcoin generation maybe not limited to 21 million as sopposed to be, they still dont know how the client will behave when they reach the last Block reward, and they think it will start over from 50 BTC....


https://github.com/bitcoin/bips/blob/master/bip-0042.mediawiki

Although it is widely believed that Satoshi was an inflation-hating goldbug he never said this, and in fact programmed Bitcoin's money supply to grow indefinitely, forever. He modeled the monetary supply as 4 gold mines being discovered per mibillenium (1024 years), with equal intervals between them, each one being depleted over the course of 140 years.

This poses obvious problems, however. Prominent among them is the discussion on what to call 1 billion Bitcoin, which symbol color to use for it, and when wallet clients should switch to it by default.

To combat this, this document proposes a controversial change: making Bitcoin's monetary supply finite.

Details

As is well known, Satoshi was a master programmer whose knowledge of C++ was surpassed only by his knowledge of Japanese culture. The code below:

    int64_t nSubsidy = 50 * COIN;
    // Subsidy is cut in half every 210,000 blocks
    // which will occur approximately every 4 years.
    nSubsidy >>= (nHeight / 210000);
is carefully written to rely on undefined behaviour in the C++ specification - perhaps so it can be hardware accelerated in future.

The block number is divided by 210000 (the "apparent" subsidy halving interval in blocks), and the result is used as input for a binary shift, applied to the original payout (50 BTC), expressed in base units. Thanks to the new-goldmine interval being exactly 64 times the halving interval, and 64 being the size in bits of the currency datatype, the cycle repeats itself every 64 halvings on all currently supported platforms.

Despite the nice showoff of underhanded programming skills - we want Bitcoin to be well-specified. Otherwise, we're clearly in for a bumpy ride

MOTHER OF ALL FUD! HOLY SHIT! WE MIGHT SEE 0.0001$

[EuroTrash]

April's fool, 2140 AD.

[windjc]

Bears and bulls being equally obnoxious these last few days.