201
|
Bitcoin / Bitcoin Discussion / Re: Satoshi Nakamoto: "Bitcoin can scale larger than the Visa Network"
|
on: March 08, 2016, 07:54:30 PM
|
One thing that seems apparent to me is the lack of willingness to compromise. Appeasement is a powerful marketing tool. Could we reasonably raise the block size limit to 1.1MB without wrecking Bitcoin? Wouldn't the good will generated be worth it? Along the way we might learn something important. I fully realize the 2MB being bandied about is already a giant compromise down from the 32MB or 8MB sizes being proposed before. Is there something special about doubling? It can be set to 1.1MB easily, right?
1.1mb is an empty gesture. and solves nothing long term. meaning its just a poke in the gut knowing that more growth would be needed soon. the 2mb is not forcing miners to make 2mb blocks. its a BUFFER to allow for growth without having to demand that core keep chaing the rules every month. meaning even with 2mb buffer. miners can set a preferential limit of 1.1mb and still have 45% of growth potential(the 2mb hard limit) not even tapped into and not needing to beg core to alter for months-years imagine it. 2mb buffer and miners grow slowly month after month growing by 0.1mb when they are happy to. without hindrance or demands just like in 2013 when miners were fully able to use the 1mb buffer the miners did not jump to 0.95mb, they grew slowly over months and months. without having to ask core to change.. Thank you franky1: I understand but a 10% jump is at least something and then if all goes well the stage would be set to jump to something more, e.g. 1.2MB. Breaking the standoff seems more important to me at this time; the world is watching us.
|
|
|
202
|
Bitcoin / Bitcoin Discussion / Re: Satoshi Nakamoto: "Bitcoin can scale larger than the Visa Network"
|
on: March 08, 2016, 07:49:29 PM
|
I have a question: The total amount work to verify N 1MB blocks is about the same as single N-MB block, right? For example, 32 1MB blocks take about the same amount of work to verify as a single 32MB block, right?
No. The scaling of validation time is quadratic (look up quadratic growth if unsure what this means). In other words, 32 1 MB blocks != a single 32 MB block. Segwit aims to scale down the validation time and make it linear. Classic (BIP109) adds a sigops limitation to prevent this from happening (so not a solution, but limitation to size of TX IIRC). If anyone claims that this is false or whatever, that means they are saying that all the people who signed the Core roadmap are wrong/lying (2 MB block size limit is mentioned there IIRC). It can be set to 1.1MB easily, right?
That would work. Thank you Lauda: https://en.wikipedia.org/wiki/Quadratic_growth ... ouchie; so if a 1MB block with y transactions in it takes x seconds to validate then 32 similar 1MB blocks will take about 32x seconds but a 32MB block can be expected to take about (32y)²x seconds. Or is the quadratic growth on something other than transaction count?
|
|
|
203
|
Bitcoin / Bitcoin Discussion / Re: Satoshi Nakamoto: "Bitcoin can scale larger than the Visa Network"
|
on: March 08, 2016, 07:34:00 PM
|
One thing that seems apparent to me is the lack of willingness to compromise. Appeasement is a powerful marketing tool. Could we reasonably raise the block size limit to 1.1MB without wrecking Bitcoin? Wouldn't the good will generated be worth it? Along the way we might learn something important. I fully realize the 2MB being bandied about is already a giant compromise down from the 32MB or 8MB sizes being proposed before. Is there something special about doubling? It can be set to 1.1MB easily, right?
|
|
|
204
|
Bitcoin / Bitcoin Discussion / Re: Satoshi Nakamoto: "Bitcoin can scale larger than the Visa Network"
|
on: March 08, 2016, 07:28:11 PM
|
I would be willing to run a full node on a testnet to see if my system could handle larger blocks, i.e. verify a large block in less than the average time between blocks.
I have a question: The total amount work to verify N 1MB blocks is about the same as single N-MB block, right? For example, 32 1MB blocks take about the same amount of work to verify as a single 32MB block, right? Just please ignore the live delivery of blocks for the moment. Or is there some advantage to large blocks where less headers have to be processed. Imagine a full node was off the air for a day or two and is just trying to catch up as fast as possible. What block size facilitates that best?
To me it seems fees tend to be inversely proportional to block size, i.e. with smaller blocks fees rise as folks compete to get into blocks, with larger blocks fees get smaller with less competition to get into blocks. What does it cost a bad actor (if there is truly such a thing in this realm) to clog up the works? I suppose we are looking for the right size of block to cause them to expend their resources most quickly. Make the block size very small and the fee competition would rise high enough to deplete the bad actor very fast; everyone suffers higher fees until they are run out of town (so to speak). Hmm, but if the block size is very small then even when there aren't any bad actors on the scene, regular legit users would be forced to compete. At the other end of the spectrum; make the block size very large and with such low competition fees would diminish. The real question here is what happens to the fees/MB across the spectrum of block sizes.
Is there *anyone* preferring a smaller than 1MB block size right now? I haven't heard of any but you never know. I do think some miners do artificially constrain the block size they produce to like 900KB or so (I'm not sure of their motivation). Even if the block size were increased then such miners could still constrain the ones they produce, right?
A transaction cannot span multiple blocks, right? I suppose the block size creates a functional limit on transaction sizes. Or is the size of a transaction constrained some other way?
|
|
|
206
|
Bitcoin / Bitcoin Discussion / Re: Mempool is now up to 25.5 MB with 22,200 transactions waiting.
|
on: March 04, 2016, 10:43:46 PM
|
I dont really see how a predicted number of blocks waiting time is a problem and how implementing FIAT( ) display in core is going to change this. The majority of people that had problems (or at least that I encountered) did not use core, but a wallet that either does no suggestion to the fee at all or uses a fixed 10000 satoshi per started kbyte (which is no good suggestion either). Ok, no fiat, if it is too hard but it would really help. Any wallet that leaves this unrevealed is hurting the Bitcoin brand.
|
|
|
207
|
Bitcoin / Bitcoin Discussion / Re: Mempool is now up to 25.5 MB with 22,200 transactions waiting.
|
on: March 04, 2016, 10:41:01 PM
|
Specifically, the right end should indicate if the transaction is in the next block - which is not guaranteed at any fee amount - then although on average it should take 5 minutes (½ of the target average of 10 minutes), it might take as much as two hours or even more to confirm. If the transaction isn't in the next block or other things happen, e.g. orphan, etc., then it could take 4 hours or even more.
|
|
|
208
|
Bitcoin / Bitcoin Discussion / Re: Mempool is now up to 25.5 MB with 22,200 transactions waiting.
|
on: March 04, 2016, 10:30:37 PM
|
That is part of the wallet... ... as long as "wallet" means bitcoin core (classic et al. might have not removed this as well). OK. Let,s say I am stupid. I allways just click NEXT. But if there were "7 DAYS" instead "normal" and "10 MIN" instead "fast" - you believe me - I would move slider even if I were in a hurry Couldn't agree more; in fact, I'd go further; the default should start way to the right and both ends should indicate both expected duration worst case and total fee amount in both BTC and fiat (at current exchange rate). It is always better to set expectations brutally realistically and then outperform rather than the other way around.
|
|
|
211
|
Bitcoin / Bitcoin Discussion / Re: Blocks are full.
|
on: March 02, 2016, 10:19:43 PM
|
A larger blocksize will make a spam attack more expensive, no?
Maybe. Maybe not. The cost of a spam attack depends on the fees associated with the transactions. With a bigger block size perhaps the spammer could get away with smaller fees. If the fees are smaller enough then it could more than offset the larger block size. If only things were simple.
|
|
|
212
|
Bitcoin / Bitcoin Discussion / Re: Blocks are full.
|
on: March 02, 2016, 10:13:34 PM
|
This is really interesting. I started running Classic recently and I too feel like I might have been the target of a DoS attack the last couple of days; my router/firewall has been reporting lots of teardrop attacks (way more than ever before) and as such has been less responsive than before. How does one determine they are being attacked for sure?
http://nodecounter.com/how_to_defeat_ddos_attacks_against_bitcoin_classic.phpThat really does not seem right; both sides could do that. Soon we will need PoW or something to vote.
|
|
|
213
|
Bitcoin / Bitcoin Discussion / Re: why transactions are taking too long ?
|
on: March 02, 2016, 09:34:14 PM
|
Lauda, the ball is in your court. Do you see the opportunity for compromise here? 1.1MB (or 2MB) *and* SegWit? Or will you stand firmly on the SegWit only approach?
Exactly why would anyone want to do a HF right now (these are not easy to do and definitely not the preference of many) because of additional 100 kB? It is pointless at the moment and some patience is necessary. Segwit is just around the corner. and a HF proposal should be presented between April and July as well.
However, keep in mind that this is not the right place to discuss this. We are moving away from the original topic. On-topic: Currently there are 17.5k unconfirmed transactions (according to blockchain.info) and the number seems to be going down for now. Hmm, there's no connection between the transaction commit time and block size? A hard fork would be a show of good faith; especially if it isn't needed at the moment. The willingness to compromise is key to being viewed as reasonable and inclusive. Resisting compromise rankles against common sense; it undermines the trust and faith folks will put in you. Do you truly believe in the SegWit-only approach so much that you're willing to give up the advantages of embracing a compromise? At a minimum, help me understand when a block size increase would be entertained. What reports do we watch?
|
|
|
214
|
Bitcoin / Bitcoin Discussion / Re: Blocks are full.
|
on: March 02, 2016, 09:23:01 PM
|
This is really interesting. I started running Classic recently and I too feel like I might have been the target of a DoS attack the last couple of days; my router/firewall has been reporting lots of teardrop attacks (way more than ever before) and as such has been less responsive than before. How does one determine they are being attacked for sure?
|
|
|
215
|
Bitcoin / Bitcoin Discussion / Re: why transactions are taking too long ?
|
on: March 02, 2016, 09:17:16 PM
|
Thanks David Rabahy, I am sorry, I am a bit sensitive when it comes to that word. I like to pride myself in at least taking a high ground in these discussions, whether I am right or wrong. High ground? As in the dryer place? The tactical advantage? Or the morally superior position? Can't a guy make a joke around here? I sincerely understand; you mean you don't use unseemly tactics, e.g. manipulation. You argue points on their merit that the rational mind will see for itself from first principles. Me too. Lauda, the ball is in your court. Do you see the opportunity for compromise here? 1.1MB (or 2MB) *and* SegWit? Or will you stand firmly on the SegWit only approach?
|
|
|
216
|
Bitcoin / Pools / Re: BITMAIN announces Antpool
|
on: March 02, 2016, 09:06:25 PM
|
Do we in fact know they are mining empty blocks on purpose? Is it possible they aren't seeing the same set of transactions we are?
Is there a log somewhere of transactions making into the Antpool mempool which they subsequently ignore?
Yes we know for sure. It has been years since bitcoin has been quiet enough for any mempool anywhere on earth to have zero transactions after a block change. The reason antpool do it - as explained numerous times before - is dual: As a workaround to make up for poorly scalable pool software in addition to relying on block header only SPV hashing. Since their infrastructure is entirely dependent on whatever they deployed as their pool software now they have zero interest in changing their approach now since it "works". It mines, it finds blocks, miners sheep their way here, so why would they change? The next block halving is going to start really hurting antpool sheep (or are they ants?) as the proportion of rewards from transaction fees will be up to 5% of the reward even at current transaction rates and they'll be missing out on those rewards on every empty block they solve. Got it; thanks! I shall unwatch the topic so it doesn't irritate me.
|
|
|
217
|
Bitcoin / Pools / Re: BITMAIN announces Antpool
|
on: March 02, 2016, 08:47:02 PM
|
Do we in fact know they are mining empty blocks on purpose? Is it possible they aren't seeing the same set of transactions we are?
Is there a log somewhere of transactions making into the Antpool mempool which they subsequently ignore?
|
|
|
218
|
Bitcoin / Bitcoin Discussion / Re: why transactions are taking too long ?
|
on: March 02, 2016, 08:42:25 PM
|
I am not manipulating you, if anyone is it is the person telling you that I am. Manipulation has a very specific meaning. I mean what I say, and I am not appealing to irrationality and emotion. If you do not believe me regarding the censorship you are welcome to test that out for yourself. I just want to see Bitcoin thrive and I earnestly believe that increasing the blocksize is the best way to do this.
Oops, my bad; I was joking; I should have added a smiley. For the record, I never felt manipulated. I am pretty sure most folks involved are indeed earnestly believing in their espoused positions; it is possible there are disruptors in here, deliberately flaming discontent. I believe the following two positions are both true at the same time; 1) the block size should be increased for the expansion of Bitcoin this does come at a cost; bigger bandwidth, etc. 2) reasonable fees are good for the health of Bitcoin naturally the tricky part is figuring out what reasonable is Folks that believe only one of these are the real source of trouble. Lauda did show eventual support for 1). It is unlikely he is a disruptor; just passionate. VeritasSapere too showed willingness to compromise even though 2MB is already a big one; unlike a disruptor. The proof is in the pudding. As a show of good faith, the Core guys ought to boost the block size if nothing else to 1.1MB; even though they don't think it is required or it even hurts a little. Sticking to the wait for SegWit (no matter how great it is) exclusively is not the smart move politically. I highly suggest depolarizing. Recruiting folks into one camp or the other is polarizing; stop it. Compromise (even a little beyond reason) goes a very long way to improving the external image/brand.
|
|
|
219
|
Bitcoin / Bitcoin Discussion / Re: why transactions are taking too long ?
|
on: March 02, 2016, 08:08:24 PM
|
Hey, Core development guys; listen up; C.O.M.P.R.O.M.I.S.E. already. Would 1.1MB really kill ya? You are getting a bad reputation out here. If 1.1MB is a waste of time in your eyes then, ok, 2MB; whatever, it is more about appearances than anything. You don't think you can ride 1MB forever, right? Give us a clue; when do you think a blocksize increase will be appropriate?
Sorry to break it to ya but the core devs would hardly be having a look at this site, let alone in one of the specific thread where one random individual has made a suggestion. Github, the place for Bitcoin geeks is the only place Oh; thanks. Um, shoot; how does one post to Github effectively? If you did post such a concept on any one of the main Core channels they would just ban and censor you, I would be very surprised if that did not happen. This is part of why many prominent developers have moved to alternative implementations where these issues can be discussed and implemented. Fine; I will deinstall Core and install, um, which one? BU? That will teach those darn Core guys; ignoring/banning me wasn't very nice. If they aren't nice to enough people then they will lose control.
|
|
|
220
|
Bitcoin / Bitcoin Discussion / Re: why transactions are taking too long ?
|
on: March 02, 2016, 08:02:56 PM
|
Bitcoin is a permisionless network, I do not think there even is such a thing as spam unless you can prove the malicious intentions of the spammers, which is sometimes the case.
With a little bit of blockchain analysis you can do this; this is what happened yesterday. I'd also put dust into this category. Ok, fine. What do I do? Offer to pay a bounty for my version? How much is this going to cost me? Literally dust off my coding skills? Geesh, I did download the Git software a while ago and goofed around with it. I am an old VMS cli kind of guy so this is out of my comfort zone.
Step 1) Ignore the manipulation attempts. An increased block size limit does not solve this problem. Step 2) Wait for Segwit and LN. The easiest/best/only? way to fight spam is by making it expensive for them. So far the only answer appears to be increasing fees. Attempting to increase adoption with unrealistic low/zero fees is misleading.
Even if we had a 2MB block size limit/Segwit this could still happen any day (as it was an attack). This doesn't solve the problem. Something that could be considered a 'solution' with instant transactions is the Lightning Network (you might want to read up on it). One day we will need to increase the block size in order to accommodate non-spam traffic; we just aren't there yet. How much non-spam traffic is flowing through these days?
According to the roundtable (a 'unnamed' expert said) that blocks are 40% full right now (IIRC) and that the rest was spam. Hey, VeritaSapere; please stop manipulating me. Perhaps a larger block size doesn't solve "this" but it certainly wouldn't hurt, right? My son and I run an informal side chain in our brains; not terribly precise but it gets the job done. We keep track of how much we owe each other (I paid for the ski lift ticket; he bought lunch, etc.) and when it gets big enough we settle in Bitcoin (or sometimes in US dollars; whichever is handy). I think LN is like this but fancier and clearly way more precise/reliable. If my son tries to screw me he's out of the will.
|
|
|
|