Last month my sister needed to apply for a mortgage. The bank told her to prepare bank statements from nearly three years. She ran to two branch offices; each teller printed a stack of A4 pages for her. On the bottom-right corner of every page, a red stamp was placed, and the timestamp was precise to the minute.
She brought the stack of papers back. The first thing she did was put them in a transparent document sleeve and store them in the home safe. I asked her whether these wouldn’t be the same as what the counter could print later—haven’t they already been stamped? She said it wasn’t like that. The teller told her: every time the documents are printed, it’s that exact moment’s copy. The stamp number and timestamp are unique. If you lose it, the bank won’t give you a second, identical copy. For later audit and review, they only recognize that one.
I watched her put the document sleeve into the safe and just stood there for a moment.
Later, when I flipped through the section about <c-1/> @NewtonProtocol in the whitepaper compliance evidence, the image that came to my mind was exactly that transparent sleeve.
Every time Newton finishes an authorization decision—every single transfer, every time it evaluates a strategy—it generates a cryptographic record on the spot. In the record, it binds: what transaction this was, which strategy was used for the evaluation (which CID), who the participating nodes were, what the aggregated signature is, and what the block height was. It all exists in an on-chain contract called TaskManager.
Just like my sister’s stack of bank statements—what feels unnecessary at the time can be pulled out when you need it.
When regulators want to check why this transfer was authorized back then, there’s no need to dig out the user’s identity information. They can simply pull the proof from the blockchain to verify directly: the strategy was indeed evaluated at that time point, the evaluator was among the nodes that had staked, and it signed.
The challenge mechanism needs it too. If someone suspects the evaluation result at the time was wrong and wants to complain, the on-chain credential is the original evidence.
In traditional finance, many compliance issues aren’t that no review is done. It’s that even when review happens, the evidence isn’t kept clearly. Later, you can’t find the papers when you go back to search the archives—or the internal systems have been updated and the versions don’t match the rules from then. That’s where the arguing starts. Newton engineers this: during evaluation, it fixes the evidence immediately, leaving no room for adding records later.
Before my sister put that stack of statements into the safe, she told me that if you did something, you should leave behind a tangible thing.
Leave a record—if you don’t need it, it’s a wasted record; but if you do need it, not a single page can be missing.
@NewtonProtocol $NEWT #Newt
She brought the stack of papers back. The first thing she did was put them in a transparent document sleeve and store them in the home safe. I asked her whether these wouldn’t be the same as what the counter could print later—haven’t they already been stamped? She said it wasn’t like that. The teller told her: every time the documents are printed, it’s that exact moment’s copy. The stamp number and timestamp are unique. If you lose it, the bank won’t give you a second, identical copy. For later audit and review, they only recognize that one.
I watched her put the document sleeve into the safe and just stood there for a moment.
Later, when I flipped through the section about <c-1/> @NewtonProtocol in the whitepaper compliance evidence, the image that came to my mind was exactly that transparent sleeve.
Every time Newton finishes an authorization decision—every single transfer, every time it evaluates a strategy—it generates a cryptographic record on the spot. In the record, it binds: what transaction this was, which strategy was used for the evaluation (which CID), who the participating nodes were, what the aggregated signature is, and what the block height was. It all exists in an on-chain contract called TaskManager.
Just like my sister’s stack of bank statements—what feels unnecessary at the time can be pulled out when you need it.
When regulators want to check why this transfer was authorized back then, there’s no need to dig out the user’s identity information. They can simply pull the proof from the blockchain to verify directly: the strategy was indeed evaluated at that time point, the evaluator was among the nodes that had staked, and it signed.
The challenge mechanism needs it too. If someone suspects the evaluation result at the time was wrong and wants to complain, the on-chain credential is the original evidence.
In traditional finance, many compliance issues aren’t that no review is done. It’s that even when review happens, the evidence isn’t kept clearly. Later, you can’t find the papers when you go back to search the archives—or the internal systems have been updated and the versions don’t match the rules from then. That’s where the arguing starts. Newton engineers this: during evaluation, it fixes the evidence immediately, leaving no room for adding records later.
Before my sister put that stack of statements into the safe, she told me that if you did something, you should leave behind a tangible thing.
Leave a record—if you don’t need it, it’s a wasted record; but if you do need it, not a single page can be missing.
@NewtonProtocol $NEWT #Newt