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

[Crypt0S0ul]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

[1686066252]

1686066252

[1686066252]

1686066252

[xhomerx10]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

Shhh!  We're watching the queen's coffin procession.

[Lucius]

https://www.bloomberg.com/news/articles/2022-09-14/south-korea-seeks-the-arrest-of-terraform-labs-founder-do-kwon

Eat shit!

Machinsky should be the next scum lord to end up behind bars

I will quote this sleazy garbage in the hope that he will get as long a prison sentence as possible. Although I would prefer that he be extradited to the US and that he get a roommate (read Schillinger (OZ)) so that he doesn't get bored in jail. Anyway, I hope someone wipes that smug smile off his face.

Kwon has said he plans to cooperate when the time comes. In an interview with crypto media startup Coinage that floated the prospect of jail time, Kwon said, “Life is long.”   

[MusaPk]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

Shhh!  We're watching the queen's coffin procession.

I don't know why the whole world is crazy for this royal family. They are just a ceremonial royal family as real power in England lies with parliament. But they got special attention whenever someone of them died, marry someone or have a new born.

[ChartBuddy]

Explanation

[JimboToronto]

I don't know why the whole world is crazy for this royal family. They are just a ceremonial royal family as real power in England lies with parliament. But they got special attention whenever someone of them died, marry someone or have a new born.

It's no different than Kim Kardashian, Amber Heard, or other celebrities.

They produce little and receive lots of attention.

File it under "entertainment".

[MusaPk]

I don't think market ever gave that much indication of bitcoin bottom price.

Current price to me is an ideal price for accumulating bitcoin as price is not going down below that. From here it will be an upward journey for sure.

Edit: just ignore the altcoins in the tweet.

[LFC_Bitcoin]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

Bear market vibes, bruh!

[Gachapin]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

Bear market vibes, bruh!

*tumbleweed*

[Gachapin]

take your fucking shitcoin scams somewhere else

[blue_hurricanger]

All this Ethereum merge shite sounds complicated and a load of bollocks. Just like a typical shitcoin would do. Just head into the direction where the wind is blowing.
No consistency, no reliable fundamentals.

Just pure shit.

The shitiest of shit.

Ultra Shit.

Shit in pure overdrive.

Yeah, it's complicated but good complicated. Not the kind of buzzwords that may sound complicated to impress you like a typical shitcoin try to flying novadays. Hate to repost but below is a chart of what is going on in the ETH development. A bit outdated since ETH PoS is going to Merge soon (ETA ~12 more hours).



And please don't hate on my boi Vitalik. Dude is like coder on steroids (or drug lol). Here, an interesting piece from Vitalik site talks about sharding and how to improve it against 51% attack. Warning, a long read. I tried to snip a few paragraphs to encourage anyone to read out the link below.
https://vitalik.ca/general/2021/04/07/sharding.html

Sharding through Random Sampling
The easiest version of sharding to understand is sharding through random sampling. Sharding through random sampling has weaker trust properties than the forms of sharding that we are building towards in the Ethereum ecosystem, but it uses simpler technology.

The core idea is as follows. Suppose that you have a proof of stake chain with a large number (eg. 10000) validators, and you have a large number (eg. 100) blocks that need to be verified. No single computer is powerful enough to validate all of these blocks before the next set of blocks comes in.

Hence, what we do is we randomly split up the work of doing the verification. We randomly shuffle the validator list, and we assign the first 100 validators in the shuffled list to verify the first block, the second 100 validators in the shuffled list to verify the second block, etc. A randomly selected group of validators that gets assigned to verify a block (or perform some other task) is called a committee.



When a validator verifies a block, they publish a signature attesting to the fact that they did so. Everyone else, instead of verifying 100 entire blocks, now only verifies 10000 signatures - a much smaller amount of work, especially with BLS signature aggregation. Instead of every block being broadcasted through the same P2P network, each block is broadcasted on a different sub-network, and nodes need only join the subnets corresponding to the blocks that they are responsible for (or are interested in for other reasons).

Consider what happens if each node's computing power increases by 2x. Because each node can now safely validate 2x more signatures, you could cut the minimum staking deposit size to support 2x more validators, and so hence you can make 200 committees instead of 100. Hence, you can verify 200 blocks per slot instead of 100. Furthermore, each individual block could be 2x bigger. Hence, you have 2x more blocks of 2x the size, or 4x more chain capacity altogether.

...

Recap: how are we ensuring everything is correct again?
Suppose that you have 100 blocks and you want to efficiently verify correctness for all of them without relying on committees. We need to do the following:

+Each client performs data availability sampling on each block, verifying that the data in each block is available, while downloading only a few kilobytes per block even if the block as a whole is a megabyte or larger in size. A client only accepts a block when all data of their availability challenges have been correctly responded to.

+Now that we have verified data availability, it becomes easier to verify correctness. There are two techniques:
 _We can use fraud proofs: a few participants with staked deposits can sign off on each block's correctness. Other nodes, called challengers (or fishermen) randomly check and attempt to fully process blocks. Because we already checked data availability, it will always be possible to download the data and fully process any particular block. If they find an invalid block, they post a challenge that everyone verifies. If the block turns out to be bad, then that block and all future blocks that depend on that need to be re-computed.
 _We can use ZK-SNARKs. Each block would come with a ZK-SNARK proving correctness.

+In either of the above cases, each client only needs to do a small amount of verification work per block, no matter how big the block is. In the case of fraud proofs, occasionally blocks will need to be fully verified on-chain, but this should be extremely rare because triggering even one challenge is very expensive.

And that's all there is to it! In the case of Ethereum sharding, the near-term plan is to make sharded blocks data-only; that is, the shards are purely a "data availability engine", and it's the job of layer-2 rollups to use that secure data space, plus either fraud proofs or ZK-SNARKs, to implement high-throughput secure transaction processing capabilities. However, it's completely possible to create such a built-in system to add "native" high-throughput execution.

[ChartBuddy]

Explanation

[cygan]

[jojo69]

[Gachapin]

meth crap

you too can fuck off with your shitcoin shilling

[BitcoinBunny]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

Shhh!  We're watching the queen's coffin procession.

I don't know why the whole world is crazy for this royal family. They are just a ceremonial royal family as real power in England lies with parliament. But they got special attention whenever someone of them died, marry someone or have a new born.

Countless reasons. From tradition, to unity, to the queen's long life, to the fact the UK hasn't been invaded for a thousand years by some little dictator twat, to the fact slavery was abolished without a stupid dumb civil war costing the lives of hundreds of thousands and the fact you are writing your words in English rather than in German or in Russian.
Indeed, I accept much of the more recent reasons are mixed with political will / reasons but the monarchy still represents most of the positive aspects as a symbol that interestingly points to consistency but also positive change at the same time.

You can ignore it if you don't care or whine like a little bitch over it like some do.

[vapourminer]

[...] And please don't hate on my boi Vitalik. [...]

ummm you do know what thread you are in, right?

we care not what happens in eth land.

if its not Bitcoin, sod off please

[BitcoinBunny]

All this Ethereum merge shite sounds complicated and a load of bollocks. Just like a typical shitcoin would do. Just head into the direction where the wind is blowing.
No consistency, no reliable fundamentals.

Just pure shit.

The shitiest of shit.

Ultra Shit.

Shit in pure overdrive.

Yeah, it's complicated but good complicated. Not the kind of buzzwords that may sound complicated to impress you like a typical shitcoin try to flying novadays. Hate to repost but below is a chart of what is going on in the ETH development. A bit outdated since ETH PoS is going to Merge soon (ETA ~12 more hours).



And please don't hate on my boi Vitalik. Dude is like coder on steroids (or drug lol). Here, an interesting piece from Vitalik site talks about sharding and how to improve it against 51% attack. Warning, a long read. I tried to snip a few paragraphs to encourage anyone to read out the link below.
https://vitalik.ca/general/2021/04/07/sharding.html

Sharding through Random Sampling
The easiest version of sharding to understand is sharding through random sampling. Sharding through random sampling has weaker trust properties than the forms of sharding that we are building towards in the Ethereum ecosystem, but it uses simpler technology.

The core idea is as follows. Suppose that you have a proof of stake chain with a large number (eg. 10000) validators, and you have a large number (eg. 100) blocks that need to be verified. No single computer is powerful enough to validate all of these blocks before the next set of blocks comes in.

Hence, what we do is we randomly split up the work of doing the verification. We randomly shuffle the validator list, and we assign the first 100 validators in the shuffled list to verify the first block, the second 100 validators in the shuffled list to verify the second block, etc. A randomly selected group of validators that gets assigned to verify a block (or perform some other task) is called a committee.



When a validator verifies a block, they publish a signature attesting to the fact that they did so. Everyone else, instead of verifying 100 entire blocks, now only verifies 10000 signatures - a much smaller amount of work, especially with BLS signature aggregation. Instead of every block being broadcasted through the same P2P network, each block is broadcasted on a different sub-network, and nodes need only join the subnets corresponding to the blocks that they are responsible for (or are interested in for other reasons).

Consider what happens if each node's computing power increases by 2x. Because each node can now safely validate 2x more signatures, you could cut the minimum staking deposit size to support 2x more validators, and so hence you can make 200 committees instead of 100. Hence, you can verify 200 blocks per slot instead of 100. Furthermore, each individual block could be 2x bigger. Hence, you have 2x more blocks of 2x the size, or 4x more chain capacity altogether.

...

Recap: how are we ensuring everything is correct again?
Suppose that you have 100 blocks and you want to efficiently verify correctness for all of them without relying on committees. We need to do the following:

+Each client performs data availability sampling on each block, verifying that the data in each block is available, while downloading only a few kilobytes per block even if the block as a whole is a megabyte or larger in size. A client only accepts a block when all data of their availability challenges have been correctly responded to.

+Now that we have verified data availability, it becomes easier to verify correctness. There are two techniques:
 _We can use fraud proofs: a few participants with staked deposits can sign off on each block's correctness. Other nodes, called challengers (or fishermen) randomly check and attempt to fully process blocks. Because we already checked data availability, it will always be possible to download the data and fully process any particular block. If they find an invalid block, they post a challenge that everyone verifies. If the block turns out to be bad, then that block and all future blocks that depend on that need to be re-computed.
 _We can use ZK-SNARKs. Each block would come with a ZK-SNARK proving correctness.

+In either of the above cases, each client only needs to do a small amount of verification work per block, no matter how big the block is. In the case of fraud proofs, occasionally blocks will need to be fully verified on-chain, but this should be extremely rare because triggering even one challenge is very expensive.

And that's all there is to it! In the case of Ethereum sharding, the near-term plan is to make sharded blocks data-only; that is, the shards are purely a "data availability engine", and it's the job of layer-2 rollups to use that secure data space, plus either fraud proofs or ZK-SNARKs, to implement high-throughput secure transaction processing capabilities. However, it's completely possible to create such a built-in system to add "native" high-throughput execution.

You proved my point exactly.

A complex problem introduced that then needs a complex solution to benefit absolutely no one on Earth.

Top job.

That is not the definition of a good programmer regardless. It is the definition of an arrogant twat who happens to be able to program.

I've worked with many programmers in the past who think they can create frameworks on their own. Only for their code to be tossed out in the end because something better comes along that is easier to use OR they should have just used a commonly accepted standard rather than building their own temporary piece of crap.
Vitalik sounds like a king amongst those types of people.

Shitcoins will continue to eat each other whilst BTC does its own thing.

The perfect network where arrogancy was avoided by its creator leaving the building in time.

[MusaPk]

Ahh. Chartbuddy made 6 Posts on this page out of 8 Posts (excluding this). When was the last time you see the WO that quiet?

Shhh!  We're watching the queen's coffin procession.

I don't know why the whole world is crazy for this royal family. They are just a ceremonial royal family as real power in England lies with parliament. But they got special attention whenever someone of them died, marry someone or have a new born.

Countless reasons. From tradition, to unity, to the queen's long life, to the fact the UK hasn't been invaded for a thousand years by some little dictator twat, to the fact slavery was abolished without a stupid dumb civil war costing the lives of hundreds of thousands and the fact you are writing your words in English rather than in German or in Russian.
Indeed, I accept much of the more recent reasons are mixed with political will / reasons but the monarchy still represents most of the positive aspects as a symbol that interestingly points to consistency but also positive change at the same time.

You can ignore it if you don't care or whine like a little bitch over it like some do.

You missed few key things also. They are the reason why countries are fighting. Kashmir, Cyprus, Palestine. Thanks to Queen.

[ChartBuddy]

Explanation