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

Update ERC-5573: require single recap in resources #303

Closed
wants to merge 4 commits into from

Conversation

chris13524
Copy link
Contributor

@chris13524 chris13524 commented Mar 8, 2024

"a Recap URI MUST occupy the final entry of the SIWE resource list" is somewhat ambiguous as to if there can be more (implied ignored) urn:recap URIs elsewhere in the resource list. Making this more explicit that there must be a single urn:recap URI.

Also adjust spacing and indent to be consistent with elsewhere in the spec & fix some caps typos.

@eip-review-bot
Copy link
Collaborator

eip-review-bot commented Mar 8, 2024

File ERCS/erc-5573.md

Requires 1 more reviewers from @awoie, @chunningham, @clehner, @cobward, @skgbafa, @wyc

@eip-review-bot eip-review-bot changed the title Explicit at most one urn:recap in resources Update ERC-5573: recap in resources Mar 8, 2024
@chris13524 chris13524 changed the title Update ERC-5573: recap in resources Update ERC-5573: require single recap in resources Mar 8, 2024
ERCS/erc-5573.md Outdated Show resolved Hide resolved
Copy link

@ganchoradkov ganchoradkov left a comment

Choose a reason for hiding this comment

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

Always nice to have explicit rules how something should work otherwise it's up to one's interpretation 💯

Copy link

@awoie awoie left a comment

Choose a reason for hiding this comment

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

What are your thoughts @chunningham?

Copy link

github-actions bot commented Aug 8, 2024

There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR 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.

Copy link

This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.

@github-actions github-actions bot closed this Feb 14, 2025
@chris13524
Copy link
Contributor Author

I still think this is worth addressing/merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants