Most audit logs are a table you are asked to believe. Amzaa's trail is sealed the moment each write happens, chained to the one before it, and its root is published outside our database, into your hands. To rewrite history, we would have to change a copy you already hold.
Change a value in a sealed row below, then re-verify. The tampered row and every row after it fail, because each hash depends on the one before. Shown here as an illustration of the behaviour.
This is an illustration, not a live console. In the product the maths is real, the table is write-once, and the root is signed.
Every write includes a hash of the write before it. Change any record and its hash no longer matches, and neither does every record that followed. There is no quiet single edit.
The trail is a WORM table. The database itself refuses updates and deletes on a sealed row. It is not a convention someone can turn off in settings.
A Merkle root summarises every entry into one value. Verifying the root proves the whole trail at once, without re-reading every row, so it stays fast at millions of records.
The root is signed and handed to you, held outside our database. A trail whose both ends we control is arithmetic. A trail whose root you hold is evidence.
Because the trail is sealed and its root is external, an examiner can be given a read-only replay of exactly what happened and when, and verify it against the root they hold. Time-travel to any prior state. Place a legal hold. Prove completeness.
The difference between "trust our report" and "verify it yourself" is the whole point.
A small cohort of regulated banks, NBFCs and the firms that own them. Early access, real influence, pricing that holds.
We are pre-launch and we will not dress it up. There are no logos on this page because there are none to show. Come and try to break the chain.