Bitcoin Forum
April 27, 2024, 07:38:49 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 [893] 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 ... 1463 »
17841  Bitcoin / Bitcoin Discussion / Re: BTC low fee taking days (or more) on: March 02, 2017, 08:37:40 AM
the problem with cores idea of fee's is not controlled by code..

kind of funny that devs removed code rules.. yes version 0.14 has totally removed the priority mechanism.
yes the priority mechanism wasnt any good as it just favoured the rich more then the poor in its formulae. but they never bothered to actually be real devs and envision a new formulae that actually does help solve the issues that causes the problems and also havnt been code devs to treat people more fairly rather then act like banker economists that punishing the innocent aswell as the malicious with the stupid 'just pay more' empty minded mindset..

so to save me re-writing what i have already wrote

we should think about changing something real simple.
the tx priority formulae to actually solve things like bloat/respend spam. where by the more bloated (tx bytes) and the more frequent (tx age) a spend is made. the more it costs.

imagine that we decided its acceptable that people should have a way to get priority if they have a lean tx and signal that they only want to spend funds once a day. where if they want to spend more often costs rise, if they want bloated tx, costs rise.. which then allows those that just pay their rent once a month or buys groceries every couple days to be ok using onchain bitcoin.. and where the costs of trying to spam the network (every block) becomes expensive where by they would be better off using LN. (for things like faucet raiding every 5-10 minutes)

so lets think about a priority fee thats not about rich vs poor but about respend spam and bloat.

lets imagine we actually use the tx age combined with CLTV to signal the network that a user is willing to add some maturity time if their tx age is under a day, to signal they want it confirmed but allowing themselves to be locked out of spending for an average of 24 hours.

and where the bloat of the tx vs the blocksize has some impact too... rather than the old formulae which was more about the value of the tx

here is one example


as you can see its not about tx value. its about bloat and age.
this way
those not wanting to spend more than once a day and dont bloat the blocks get preferential treatment onchain.
if you are willing to wait a day but your taking up 1% of the blockspace. you pay more
if you want to be a spammer spending every block. you pay the price
and if you want to be a total ass-hat and be both bloated and respending often you pay the ultimate price

yes its not perfect. but atleast lets think about using CODE to choose whats acceptable. rather than playing bankers economic value games of rich guys always win, or the bankers ecomonic games of 'just pay more.. that way we are no longer pushing the third world countries out of using bitcoins mainnet.



the other problem recently is that core changed the fee calculations by miners from being reactive to demand.. to be done using an average estimator, which is proved by math to be biased to increase even during low demand. this needs to go back to reactive
17842  Bitcoin / Bitcoin Technical Support / Re: Is waiting 24 hours for an inbound transaction to clear common? on: March 02, 2017, 03:56:32 AM
you should see it as a unconfirmed transaction very quickly.. but getting confirmed has become less guaranteed recently
17843  Bitcoin / Bitcoin Discussion / Re: Are Chinese bitcoin investors that gullible? on: March 02, 2017, 03:25:04 AM
ICO=pre-mined coins

majority of pre-mined coins are pump and dumps.
it does not matter how many coins are produced or any of that. unless a coin serves an actual purpose and actually has places to use a coin. its useless.

treat ICO's as penny stocks (pumps and dumps) only throw a penny at them, and at most just the same amount you would waste on fast food that just gets flushed away in the toilet 6 hours later.

and as for all governments that all make the standard investment advice of "investors should consider it as carrying a “high degree of risk”. and not to expect guaranteed returns or profits. because you can make a loss aswell as a gain"
17844  Bitcoin / Bitcoin Discussion / Re: What happens if BU fails VS What happens if SegWit fails on: March 02, 2017, 02:56:40 AM
I admit that I still try to wrap my mind around the technical discussions about Bitcoin but knowing that there is politics involved here still makes me doubt what the hard fork to BU, Classic or XT is really all about. There has to be something like a power grab here. Also the argument that the Bitcoin Unlimited developers are not as good as the Core developers and contributors deserves notice.

until you read the code and grasp the concepts of bitcoin. you will be stuck in the social drama of politics.
dont be so easy to grab onto some human and kiss their ass because of X or Y.
one day that human wont be here, but bitcoin will. so care more about bitcoin and less about the human

learn what the code does and let the code help you make your decisions.

core code is not a simple fix. its about changing the network topology and favouring nodes (centralising)

other implementations such as xt, classic, bitcoinj, btcd, bu and half a dozen others  are not about kings or gaining control of the network. they ALL want to use consensus to have all implementations on the same level playing field where nodes have the independent decentralised power, not devs not miners.

the whole point of bitcoin is that its not reliant on some central team of decision makers

so instead of playing the social games of which team is better. instead think.
let there be many teams so that none have power and only the nodes form a consensus of what should move forward.

that way the 'teams' become more like workers rather than managers. where the teams work to find the best solutions to bitcoin problems. instead of fighting to be kings and herding sheep in only a direction they want
17845  Alternate cryptocurrencies / Altcoin Discussion / Re: Altcoin Learnings: SW kills LTC + HF makes ETH strong -> Bitcoin path written? on: March 01, 2017, 11:55:44 PM
stop thinking HardFork only= altcoin creation!!!

even a softfork can create an altcoin. and core have admitted they will and can by showing how segwit filters data and black/white listing nodes

a consensus is DIFFERENT than a bilateral split(altcoin creation).
ethereum was a bilateral split and intentionally split because the nodes added a ban opposing node connection rule --oppose-dao-fork

a hard consensus just causes orphan drama and a SINGLE chain after the orphan drama subsides where the small minority just wont sync at all and left dead.

orphans prevent a second chain co-existing. the only way to get a minority to survive is to literally ban the opposing nodes so that they can build ontop their minority without worry of orphans shutting them down.

sipa learned that lesson the hard way in 2013 with the leveldb bug he created.
17846  Bitcoin / Bitcoin Discussion / Re: What happens if BU fails VS What happens if SegWit fails on: March 01, 2017, 11:11:41 PM
  Regarding BU people are more concerned about the risk of an technical problem. 

The opponents of BU are small block advocates that prefer the average user be
able to run an LN node for hop charging profit, rather than be able to transaction on chain.. and are more
concerned about having transaction fees pay themselves rather than pay for security
in the future even though that concern is decades away.

While I fully disagree with both of those reasons, at least they have some inkling of plausibility.
However I haven't seen any credible argument for the possibility of a technical problem with BU.

 

FTFY
17847  Bitcoin / Bitcoin Discussion / Re: What happens if BU fails VS What happens if SegWit fails on: March 01, 2017, 10:50:01 PM
^ look at him talking about something he doesnt understand

segwit only works for people using segwit keys. anyone sticking with native keys can still cause signop issues within blocks.
the only way to avoid sigop issues in blocks is that 0% .. ZERO .. again ZERO(emphasised 3 times) users have funds on native tx's.

segwit does not disarm native transactions so sigop and malleability will continue.
segwit only disarms the innocent that voluntarily move funds to segwit tx's.. it does not disarm the malicious users

segwits 4mb wight is not a real 'feature' that all bitcoin users get to benefit from.

firstly only IF 100% of users use segwit keys, they would notice about a 2.1mb transaction one time boost.
the other 1.9mb is spare and unusable for anyone until future features ar added that append trivial data to the end of a tx for things like
confidential tx's

if the base block sticks to 1mb. the max expectation is ~4500tx with 2.1mb weight.
then if confidential payment codes and other features append data.. its still 4500tx but bloated to take up the spare space of the 4mb weight
17848  Bitcoin / Bitcoin Discussion / Re: Peter Schiff being an idiot on national television on: March 01, 2017, 09:46:31 PM
when speculators pretend to not hold bitcoin but have a negative opinion on bitcoin right at the point of bitcoin rising. its because they just sold and are now gonna fud stuff to tank the price.

never mentioning the technicals just something financial that will affect the price so they can buy in cheaper again and rinse and repeat.

soon we will see many more gold bugs(holders) talk about how bitcoin is bad and gold is good. not because their right but because they have gold and they want bitcoin and will say how great their gold is while in reality getting rid of their gold.

the best advert to sell and get rid of gold is to tell people how great gold is and offer them some to slowly get rid of what their holding
17849  Bitcoin / Bitcoin Discussion / Re: WHY ....... on: March 01, 2017, 02:12:09 PM
what if I can ask every single human on Earth 1 peso ($0.02)? I would probably be rich. Cheesy

thats called a pyramid scheme Cheesy Cheesy Cheesy
but done with the full knowledge that the people are giving up their small amounts to make another person rich is not illegal, and then it becomes known as a lottery
17850  Bitcoin / Bitcoin Discussion / Re: What happens if BU fails VS What happens if SegWit fails on: March 01, 2017, 12:42:17 PM
just to clarify kilo's point because he appears to be a hott head that runs in different directions rather than explaining the point rationally

pink flower said
Quote
I think youre misinformed or youre misinforming others about the Lightning Network. BTC Core doesnt have a monopoly on what layer is built on the network if segwit is activated. There are other groups who are already coding other executions of it.

well core have already positioned themselves as a ringfence around the pools with their "fibre" nodes.
if pools adopt segwit then the segwit pools will white list the "fibre" nodes as their way to maximise propagation efficiency.

segwit is known to blacklist nodes they dislike and whitelist other nodes. known to not relay certain transactions.

 so they can be biased against any smart contract that is not produced by LN(blockstreams version of second layer smart contracts) by  not relaying those to pools.
causing the issues for opposing second layer services by not being able to settle or set up channels in a timely manner. because their transactions will not be added to pools mempool or refused to enter a block
(much like core loving pools refuse to do 'first seen, first added' for transactions. and instead biasedly add transactions by who sent it and how much is paid(BTCC does this))

with core being the upstream filters (gmaxwells own words) and also demonstrated in cores own userguide.. core have set themselves up to centralise the network.

try reading the documentation and code whilst wearing a critical /logical thinking cap. and not a fanboy cap.
dont think about the limited benefits, promotional sales pitches.. look for the fine print limitations and realities.
EG
https://bitcoincore.org/en/2016/10/27/segwit-upgrade-guide/
Quote
If you still don’t wish to upgrade, it is possible to use a newer Bitcoin Core release as a filter for older Bitcoin Core releases.
meaning you have to have a segwit node. to be able to be accepted by the other nodes.. and you are then able to whitelist your own non segwit node. (basically other peers will reject you unless you pretend you are a segwit node)
Quote
In this configuration, you set your current Bitcoin Core node (which we’ll call the “older node”) to connect exclusively to a node running Bitcoin Core 0.13.1 or later (which we’ll call the “newer node”). The newer node is connected to the Bitcoin P2P network as usual. Because the newer node knows about the segwit changes to the consensus rules, it won’t relay invalid blocks or transactions to the older node—but it will relay everything else.

When using this configuration, please note that the older node, if it uses Bitcoin Core defaults, will not see transactions using segwit features until those transactions are included in a block.

Configuration:

For the newer node,
start it normally and let it sync the blockchain. At present, you cannot use a pruned node for this purpose because pruned nodes will not act as relay nodes. You may optionally start the newer node with either or both of the following command line parameters so that it treats the older node as special (these options may also be placed in Bitcoin Core’s configuration file):

  -whitebind=<addr>
       Bind to given address and whitelist peers connecting to it. Use
       [host]:port notation for IPv6

  -whitelist=<netmask>
       Whitelist peers connecting from the given netmask or IP address. Can be
       specified multiple times. Whitelisted peers cannot be DoS banned
       and their transactions are always relayed, even if they are
       already in the mempool, useful e.g. for a gateway

For the older node, first wait for the newer node to finish syncing the blockchain and then restart the older node with the following command line parameter (this may also be placed in the Bitcoin Core configuration file):

-connect=<IP_address_or_DNS_name_of_newer_node>


if you think the image is some anti core propaganda wallpaper from reddit.. check where the image is coming from (hint here is the link)
https://bitcoincore.org/assets/images/filtering-by-upgraded-node.svg

there are other little tip-bits of agenda hinted at in the userguide. how segwit will reject blocks that are not produced by segwit pools ensuring core has control of the network
Quote
If segwit reaches locked-in, you still don’t need to upgrade, but upgrading is strongly recommended. The segwit soft fork does not require you to produce segwit-style blocks, so you may continue producing non-segwit blocks indefinitely. However, once segwit activates, it will be possible for other miners to produce blocks that you consider to be valid but which every segwit-enforcing node rejects; if you build any of your blocks upon those invalid blocks, your blocks will be considered invalid too.



oh and by the way.
when pools make segwit blocks.. they wont be organically backward compatible. they will need to be 'filtered' to be presentable in a manner old nodes can understand.

meaning if segwit has a bug. the you cant just turn off segwit nodes and go back to old nodes which will understand the blockchain.
pools then have to do the filtering of the blocks while they too downgrade which can cause alot of disruption. due to them having to move funds back to native key types and other things to undo a segwit activation

where as a bu pool simply make blocks under 0.999mb without needing to downgrade/filter or move funds back. because BU uses the same mechanisms and transactions that were around for 2009-2016



p.s
if you feel my post is just a wall of text and you have not bothered reading it simply because its a wall of text. then you obviously dont have the concentration span to read userguides or code. this lack of attention span reduces your ability to understand bitcoin fully, so work on it
17851  Bitcoin / Bitcoin Discussion / Re: What happens if BU fails VS What happens if SegWit fails on: March 01, 2017, 11:38:47 AM
BU has known attack vectors, it's part of the BU "design".

The BU concept is presented as that everyone is perfectly rational and has perfect goodwill towards BU, and so picks a sensible figure that everyone can handle. The reality is the soft 16MB limit can be quickly and easily reached if someone malicious floods the network with 16MB signalling.
its called a sybil attack.
a malicious core loving pool can also sybil attack with loads of core nodes flooding the network and then make changes too..
same thing. nothing specific that is only attackable via BU

Also, BU wasn't (in the past) programmed to follow the longest PoW chain. That would cause the BU blockchain to fork spontaneously into different blockchains
nope
learn consensus and orphans
as long as there's sufficient disagreement between the nodes about what the blocksize should be (a minor incident like this happened recently with a BU mining node, implying these kind of risks are still programmed into the software not as a bug, but as a feature).
and that block was orphaned in 2 seconds

orphans happen daily. orphans are a protection mechanism. orphans are good. yes it causes drama but the end result is a single chain

pools know orphans have a positive job of cleaning up the disagreements. pools also know they cause drama for the community so pools usuallly dont do anything to cause much drama.

hense why pools would take baby steps, testing the water and seeing how much orphan drama is or is not caused.
17852  Bitcoin / Bitcoin Discussion / Re: Good article on why BU sucks on: February 28, 2017, 11:53:31 PM
What I have not heard from these others -- as of yet -- is what _their_ proposal for a market-driven blocksize might be.

most of those opposing it havnt even read the code. infact they havnt even read segwits code either.
its just a political king vs king debate about humans and who should be their Sheppard.

they cant even fathom the difference between an intentional split and a consensus upgrade

anyone that has made a dynamic block concept has literally got the same conditions.. but then added in stupid things like messing with the block reward as a penalty. (knowing that it doesnt change security) but does cause political debate

a few things that make a good consensus that has better features of fixing things

1. nodes first agree then pools follow (obvious standard hard consensus)
2. limit tx sigops (meaning native or new tx types are both limited. = proper quadratic limitation that cant be bypassed
3. a new priority fee formulae that doesnt care about rich or poor as priority measure but about how bloated a tx is and how old a tx is as the main measures
4. where the nodes include a speed check mechanism where it count the time it requested a new known block and when its fully validated to set a score of capability which could be added as a useragent flag.
5. having the ability to download patches/update files within nodes that update settings/values without specific dev decision or waiting for major releases . that way nodes can be more independant and form consensus based on rules of the network. not politics of humans
17853  Bitcoin / Bitcoin Discussion / Re: Good article on why BU sucks on: February 28, 2017, 07:52:09 PM
According to my understanding of the Bitcoin white paper, miners, broadcasting blocks too costly for mining peers to process, run the risk of other miners rejecting those blocks in favor of less costly blocks. While I disagree with BU's dynamic block size approach, I'm of the thought miners should make their own assessments on the risks/rewards of publishing a certain block:
1) Large block propagation outpaced by smaller blocks
2) Transaction fee per block
3) Block acceptance by mining peers

4)I'm curious what people's views on a market-approach for block size, whereby transaction senders (buying space to fit said transaction into a block) and miners (selling space to fit said transactions into a block) find stable equilibrium sizes for the average block

1. lets say all the nodes have some speed test mechanism that reveals they can cope with upto 8mb blocks..
lets say they flag that for the next 3 months they will be ok with 2mb as an extra cautious preference.
POOLS will then make blocks BELOW 2mb. which will start off with 1.001mb just to test the water and see the orphan risk of going beyond old limits.
which means with baby steps of safety it will take many blocks to get to 2mb..
emphasis it took from 2009-2013 to get to 500k even though there was a 1mb limit. then took from 2013-15 to get to 0.999mb even though there was still the 1mb limit..
so.. for emphasis. DO NOT PRESUME instant 2mb or 8mb will be filled blocks 1 block after activation. as that WONT happen



2. pools DO NOT CARE about fee's. they are happy with the block reward income. the fee is just a bonus. not a need income.. do not presume pushing the fee war today has anything to do with the pools or to do with the community "helping" the pools. its not. we do not need to push the fee war today. it can naturally grow over the next couple DECADES!!



3) refer to 1. pools wont do anything that the majority of nodes cannot accept because it ends up as orphaned otherwise. if a pools block is orphaned. the pool will stop doing it because its just wasting money for an activity that literally gets thrown into the metaphorical trashcan



4) this can be done by developing a new 'priority formulae' that is nothing like the old useless formulla that just had a rich guy vs poor guy preference. and instead charges bloaters/spammers more.
i posted a quick idea of one where the formulae only cared about lean tx's and tx's that didnt want to respend every block. rewarding the lean infrequent spenders and punished the bloated frequent spenders

imagine that we decided its acceptable that people should have a way to get priority if they have a lean tx and signal that they only want to spend funds once a day. where if they want to spend more often costs rise, if they want bloated tx, costs rise.. which then allows those that just pay their rent once a month or buys groceries every couple days to be ok using onchain bitcoin.. and where the costs of trying to spam the network (every block) becomes expensive where by they would be better off using LN. (for things like faucet raiding every 5-10 minutes)

so lets think about a priority fee thats not about rich vs poor but about respend spam and bloat.

lets imagine we actually use the tx age combined with CLTV to signal the network that a user is willing to add some maturity time if their tx age is under a day, to signal they want it confirmed but allowing themselves to be locked out of spending for an average of 24 hours.

and where the bloat of the tx vs the blocksize has some impact too... rather than the old formulae with was more about the value of the tx

here is one example


as you can see its not about tx value. its about bloat and age.
this way
those not wanting to spend more than once a day and dont bloat the blocks get preferential treatment onchain.
if you are willing to wait a day but your taking up 1% of the blockspace. you pay more
if you want to be a spammer spending every block. you pay the price
and if you want to be a total ass-hat and be both bloated and respending often you pay the ultimate price

yes its not perfect. but atleast lets think about using CODE to choose whats acceptable. rather than playing bankers economic value games of rich guys always win, that way we are no longer pushing the third world countries out of using bitcoins mainnet.
17854  Bitcoin / Bitcoin Discussion / Re: Johnny (of Blockstream) vs Roger Ver - Bitcoin Scaling Debate on: February 28, 2017, 07:29:57 PM
At least one time, Franky posted for more than 24 hours consecutively. It's pretty obvious that there was more than 1 person posting using the Franky1 account that day, Franky2 and Franky3 presumably. The Franky on duty at the end of that day claimed that he doesn't need sleep

sorry to burst your bubble. but i am one person

i just have the freedom to travel alot so my sleep habits change.
this includes only sleeping in short periods and sporadically.

it might be worth you going travelling one day and see beyond your cabin fever small lifestyle
see different people, different cultures, gain an open mind beyond your bubble.

17855  Bitcoin / Bitcoin Discussion / Re: Good article on why BU sucks on: February 28, 2017, 07:18:08 PM
whale panda has not read a line of code of BU nor read segwit.

here is a funny part of his earlier attempt at promoting segwit
https://keepingstock.net/segwit-eli5-misinformation-faq-19908ceacf23#.qvojlmtn8
Quote
Some people have called segwit a “hack” because it is implemented as a soft fork. The practical differences between soft and hard fork implementation are very minor; however, under a hard fork, every node must upgrade and every software project must be adapted in order to function at all. As a soft fork, nodes can optionally upgrade.

those that dont upgrade to segwit. and thus dont use segwit keys are not disarmed from malleating, quadratic bloating and other things..

also it adds another attack vector where one could grab a segwit unconfirmed tx and throw it into a non segwit node and mess with the tx.
meaning by saying sw is backward compatible they are admitting that malleability, quadratics and new attacks are not fixed. because malicious people will just use native bitcoin nodes.

its like 2 kids fighting where one of the kids has a sharp object.. sw is simply telling the innocent kid to stand on the naughty step and never play with sharp objects. but doesnt stop the kid with the sharp object.

17856  Bitcoin / Wallet software / Re: Seed / Wallet question on: February 28, 2017, 06:58:32 PM
a "wallet" using 2 networks. wont be a full node. so there are risks that it may grab ur privkey

dont use it for large amounts and do some research on the company/devs that created it.

check to see if they have open sourced their code and use the open source to create a compiled wallet after reviewing the code doesnt contain trojans or ways to send the privkeys to someone
17857  Bitcoin / Bitcoin Discussion / Re: Johnny (of Blockstream) vs Roger Ver - Bitcoin Scaling Debate on: February 28, 2017, 06:47:40 PM
The BS Core marketing campain in combination with reddit/bitcoin style has fully brainwashed some neutral individuals with the psychological and political useful trick to spread real fear about any HF.

I wonder how they could logically conclude that if SW is not enough for on-chain scaling there is need for a HF,... Later ?  WTF ?

So the earlyier we do a HF the better and thanx to ETH we are alerted and prepared - we do better! But how on earth can this be done safely now at all with this psych fear anchor thrown ?  I m really curious what this 'later' agenda looks like if BS Core needs to remove this fear by magic and initiate a good HF?  SW yourself!

because the BS core army are deliberately talking about a harkfork umbrella term using the worse case bilateral fork subcategory.. with all the fake doomsdays and fake scares of calling anything not core an altcoin.
(ethereum was not a real hard consensus fork. it was a intentional hard bilateral fork)


later they will get some dude to magically wake people up and teach the community that CONSENSUS is different than BILATERAL(intentional) splits. and then reteach their sheep that a consensus fork was always possible and the BS core army can now do a consensus fork because they have now pulled some statistics out of their rear end that shows consensus is safe..

strangely the same as how 4mb is now magically safe even though 2mb was bad

they have a road map of scripts of when an how to reveal their plot. but i just want them to man up reveal their agenda and just bypass this crappy delay stuff and get on with a proper bitcoin hard consensus vote that allows real onchain growth
17858  Bitcoin / Bitcoin Discussion / Re: Good article on why BU sucks on: February 28, 2017, 06:35:03 PM
Agreed Franky, but why not be ready, if it does happen? None of the big social media sites have accepted Bitcoin yet, but imagine if they do? Let's

say Facebook incorporate Bitcoin into their platform, will Bitcoin be in a better position if they are ready for that traffic or will they sit back and

say, nah.... this will not happen over night... so let's adapt to that, when it happens or 3 months after that.  Roll Eyes

private contracts can be done right now.
all LN is, is a snazzy GUI for private contracts.

but even LN's GUI has bugs and issues. both at concept and at its current 'feature' offering promotion

facebook themselves can within a couple days set up their own private contracts and be their own smart contract network(hub).

segwit is not needed. blockstream coded LN is not needed

but with that said ONCHAIN REAL growth of REAL block scaling should happen too.
17859  Bitcoin / Bitcoin Discussion / Re: Good article on why BU sucks on: February 28, 2017, 06:12:35 PM
Don't get tricked, there is no way to have massive-volume onchain transactions in a decentralized and cheap way


I'd add a caveat to that: that's not possible today. With tomorrow's internet infrastructure and and a further improved Bitcoin client, maybe it could be done. But now, reality says only 2nd layers can scale up to worldwide demand for cheap and decentralised transactions.

I don't see how.  but can we outcompete VISA

to blockersteam lovers

stop thinking "bitcoin 7billion users by midnight." "gigabytes by midnight"
both blockstream scripts have failed to spark about 2 years ago, so give up trying to use them...

natural growth takes time.
halting that natural progressive growth using fears of "X by midnight" is your own failing.



if you ever have kids i bet you would break the poor todlers legs before it can walk and then tell child protection agency your doing it because you fear it will run infront of a car when it gets older.

you would then try to seek society granting you permission that your child should be classed as disabled so you can then get a whelchair(ln) because its faster than walking and then claim SS benefits for being the carer..

you blockstreamers want to cripple bitcoin just to take advantage of the community for your own personal gain
17860  Bitcoin / Bitcoin Discussion / Re: Johnny (of Blockstream) vs Roger Ver - Bitcoin Scaling Debate on: February 28, 2017, 05:51:43 PM
i hate this because gmaxwell loves his monero
I don't do anything with monero.
really??
Other contact info:    XMR: 43pCtCRUn6nRdvmpqzoHJy4NwFsRrEqywhjwfbiUqTtqBAHxCNzdctbHZjf1AZKtTkAjgKmhYgkqBU9 T4BEfAgBqKwK21M7

not so much bitcoin.
I own a considerable amount of Bitcoin and am paid partially in Bitcoin.
partially paid.

i feel gmaxwell doesnt care about bitcoins survival and
yet people are following gmaxwell, because of old outdated stuff he done before he got into the bankers pockets and changed motives.

I am not paid by bankers. I am paid by a company I founded whos investors are not bankers.  
investors are not bankers?
so the fiat money is just magically there from some basement dweller.. and not from some financial institution...pfft.. keep trying.

And many people are excited about work I've done that was funded by this company like Confidential Transactions and sidechains.
which are not part of bitcoin.
also you love to only circle yourself within a niche group of people that agree with you. you will only hear cheers and applauds towards you because you dont like to hear the negative. what you suffer from is called cabin fever
its like a little girl who thinks she really is a princess because she is only listening to her biased dad complement her. so she starts to wear the dresses and acts the part to please those who complement her.

and allowing bitcoin to change due to human emotion of trust of another human. without bothering to just read what code was wrote and what the actual codes does to the network.
I think Bitcoin is okay the way it is.
because its the way your team have moved it. not the way the REAL community want it moved.
your buddy matt corallo changed the network topology (your words segwit node being upstream filter (hint: FIBRE)
your other buddy is making the commercial LN hub mechanism so you can repay your investors with all them fee's your looking forward to making in LN

the thing is those complimenting you have admitted they have not read the code or done much research.. their trust is in the "princess" not the actual code.
you sold them a sales pitch and not revealed the small print in a manner they can read

you also fail to be completely honest about segwit not being as promised.
it wont fix the issues at activation
it wont fix the issues purely by having 100% of pool using segwit nodes.
it wont fix the issues purely by having 100% of pool using segwit nodes.
it only fixes the issues IF(strong if) 100% p2wpkh/p2wsh key use.. which will never happen. malicious people will stick to using native transactions. meaning problem still exists
Pages: « 1 ... 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 [893] 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 ... 1463 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!