Bitcoin Forum
May 25, 2024, 06:52:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 [76] 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 ... 161 »
1501  Bitcoin / Bitcoin Discussion / Re: Is it possible to restart the blockchain? on: February 12, 2019, 09:17:49 AM
I get what you're saying with checkpoints from a practical view. The problem is, once you give developers that control, it's like Pandora's Box. It might begin an endless political controversy. How much proof of work is enough before Bitcoin is ultimately decided by human consensus? Maybe not two days worth of blocks, but how about a month or a year -- is that enough? Does this open up new selfish mining attack vectors where the attacker would release their chain reorg directly before a checkpoint is hard coded?

I guess this can be easily controlled

I don't know which specific approach should be used but as I understand the probabilities can be easily calculated. So there likely shouldn't be a lot of human arbitrariness in deciding how much of the blockchain should remain before we prune it.

What is that based on? What are the probabilities?

In other words, if leaving 1 year of transactions is enough to make such an attack nearly impossible, it seems like a good trade-off, especially if we consider the exponential growth of the blockchain in the future. Indeed, it may not come at all, but what are we all doing here then?

I think the burden is on you to show why it's so important to free up that storage space. It's not a major problem for scaling. Why is it a good trade-off? What will we gain?

Further, there seems to be a misunderstanding. The checkpoint which I speak about should only refer to old transactions (say, older than a year), while you seem to mean that it should lock all transactions immediately prior to the checkpoint. This is not how I imagine that

A checkpoint makes all transactions prior to the checkpoint irreversible. If that's not what you mean, maybe you should clarify.
1502  Bitcoin / Bitcoin Discussion / Re: Is it possible to restart the blockchain? on: February 11, 2019, 11:01:10 PM
That goes against the entire philosophy of proof of work, though.

The point of proof of work is that it is cumulative -- there is a chain of work proven back to the genesis block. If one block is invalid, every block mined on top of it is invalid. This is a basic mechanism to prevent dishonest mining.

What you're suggesting are called "checkpoints", and then pruning the blockchain below the last checkpoint. The early versions of Bitcoin actually included checkpoints to ensure reliability of confirmations. The use of checkpoints has been phased out -- there hasn't been one coded into the protocol since 2014. This is because of what I mentioned earlier: Checkpoints give developers power over Bitcoin's security model because developers can make blocks irreversible when they otherwise would have been reorganized by miners

I understand what you say

And in fact, I'm not arguing with that. But you don't want to understand me. Basically, you are taking a position of a Bitcoin maximalist (extremist) even if Bitcoin itself is a bunch of trade-offs (not even mentioning earlier used checkpoints). I'm not saying that we should set checkpoints every other day but pruning the blockchain after 1 year of transactions (or running a ghost version for those who need it) may be a trade-off that we should have if the size of the blockchain is set to expand dramatically in the coming years.

I think pruning is great. Anyone who doesn't have the storage space for the entire blockchain should do it. However, since storage space is not a critical bottleneck in Bitcoin scaling and isn't a major threat to node decentralization, I think it would be a net loss to implement it at the consensus level. The tradeoff isn't worth it.

I get what you're saying with checkpoints from a practical view. The problem is, once you give developers that control, it's like Pandora's Box. It might begin an endless political controversy. How much proof of work is enough before Bitcoin is ultimately decided by human consensus? Maybe not two days worth of blocks, but how about a month or a year -- is that enough? Does this open up new selfish mining attack vectors where the attacker would release their chain reorg directly before a checkpoint is hard coded?
1503  Bitcoin / Press / Re: [2019-02-04] Ex Bitcoin Foundation chair claims billions ahead of Mt.Gox victims on: February 11, 2019, 10:46:11 PM
OK so I'm perusing stories for my next news roundup article...

Can someone explain to me what the appeal of a GOX reboot is? Its like re-invigorating a movie franchise that everyone hated. The Mighty Ducks Part III.

Is it pretty much just to satisfy duped customers? Not sure a GOXCoin is gonna cut it.

https://cointelegraph.com/news/goxrising-movement-aims-to-reboot-mt-gox-exchange-make-gox-coin-for-creditors

I think it's a niche of duped customers who hopes to recover their BTC through a token pump. Maybe it's inspired by Binance's BNB. I think this is the general idea: Leverage the brand (people at least have heard of it) and customer database, pay for a state-of-the-art trading back end since the bankruptcy trust has much more assets than liabilities, and pay victims with a pro rata share of a dividend-paying ICO token that could be traded on other exchanges.

As I was saying, the people promoting it are probably just hoping to sell into a GOXCoin pump and walk away. It's less about launching a working exchange and recovering real money for victims. What are the chances of that happening?
1504  Bitcoin / Press / Re: [2019-2-11] Generational change – the most powerful Bitcoin price catalyst on: February 11, 2019, 10:35:49 PM
Can't give up on the young 'uns completely now. There's enough data, at least in the connected worlds where developed millennials are continuously plugged in, to show that their trust in the banking institutions (or any institution of authority for that matter) have never been this low. Some can even substantiate that distrust. At the same time, trust in technology is at an all-time high. Might not be their generation getting at the bit to get to Bitcoin, but their children maybe?

I definitely think so. There's a perfect storm brewing. It's tough to say when full-fledged adoption will happen, but if trust in banks and governments continues to decline while people increasingly embrace technology, I don't see any way around it.
1505  Bitcoin / Bitcoin Discussion / Re: Is it possible to restart the blockchain? on: February 11, 2019, 08:04:18 PM
If you "restart" the blockchain by taking a "snapshot" at a set time, you lose all the history leading up to that snapshot, meaning you cannot verify it. You therefore have to trust that the snapshot you are downloading is accurate. If you are running a full node, you can verify the entire history of bitcoin yourself and then prune it locally as much as you want. Does a forced global pruning not mean you have to trust a third party to send you an accurate snapshot?

But do you need to actually verify all the past blocks?

As I see it, that simply doesn't make any sense and that's likely the reason why no one is doing this in practice (honestly, I don't know, so bear with me). In this way, there is no real need in blocks older than a certain age (say, 1 month) as far as supporting the network is concerned.

That goes against the entire philosophy of proof of work, though.

The point of proof of work is that it is cumulative -- there is a chain of work proven back to the genesis block. If one block is invalid, every block mined on top of it is invalid. This is a basic mechanism to prevent dishonest mining.

What you're suggesting are called "checkpoints", and then pruning the blockchain below the last checkpoint. The early versions of Bitcoin actually included checkpoints to ensure reliability of confirmations. The use of checkpoints has been phased out -- there hasn't been one coded into the protocol since 2014. This is because of what I mentioned earlier: Checkpoints give developers power over Bitcoin's security model because developers can make blocks irreversible when they otherwise would have been reorganized by miners.
1506  Bitcoin / Press / Re: [2019-02-02]Amazon Might Have to Issue a Cryptocurrency Soon on: February 11, 2019, 07:28:32 PM
It's marketing. People here seem to be so tied to their this or that doesn't work way of thinking.

Bitcoin as an additional payment option doesn't cost anything if it isn't being used, but will very likely result in a wave of customers they otherwise wouldn't have.

Implementing Bitcoin support absolutely has costs.

They need to dedicate developer and server resources on an ongoing basis. They need to develop and maintain a robust wallet and custody solution, as well as a robust solution for currency conversion. They also need to account for custody risks. Or if they hire a processor like Bitpay, that's a 1% cost right there, which is only a tiny bit better than Visa. I also assume processors like Visa give giants like Amazon favorable fee arrangements as well, so Bitpay may in fact be worse.

I also strongly disagree that it'll "very likely result in a wave of customers they otherwise wouldn't have." What businesses implemented Bitcoin support and then saw massive growth? I remember several cases where businesses added Bitcoin then later dropped it because there was no interest. Adding Bitcoin as a payment option has never driven consumers to Bitcoin.

Besides, Amazon doesn't need to achieve growth that way. They are basically taking over the world by expanding their core logistics model and consolidating neighboring industries. As long as they offer all the major payment options consumers want, this is an afterthought to them at best.

BitPay alone did +$1 billion in conversions last year, where it's safe to say that the far majority of this is related to Bitcoin.

Give people the merchants they frequently shop at, and this $1 billion will become +$2 billion, and more as time goes by.

I'm pretty sure that Bitcoin holders intent on buying stuff on Amazon already buy gift cards with bitcoins -- Bitrefill, Bitpay, other gift card malls. If they use it directly on Amazon instead (or on Amazon through Bitpay), I just don't see it making a big difference.
1507  Bitcoin / Bitcoin Discussion / Re: How does block size harm decentralization? on: February 11, 2019, 07:10:31 PM
squatter what you are quoting about what miners removed was not the fee priority formulae. but a dedicated 10% of blockspace for zero fee users that 'aged out' of the fee formulae.. in essense if you havnt spent your funds for x confirms then your transaction doesnt need to pay fee's because it wont be calculatable by the fee formulae. plus it makes pools not get anything.
what miners did had nothing to do with the formulae itself.

The formula itself was never part of the protocol. That's why miners stopped supporting it once they realized they could increase their revenues with fees.

Core only removed priority from its fee and confirmation estimations because it was making those estimates inaccurate, as miners had completely stopped supporting it.

What miners did had everything to do with the formula: Miners are the ones who made sure transaction priority ceased to exist. For that, you can thank miners for being rational. It had absolutely nothing to do with Core.

pools cant change bitcoin rules. only devs can when devs make node upgrade options. so it was the devs that removed the fee formulae

You're confused about what "Bitcoin rules" are. Transaction priority was never a consensus rule. It was a client side rule. Not required by the protocol. That's why there was no fork when miners (and later Core) removed it from their clients.
1508  Bitcoin / Bitcoin Discussion / Re: How many BTC is in circulation? on: February 11, 2019, 06:58:15 PM
What was their criteria beyond the coins not having moved? Beyond burner addresses and publicly known events like that Polish exchange that deleted its private keys that's all they have to go own in most cases. I've got coins that haven't moved for over five years. They certainly ain't lost.

have you ever moved the bcash or other forks associated with your keys? apparently they mined a lot of data from that

That's interesting. I'm not sure why that never dawned on me. When Bitcoin Cash forked, people started sweeping keys to recover and sell the coins. Unless those sweeps were done extremely carefully, the hard forks probably handed Chainalysis an incredible amount of address clusters and transaction history on a silver platter!

On top of risking malware, people take big privacy risks to recover hard forked coins.
1509  Bitcoin / Bitcoin Discussion / Re: How many BTC is in circulation? on: February 10, 2019, 10:50:36 PM
I remember Jameson Lopp (of statoshi.info) said he did a study on this and came to similar numbers as Chainalysis.

I don't buy these figures of 20-25% of the supply being lost.

It's worth noting that Chainalysis put the estimate at 2.78 million - 3.79 million. "Nearly 4 million" is what made the headlines. They also included the early "Satoshi" coins in those numbers, which they estimate = about 1 million bitcoins.

If we take the low end and table the Satoshi discussion, that's around 10%.
1510  Other / Beginners & Help / Re: My experience with running a lightning network channel on: February 10, 2019, 10:28:54 PM
So imagine I have 10 BTC. And I want to promote and expand the LN network. So I open 10 different channels with 1 BTC each with 10 different people. I don't actually use any of these channels.  I just leave them there to allow others to use them within the network. So that way, these other 10 people can spur payments at each other via my node.

So the Bitcoin wallet backs up my channels on the cloud for when I go offline. And so I go offline and I store my Bitcoin in cold storage. No sweat, the channels are all backed up in the cloud, right?

Is my coin still as safe as if it were all in cold storage? Or is there a risk of loosing it to the cloud?

To keep your channels open, you'd want to remain online, or at least come online periodically to make sure no one tries to steal your coins by broadcasting an old channel state. Otherwise you'd want to hire a watchtower service to handle this for you. You can't really "back up" your channels and go offline.

With Lightning, your private keys are always online. It's always safer to keep your coins in cold storage. I would only use a limited amount in payment channels, an amount I were willing to lose -- same as an online desktop or mobile wallet.
1511  Bitcoin / Bitcoin Discussion / Re: How does block size harm decentralization? on: February 10, 2019, 08:49:35 AM
If you keep giving users more block space for free, they'll keep taking it, regardless of the long term costs. Raising the ceiling higher and higher means there is no mechanism to enforce fees. How's that going to work a few halvings down the road when block rewards are amounting to little more than 1.5 BTC? "Free transactions for all" sounds like a nice socialist paradise, but miners aren't in this for charity.

Every one of us has incentive to avoid paying fees. So, why do people like me still oppose bigger blocks and prefer the settlement layer approach? Because I also hold bitcoins, and I know that the block size limit is integral to guaranteeing the security of Bitcoin and thus the value of my coins.

ever thought of actually having a fee mechanism
a fee priority formulae like what was available for several years before core moved it.

Fee priority didn't solve this problem. It was actually just a way for users to pay less fees!

It was miners who took it upon themselves to remove transaction priority because it was node policy, not part of the protocol. Transaction priority was losing them revenue so they stopped enforcing it. It made no sense to keep using priority in Core's fee calculations if no miners were actually using it. There's some good discussion of the issue here, including this bit:

Quote
After blocks started getting full, many miners, out of the interest of getting as much income as possible, chose to stop reserving this space for priority. There is more money to be made by choosing a few hundred transactions that paid more fees than it was to choose a few hundred transactions that didn't but had priority. Since no one miner was actually using priority, Bitcoin Core removed priority from its fee and confirmation estimations so that the given values would be more realistic and the code would be simpler.

The following pull requests and the issues linked within them contain some of the discussions that the Core devs had when removing priority: https://github.com/bitcoin/bitcoin/pull/9602, https://github.com/bitcoin/bitcoin/pull/7022, https://github.com/bitcoin/bitcoin/pull/7008.
1512  Bitcoin / Press / Re: [2019-02-02]Amazon Might Have to Issue a Cryptocurrency Soon on: February 10, 2019, 08:37:20 AM
I think chargebacks alone should be a big bonus for many people and the increased security should also benefit a lot of people. eCommerce payment systems like credit cards and PayPal are not even close to be the ideal solution for these kinds of applications, because it is by nature ineffective by being centralized technologies.

Why we are still using these ancient technologies are beyond me, Bitcoin is much better and also widely acceptedCool

That's just the thing. Bitcoin isn't widely accepted. This is still the early adopter phase.

Amazon would love to accept BTC if customers really wanted it -- it's a merchant's dream. I assume they don't bother because there isn't actually strong demand for it, and if there were, there may not be enough market liquidity to liquidate their coins without losses. It's just an unnecessary risk for them.
1513  Bitcoin / Bitcoin Discussion / Re: How does block size harm decentralization? on: February 10, 2019, 08:20:31 AM
causing a transaction backlog and fee pressure NOW kills off the desire and utility of bitcoin.

How do you know? Any evidence or just more empty conjecture?

evidence... hmmm
how about people frustrated with bitcoin to such a point they are actively promoting LN....
how they are frustrated with waiting for bitcoin innovation that they are willing to losen their morals and principles and understanding of bitcoin to actively want to have a different network where funds are locked into counterparty management(banking).

every person that WANTS LN are people secretly pee'd off with bitcoin fee's and limited transaction ability... if they were not peed off, and happy with bitcoin. they would not be so hard nose about promoting LN as LN would not be something they would want/need

That's obvious, though. Wouldn't you rather get something for free rather than paying the actual cost? Neither Bitcoin nor Lightning are perfect, but it's the closest we can get to having our cake and eating it too.

If you keep giving users more block space for free, they'll keep taking it, regardless of the long term costs. Raising the ceiling higher and higher means there is no mechanism to enforce fees. How's that going to work a few halvings down the road when block rewards are amounting to little more than 1.5 BTC? "Free transactions for all" sounds like a nice socialist paradise, but miners aren't in this for charity.

Every one of us has incentive to avoid paying fees. So, why do people like me still oppose bigger blocks and prefer the settlement layer approach? Because I also hold bitcoins, and I know that the block size limit is integral to guaranteeing the security of Bitcoin and thus the value of my coins.
1514  Bitcoin / Bitcoin Discussion / Re: Is it possible to restart the blockchain? on: February 10, 2019, 05:33:49 AM
Let's assume at some point in the future the blockchain is 300 GB, a crude (but fine for this quick example) technique would be to split it into 3 parts; each containing 100GB. If you don't want to store the first 200 GB since it's irrelevant to you (but you'd still like to verify transactions yourself) you could just store some type of Merkle hash of all the blocks of the first 100GB and another for the second 100GB.

If one day you decide you want to validate everything since the genesis block you could ask your peers for the blockchains you don't have (the first 200GB) by providing your hashes. To confirm that it's the real deal, you would need to hash each chain you get to see if it matches your hash of that chain.

Sounds like sharding, which is planned for Ethereum in the future. Sharding doesn't seem compatible with proof-of-work because the vast majority of nodes won't ever fully validate the blockchain, only the shard to which they belong to. An SPV proof would be possible, and that would provide a decent level of security. Downloading the whole blockchain and then pruning it defeats the purpose, though, so most people would never do it.

if all nodes stored part of the full chain, it's possible that sections of the chain could be lost forever

That seems to be the biggest risk -- like a torrent with no seeders and only leechers.
1515  Economy / Exchanges / Re: QuadrigaCX: $190 million locked after founder died in December 2018 on: February 10, 2019, 01:45:59 AM
The fact that Reddit users have exposed wallet addresses that belong to QuadrigaCX have been used AFTER news of the death of its founder and CEO Gerald Cotten means that people have a right to be suspicious.

That does not necessarily mean that Gerald Cotten is alive, it could be a simple as him sadly succumbing to his illness and passing away in India while he was trying to open an orphanage and others have access to wallets belonging to QuadrigaCX.

The bankruptcy filing states that Cotten is the only one with access to the cold storage wallets. Presumably, there are other wallets the company can still access. They may be consolidating those funds as we speak. The Reddit sleuthing -- while convincing on a preliminary read -- doesn't seem to conclusively identify any cold storage wallets.

A body being formally identified along with an autopsy carried out in his native Canada would ideally help solve the problem.

I think bringing him home alive would be much more effective at solving the problem. Cheesy
1516  Bitcoin / Bitcoin Discussion / Re: Is it possible to restart the blockchain? on: February 10, 2019, 01:33:34 AM
Not quite. Light clients in Ethereum are not capable of fully validating a block by themselves. It's the SPV model -- looking up a transaction and validating headers but not validating entire blocks. What the OP is talking about sounds more like fully validating nodes that prune their blockchain to save storage space

Yes, I'm talking about full nodes

That is, the nodes which actually support the network and which (if my understanding is correct) have to keep the whole blockchain in their local storage. Thus pruning the blockchain will make the life easier for them as they won't have to keep all this information that they may never need.

There's a distinction that the Bitcoin Wiki makes between "full node" and "archival node" which I think is pretty useful:

Quote
What makes a full node?
Full nodes download every block and transaction and check them against Bitcoin's consensus rules.

Quote
Archival Nodes
A subset of full nodes also accept incoming connections and upload old blocks to other peers on the network. This happens if the software is run with -listen=1 as is default. Contrary to some popular misconceptions, being an archival node is not necessary to being a full node.

Archival nodes help the network by bootstrapping full nodes who need to download and validate the entire blockchain. You can prune the chain and even turn listening off and still be a full node -- it just means fully validating.
1517  Other / Beginners & Help / Re: My experience with running a lightning network channel on: February 09, 2019, 11:23:47 PM
I don't get it. So I have a few questions before I open an LN channel.

If I open a channel and I commit 1 BTC to it, does that mean the maximum amount I can send are receive is 1 BTC? Or does that mean I can send and receive several 1 BTC (or less) payments?

Lightning uses bidirectional channels -- there are two parties per channel. The capacity limit for each channel is the sum total committed by both parties. If two people commit 0.5 BTC to a channel, the total capacity of the channel is 1 BTC -- that's the total that can be settled when the channel is closed. Neither of you can settle the channel with more BTC than the two of you put in. Any more than that and you'd be creating bitcoins out of thin air. The Bitcoin protocol doesn't like that. Tongue
1518  Bitcoin / Bitcoin Discussion / Re: Is it possible to restart the blockchain? on: February 09, 2019, 10:42:53 PM
That would basically be erasing the blockchain and simply starting from the UTXOs. This is what lite wallets on ETH actually do.

Not quite. Light clients in Ethereum are not capable of fully validating a block by themselves. It's the SPV model -- looking up a transaction and validating headers but not validating entire blocks. What the OP is talking about sounds more like fully validating nodes that prune their blockchain to save storage space.
1519  Bitcoin / Bitcoin Discussion / Re: How does block size harm decentralization? on: February 09, 2019, 06:53:37 PM
causing a transaction backlog and fee pressure NOW kills off the desire and utility of bitcoin.

How do you know? Any evidence or just more empty conjecture?

Both transaction fees and price steadily rose from 2015 until the end of the run in December, 2017. Users were obviously willing to pay higher and higher fees. When Bitcoin has even more utility because of increasing adoption, a robust LN, sidechains, smart contract ecosystem, etc. I think that would justify higher fees yet.

Larger blocks cause propagation delays. This increases orphaning rates, which disproportionately hurts smaller miners

propagation is currently SECONDS.. so SCALING block sizes to atleast get passed the implied 600k transactions a day limit is not going to cause issues.

That's the best case scenario, and it's with a base block size of 1MB. Witness data is not a problem for the quadratic sighashing problem, but increasing the base block size is. Some contrast to your "data":

Quote
In essence, doubling the size of a transaction can double both the number of signature operations, and the amount of data that has to be hashed for each of those signatures to be verified. This has been seen in the wild, where an individual block required 25 seconds to validate, and maliciously designed transactions could take over 3 minutes.
1520  Bitcoin / Legal / Re: SEC tendering for blockchain analysis companies on: February 09, 2019, 06:10:23 PM
An example of how an attacker/troll could incriminate someone is sending money to one of the 2 banned addresses by the US government (which have a fine of up to $250,000 per transaction) and within the same transaction send money to one of your addresses. De facto you've now have received money by a criminal. You now send this money into an exchange linked to your name and the rest is history.

If someone sent coins to both you and the designated addresses, you weren't transacting with the sanctioned individuals and your coins didn't come from them. If you receive coins from the designated addresses, you're obligated to freeze the funds and contact the Treasury Department within 10 days. That's all.

If you've looked into how unlikely address collisions in Bitcoin are, then you know this scenario is ridiculously unlikely. No terrorists are going to troll you by sending real money to your wallet. Worrying about this is ridiculous.
Pages: « 1 ... 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 [76] 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 ... 161 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!