Bitcoin Forum
June 25, 2019, 06:55:03 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 [22] 23 24 25 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 ... 822 »
421  Bitcoin / Bitcoin Discussion / Re: Comparison of Offchain Solutions for Crypto Coins on: March 27, 2019, 09:33:01 AM
How do you force people globally to adhere to KYC/AML regulations,

my answer to this is. its not the basement dwelling hobbiest who sets up a node that allows 8000+ connections to be a good 'hub'. as thats then just socio-political risk of getting caught if they dont register as a custodian/msb.
plus these hobbiest hubs wont have the liquidity to honour their promises of funding say $60 each for 8000 users ($480,000)

its the established businesses that self declare they are regulated custodians and are publicly advertising that for X fee they offer quality trustable service and best online % uptime, best liquidity of routes and best chance of route success. all available in exchange for some registration/basic ID requirements

.. after all why do you think things like coinbase.com are so popular even with kyc headaches and 1.5% fee's..
because people think that regulation=protection/trust/honour

after all.. in a world where paper money is still a thing. why do you think people even bother using a bank.
its never truly about 'force' its about planting the utopian thought that something is great if you use a commercial service/ network which has restrictions/limitations/headaches, but its fluffy cloud utopian benefits outweigh peoples freedoms
thus people voluntarity give over thir id.
(facebook is great example of Id/lifestory grabbing service, in exchange for some fluffy service/benefit)
422  Bitcoin / Bitcoin Discussion / Re: Bolt-A-Thon: World's First Online Lightning Network Conference and Hackathon on: March 26, 2019, 05:07:47 PM
physical conferences are also called seminars
virtual conferences are called webinars.

found it strange they not using the latest lingo
423  Bitcoin / Bitcoin Discussion / Re: Comparison of Offchain Solutions for Crypto Coins on: March 26, 2019, 04:32:14 PM
fractional reserve on LN. it has begun

https://www.bitrefill.com/buy/lightning-channel/

500,000 sats capacity You pay 0.000403 BTC
2,000,000 sats capacity You pay 0.001341 BTC
4,000,000 sats capacity You pay 0.002011 BTC
8,000,000 sats capacity You pay 0.003753 BTC
16,000,000 sats capacity You pay 0.004825 BTC

until windfury understands a millisat is not a sat.(payment contract vs broadcast tx 2 different things)
until windfury understand a signed payment channel is not a signed bitcoin transaction
until windfury understand the concepts of factories, watchtowers.
until windfury understands that what happens inside a channel is not a blockchain
until windfury understands the LN is not bitcoin
until windfury understands LN is not community audited, regulated, consensused
until windfury understands LN does not have the byzantine gnerals solution
until windfury actually spends more time researching LN before promoting it.

then there is no point

wind fury. lets get back to basics.
imagine just the bitcoin protocol
if there was a bitcoin signed tx. but it is never broadcast, never relayed never enters anyones mempool...
is it a settled transaction paid in full?

if someone wrote you a cheque for $1billion. its signed. but has not ben submitted to the banks to be cleared.
is it a settled transaction paid in full?

knowing channels are just 2 party, no community oversight. where if you paid me $1 i would open a channel with you to credit you with 2btc channel. (obviously ur happy with the deal as its me at risk, not you)
and due to the privacy stuff. the routers dont blockchain check every nodes balance. they just htlc request 'can you handle 2btc' to which you would say yes. alot of things can get messed up in LN.

you really need to go research this stuff and not just spout out the utopian sales pitch
424  Bitcoin / Bitcoin Discussion / Re: Agustin Carstens is more aggressive in rejecting crypto than Warren Buffet on: March 25, 2019, 07:27:11 PM
hey people
you lot do realise that agustin said about the bubble A YEAR AGO
right when there was a bubble spike in bitcoin

in short. old news. boring, outdated
425  Bitcoin / Bitcoin Discussion / Re: My friend told me a new concept Lightning Network, but I don't fully understand on: March 25, 2019, 04:36:29 PM
LN still has issues and a risk

recently a stunt was done t buy pizza using LN and it only had a 10% success rate (1500 attempts, 150 successes)
the main issues with LN which wont be solved easily/ever are as follows:

the sender, router(middlemen) and destination ALL need to be online for a payment to flow
to have an increased chance of payment flow users have to split up their value into multiple channels and hope to find a route between them and the destination
even at the payment success, the funds are not real blockchain confirmed/settled balance so still risks of loss of value
426  Other / Archival / Re: Found a burn address on: March 23, 2019, 01:31:49 PM
a burn address is an obvious address thats set up with such a lengthy address that there is no way anyone created it via vanity or private key

EG
a burn address would look like
1Burn1nhellmofothereaintanykey

here is a couple real examples
https://www.blockchain.com/btc/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr
https://www.blockchain.com/btc/address/1111111111111111111114olvt2

what i think the OP is doing is making a normal address and trying to cal it a burn address thinking people will throw coins into HIS address.
427  Bitcoin / Bitcoin Discussion / Re: How do you feel about control versus freedom in Bitcoin? on: March 23, 2019, 10:05:44 AM
again doomad you are ignorant of facts

firstly
controversial fork of august 1st 2017(apartheid analogy) was not to do with the actual activating segwit.
it was about disconnecting opposition

secondly
controversial fork of august 1st 2017(apartheid analogy) was not requiring the community nodes to do a dang thing
it did not need 9500 nodes to manually disconnect opposition..
it did not need majority do something to cause the controversial network affecting (aparthied analogy) bilateral split

can you stop pretending it was a 'individual freedom' where you had the choice of going into your node and disconnecting who you wanted. it would have still happened even if general community did nothing.

the purpose was to FAKE a majority by diluting the network to then cause the network to appear like segwit was in full agreement.

this kind of immoral control stuff is exactly what the problems with digital money pre millenium. and how it took satoshi nakamoto to  come up with a byzantine solution.. but now there is no byzantine generals(plurals) and things are now just a single general. the whole point of blockchains and decntralisation is lost. because consensus has now ben bypassed

the real MORAL flow of a consensus should be as follows
1. feature proposed.
2. users adopt or not
3. if adoption reaches a threshold it activates. if it doesnt reach a threshold it doesnt activate
4. the threshold should be high enough or have a waiting period for any laggers to update after activation threshold before the network change so that it doesnt cause much orphan drama
5. if orphan drama is noticable after network change then disconnect opposing nodes that are causing orphans

NOT
1. feature proposed
2. disconnect opposing nodes even before activation, even when they are not causing any orphan drama. but done so just to get feature activated at any cost
3. less nodes on network but those remaining are showing as agreeing.. certain blocks are rejected by fibre even before reaching main relay stream thus again making it appear as full agreement

try to learn why the cypherpunks got excited about satoshis byzantine generals solution.
try to understand why bitcoin WAS revolutionary and WAS decentralised.
i know you advocate that you prefer core control and love to defend the core devs

but put the core dev defense hat away and instead think for a few minutes. what if the core devs and their partners done the same 2017 tactics, not for segwit, but for a feature that would have killed bitcoin. knowing general nodes were acting just as sheep. where cores tactics only needed their fibre and their dns seeds and not the community to activate

bitcoin 2015-19 is not the same ethos as bitcoin 2009-2015

oh and as for your silly rant about
"You have a preconceived notion that "threshold" always means 95% hardfork."
1. no where have i said its always was, is , should be 95%.
the reason i mention 95% is because that was the threshold of bip9. which CORE USED and which CORE had to IMMORALLY disconnect nodes to fake achieving.
2. i never set the threshold as 95% i didnt choose/code/invent, i had nothing to do with 95% so go do some research next time.
3. again show me any code that makes you think im some authoritarian that produced a high threshold... hint i didnt
4. so stop trying to make it out that i am the nasty controller and authoritarian. when the only people that coded immoral consensus bypassing crap were the core devs
5. also a true consensus if majority threshold was reached MORALLY, it would not even be a "hardfork".. which just shows you really need to do some research
428  Bitcoin / Bitcoin Discussion / Re: How do you feel about control versus freedom in Bitcoin? on: March 23, 2019, 01:41:40 AM
"there is no vote"
well thats true now core have ways to bypass consensus

but bitcoin 2009-2017 was not always that way
2009-2015 consensus did function. there wer mutple brands on one network. none of them had mandated apartheid consensus bypassing code. it was a simpl reach a certain vote threshold and the proposed featur activates. if a feature didnt get the vote it wont activate

ya from 2015-2017 core slowly eroded away the consensus mechanism making nodes more like sheep with their "compatibility" consensus bypass stuff by not requiring nodes to upgrade to show opt-in/consent/vote to activate
and by knocking nodes opposing a core proposal off the network BEFORE a vote
so now that everything is core dev controlled (code, nodes, fibre, dns seeds) even a vote is not needed


so doomad by saying consensus(voting) doesnt exist, there is no thresholds needed anymore. no need for byzantine generals theory solution. thus admitting core are in control and decentralisation is dead.
(distribution vs decentralisation are 2 diffrent things)

and if doomad dares to flip flop to then say nothing gets activated unless majority vote to activate it.. then he is just flip flopping and being pedantic

doomad.. your flip flops are stupid
you say there is no vote and then say majority.(facepalm)

if there is no vote then there is no majority/threshold
dont then say there is consensus because you will ofcourse then say the network is permissionless and devs dont need consent

for months you keep flip flopping. atleast stick to one narrative
again stop flip flopping. stick to one narrative. admit core control the network. (no vote/no permission=nodes are just sheep)
429  Bitcoin / Bitcoin Discussion / Re: How do you feel about control versus freedom in Bitcoin? on: March 22, 2019, 10:59:48 PM
me uncivil??
if 'flip flop' is uncivil, then look at your own insults.

my authoritarian??
sorry but you mean you and cores authoritarian
show some code i wrote that changed the network
show a brand/client software i wrote
show a brand which i own that has the same command/control of the network to do inflight upgrades and consensus bypasses that core done...
(hint you wont find any)

you really have no clue

1. CORE done some immoral and consensus bypassing practices. not me
2. you first said you 'didnt agree' but then said you agreed (hence flip flop)
3. again writing code anyone can do it. writing it on github, writing it on the thigh of a blonde woman, write it on a napkin
BUT thats where you get pedantic with your chosen wording. because:
a. when what they wrote is not a feature upgrade that uses consensus. but a network split to remove opposition to a future vote of an upgrade... thus faking that future vote... thts a whole different story

b. they didnt just write it. they implemented it in such a way that it didnt need the network to agree to it
c. you say it didnt need a vote. then say 'users are free to use it and it wont do anything unless user agreement'... yet reality is the DEVS didnt need users for the network split (pre feature vote). they just needed fibre and dns seeds(which they controlled.. not the community)
d. if you think a dev should have enough control to change a network without the community consent then you have already denounced decentralisation. already denounced the whole point of blockchains, byzantine generals solution, denounced
user indepeendance

so
if you think its ok for a dev to implement code through their commercial team of fibre, dns seeds and NYA.. imagine the event happened the same method. but the future vote after the apartheid (controversial fork of opposition) was a feature that would ruin bitcoin. such as code that makes UTXO time out after 2 days and give funds to mining pools. or changed the block reward. or to make block 'gigabytes by midnight'

would you be so willing to let devs just kick opposition off the network to activate such features after by faking consnsus agreement vote of those features.

also
if your ok saying the community dont get a say/vote/choice. and shouldnt.. and how you will defend devs control.
then your saying you will defend thee shepherd because the network is just sheep
430  Bitcoin / Bitcoin Discussion / Re: How do you feel about control versus freedom in Bitcoin? on: March 22, 2019, 09:31:34 PM
in a different topic doomad show admiration for mandatory dated bans and was very loudly proud of their attempts to kill off 2x

Pretty sure I just said I'm not denying that incompatible nodes were disconnected.  Here's the rationale for it
....
 I agreed with it then and I agree with it now.

mmhmm.. u agreed that nodes should be disconnected 3 months BEFORE an activation of those nodes bips
mmhmm.. u agreed that nodes should disconnect BTC1  (Segwit2x) nodes 3 months before segwit2x activates

anyway. im done trying to translate ur flip flops. might be worth u doing some research on what bitcoin is all about and how bitcoin was invented to stay away from needing a "core"
and then maybe finally you can decide if ur a flip or a flop. and atleast stick with one narrative

..
as for writing code..
anyone can write code. they can write it on a napkin, a thigh of a blonde prostitute, write it in github. nothing stops anyon writing code.

but if those writing code have access to certain things where their code can cause network wide changes without the networks consent. then thats a different matter.

take the august 2017 events. it did not require 95% of the community to agree using a true open consensus.. it just required mattblue to add it to his fibre, thus the blocks that got relayed beyond fibre would all be missing old flags, thus faking agreement by simply not letting the mainnet community of nodes get opposing blocks
and as for node bans. adding certain stuff to the DNS seeds thus when nodes make connections they wont get a list of opposing nodes, thus have nothing to need to manually/individually disconnect

and if you want to deny that august first event didnt happen. check the IMMUTABLE blockchain
and if you want to deny that core struck first on august first. check the IMMUTABLE blockchain

core changed block flag/format at a certain block. and it wasnt for like 5 hours did the opposition react by getting their first block to start their own chain after cores actions

again core wrote the code. not some bitcoin AI. so please dont try now suggesting that some AI was involved or random users wrote the code or that the code just sprung out of nowhere. core wrote it. thy knew how to implement it and they used it to get segwit1x activated
and again it was not a case of ~9500 nodes agreeing.
431  Bitcoin / Bitcoin Discussion / Re: Why Bitcoin needs Segregated Witness on: March 21, 2019, 02:36:27 PM
9 years later and that benchmark has still not ben surpassed

While what you are saying is true, you have to admit that there are very few backward compatible solutions that Bitcoin could implement.
Of course, the network could (and probably should) reinvent itself entirely, as efficiency is clearly not its biggest strength. But it won't, because Bitcoin's popularity also gave it great inertia, and all changes have to both satisfy all parties AND can't allow the network to fork into pieces.

the thing is. the network DID controversially fork

there was a controversial hard fork in summer 2017, to get rid of opposition. to then fake approval for segwit to activate after the controversy

if devs were smart they would have used the controversial date to include extra features that could only be included using a controversial fork

the whole 'compatibility' ruse was not about network security but as a ploy to try and get segwit activated without having to reach the ultimate consensus %

..
but anyway. here is some funny facts
1. Sipa (pieter wuille) the innovator/dev of segwit still to this day does not trust his bitcoin donations on segwit bech32 addresses
http://bitcoin.sipa.be/  - bottom right of page -  1NrohbDoPkARCGdjvtnXbwFLwoBH86pskX

2. BTCC, the biggest bitcoin mining pool that sponsored advocated and promoted sgwit as being the best thing ever, did not trust bitcoin blockrewards to be put on segwit bech32 addresses
13TEThZNnKPk34HYAuo1QqYMwDdjF3qeHx
even its last block (543,040) used legacy
432  Bitcoin / Bitcoin Discussion / Re: Why Bitcoin needs Segregated Witness on: March 21, 2019, 01:09:37 PM
I like SegWit's idea of trying to relieve/alleviate the stress on the nodes and cramming more transactions in a block compared to the previous LBTC code,

it doesnt cram more transactions in. .
back in 2010 there was some math done and it was shown that bitcoins 1mb can fit 600k tx a day
9 years later and that benchmark has still not ben surpassed
also the wishy washy code of MISCOUNTING data does not make more transactions, it just fools a software rule into doing something. but at the hard drive storage of a full block of transaction data. the bytes per transaction of a segwit tx vs a legacy tx actually show a segwit tx uses slightly more bytes per tx

433  Economy / Service Announcements / Re: Circle.com is doomed on: March 21, 2019, 04:28:31 AM
circle is just a brand name /subsidiary of DCG.co

once you see all the stuff DCG.co are involved in you will see that circle itself doesnt have to be a powerhouse/ big player / asset itself, but just a brand/arm of a larger body

434  Bitcoin / Bitcoin Discussion / Re: Why Bitcoin needs Segregated Witness on: March 20, 2019, 09:06:52 PM
firstly
segwit has not fixed malleability.
it created a new TX format that people can use to (at the time) show they cannot perform malleability.
a. people could continue to use old legacy tx formats and still malleate
b. recently due to new feature needs. core devs introduced a new sighash opcode that actually allows segwit tx's to malleate again..

secondly
the wishy washy code of witness scale factor. does not actually give more transaction capacity per real hard drive storage bytes of full block data.
stripped blocks do not contain signature data to validate a tx is truly authentic. thus having a node storing stripped data is not a guarantee to hold valid data or a ability to relay full data to real full nodes. thus no point being a node messing with stripped data

thirdly
the purpose of segwit is actually to change bitcoin to have a new gateway tx format that would allow features to be done that would suit another network (LN)

fourthly
segwit was conceived to edit bitcoin to give bitcoin a doorway to an alternative network.
the other network was not edited to be purely bitcoin functional
the esssence is to eventually persuade users to de-burden themselves of using the bitcoin network and use another network. thus reduce bitcoin networks utility
435  Bitcoin / Bitcoin Discussion / Re: Bitmain Bitcoin mining equipment is expensive on: March 20, 2019, 08:48:09 PM
28terra hashes for $1200 is expensive?

dang
AMD-ATi GPU offers only upto 1gigahash, but charges $600+
if you want to mine without asics. it would cost you 28,000x $600 to GPU mine bitcoin

so is ATI's $16,800,000 for 28terrahash expensive..
or is asics $1200 for 28trrahash

i think ASICS are cheap
436  Bitcoin / Bitcoin Discussion / Re: How do you feel about control versus freedom in Bitcoin? on: March 20, 2019, 08:23:01 PM
"Is it wrong or immoral to create code that causes a client to disconnect another client from the network if the features they propose are not compatible?  Should users be allowed to disconnect incompatible clients if they want to?  Or is this a way to cheat consensus and deprive the users running that client of the chance to express their support for a change in the rules?  And, in this morality judgement, should we consider whether replay protection is included in the the client being disconnected if that means users can be safeguarded from replay attacks? "

code that is set to automatically ban nodes/reject blocks of an opposing brand on a certain date, by strategic nodes(thus not requiring all users to agree to the plan.
and doing so BEFORE the a future feature the code writers wrote even activates. is immoral

by this i dont mean a independant user decides to manually disconnect its peer, whereby the peer is then free to connect to someone else. i mean where a BRAND produces code that would cause a network affecting disconnect.

as it is the same as apartheid. banning black people from voting in a election only allowing certain demographs to vote.
where by only white supermisists only get a vote in the later actual vote
and same goes for the 'compatible' nodes (analogy mixed race) which dont get a actual vote, they are handed a voting card but treated automatically as abstainers and not counted. thus again faking consensus while given the illusion of being part of the community still

banning nodes AFTER activation. to reduce orphans, fine.
but doing a mandated apartheid banning threat before consensus is reached is immoral

as for "hardfork" at 95%
if 95% are running software that accepts a feature to allow activation. those 95% wont see/feel a fork. the 5% not running will just stall out at a certain block number (stall, not fork)(2013 leveldb) or would if 'compatible' be handed stripped/mutated/edited data to atleast get some resemblance of still bing part of the blockchain, though at a downgraded position than before.

however doing things such as a controversial hard fork/threatening behaviour before activation of feature. purely to get/persuade people into activating a feature, where an actual hard fork larger community participants will be affected prior to activation. is not the spirit of consensus agreement.

as odolvlobo says below. alternative brand clients would be advantageous. and if a feature was truly beneficial to the community alternative clients could easily agree on it as they would see/want the advantages too.
obviously without community agreement obviously the feature needs to be worked on a bit more before being accepted.

by only having one brand that deems themselves authority/reference/core part of the network to just activate stuff under whatever policy they please leaves the network at risk to low quality code activations and trojans/tactics that go against the very purpose of bitcoins invention. thus having an array of diversity is beneficial. and single branding is actually more of a risk
437  Bitcoin / Bitcoin Discussion / Re: What's to stop a 'Bitcoin 2' taking over... on: March 20, 2019, 11:38:27 AM
Extremely limited supply cap (such as the 42 coin and One coin) ultimately defeats bitcoin in terms of rarity, but that does not make them better coins in any way. Also, fancy features found on a coin and 100% anonymity does not guarantee a coin to get the lion's share of the market. At the end of the day (at least at these current days), speculative purposes and market activity is what entices people to buy whichever coin they want. Bitcoin gets the huge market share over any other altcoins out there but its features are somewhat behind over the current altcoins that devs are introducing, so again, cool features and rarity does not guarantee an altcoin a spot at the top when it comes to market share.

i prefer my analogy better.
my dog does 1 poop a day and will live 12 years average. thats a rarity of 4380 poops ever to be avaiable.
that makes my dogs poop worth 4795x more then bitcoin. lets start the bids. who wants a bag of poop for $19m. any takers

rarity and perceived value based purely on rarity does not give something real value.
function/utility/purpose gives it value. and its the desire of multiple people wanting it that gives it value.

if people start seeing it as too expensive to handle, slow/heavy boring. and they find something else fastr/cheaper mor useful. then value dies of the first thing.
(myspace vs facebook, aol vs skype)

the main thing that can actually kill bitcoin and promote another coin is if merchants/exchanges start shifting away from bitcoin and promote altcoins. EG merchant shopping cart tools drop btc and only accept LTC

take 2017
imagine if all the NYA agreement srvices (bitpay, coinbase, multiple exchanges) decided to not support cores segwit thus not support bitcoin. and instead would only support litcoin
soon enough people holding bitcoin wont find services/merchants or ways to spend their btc. so btc would lose value. mining pools will realise they dont have exchanges to swap their btc for fiat. so drop their hashrate and pool hop to an altcoin that is exchange acceptable

in essense its not about 'faith' that bitcoin has value du to rarity or being first or having value just for sake of value. its actually UTILITY/SPENDABILITY
438  Bitcoin / Bitcoin Discussion / Re: Bitmain Bitcoin mining equipment is expensive on: March 19, 2019, 11:32:38 PM
Bitmain was facing multiple lawsuits, that's why they hiked up the miner's price to pay off the debt.

https://go.daneel.io/news?s=bitmain-mined-crypto-for-its-own-benefits-on-devices-owned-by-the-customers
article errors
1. samson MOW(not chow). of previous fame. the mining competitor BTCC which is now dead due to BTCC failures of their own IPO to DCG

2. everyone know asics go through a QC testing phase of being run for a while before shipping. this is not new or exclusive to bitmain. even other manufacturers did it.

3. the cost of manufacturing asics is not that high. so they did not sell at a loss

4. insinuating TSMC sold all its BM1397 chips to apple,samsung etc is a complete falacy.
ASIC chips are designed for one purpose. you cant just take a BM1397 chip and give it to a phone company and then the phone company use it for another purpose.. ASICS are ASICs because they are ASICS
the BM1397 chip is a specific chip for bitmain mining bitcoins PoW. it does no other job, thus useless for cell phone companies

5. TSMC only making enough chips for 1000 rigs.. thats a pretty low minimum order.. even that sound suspiciously false
439  Bitcoin / Bitcoin Discussion / Re: Do you run a Core node? One of the users here thinks you're a sheep. on: March 19, 2019, 10:41:03 PM
nodes did not need to upgrade to segwit in summer 2017!!

core made it so nodes that dont upgrade are handed a stripped block
thus nodes did not need to upgrade to give permission

again your amnesia has made you forget your admiration flop of loving the "compatibility" fix they done
core devs didnt need 9500+ nodes to go into the debug/console to RKT out opposition.
core devs had their own strategic nodes to handle it. again nodes didnt need to do anything

core even made it so pools didnt need to upgrade their nodes. all they had to do is change a version number in their block id even while running old nodes just to stay on the network

segwit 1x got activated without needing true consensus because core CODED a way to bypass true consensus for the summer 2017 event

dang your flip flop amnesia is playing you up

what YOU dont understand is bitcoins byzantine generals theory solution of consensus 2009-2015.. had slowly got eroded down. and by summer 2017 core was able to totally bypass it without users vote

...
what you dont understand is bitcoin lost its open diversity and multiple brands working on the same level playing field of true consensus.

devs are happy to admit as much. they are totally happy showing off their involvement. so i see no reason why you have to try insinuating they were not involved..

bitcoins revolutionary decentralised network ethos of 2009+ is not the same as bitcoins distributed core centric network of 2017+
i really think its time you either take the core defense hat off.. coz they dont need you wearing it. or you need to update your research beyond the echo's of promo material handed to you 4+years ago


EDIT to address the post below instead of spamming the topic

about the stripped blocks and downstream/bridged/filtered nodes
Also, you should be thankful.  The way in which is was implemented means you're free to stay on the same chain and keep taking full advantage of the security and utility of Bitcoin.  Way to keep bitching about your freedom to coexist, though.  Doesn't make you sound like an entitled ingrate at all.   Roll Eyes

1. nodes getting stripped blocks are not getting full block data. they are also not part of the main relay stream. its why they dont get unconfirmed segwit transactions to relay. its why they dont get witness data to validate a segwit tx is valid,
its why thy dont relay blocks to other nodes (because segwit nodes would not accept a stripped block

2. they are NOT taking full advantage of the security and utility of the network because they are not fully validating the blocks they are just giving transactions a pass without independent validation and just treating is as a pass because thats how the code has been wrote. and guess who wrote the code, core..

3. bitnodes.earn.com suggests over 10k nodes. but do you realise that less than 7k nodes are part of the full validation/ relay stream of nodes(and i am not talking about 30%+ spv/lit nodes either, im talking about 30% of nodes that were/meant to be/have been full validation nodes.. but are not)

4. your flip flopping how the way segwit was activated was a way to have certain nodes stay on the same network even when they didnt upgrade their node to say they were able and ok with segwit. (thus hypocritically admitting 95% true consensus was not reached, but making it sound like a good thing)

but those nodes didnt get a vote in a true consensus. you dug yourself a hole.. by you trying to twist the bypass into a positive you actually admitted the negative.

think of the logic. how can 70% being full relay/validation capable and showing readiness for segwit AT MOST NOW(so lower numbers then) have contributed to a 95% agreement..
dont you get it. 30% of nodes allowed to stay but not part of the main relay stream means 30% abstain...which is not 95% agree.. and back then the numbers would have been less that 70% ready, meaning higher than 30% abstain/not agree. and if you did include the nodes that got kicked off(total objection) the number would have been even worse where there would have been more like a 50% non agreement

again not near a 95% full community agreement..

5. you also want to pretend history is different 'because core said that' (facepalm) now your sounding worse than just a echo chamber repeater.
maybe you have to realise that 'those securing the network' is not 95% of the whole community of nodes that were told they were still 'full nodes' even if they dont upgrade.
maybe you have to realise that 'those securing the network' is a much lower number then you think. as its definitely not the 10k nodes of bitnodes.earn.com.
core messed with the 95% rule and done a few different tricks such as NYA and bip 148 and other things with strategic nodes

6. i find it funny how you try to down play the controversy of 2017 to sound like it is just me alone that was some big massive influencer/objector, decision power.. yet atleast 30-50% of the network found segwit1x controversial and not 5%
also me having an opinion on a forum is discussion. you keep saying how i pretend cor needed my permission. again as if your trying to push that i am some big player.. again your exaggerating social drama..
i am voicing my opinion on a discussion forum and also reminding people of what actually happened in regards to the 2017 controversy. you are the own trying to twist the power play around to try making core sound innocent and then double twist to make it sound like there were only a couple objectors.

my opinion, is simple. node statistics. code and even some devs willful admissions
 without a full unprovoked, un wishy washy, untricked game playing, true consensus. core would not have got 95% for segwit1x activation using a real consensus mechanism in summer/autumn 2017
core would have had to have gone back to the drawing board and recode something that would have been more community acceptable.
but core didnt. instead they done their tricks and used thier strategic nodes to fake a 95% acceptance

even the segwit2x part which you were very vocal about celebrating. was not down to 10k nodes (lets say9500) all independently going in and upgrading and saying lets ban thousands of segwit2x nodes to prevent 2x activation
again it was only a few strategic nodes that done that.

7. saying core done it as a softfork.. is funny..
core actually instigated a controversial hardfork in summer 2017. to gain control of the network to then have enough control to be able to then soft/inflight upgrade the network autumn+ 2017
atleast wake up to reality.

8. and before you flip flop again. the nodes that are on the network are not on the same level playing field in regards to validation/relay. infact the number is far less than 70% are at the main relay/validation stream layer
you might want to do some research
(and im not taling light/spv either before you insinuate)
440  Bitcoin / Bitcoin Discussion / Re: Do you run a Core node? One of the users here thinks you're a sheep. on: March 19, 2019, 10:05:36 PM
Core need the community's permission to do what?  Answer the question.  

pre CORE changing the rules of consensus and doing the consensus bypass. (pre summer 2017)
core needed communities permission to ACTIVATE a feature..

as displayed by them only getting 35% spring 2017. which they hated.

but instead of going back to the drawing board and coding something else that would have got community permission (consensus) by offering something the majority would upgrade to

they instead stuck with the same feature and instead changed how consensus should be reached by doing the compatibilty bypass and the mandated strategic nodes to kick off blocks/opposition and fake choic of a fake option for sgwit2x to fake a consensus activate segwit1x. by which users were not needing to upgrade 95% to segwit1x to give permission (compatiblilty and aparthied ensured that segwit1x would activate at lower)

and now the network is unopposed due to fear of being regulated off the network in rkt campaigns. core can do as they please

and please dont try insinuating that i am the only opposer
and please dont try insinuating 9500 nodes all manually banned nodes and rejected blocks
and please dont try insinuating it required 9500 nodes to al upgrade to segwit1x

atleast do some research on cores code tricks to win core dominance

which is why now core can do as they please due to 'compatibility' and their strategic nodes and people are now just sheep
(the only insult you can find i mentioned) unlike your insult onslaught.

P.S devs dont need defending to pretend they dont control the network. they are more than happy to admit it. Luke certainly loves his 'inflight upgrades' and his involvement in the mandated stuff
sipa and gmax loved adding in bc1q tx formats spring 2018 without require network permission

so try giving the defend core dev stance a rest. they are happy that opposing node brands would be rekt off the network or stripped down to downstream/filtered nodes instead of being part of the real consensus relay stream part of the network
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 [22] 23 24 25 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 ... 822 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!