Profile of kozi in Optimism
Posts by kozi
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: March 7, 2024, 9:31 p.m.
Content: Hello @mmurthy I can confirm that we have completed all milestones on time. Please note that: kozi: For the “Integrate Herodotus with SnapshotX for usage on Optimism L 2 ” milestone, the source of truth will be the HerodotusDev GitHub and written confirmation from the Snapshot team stating they have received everything they need to complete their integration. Please note that SnapshotX going live in production on Optimism is dependent on engineering from the Snapshot team. Our milestone pertains to completing all necessary Storage Proof elements that the Snapshot team will require.
Likes: 0
Replies: 0
No likes yet.
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: March 7, 2024, 4:31 p.m.
Content: Hello @mmurthy
I can confirm that we have completed all milestones on time. Please note that:
kozi:
For the “Integrate Herodotus with SnapshotX for usage on Optimism L 2 ” milestone, the source of truth will be the HerodotusDev GitHub and written confirmation from the Snapshot team stating they have received everything they need to complete their integration. Please note that SnapshotX going live in production on Optimism is dependent on engineering from the Snapshot team. Our milestone pertains to completing all necessary Storage Proof elements that the Snapshot team will require.
Likes: 0
Replies: 0
No likes yet.
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: Nov. 1, 2023, 12:17 p.m.
Content: Yes, all the critical milestones have been completed.
Likes: 3
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: Nov. 1, 2023, 8:17 a.m.
Content: Yes, all the critical milestones have been completed.
Likes: 3
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: Oct. 31, 2023, 11:53 p.m.
Content: Hello @Gonna.eth We have successfully completed all of the required benchmarks for the cycle 11 grant. Focusing on our deliverables, we have: Develop a proven off-chain compressor for historical Ethereum blockhashes This repository unlocks Ethereum historical block hash access for smart contracts. The codebase has also been Audited by ABDK. github.com abdk-consulting/audits/blob/main/herodotus/ABDK_Herodotus_Herodotus_v_ 3 _ 0 .pdf This file is binary. show original docs.herodotus.dev Historical Block Hash Accumulator 1 Develop a circuit that accesses the compression accumulator - Merkle Mountain Range. Our proposal was originally written in March 2023 . Back then we thought that we will build this Merkle Mountain Range only with Poseidon. However, as we saw the efficiency of the Keccak 256 built-in significantly improve, we decided to build two MMRs. One using Keccak and one using Poseidon. Because we have a MMR with Keccak, we decided to skip this part. We realized that it is much cheaper to verify an MMR proof against a root built with Keccak rather than verify on Optimism a Groth 16 proof that proves to the valid verification of an MMR built with Poseidon. Ultimately, we have still achieved the same goal but with a different approach. docs.herodotus.dev Historical Block Hash Accumulator 1 docs.herodotus.dev Initial Accumulation Event Storage proof verification against hashes retrieved from the accumulator. This has been completed and the tests for this have been written. https://docs.google.com/document/d/ 1 Cr-nqwMQEa 2 jswIo 6 MdsO 3 bdZl-gnwFNAEwuy 2 zF 6 jk 3 Project report on development, integration, and usage in SnapshotX. We have achieved feature parity between the Herodotus Cairo smart contracts and Herodotus Solidity contracts which would be needed by the SnapshotX team. We have also built a Timestamp-to-Block Number Mapper in Solidity which Snapshot has specifically requested as a prerequisite for their deployment on EVM chains. The repository and corresponding documentation/research can be found here: docs.herodotus.dev Timestamp-to-Block Number Mapper 1 The Timestamp-to-Block Number Mapper facilitates the mapping of block numbers to their corresponding timestamps. Complete detailed documentation of the developed Optimism codebases. Completed. https://docs.google.com/document/d/ 1 Cr-nqwMQEa 2 jswIo 6 MdsO 3 bdZl-gnwFNAEwuy 2 zF 6 jk/edit?usp=sharing 3 Integrate Herodotus with SnapshotX for usage on Optimism L 2 , completing Storage Proof elements. Pending Snapshot integration. All required codebases have been completed. This includes: Ethereum Historical Block Hash Accumulator has been completed and audited by ABDK. Timestamp-to-Block Number Mapper has been implemented in Solidity. github.com 1 //github.com/HerodotusDev/herodotus-evm/tree/master/src/timestamps-mapper docs.herodotus.dev Timestamp-to-Block Number Mapper 1 The Timestamp-to-Block Number Mapper facilitates the mapping of block numbers to their corresponding timestamps. Herodotus on EVM has been completed (MVP, as we intend to optimize the codebase over the next few months) GitHub GitHub - HerodotusDev/herodotus-evm Contribute to HerodotusDev/herodotus-evm development by creating an account on GitHub. docs.google.com OP Stack Grant Report - Public 7 Herodotus Report about Optimism codebases Background Reading data from Optimism and any OP Stack roll-ups can be done by retrieving block hash from outputRoot Recently Optimism has upgraded to Bedrock and now what gets committed to L 1 is the... Off-chain EVM Headers Processor, which maintains the logic of maintaining and building our two MMRs. GitHub - HerodotusDev/offchain-evm-headers-processor Please let me know if additional information is needed.
Likes: 2
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: Oct. 31, 2023, 11:53 p.m.
Content: Hello @Gonna.eth We have successfully completed all of the required benchmarks for the cycle 11 grant. Focusing on our deliverables, we have: Develop a proven off-chain compressor for historical Ethereum blockhashes This repository unlocks Ethereum historical block hash access for smart contracts. The codebase has also been Audited by ABDK. github.com abdk-consulting/audits/blob/main/herodotus/ABDK_Herodotus_Herodotus_v_ 3 _ 0 .pdf 1 This file is binary. show original docs.herodotus.dev Historical Block Hash Accumulator 2 Develop a circuit that accesses the compression accumulator - Merkle Mountain Range. Our proposal was originally written in March 2023 . Back then we thought that we will build this Merkle Mountain Range only with Poseidon. However, as we saw the efficiency of the Keccak 256 built-in significantly improve, we decided to build two MMRs. One using Keccak and one using Poseidon. Because we have a MMR with Keccak, we decided to skip this part. We realized that it is much cheaper to verify an MMR proof against a root built with Keccak rather than verify on Optimism a Groth 16 proof that proves to the valid verification of an MMR built with Poseidon. Ultimately, we have still achieved the same goal but with a different approach. docs.herodotus.dev Historical Block Hash Accumulator 2 docs.herodotus.dev Initial Accumulation Event Storage proof verification against hashes retrieved from the accumulator. This has been completed and the tests for this have been written. https://docs.google.com/document/d/ 1 Cr-nqwMQEa 2 jswIo 6 MdsO 3 bdZl-gnwFNAEwuy 2 zF 6 jk 3 Project report on development, integration, and usage in SnapshotX. We have achieved feature parity between the Herodotus Cairo smart contracts and Herodotus Solidity contracts which would be needed by the SnapshotX team. We have also built a Timestamp-to-Block Number Mapper in Solidity which Snapshot has specifically requested as a prerequisite for their deployment on EVM chains. The repository and corresponding documentation/research can be found here: docs.herodotus.dev Timestamp-to-Block Number Mapper 1 The Timestamp-to-Block Number Mapper facilitates the mapping of block numbers to their corresponding timestamps. Complete detailed documentation of the developed Optimism codebases. Completed. https://docs.google.com/document/d/ 1 Cr-nqwMQEa 2 jswIo 6 MdsO 3 bdZl-gnwFNAEwuy 2 zF 6 jk/edit?usp=sharing 4 Integrate Herodotus with SnapshotX for usage on Optimism L 2 , completing Storage Proof elements. Pending Snapshot integration. All required codebases have been completed. This includes: Ethereum Historical Block Hash Accumulator has been completed and audited by ABDK. Timestamp-to-Block Number Mapper has been implemented in Solidity. github.com 2 //github.com/HerodotusDev/herodotus-evm/tree/master/src/timestamps-mapper docs.herodotus.dev Timestamp-to-Block Number Mapper 1 The Timestamp-to-Block Number Mapper facilitates the mapping of block numbers to their corresponding timestamps. Herodotus on EVM has been completed (MVP, as we intend to optimize the codebase over the next few months) GitHub GitHub - HerodotusDev/herodotus-evm Contribute to HerodotusDev/herodotus-evm development by creating an account on GitHub. docs.google.com OP Stack Grant Report - Public 8 Herodotus Report about Optimism codebases Background Reading data from Optimism and any OP Stack roll-ups can be done by retrieving block hash from outputRoot Recently Optimism has upgraded to Bedrock and now what gets committed to L 1 is the... Off-chain EVM Headers Processor, which maintains the logic of maintaining and building our two MMRs. GitHub - HerodotusDev/offchain-evm-headers-processor Please let me know if additional information is needed.
Likes: 2
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: Oct. 31, 2023, 7:53 p.m.
Content: Hello @Gonna.eth
We have successfully completed all of the required benchmarks for the cycle 11 grant.
Focusing on our deliverables, we have:
Develop a proven off-chain compressor for historical Ethereum blockhashes
This repository unlocks Ethereum historical block hash access for smart contracts. The codebase has also been Audited by ABDK.
github.com
abdk-consulting/audits/blob/main/herodotus/ABDK_Herodotus_Herodotus_v_ 3 _ 0 .pdf
This file is binary. show original
docs.herodotus.dev
Historical Block Hash Accumulator
Develop a circuit that accesses the compression accumulator - Merkle Mountain Range.
Our proposal was originally written in March 2023 . Back then we thought that we will build this Merkle Mountain Range only with Poseidon. However, as we saw the efficiency of the Keccak 256 built-in significantly improve, we decided to build two MMRs. One using Keccak and one using Poseidon. Because we have a MMR with Keccak, we decided to skip this part. We realized that it is much cheaper to verify an MMR proof against a root built with Keccak rather than verify on Optimism a Groth 16 proof that proves to the valid verification of an MMR built with Poseidon. Ultimately, we have still achieved the same goal but with a different approach.
docs.herodotus.dev
Historical Block Hash Accumulator
docs.herodotus.dev
Initial Accumulation Event
Storage proof verification against hashes retrieved from the accumulator.
This has been completed and the tests for this have been written.
https://docs.google.com/document/d/ 1 Cr-nqwMQEa 2 jswIo 6 MdsO 3 bdZl-gnwFNAEwuy 2 zF 6 jk
Project report on development, integration, and usage in SnapshotX.
We have achieved feature parity between the Herodotus Cairo smart contracts and Herodotus Solidity contracts which would be needed by the SnapshotX team.
We have also built a Timestamp-to-Block Number Mapper in Solidity which Snapshot has specifically requested as a prerequisite for their deployment on EVM chains. The repository and corresponding documentation/research can be found here:
docs.herodotus.dev
Timestamp-to-Block Number Mapper
The Timestamp-to-Block Number Mapper facilitates the mapping of block numbers to their corresponding timestamps.
Complete detailed documentation of the developed Optimism codebases.
Completed.
https://docs.google.com/document/d/ 1 Cr-nqwMQEa 2 jswIo 6 MdsO 3 bdZl-gnwFNAEwuy 2 zF 6 jk/edit?usp=sharing
Integrate Herodotus with SnapshotX for usage on Optimism L 2 , completing Storage Proof elements.
Pending Snapshot integration. All required codebases have been completed. This includes:
Ethereum Historical Block Hash Accumulator has been completed and audited by ABDK.
Timestamp-to-Block Number Mapper has been implemented in Solidity.
github.com
//github.com/HerodotusDev/herodotus-evm/tree/master/src/timestamps-mapper
docs.herodotus.dev
Timestamp-to-Block Number Mapper
The Timestamp-to-Block Number Mapper facilitates the mapping of block numbers to their corresponding timestamps.
Herodotus on EVM has been completed (MVP, as we intend to optimize the codebase over the next few months)
GitHub
GitHub - HerodotusDev/herodotus-evm
Contribute to HerodotusDev/herodotus-evm development by creating an account on GitHub.
docs.google.com
OP Stack Grant Report - Public
Herodotus Report about Optimism codebases Background Reading data from Optimism and any OP Stack roll-ups can be done by retrieving block hash from outputRoot Recently Optimism has upgraded to Bedrock and now what gets committed to L 1 is the...
Off-chain EVM Headers Processor, which maintains the logic of maintaining and building our two MMRs. GitHub - HerodotusDev/offchain-evm-headers-processor
Please let me know if additional information is needed.
Likes: 2
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: April 2, 2023, 11:44 p.m.
Content: Hello @Gonna.eth , We have a simple API demo demonstrating how storage proofs can be used to generate an inactivity proof for a starknet account. Storage proofs are generated for the accounts nonce at two distinct block numbers. As the nonces are the same at both times, these proofs could be used to trigger a deadman switch or other account recovery mechanism. You can watch the short YouTube video demo from Starkware Sessions 2023 here: https://youtu.be/PZLjhUDG-NY?t= 234 2 (the demo starts at 3 : 54 ). The GitHub repository for the demo can be found at https://github.com/HerodotusDev/account-inactivity-proof 1 . This diagram might also give you some insight into how such a recovery process could look: https://twitter.com/HerodotusDev/status/ 1614172762108751874 3 . I think it is worth mentioning that even though we specified account abstraction wallets in that diagram, this would also be possible for an EOA! Maybe someone will build this in the future! Regarding grant size, we firmly believe that the 50 , 000 OP token allocation is fair, considering the resources and team size we plan on dedicating to complete our proposed deliverables. The Snapshot integration is a common good as it will help in governance and help uphold the vision and values of the Optimism Collective :slight_smile:
Likes: 3
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: April 2, 2023, 7:44 p.m.
Content: Hello @Gonna.eth ,
We have a simple API demo demonstrating how storage proofs can be used to generate an inactivity proof for a starknet account. Storage proofs are generated for the accounts nonce at two distinct block numbers. As the nonces are the same at both times, these proofs could be used to trigger a deadman switch or other account recovery mechanism.
You can watch the short YouTube video demo from Starkware Sessions 2023 here: https://youtu.be/PZLjhUDG-NY?t= 234 (the demo starts at 3 : 54 ).
The GitHub repository for the demo can be found at https://github.com/HerodotusDev/account-inactivity-proof.
This diagram might also give you some insight into how such a recovery process could look: https://twitter.com/HerodotusDev/status/ 1614172762108751874 .
I think it is worth mentioning that even though we specified account abstraction wallets in that diagram, this would also be possible for an EOA! Maybe someone will build this in the future!
Regarding grant size, we firmly believe that the 50 , 000 OP token allocation is fair, considering the resources and team size we plan on dedicating to complete our proposed deliverables. The Snapshot integration is a common good as it will help in governance and help uphold the vision and values of the Optimism Collective :slight_smile:
Likes: 3
Replies: 0
No replies yet.
-
[Cycle 11] - Herodotus - Storage Proofs
by kozi - No Role
Posted on: March 22, 2023, 11:57 a.m.
Content: Hello @Gonna.eth, I appreciate the feedback on our proposal and have taken it into consideration while updating our project milestones. To address the governance structure, Herodotus will not be structured as a DAO. The decision-making process regarding votes on Optimism will be managed by the founding team, Marcello Bardus and myself (Kacper Koziol). We are committed to the long-term vision of the ecosystem and will actively participate in the governance process. Please find below our proposed Benchmark and Critical Milestones: Project Milestone Type Milestone Source of Truth Deadline Herodotus Storage Proofs Benchmark Develop a proven off-chain compressor for historical Ethereum blockhashes HerodotusDev GitHub August 31 , 2023 Herodotus Storage Proofs Benchmark Develop a circuit that accesses the compression accumulator - Merkle Mountain Range. HerodotusDev GitHub August 31 , 2023 Herodotus Storage Proofs Benchmark Storage proof verification against hashes retrieved from the accumulator. HerodotusDev GitHub August 31 , 2023 Herodotus Storage Proofs Benchmark Complete Herodotus codebases to support the Optimism chain. HerodotusDev GitHub October 31 , 2023 Herodotus Storage Proofs Critical Project report on development, integration, and usage in SnapshotX. HerodotusDev GitHub October 31 , 2023 Herodotus Storage Proofs Critical Complete detailed documentation of the developed Optimism codebases. docs.herodotus.dev & HerodotusDev GitHub October 31 , 2023 Herodotus Storage Proofs Critical Integrate Herodotus with SnapshotX for usage on Optimism L 2 , completing Storage Proof elements. HerodotusDev GitHub & written confirmation from Snapshot team October 31 , 2023 Please note that the given timelines include a buffer for potential roadblocks. We are confident in our ability to achieve these milestones faster than outlined above but wanted to be on the safe side with our deadline dates. All components of the grant will be completed by October 31 , 2023 . Regarding the suggestion to decrease the grant size, we would like to emphasize that due to the significant company resources, we will spend on salaries for our current 12 -person team and our commitment not to sell the tokens we are granted, we believe that the 50 , 000 OP token allocation is fair and will allow us to participate in shaping the Optimism ecosystem in the future. Our solution will drive considerable value to the Optimism ecosystem, help retain projects and developers, and unlock new application designs. For the “Integrate Herodotus with SnapshotX for usage on Optimism L 2 ” milestone, the source of truth will be the HerodotusDev GitHub and written confirmation from the Snapshot team stating they have received everything they need to complete their integration. Please note that SnapshotX going live in production on Optimism is dependent on engineering from the Snapshot team. Our milestone pertains to completing all necessary Storage Proof elements that the Snapshot team will require. I hope this updated response addresses your questions and demonstrates our commitment to the Optimism ecosystem. Thank you for your consideration.
Likes: 4
Replies: 2
Replies:
- Gonna.eth: kozi:
I hope this updated response addresses your questions
Yes, thank you.
Keep watch on the forum, more questions can come from other council members.
- kozi: Hello @mmurthy
I can confirm that we have completed all milestones on time. Please note that:
kozi:
For the “Integrate Herodotus with SnapshotX for usage on Optimism L2” milestone, the source of truth will be the HerodotusDev GitHub and written confirmation from the Snapshot team stating they have received everything they need to complete their integration. Please note that SnapshotX going live in production on Optimism is dependent on engineering from the Snapshot team. Our milestone pertains to completing all necessary Storage Proof elements that the Snapshot team will require.
