@NewtonProtocol #Newt
The part that kept irritating me on Newton was not the challenger.
It was slashing path sitting there all formal and untouched. Like diagram solved courage too.
That part always ages badly.
Alright...
Because Newton can do its side of it. Operator network misbehaves. Challenger exists. Slashing path exists. On paper, accountability is there. Fine. Operator failure is punishable. Very clean.
Early quorum exit already gave desk a clean Newton result.
Then the humans show up.
A bad operator result lands. Or a dirty one. Or just one that smells wrong enough that somebody should push harder. But now it's not only a Newton protocol problem. Now it's one desk deciding whether to light up a Newton's slashing path that drags in counterparties, signatures, blame. whatever.
Live politics. Different slashing path.
I know that Newton pause.
Everybody likes slashing right up until a real name has to pull it.
That's the split.
Newton kept the punishment path ready.
Nobody wanted to be first.
Then workflow starts doing the usual little coward thing. Ask for one more review. Wait for one more signal. Let operator result sit. Let capital move. Okay.
Vault curator goes quiet.
Operator result just sits there.
Aggregate BLS came back clean. Challenger? Idle.
That Newton Protocol quiet again.
By the time somebody asks for exact Newton rule path, challenger is still there, slashing is still there, and live minute to pull it is already rotting.
Challenger still idle.
I've seen that Newton hesitation get buried in plain sight.
Challenger there.
Nobody wanting to own first pull.
Little late.
Because once Newton already responded, slashing stops feeling like control. Starts feeling like escalation. And desks are always brave about slashing in diagrams. Less brave when the operator network is live and somebody has to own what happens after the first pull.
Beautiful on paper.
Bad stomach for first pull.
So what exactly was live on @NewtonProtocol ?
The slashing path.
Or just the hope somebody else would pull it first?
#newt $NEWT $ARPA $LAB
The part that kept irritating me on Newton was not the challenger.
It was slashing path sitting there all formal and untouched. Like diagram solved courage too.
That part always ages badly.
Alright...
Because Newton can do its side of it. Operator network misbehaves. Challenger exists. Slashing path exists. On paper, accountability is there. Fine. Operator failure is punishable. Very clean.
Early quorum exit already gave desk a clean Newton result.
Then the humans show up.
A bad operator result lands. Or a dirty one. Or just one that smells wrong enough that somebody should push harder. But now it's not only a Newton protocol problem. Now it's one desk deciding whether to light up a Newton's slashing path that drags in counterparties, signatures, blame. whatever.
Live politics. Different slashing path.
I know that Newton pause.
Everybody likes slashing right up until a real name has to pull it.
That's the split.
Newton kept the punishment path ready.
Nobody wanted to be first.
Then workflow starts doing the usual little coward thing. Ask for one more review. Wait for one more signal. Let operator result sit. Let capital move. Okay.
Vault curator goes quiet.
Operator result just sits there.
Aggregate BLS came back clean. Challenger? Idle.
That Newton Protocol quiet again.
By the time somebody asks for exact Newton rule path, challenger is still there, slashing is still there, and live minute to pull it is already rotting.
Challenger still idle.
I've seen that Newton hesitation get buried in plain sight.
Challenger there.
Nobody wanting to own first pull.
Little late.
Because once Newton already responded, slashing stops feeling like control. Starts feeling like escalation. And desks are always brave about slashing in diagrams. Less brave when the operator network is live and somebody has to own what happens after the first pull.
Beautiful on paper.
Bad stomach for first pull.
So what exactly was live on @NewtonProtocol ?
The slashing path.
Or just the hope somebody else would pull it first?
#newt $NEWT $ARPA $LAB