sipa changed the topic of #bitcoin-wizards to: This channel is for discussing theoretical ideas with regard to cryptocurrencies, not about short-term Bitcoin development | http://bitcoin.ninja/ | This channel is logged. | For logs and more information, visit http://bitcoin.ninja
zzyzx is now known as Guest94951
Tiraspol has joined #bitcoin-wizards
Tiraspol has joined #bitcoin-wizards
JackH has quit [Remote host closed the connection]
oleganza has quit [Quit: oleganza]
oleganza has joined #bitcoin-wizards
Dizzle has quit [Quit: Leaving...]
oleganza has quit [Ping timeout: 250 seconds]
darmou has joined #bitcoin-wizards
sausage_factory has joined #bitcoin-wizards
blackwraith has quit [Ping timeout: 264 seconds]
AusteritySucks has quit [Ping timeout: 250 seconds]
Guest94951 has quit [Quit: ChatZilla 0.9.92 [SeaMonkey 2.39/20151103191810]]
mihar_ has quit [Remote host closed the connection]
roidster has joined #bitcoin-wizards
roidster is now known as Guest22421
mihar has joined #bitcoin-wizards
Guest22421 is now known as roidster
JackH has joined #bitcoin-wizards
tachys has quit [Remote host closed the connection]
AusteritySucks has joined #bitcoin-wizards
mihar has quit [Remote host closed the connection]
Emcy has quit [Read error: Connection reset by peer]
Emcy has joined #bitcoin-wizards
wumpus has quit [Ping timeout: 256 seconds]
wumpus has joined #bitcoin-wizards
dEBRUYNE has quit [Read error: Connection reset by peer]
dEBRUYNE has joined #bitcoin-wizards
atgreen has quit [Remote host closed the connection]
dnaleor has quit [Ping timeout: 264 seconds]
veleiro has quit [Ping timeout: 250 seconds]
ghtdak has quit [Ping timeout: 256 seconds]
ghtdak has joined #bitcoin-wizards
bityogi has joined #bitcoin-wizards
dnaleor has joined #bitcoin-wizards
dnaleor has quit [Remote host closed the connection]
dnaleor has joined #bitcoin-wizards
tjader has quit [Ping timeout: 240 seconds]
tjader has joined #bitcoin-wizards
erasmospunk has joined #bitcoin-wizards
<adam3us>
so i have been musing if one can create a new upgrade mechanism that is safe & fast, but protects old full nodes from funds loss on weak hashrate chain. this upgrade mechanism itself maybe deployable via firmfork (which forces SPV client upgrade) or possibly by hardfork which may not force SPV client upgrade.
<adam3us>
it seems that part of the challenge is for safety hard-forks if used at all should be deployed well in advance. and yet future network capacity and decentralisation headroom is uncertain.
merlincorey has quit [Changing host]
merlincorey has joined #bitcoin-wizards
GAit has quit [Quit: Leaving.]
mihar has joined #bitcoin-wizards
RoboTeddy has quit [Read error: Connection reset by peer]
RoboTeddy has joined #bitcoin-wizards
<MRL-Relay>
[othe] why not just plan sheduled mandatory upgrades, once or twice a year?
tachys has joined #bitcoin-wizards
mrkent has joined #bitcoin-wizards
<adam3us>
[othe] funds loss risk
<adam3us>
for example if fullnodes treated as an empty block devoid of transactions (except for coinbase) any block versions that are higher than it understands, we get a backwards compatible to SPV node firm fork. that means a fullnode would not accept payment, and miners would orphan (soft-fork) any blocks created on the old version
<adam3us>
in this way, we could have a safe fast upgrade when consensus exists for it.
tjader has quit [Ping timeout: 272 seconds]
<MRL-Relay>
[othe] in monero too old nodes stop working (1 year currently), you are forced to upgrade, even if there was no protocol changes
<kanzure>
adam3us: forcing spv clients to stop seems like a dangerous precedent because then you need only the miners to deploy that.
<kanzure>
funds loss is not the only form of security issue for old full nodes on old chain
<kanzure>
mandatory updates are not possible in this system without extreme regulatory burden
<kanzure>
other problem is that coinbase transactions will still occur on old chain, so you end up with double minting
coinoperated has quit [Ping timeout: 256 seconds]
<kanzure>
adam3us: i suspect we should start first with describing the full range of problems, instead of one-at-a-time. by thorough enumeration of the system incompatibilities with a hard-fork, we can get a better understanding of what we're up against.
mrkent_ has joined #bitcoin-wizards
zooko has quit [Read error: Connection reset by peer]
dEBRUYNE has quit [Ping timeout: 256 seconds]
mrkent has quit [Ping timeout: 250 seconds]
<adam3us>
kanzure: "forcing spv clients to stop" it's the reverse: stop non-upgraded fullnodes but keep SPV nodes (as are anyway trusting miners, who are in turn held to account by economic full-nodes)
raedah has quit [Ping timeout: 264 seconds]
<kanzure>
"and miners would orphan (soft-fork) any blocks created on the old version" this would require eternal mining i think.
copumpkin has joined #bitcoin-wizards
GAit has quit [Quit: Leaving.]
<adam3us>
it's not merge-mining, just that version 4 block miners would consider version 3 blocks invalid and orphan them
trakinas has quit [Read error: Connection reset by peer]
murch has joined #bitcoin-wizards
<kanzure>
on a broader note (not directed at adam3us' recent messages), even uncontroversial hard-forks are going to have many many safety and security concerns for live migration of a system of this scale. focusing on the concerns of a controversial hard-fork seems sort of silly, since non-controversial hard-forks seem easier to consider and yet also sharing many of the risks and problems (which are only elaborated in the controversial case).
GAit has joined #bitcoin-wizards
blackwraith has joined #bitcoin-wizards
priidu has quit [Ping timeout: 272 seconds]
phiche has joined #bitcoin-wizards
GAit has quit [Read error: Connection reset by peer]
GAit has joined #bitcoin-wizards
blackwraith has quit [Ping timeout: 240 seconds]
Linus_ has joined #bitcoin-wizards
Emcy has quit [Read error: Connection reset by peer]
Emcy has joined #bitcoin-wizards
Emcy has quit [Changing host]
Emcy has joined #bitcoin-wizards
ThomasV has joined #bitcoin-wizards
dEBRUYNE has joined #bitcoin-wizards
tjader has quit [Ping timeout: 240 seconds]
Guyver2 has joined #bitcoin-wizards
tjader has joined #bitcoin-wizards
erasmospunk has quit [Remote host closed the connection]
ebfull has joined #bitcoin-wizards
justanotheruser has quit [Read error: Connection reset by peer]
rusty2 has joined #bitcoin-wizards
justanotheruser has joined #bitcoin-wizards
psztorc has joined #bitcoin-wizards
<psztorc>
@adam3us > so i have been musing if one can create a new upgrade mechanism that is safe & fast, but protects old full nodes from funds loss on weak hashrate chain
<psztorc>
I was having a similar idea...my goal was to make it so that the network can easily change PoW, without the need of a programmer, or of anyone needing to do anything.
<kanzure>
that sounds a lot like having nothing happen at all :)
<psztorc>
My solution was a predetermined list of PoW-functions...if you couldn't find enough blocks in x=8 hours, it would start watching the current PoW-function, in addition to looking for blocks on the next PoW-function.
<kanzure>
i suspect that we will find that it is important to have a high threshold for difficulty of computing a certain proof-of-work output vs. the difficulty of changing the proof-of-work algorithm
bsm117532 has quit [Remote host closed the connection]
<psztorc>
It falls into the "have network respond to sudden drop in hashrate" category.
<kanzure>
if the purpose of a pre-determined proof-of-work function list is to prevent mining centralization, then i would submit to you that larger miners are always going to have more resources to pursue the entire list
<psztorc>
@kanzure I explained what the purpose was...
<psztorc>
feel free to scroll up and read it again.
<kanzure>
"change pow" is not a purpose.
<psztorc>
"change pow" *is* a purpose, but not the purpose I stated.
<psztorc>
Quit trolling me.
<kanzure>
if you mean "have network respond" quote, then i'm not sure what scrolling was about... still looking.
<kanzure>
also, it seems fair for me to guess that you might have had the purpose of preventing mining centralization, since this is sometimes what others are intending when they propose a list of hash functions. i understand this is not your purpose but since i am having such a tremendously hard time finding the text that you are referring to, it seems fair for me to point out where the misunderstanding originates from (in addition to the ...
<kanzure>
... frantic scrolling).
* nsh
hands out cookies and goodwill
<psztorc>
Ugh
<psztorc>
Almost every time I come here I regret it.
bsm117532 has joined #bitcoin-wizards
earthris1 has quit [Quit: leaving]
<psztorc>
As you are no doubt aware, it has been suggested that Bitcoin Core might need to change it's PoW function.
<kanzure>
i guessed your purpose was x, you said "it's not x", then you called me a troll while i'm scrolling around looking for your stated purpose... geeze.
earthrise has joined #bitcoin-wizards
<psztorc>
In the even that a large majority of mining power existed on Classic or something else.
<psztorc>
However, there is a tiny problem with this, in that there are a few moments of "hangtime" where individuals would have to [1] decide which PoW-f to use [2] code it up without introducing bugs and [3] get the software installed everywhere.
belcher has joined #bitcoin-wizards
<kanzure>
new-pow bootstrapping procedures are also under-determined at the moment. most proposals made in the open would be immediately scooped by botnet operators, unfortunately. but perhaps botnet operators would be better behaved.... maybe.
<psztorc>
Of course, users would need to wait for many confirmation, after a PoW change.
<psztorc>
But that is not specific to the _way_ in which the PoW is changed.
<belcher>
does anyone know why p2pool isnt used more in bitcoin? is it a software problem with p2pool itself or is it just that most of the asics are owned by theirs manufacturers who dont need a pool
<kanzure>
belcher: one of the reasons why p2pool isn't merged into bitcoin core is because p2pool is python.
<psztorc>
Moreover, a threat only _succeeds_ if you don't need to carry it out.
<bsm117532>
belcher: I've been trying to understand that, and AFAICT it stems from a lot of misunderstandings.
<bsm117532>
Also it has higher payout variance than centralized pools, I think.
<belcher>
bsm117532 right, because centralized pools can pay per regular time interval ?
Giszmo has quit [Quit: Leaving.]
<psztorc>
One reason is that I don't think P2Pool really _does_ anything.
<psztorc>
It is a very clever idea, but you can already point your miner at a different pool at any time.
<kanzure>
belcher: no.
<psztorc>
Anyway, my solution would help to respond to the loss of hashpower for _any_ reason, while still (I think) being resistant to most of the security vulnerabilities that were introduced by previous attempts.
<psztorc>
This includes any hashrate collapse which might occur as a direct and sole result of the blockreward-halving, as previously discussed.
Misterate has joined #bitcoin-wizards
mihar_ has joined #bitcoin-wizards
mihar_ has quit [Remote host closed the connection]
mihar_ has joined #bitcoin-wizards
mihar_ has quit [Client Quit]
Misterate has quit [Remote host closed the connection]
mihar has quit [Ping timeout: 264 seconds]
markus-k has joined #bitcoin-wizards
Misterate has joined #bitcoin-wizards
Giszmo has joined #bitcoin-wizards
kang_ has quit [Quit: Page closed]
bsm117532 has left #bitcoin-wizards [#bitcoin-wizards]
Misterate has quit [Remote host closed the connection]
Misterate has joined #bitcoin-wizards
rusty2 has quit [Ping timeout: 276 seconds]
yosso has joined #bitcoin-wizards
Misterate has quit [Remote host closed the connection]
zorba_tg has joined #bitcoin-wizards
binns has quit []
<zorba_tg>
psztorc: A drop in block rate could be a result of other scenarios, not only hard fork
Linus_ has quit [Ping timeout: 240 seconds]
Misterate has joined #bitcoin-wizards
zorba_tg has quit [Ping timeout: 240 seconds]
yosso has quit [Ping timeout: 272 seconds]
moa has joined #bitcoin-wizards
<psztorc>
zorba_tg: Indeed. Do you think that all such scenarios are undesireable? If the miners don't mine enough for the network to make it to the next difficulty adjustment, they have failed the users.
<psztorc>
Yet, users can't do anything about it, because they lack esoteric specialized hardware.
tjader has quit [Ping timeout: 276 seconds]
AaronvanW has quit [Ping timeout: 250 seconds]
tjader has joined #bitcoin-wizards
<psztorc>
Let me clarify that my idea is similar to adam3us 's in some ways, but exactly the opposite of it in others.
<psztorc>
It tries to force Upgrade Only With Overwhelming Consensus in more of a mean way than a nice way.