For fifteen years, blockchain has treated a valid signature as the final proof of intent. Newton ProtOcol separates authentication from authorization.
i found the exact mechanism inside Newton that makes a stolen seed phrase not enough by itself anymore.
you set a threshold. below it, your signature alone still moves funds, same as any wallet today. above it, Newton's policy engine requires something more before the transaction can execute.
not instead of your key. in addition to it.
the flow runs signature, then second factor, a bound device, a passkey, a biometric check, or a session key depending what you configured, then a threshold check confirms the conditions actually match what you set. only when all three align does Newton issue an attestation. no attestation, no execution. the vault action simply does not go through.
that ordering is the part i keep coming back to.
someone phishing your seed phrase still walks away with a valid signature. Newton's authorization layer does not care that the signature is valid. it checks whether the second factor and the threshold condition are also satisfied, and if either one is missing, the attestation never gets issued.
the key was always the entire lock in self custody. one factor, full control, one point of failure.
Newton does not take that control away. you still hold the key, the wallet is still yours, nothing here is custodial. what changes is that past the line you drew, the key alone stops being sufficient.
a stolen key with no second factor now hits a threshold check it cannot pass.
@NewtonProtocol #Newt $NEWT
i found the exact mechanism inside Newton that makes a stolen seed phrase not enough by itself anymore.
you set a threshold. below it, your signature alone still moves funds, same as any wallet today. above it, Newton's policy engine requires something more before the transaction can execute.
not instead of your key. in addition to it.
the flow runs signature, then second factor, a bound device, a passkey, a biometric check, or a session key depending what you configured, then a threshold check confirms the conditions actually match what you set. only when all three align does Newton issue an attestation. no attestation, no execution. the vault action simply does not go through.
that ordering is the part i keep coming back to.
someone phishing your seed phrase still walks away with a valid signature. Newton's authorization layer does not care that the signature is valid. it checks whether the second factor and the threshold condition are also satisfied, and if either one is missing, the attestation never gets issued.
the key was always the entire lock in self custody. one factor, full control, one point of failure.
Newton does not take that control away. you still hold the key, the wallet is still yours, nothing here is custodial. what changes is that past the line you drew, the key alone stops being sufficient.
a stolen key with no second factor now hits a threshold check it cannot pass.
@NewtonProtocol #Newt $NEWT