Closed ramtinms closed 1 month ago
Just a heads up we have new findings and received more feedback and I will update this Flip soon with more details.
@ramtinms
@turbolent just changed the state to "proposed".
Does the current state of the proposal reflect the changes that were made in the implementation?
@turbolent I've updated the contract and I believe it should be up to date now.
@franklywatson 13cc05f changed the status to implemented, but the FLIP hasn't even been accepted yet? See https://github.com/onflow/flips?tab=readme-ov-file#proposal-states
@KshitijChaudhary666 what is the process for moving this forward? is there a meeting to present it?
@ramtinms This proposal probably lies in between the Cadence Language and Execution Working Group and Flow Core-Protocol Working Group.
Maybe indicate that this proposal is ready for a final round of feedback, and will get approved unless there are any further concerns brought forward. For example, post in Discord and in the forum.
We can maybe schedule a working group meeting soon to have a last discussion, and then get it approved (so far sentiment has been positive).
@ramtinms Is the FLIP up-to-date with the latest changes made in flow-go?
@KshitijChaudhary666 what is the process for moving this forward? is there a meeting to present it?
Hey - simply talking from a FLIP-lifecycle-perspective - presenting the FLIP in the next WG meeting for a final feedback like @turbolent proposed does make sense to me. Once the author is confident of the community sentiment, the status of the FLIP could be changed to "accepted" and thereafter go to implementation @vishalchangrani
@turbolent I believe it has all the recent changes. @sideninja any thing we might be missing?
Discord conversation on getting this FLIP over the finish line and a Working Group Meeting for a final discussion and getting the FLIP formally approved: https://discord.com/channels/613813861610684416/1167476806333513800/1237414321445797939
Thank you for the insightful discussions on this FLIP. We feel there is an overwhelming support from the active developer community and the broader ecosystem.
On May 15th, 2024 10-11am PT (17-18:00 UTC) we'll hold a joint meeting of the Core Protocol Working Group and the Cadence Language and Execution Working Group, where we would like to briefly go over it together and approve this FLIP unless there are any major concerns remaining.
You can add the meeting to your calendar via this link or find it on our 📆 Flow Events & Working Groups calendar along with all the other working group meetings. Everyone is welcome 💚
Minor, but would be great to resolve: There are still a few differences between the EVM contract in the implementation and in the FLIP:
timestamp
field in EVMBlock
, missing in FLIP@ramtinms @sideninja Could you please update FLIP (more important) and implementation to bring them in sync?
@turbolent I plan to, after I also complete this one https://github.com/onflow/flow-go/issues/5911
links to the video recording and meeting transcript here (at the bottom)
As there were no concerns in the meeting, we intend to move this FLIP to approved/accepted on Wednesday May 22nd, unless significant concerns are brought up here. Thank you.
@turbolent I updated all the recent changes in the FLIP. As far as the content goes I believe it should be up to date.
👉 Announcement 👈
Thank you for the insightful discussions on this FLIP. We feel there is an overwhelming support from the active developer community and the broader ecosystem.
On May 15th, 2024 10-11am PT (17-18:00 UTC) we'll hold a joint meeting of the Core Protocol Working Group and the Cadence Language and Execution Working Group, where we would like to briefly go over it together and approve this FLIP unless there are any major concerns remaining.
You can add the meeting to your calendar via this link or find it on our 📆 Flow Events & Working Groups calendar along with all the other working group meetings. Everyone is welcome 💚