"If Bitcoin hasn't profoundly shocked you, you haven't understood it yet" - Niels Bohr, 1957

I'm not totally sure if this quote is accurated. It seems right!

submitted by /u/el_timinou
[link] [comments]

Free Telegram channel for futures and spot signals with 93% success rate pm me for link (going premium soon so join before it’s too late)

submitted by /u/Sleiman91011 [link] [comments]

source https://www.reddit.com/r/btc/comments/r8ylqt/free_telegram_channel_for_futures_and_spot/

🥳 Black Friday Blowout Sale, entire market 20% off 🥳

submitted by /u/dystopianmonke [link] [comments]

Renowned Poker Star Doug Polk Becomes Coinflex’s First Global Brand Ambassador – Press release Bitcoin News

submitted by /u/i_have_chosen_a_name [link] [comments]

source https://www.reddit.com/r/btc/comments/r8wj7l/renowned_poker_star_doug_polk_becomes_coinflexs/

A meme for my fellow Bitcoin Cashers

submitted by /u/Remora_101 [link] [comments]

source https://www.reddit.com/r/btc/comments/r8xehd/a_meme_for_my_fellow_bitcoin_cashers/

Partial indexing on pruned node?

When you run a full node, you can index the data by address or transaction for fast queries. Such indexed nodes are used by applications like wallets, which need to be able to retrieve arbitrary tx data quickly.

Some nodes have indexing built in (BCHD, Bitcoin Verde), while others expect a separate indexer service to run alongside the node (BCHn, Flowee). To my knowledge, all of them expect to index the entire blockchain and do not work at all with pruned nodes.

This is a problem because the indexes consume a lot of risk space, even more than the blockchain itself (~400GB last time I checked and probably more by now). That means the cost of a cloud server that can host the index is a little high.

What I'm wondering is, would it be possible to run a pruned node and maintain only a partial index? For example, just index the data for the current UTXO set and the last N blocks (say 1 week or 1 month of blocks). Then just discard index data for spent transactions further in the past.

This would give you all the data you need for a wallet backend that allows you to view, send and receive your available funds. You just wouldn't be able to retrieve older transaction history for already-spent funds. It would also give you a buffer of N blocks of historic transactions which you could query if you needed to (e.g. to check whether a disputed payment was sent by a customer).

This seems like it would make it much cheaper and more accessible to run a node that can be an application backend, even when blocks get up to 256MB or larger.

My question: is there any technical reason that this cannot be done?

submitted by /u/fatalglory
[link] [comments]

source https://www.reddit.com/r/btc/comments/r8xnhs/partial_indexing_on_pruned_node/

Panic? I'm already down around 30k in less than a week.

DISCLAIMER: This is a throwaway and I don't check DMs or pay attention to anything on this account. Don't try to scam me, it won't work.

Here's a reason you shouldn't panic.

Prior to this week, my wealth allocation was around 40% crypto (mostly BTC) and 60% stock market. Then, on November 29th and November 30th, I wanted to rebalance my allocations to 75% (mostly BTC) and 25% stocks, so this is very close to "going all-in" at around 60k per BTC. I moved a total of $70k USD from stocks to crypto between those two days. Fast forward to today, my crypto holdings are down 28k USD.

How does it feel? Fine. I haven't sold, and therefore I haven't lost. Will I sell? Not a chance, even if BTC drops to 8k per coin.

How do I recover? By DCA'ing. Each time I will deposit more fiat into crypto, I will be lowering my average cost per share. Then when Bitcoin inevitably reaches a new ATH, my gains will be even higher than if ATH happened today.

Moral of the story? There's no reason to panic unless you sell.

submitted by /u/ThrowMeABone38
[link] [comments]