Author

Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 21078. (Read 26720832 times)

sr. member
Activity: 398
Merit: 250
sr. member
Activity: 252
Merit: 250
The Stamp bid wall is strengthening. Can't say the same for Finex, but unless you use Finex to trade I would recommend watching Stamp. It seems to act more consistently and be a better predictor. Just my opinion.
sr. member
Activity: 434
Merit: 250
Who here has a strong preference for BitcoinBlockstream Edition AKA Bitcoin Core?
sr. member
Activity: 293
Merit: 250
 Sad Sad Sad   well .. so just sell until the price falls. time to buy will    Wink
it's a really bad situation.

I would never say but now I say to everyone - sell everything until it's time!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

If in future  still will  have the Bitcoin price.. will be time to buy.

Banks want technologies blockchain, but not our bitcoin! they make our bitcoin or just use blockchain tech to transfer fiat money..

but chinese ****** can destroy everything... believe me!!
legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
sr. member
Activity: 434
Merit: 250
hero member
Activity: 821
Merit: 1003

Or a half decent solution come out of the core team that addresses the need for bigger blocks but doesn't fork the network, raise the block size so large the spam bloat on the chain will render it humongous  or move us from a team of core devs to two mavericks.

Would absolutely love for the core dev team to get on-board with bigger blocks and I'm sure most other people would too. Now that their bluff has been called, maybe we'll see them implement something.

Have I got my facts straight?

The XT devs want bigger blocks which increase at a humungous rate each year, to log every user's IP for blacklisting purposes, and to disable Tor use for wallets.

The core devs want to implement something called the Lightning Network and sidechains.

Are there any devs left who just want to increase the block size to 8MB and not tamper with anything else?



log everyone's IPs, blacklist and block tor?

thank to let me know, I will never use XT and will always fight it
sr. member
Activity: 476
Merit: 500
legendary
Activity: 2856
Merit: 1520
Bitcoin Legal Tender Countries: 2 of 206

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.


That's true. It could be a BIP 101 block...

I don't really think it's either - the version in that block is "536870919", where the version field in a normal block (up to now) has been 1, 2, or 3.  I don't think any of the current BIP proposals or XT client creates weird versions like that, do they?  I would have expected maybe "4".  I confess that I have not looked at the XT code to see what it puts in the version field, but I would not expect what appears to be a large random number.

I think maybe the version field just got corrupted in that block somehow.


 Try looking at that number in hex, and then referring to the specs.

i cannot find it in the code. currently i'm looking in block.h

anyone able to identifiy it within the code?

EDIT: was blind like a chicken. it is there.

/** Blocks with version fields that have these bits set activate the bigger-block fork */
const unsigned int SIZE_FORK_VERSION = 0x20000007;
hero member
Activity: 546
Merit: 500
Warning: Confrmed Gavinista

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.


That's true. It could be a BIP 101 block...

I don't really think it's either - the version in that block is "536870919", where the version field in a normal block (up to now) has been 1, 2, or 3.  I don't think any of the current BIP proposals or XT client creates weird versions like that, do they?  I would have expected maybe "4".  I confess that I have not looked at the XT code to see what it puts in the version field, but I would not expect what appears to be a large random number.

I think maybe the version field just got corrupted in that block somehow.


 Try looking at that number in hex, and then referring to the specs.
legendary
Activity: 929
Merit: 1000

Or a half decent solution come out of the core team that addresses the need for bigger blocks but doesn't fork the network, raise the block size so large the spam bloat on the chain will render it humongous  or move us from a team of core devs to two mavericks.

Would absolutely love for the core dev team to get on-board with bigger blocks and I'm sure most other people would too. Now that their bluff has been called, maybe we'll see them implement something.

Have I got my facts straight?

The XT devs want bigger blocks which increase at a humungous rate each year, to log every user's IP for blacklisting purposes, and to disable Tor use for wallets.

The core devs want to implement something called the Lightning Network and sidechains.

Are there any devs left who just want to increase the block size to 8MB and not tamper with anything else?

legendary
Activity: 2674
Merit: 2373
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Or a half decent solution come out of the core team that addresses the need for bigger blocks but doesn't fork the network, raise the block size so large the spam bloat on the chain will render it humongous  or move us from a team of core devs to two mavericks.

Would absolutely love for the core dev team to get on-board with bigger blocks and I'm sure most other people would too. Now that their bluff has been called, maybe we'll see them implement something.
hero member
Activity: 910
Merit: 1000

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.



It is an XT block. Sadly. Slush confirmed it, saying they allowing miners to choose and using v3 for core blocks and 536870919 for XT blocks.

Version: 536870919(10) = 0x20000007 (hex)

Edit: Sorry, someone on reddit said that, not Slush. https://www.reddit.com/r/bitcoinxt/comments/3hhbm5/first_mined_xt_block_370434/

source?

Sorry, edited my post. It was just someone on reddit. *Shame on me*
legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
legendary
Activity: 2856
Merit: 1520
Bitcoin Legal Tender Countries: 2 of 206

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.



It is an XT block. Sadly. Slush confirmed it, saying they allowing miners to choose and using v3 for core blocks and 536870919 for XT blocks.

Version: 536870919(10) = 0x20000007 (hex)

source?
legendary
Activity: 2856
Merit: 1520
Bitcoin Legal Tender Countries: 2 of 206
234 on Stamp now. Did we see the bottom a number of hours ago? I think the day opened at 224 so have we found the bottom? I'd really like it if we didn't go any lower than 220. Anybody got an opinion? Could we go any lower than 220?

don't modify the result with the answer to your question dude!

https://en.wikipedia.org/wiki/Schrödinger%27s_cat
hero member
Activity: 910
Merit: 1000

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.



It is an XT block. Sadly. Slush confirmed it, saying they allowing miners to choose and using v3 for core blocks and 536870919 for XT blocks.

Version: 536870919(10) = 0x20000007 (hex)

Edit: Sorry, someone on reddit said that, not Slush. https://www.reddit.com/r/bitcoinxt/comments/3hhbm5/first_mined_xt_block_370434/
legendary
Activity: 3556
Merit: 9709
#1 VIP Crypto Casino
234 on Stamp now. Did we see the bottom a number of hours ago? I think the day opened at 224 so have we found the bottom? I'd really like it if we didn't go any lower than 220. Anybody got an opinion? Could we go any lower than 220?
legendary
Activity: 1066
Merit: 1098

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.


That's true. It could be a BIP 101 block...

I don't really think it's either - the version in that block is "536870919", where the version field in a normal block (up to now) has been 1, 2, or 3.  I don't think any of the current BIP proposals or XT client creates weird versions like that, do they?  I would have expected maybe "4".  I confess that I have not looked at the XT code to see what it puts in the version field, but I would not expect what appears to be a large random number.

I think maybe the version field just got corrupted in that block somehow.

legendary
Activity: 1174
Merit: 1001

I'm not sure that block is really an XT block.  It was mined by Slush pool, which is still creating all version 3 blocks.  That particular block has a bizarre version field for some reason.


That's true. It could be a BIP 101 block...
Jump to: