Profile of zhivkoto in Optimism
Posts by zhivkoto
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: Jan. 18, 2024, 1:32 p.m.
Content: Hey @chom, thanks for checking it! This hasn’t been accepted into the mainnet yet, but we hope it will. The only thing left is final approval by the core team. After initial back and forth on the implementation was cleared, the PR had been left open for months and has recently been closed due to inactivity. Any way to bring this forward to the core team’s attention? cc @tynes for visibility
Likes: 1
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: Jan. 18, 2024, 8:32 a.m.
Content: Hey @chom, thanks for checking it!
This hasn’t been accepted into the mainnet yet, but we hope it will. The only thing left is final approval by the core team.
After initial back and forth on the implementation was cleared, the PR had been left open for months and has recently been closed due to inactivity.
Any way to bring this forward to the core team’s attention?
cc @tynes for visibility
Likes: 1
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: Sept. 26, 2023, 1:51 p.m.
Content: hey @jrocki.bedrock and @lavande, appreciate spreading the word about Demo Day. At this point, we’ve decided not to apply as our mission proposal is very technical and the deliverable is only visible on github and yet to be merged. Once our mission has had a bigger impact (implemented + people using it), we’ll make sure to tell the world and share findings!
Likes: 3
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: Sept. 26, 2023, 9:51 a.m.
Content: hey @Jrocki and @lavande, appreciate spreading the word about Demo Day. At this point, we’ve decided not to apply as our mission proposal is very technical and the deliverable is only visible on github and yet to be merged.
Once our mission has had a bigger impact (implemented + people using it), we’ll make sure to tell the world and share findings!
Likes: 3
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: Sept. 20, 2023, 1:10 p.m.
Content: hey @lavande. thanks for checking in! We have developed the contract extension as decribed in the original post and have a pending pull request here - contracts-bedrock: extend the l 1 block contract to store historical block hash data by vladimir-trifonov · Pull Request # 6903 · ethereum-optimism/optimism · GitHub 6 . After some back and forth, addressing comments etc. - our work should be considered done, pending implementation / merging by the Optimism development team. Once it’s implemented, the L 1 block contract extension should be ready to be leveraged by builders in the Optimism ecosystem. Appreciate the RetroPGF shout out. Once we see measurable impact from our efforts, we’ll make sure to apply! Thanks!
Likes: 1
Replies: 1
Replies:
- chom: Wondering if this is going to be accepted to the Optimism mainnet or not?
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: Sept. 20, 2023, 9:10 a.m.
Content: hey @lavande. thanks for checking in!
We have developed the contract extension as decribed in the original post and have a pending pull request here - contracts-bedrock: extend the l 1 block contract to store historical block hash data by vladimir-trifonov · Pull Request # 6903 · ethereum-optimism/optimism · GitHub 8 . After some back and forth, addressing comments etc. - our work should be considered done, pending implementation / merging by the Optimism development team.
Once it’s implemented, the L 1 block contract extension should be ready to be leveraged by builders in the Optimism ecosystem.
Appreciate the RetroPGF shout out. Once we see measurable impact from our efforts, we’ll make sure to apply!
Thanks!
Likes: 1
Replies: 1
Replies:
- chom: Wondering if this is going to be accepted to the Optimism mainnet or not?
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: July 21, 2023, 6:49 a.m.
Content: Yes, just sent an email!
Likes: 1
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: July 21, 2023, 2:49 a.m.
Content: Yes, just sent an email!
Likes: 1
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: July 6, 2023, 8:58 a.m.
Content: Hey @brichis, that’s a great question. Thank you for looking at our proposal. One can make a case for this proposal being both under Intent # 1 and Intent # 2 (novel use cases). The case for # 1 is that it will allow building decentralized components of the OP stack - e.g bridges. Data messaging protocols(bridges) won’t be forced to use zk light clients or centralized oracles, but will be able to use client-side ran libraries that reason about the data in the current and past state of L 1 . Another point for that case is that it will also help decentralize the stack with one more team doing work on it. It is the first time we write a mission proposal and were a bit confused which intent is the most appropriate, but hope our reasoning makes sense as the proposal should be a net positive for both intent # 1 and intent # 2 .
Likes: 2
Replies: 0
No replies yet.
-
[FINAL] Extend the L1Block contract to store historical block hash data
by zhivkoto - No Role
Posted on: July 6, 2023, 4:58 a.m.
Content: Hey @brichis, that’s a great question. Thank you for looking at our proposal.
One can make a case for this proposal being both under Intent # 1 and Intent # 2 (novel use cases).
The case for # 1 is that it will allow building decentralized components of the OP stack - e.g bridges. Data messaging protocols(bridges) won’t be forced to use zk light clients or centralized oracles, but will be able to use client-side ran libraries that reason about the data in the current and past state of L 1 .
Another point for that case is that it will also help decentralize the stack with one more team doing work on it.
It is the first time we write a mission proposal and were a bit confused which intent is the most appropriate, but hope our reasoning makes sense as the proposal should be a net positive for both intent # 1 and intent # 2 .
Likes: 2
Replies: 0
No replies yet.
