Skip to content
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

NEP-485: Shared Ephemeral Storage #485

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Conversation

encody
Copy link

@encody encody commented Jun 16, 2023

No description provided.

@render
Copy link

render bot commented Jun 16, 2023

@encody encody marked this pull request as ready for review June 16, 2023 15:57
@encody encody requested a review from a team as a code owner June 16, 2023 15:57
@encody encody changed the title NEP: Shared Ephemeral Storage NEP-485: Shared Ephemeral Storage Jun 16, 2023
@encody encody marked this pull request as draft June 19, 2023 13:37
neps/nep-0485.md Outdated Show resolved Hide resolved
neps/nep-0485.md Outdated Show resolved Hide resolved
@frol frol added WG-protocol Protocol Standards Work Group should be accountable S-draft/needs-author-revision A NEP in the DRAFT stage that needs an author revision. A-NEP A NEAR Enhancement Proposal (NEP). labels Jun 20, 2023
Comment on lines +73 to +75
- How long should the code live in SES before it expires?
- How would SES integrate with dynamic sharding?
- What happens when you `FUNCTION_CALL` a SES contract that references expired code?
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you clarify/outline the motivation for expiring contract code (why expiring is needed, and what are the alternatives) ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the code doesn't expire, there's no guarantee that its storage will be paid for, but the validators are still required to keep it alive.

@walnut-the-cat
Copy link
Contributor

Hello! Protocol NEP moderator here. it seems there hasn't been any activity on this NEP for quite some time. Is it still on going? Or shall we close NEP for now? cc. @encody

@walnut-the-cat
Copy link
Contributor

Another ping on status of this NEP. As more than two months have passed since the last activity, if we don't hear back from the author by December 4th, we will mark the NEP as retracted for now. Thanks-

@walnut-the-cat
Copy link
Contributor

I will assume this NEP is inactive and label as retracted for now. If anyone picks the NEP up again, please ping NEP moderators to make it active.

@walnut-the-cat walnut-the-cat added S-retracted A NEP that was retracted by the author or had no activity for over two months. and removed S-draft/needs-author-revision A NEP in the DRAFT stage that needs an author revision. labels Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-NEP A NEAR Enhancement Proposal (NEP). S-retracted A NEP that was retracted by the author or had no activity for over two months. WG-protocol Protocol Standards Work Group should be accountable
Projects
Status: RETRACTED
Development

Successfully merging this pull request may close these issues.

7 participants