Topic: A few lines of code... (Read 1292 times)

How is it not important even if you have to download it once one? It has to fit on your hard disk, so use your brain. 8MB blocks would mean the average computer user which has a 1TB hdd, wouldn't be able to run a node and since 8MB would get quickly filled again, people would demand more because you make them used to low onchain fees which is a mistake. The result is we end up with datacenters running nodes and no people runs nodes anymore, in other words we are fucked, stuck with a bitcoin run by corporations instead of people on their personal computers as it should be to be able to survive government control. The Blockstream conspiracy shit is so 2015, time to think for once.

If it becomes the Bitcoin-killing Altcoin, everyone will have a stab at that, because we all know, the highest trees catch the most wind. The

main difference between that, and Bitcoin will be that the new Alt coin will have a Master, not like Bitcoin, where the Master fled the

scene. A individual or a known group of people, will be a easy target, and I do not know if anyone is ready to take on that challenge. 

you got me triggered right there

Well no one wants to leave bitcoin because it is the grandfather of crypto and in different ways, we've all grown attached to it.

Bosses already decided, they will implement Segregated Witness, even if it takes 10 years to do it.

The protocol for Lightning is a scam, owned by scammers who took over bitcoin.  SegWit was crammed down our throat so they could get Lightning working and it does nothing appreciable for actually improving Tx bandwidth.  Bitcoin is hijacked by Blockstream so they can own blockchain access via their bullshit 'Lightning'.  Everyone can see it.  The protest will become quite a bit louder the day they announce the fees.  But then it will be far too late.

That's another aspect of Segwit.

The nested outputs format (described above by achow101) will be joined by a native segwit output format at some point. Native segwit format has a small space saving compared to both the standard outputs now or nested format (which incur a small size increase when compared to traditional outputs).

In addition, Segwit is a pre-requisite to Lightning channels, which will do more than any other improvement can to scale transaction rate. 8MB will be a long way off once the protocol for Lightning is ready.  

Thanks for explaining it to me!
I think we should at least go to 2mb blocks, yes I noticed that sometimes my transaction is stuck due to 1mb blocks and more transaction get created than that 1mb block could handle. 2mb blocks is a solution for the short term, but what happens if we eventually hit the 8mb blocks and those will be full? We go to 16mb blocks? Or do we have other options, like reducing the storage every transaction uses?

no, im saying the opposite

your post needs to be answered in two parts.
transactions are not confirmed instantly. they are seen on the network(unconfirmed) near instantly. but not confirmed instantly.
transactions are seen, but are then held in a list.

while mining groups are solving a block(previous list) they are building up a new list ready for the next block, they select the transactions that validate and have a good fee and make an unsolved block. this occurs on average (based on a two week measure) roughly 10 minutes
then when the previous block is solved they start working on the next block.
when the blocks are solved. the transactions in those blocks are classed as confirmed.

lets say each 1mb block has a max buffer of 2500tx's

in 2013 blocks only had a thousand transactions due to not many transactions were being sent around inbetween each block. so every transaction went in and still had space for more transactions..
as bitcoin got more popular more transactions start happening and blocks started to get more filled up

today we are at the limit and its causing bottlenecking often.

if we moved to 2mb. mining groups could add more transactions. and have space to allow for future growth before hitting the wall again.
if we didnt move to 2mb but to 4mb. mining groups could add more transactions. and have space to allow for future growth and hitting the wall again wont happen for a longer period compared to 2mb.

everyone knows that a 2mb or a 4mb is safe.. but some are trying to jump the gun with a 8mb block limit so that we wont hit that limit for years to atleast not keep having this debate every few years.
they are sick of the oliver twist script of asking devs "please sir can i have some more"

I don't think you have read any source code for any of the proposed hard forks to increase the block size limit. It most certainly is not just "a few lines of code". This is Gavin's original implementation PR that he submitted to Bitcoin Core: https://github.com/bitcoin/bitcoin/pull/6341. It is most certainly more than just a few lines of code. Why? Because it must include proper deployment of the hard fork and unit tests (tests are always necessary regardless of the change). Furthermore, IIRC that PR did not include anything about fixing the O(n^2) signature validation problem, that needs to be fixed separately with another set of code changes. Lastly, to help reduce the bandwidth, so that people can actually still run full nodes, you need something like XThin or Compact Blocks, which is yet another large code change. Suffice to say, it is most certainly not just "a few lines of code" and a "tiny change".

Because it is a good thing and it fixes a ton of issues. Segwit fixes malleability issues, which have been a problem in the past when people have maliciously attacked Bitcoin transactions by malleating them. It also fixes the O(n^2) signature validation issue and makes it O(n) which is much much better. It introduces script versioning and allows for further improvements to the scripting system. And of course, it can also help with increasing the number of transaction that will fit into a block.

Segwit does not use different keypairs. It still uses the exact same Elliptic Cure Cryptography with the secp256k1 curve. Segwit uses different scripts, which are completely separate from keypairs.

In what way? You can still send to traditional outputs. Segwit uses nested outputs so that people can still send to segwit wallets and the receiver can still take advantage of segwit.

And so did every other soft fork.

What about your bandwidth? It's not storage that's the issue, its bandwidth. You have to download the entire blockchain in order to run a full node. And then you have to upload and download all of the blocks. If you have a bandwidth cap (e.g. you have comcast), then you are royally screwed and can't run a full node.

---

For those of you who claim that Bitcoin Core is "centrally planning" Bitcoin, you should take a look at Bitcoin Classic. Thomas Zander commits directly to the development branch of Classic. He doesn't follow a pull request and code review process like Bitcoin Core does. He is centrally planning the direction of Classic by taking its development directly into his own hands by bypassing code review and just putting his changes into the repo.

Do you mean that the bitcoin blockchain is coded so the transactions will first gather up to a big total and than will be confirmed instead of one by one? So basically it is meant to be non instant confirmation?

200GB is nothing.  Super fucking tiny.  The total size of the chain isn't at all important.  You only download it once.  You can buy 10 terabyte for very cheap.  So, 200GB is laughably small.

The real issue is passing 8MB around to all the nodes every ten minutes.  Some effects occur there.  No big deal.  Internet is freaking fast and getting freaking faster.  Netflix bandwidth load is >>>>>>> than bitcoin with 8MB. 

If we want people to be able to run a node behind a 1200 baud modem, then 8MB is problematic.  If we abandon those having 1200 baud and less, then the only reason to keep 1MB is to drive need for Blockstream's bullshit solutions. 

8MB blocks are very lightweight for nearly all modern systems. 

this is why last year the community agreed that 2mb was an acceptable amount everyone could agree with.
even core think its ok to have 4mb now.. very funny i found that. but they dont want to have the extra 3mb for proper capacity. but to be abused by funky signatures, payment codes and other non traditional features.

but here is the thing

2mb, 4mb, 8mb.
the blockchain is not going to bloat to those settings the day the setting is active.
just like after the 500k db bug was sorted in 2013, blocks didnt instantly jump to 1mb completely filled blocks the next day.

these limits are not about "dont process a block unless its full".. to cause instant bloat. but instead "here is some extra space to allow slow natural growth without being crushed against a wall"

in short the rule is a BUFFER to allow growth unhindered for a while, not a minimal requirement that needs to be filled instantly

If we go to 8 mb blocks, wouldn't the size of the blockchain .dat file increase with 400%?
That would mean over 200gb for downloading the blockchain, which is prety asburd. Then more people will use online wallets that are less secure.

you know your team leaders altcoin monero already has it. but i guess you wanted someone else to advertise it so that you dont have to.
not clever because we all know you love monero and know about monero even if you pretend not to.


a INTENTIONAL and CONTROVERSIAL fork is scary? remember Ethereum was not a consensus fork it was a intentional split using --oppose-dao-fork to separate the chains PERMANENTLY

dont try bringing ethereums intentional split. into a debate about consensual upgrades.

The codes may be few but for its getting accepted by majority of bitcoin community is not easier. Whole community is divided between size should remain same 1mb and another who want block size to be increased to include as much transaction as possible.

Even if you come out with a superior technology,
(which can be argued already)
people are slow to change when it comes to money. No one wants to lose their investment.
A fork is fucking scary. Look at all the chaos that happened with Ethereum. And that was an alt-coin with nowhere near the value of Bitcoin.
Most people are in this game to make money, not to advance the technology.

Gentlemen, you are having a serious problem answering a simple question.


If "a few lines of code" would solve the cryptocurrency scaling problem, how come no-one is coding that up into a super Bitcoin-killing altcoin? They'd be rich, wouldn't they?

lol carlton keep digging a deeper hole.

guess what
other implementations are running right now. people can use their traditional keypairs in them right now. nothing has broken and users can transaction without issue.

however
segwit uses different keypairs, where other older implementations cannot validate signatures of segwit keypairs. segwit keypairs cannot directly move funds back to traditional keypairs without having to spend funds twice to get it back to traditional configuration that can be validated by traditional implementations.
meaning its a headache to transact with others.
segwit makes traditional implementations no longer full validating nodes. and instead just limp wristed relay nodes.

oh and to add
i know you will try comparing other implementations consensus rules as the same as the ethereum intentional fork.

but here is the issue you keep missing.. ethereum added  --oppose-dao-fork INTENTIONALLY. because they didnt want the consensus orphaning mechanism to sort it out.

ethereum split away from the consensus mechanism intentionally
segwit has a work around to avoid the consensus mechanism intentionally

yet,
other implementations want to utilise the consensus mechanism PROPERLY to get a true upgrade.
the funnier part is that segwit fanboys can actually join the real proper consensus mechanism and still get segwit features aswell as a true and proper capacity buffer upgrade all in one go..
EG 2mb base 4mb weight.

but no segwit fanboys want to keep the base at 1mb (1mb base 4mb weight.) and have fake 'consent' and not tell people the falseness of such

carlton. i wish one day you would actually take your "Gmaxwell/adamback for btc president" hat off and instead put a "decentralised logical bitcoin upgrade" hat on.

I'll answer the question -
Blockstream is the Alt!!

>8MB blocksize was in effect the day the first block got mined.  <-----    The real Bitcoin!!!