I was playing around on @NewtonProtocol VaultKit with a simple reallocate request. I thought it will work right away, but Newton rejected it flat. My first gues was a nonce issue, because that happens alot on blockchain.
I sent the exact same request again. Same amount, same vault, sam target. This time Newton accepted it without any issue. Thats when I realized the real problem was not the action itself.
The approval had already expired, not because of time, but due to Oracle Price Slippage. The price feed shifted slightly in background, and the state changed just enough to break the signature.
After diging more, I understood that VaultKit works on an Intent-Based Architecture. Every approval is bound to one exact intent, the vault, amount, and state all get locked into the signature. Change even a small thing, or let the oracle data move a bit, and you need a fresh approval. No shared permission works here.
I only tested this few times, so maybe my understanding is off. But it made me wonder how Newton handles fast reallocations when market gets crazy. With Newton, each move demands its own fresh approval, no batch signing. It feels strict, but thats also what keeps every VaultKit action separate and secure. I think Newton is built this way for safety, even if it makes quick trading harder for people like me.
#VitalikOutlinesLeanEthereumRoadmap
#UKFCAPublishesCryptoRegFramework
$LAB $VANRY $NEWT
I sent the exact same request again. Same amount, same vault, sam target. This time Newton accepted it without any issue. Thats when I realized the real problem was not the action itself.
The approval had already expired, not because of time, but due to Oracle Price Slippage. The price feed shifted slightly in background, and the state changed just enough to break the signature.
After diging more, I understood that VaultKit works on an Intent-Based Architecture. Every approval is bound to one exact intent, the vault, amount, and state all get locked into the signature. Change even a small thing, or let the oracle data move a bit, and you need a fresh approval. No shared permission works here.
I only tested this few times, so maybe my understanding is off. But it made me wonder how Newton handles fast reallocations when market gets crazy. With Newton, each move demands its own fresh approval, no batch signing. It feels strict, but thats also what keeps every VaultKit action separate and secure. I think Newton is built this way for safety, even if it makes quick trading harder for people like me.
#VitalikOutlinesLeanEthereumRoadmap
#UKFCAPublishesCryptoRegFramework
$LAB $VANRY $NEWT