Re: [bitcoin-dev] A Small Modification to Segwit

On 04/09/2017 05:20 PM, Erik Aronesty via bitcoin-dev wrote: > Have you read the cuckoo cycle paper? Finding cycles in massive graphs > is just about the worst thing to use an ASIC for. It's actually the best thing to use an ASIC tightly coupled with DRAM for - for example, HBM and HBM2 which

Re: [bitcoin-dev] A Small Modification to Segwit

Have you read the cuckoo cycle paper? Finding cycles in massive graphs is just about the worst thing to use an ASIC for. It might be a hitherto before unknown emergent property of cryptocurrencies in general that POW *must* change every 7-9 years. Could bake that into the protocol too... On

Re: [bitcoin-dev] A Small Modification to Segwit

On Apr 9, 2017 7:00 PM, "Jared Lee Richardson via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: I can speak from personal experience regarding another very prominent altcoin that attempted to utilize an asic-resistant proof of work algorithm, it is only a matter of time before the

Re: [bitcoin-dev] A Small Modification to Segwit

I can speak from personal experience regarding another very prominent altcoin that attempted to utilize an asic-resistant proof of work algorithm, it is only a matter of time before the "asic resistant" algorithm gets its own Asics. The more complicated the algorithm, the more secretive the asic

Re: [bitcoin-dev] A Small Modification to Segwit

Curious: I'm not sure why a serious discussion of POW change is not on the table as a part of a longer-term roadmap. Done right, a ramp down of reliance on SHA-256 and a ramp-up on some of the proven, np-complete graph-theoretic or polygon manipulation POW would keep Bitcoin in commodity hardware

Re: [bitcoin-dev] A Small Modification to Segwit

Jorge, Why won't the attacker use asicboost too? (Please don't say because of > patents) > > We're assuming the ASIC optimization in my example is incompatible with ASICBoost. But if the new optimization were compatible with ASICBoost, you're right, the network would be in an equivalent situation

Re: [bitcoin-dev] A Small Modification to Segwit

Why won't the attacker use asicboost too? (Please don't say because of patents) On 9 Apr 2017 12:26 am, "Jimmy Song" wrote: > Jorge, > > Suppose someone figures out an ASIC optimization that's completely > unrelated that gives X% speed boost over your non-ASICBoosted >

Re: [bitcoin-dev] A Small Modification to Segwit

On 8 Apr 2017 8:31 pm, "praxeology_guy via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: There is the equation: Power Cost + Captial Rent + Labor ~= block reward + fees I don't know why many people insist on calling the subsidy the blick reward. Thw block reward is both the block