-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: Standard for Insurance Policies as ERC-721 Non fungible tokens #1523
Comments
There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
We are currently piloting the EIP so please leave this issue open for the time being. |
Thank you bot! |
There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
Hi, this is still work in progress. Please don't close it. |
Sorry, fat finger. This EIP should remain open. |
Since this EIP has become stagnant, we are closing this discussion issue for housekeeping purposes. You may continue discussion here on the closed issue (it won't be locked), but if you want to revive the EIP (bring it back to Draft or Review status), you will need to create a thread over at https://ethereum-magicians.org/ and update the discussions-to link in the EIP to point there instead (that is where all discussions happen now). |
This is a good initiative and worth reviving. Happy to engage to develop this standard. |
Standardizing the way insurance policies are handled will be crucial for the development of an open standard for insurance on the ethereum blockchain.
We have drafted a first version and invite the community to engage in the discussion.
PR is here:
#1523
The text was updated successfully, but these errors were encountered: