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.

Sign up for GitHub

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

Jump to bottom

docs: payment verifications & internet identifiers #72

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: payment verifications & internet identifiers #72

wants to merge 2 commits into from
+294 −24

Conversation

ATXMJ
Copy link
Contributor

@ATXMJ ATXMJ commented May 5, 2023

No description provided.

@ATXMJ ATXMJ changed the title Payment Verifications & Internet Identifiers docs: payment verifications & internet identifiers May 5, 2023
@ATXMJ ATXMJ marked this pull request as draft May 5, 2023 21:59
@mistakia mistakia added the need/triage Needs initial labeling and prioritization label May 5, 2023
@ATXMJ ATXMJ force-pushed the docs/payment-verifications-and-internet-identifiers branch 2 times, most recently from 8a1b34c to fce9714 Compare May 6, 2023 14:50
@ATXMJ
Copy link
Contributor Author

ATXMJ commented May 9, 2023

@mistakia do you think the Internet Identifiers content should be extracted to a different page?

@mistakia
Copy link
Owner

mistakia commented May 9, 2023

@mistakia do you think the Internet Identifiers content should be extracted to a different page?

Think it's fine to keep as a single page for now.

We haven't really established a guideline for when a page should be broken into sub-pages. It should occur when a certain number of distinct sections exist and the page exceeds a certain length. I think we've yet to clearly exceed those thresholds here.

@ATXMJ ATXMJ marked this pull request as ready for review May 11, 2023 20:29
@ATXMJ ATXMJ force-pushed the docs/payment-verifications-and-internet-identifiers branch from cae1dd3 to caf26df Compare September 16, 2024 17:41
@ATXMJ ATXMJ force-pushed the docs/payment-verifications-and-internet-identifiers branch from caf26df to 7c57e9c Compare September 16, 2024 17:55
@ATXMJ
Copy link
Contributor Author

ATXMJ commented Sep 16, 2024

I've removed the section on amount-based payment verification.

@mistakia anything else you'd like changed before we merge this?

I'm seeing more identifier services coming online, and would like to encourage them to adopt these protocols.

@Zosoled
Copy link

Zosoled commented Sep 17, 2024 •
edited
Loading

I propose the following for the <local-part> of the .well-known/nano-currency.json implementation:

  • The server MAY accept combination of uppercase and lowercase letters.
  • The server MUST save the primary key of the entry as all lowercase.
  • The server MAY additionally save the original casing of the entry for front-end display.
  • The server MUST prevent case-insensitive duplicates of the <local-part> (e.g. existing entry 'JohnDoe' prevents a new entry 'johndoe', 'JOHNDOE', etc.)
  • The server MUST convert the <local-part> of incoming queries to lowercase in order to look up the proper primary key.

EDIT: Obviously if there is a better way to word all that, feel free to change it up.

@kopeboy kopeboy mentioned this pull request Oct 10, 2024
Open
keerifox
keerifox reviewed Jan 14, 2025
View reviewed changes
docs/getting-started-devs/integrations.md
@@ -184,7 +184,7 @@ For convenience, users may prefer to use internet identifiers as an alternative

For this reason, it is preferable for Nano wallet clients to support handling of Nano internet identifiers in addition to Nano public addresses.

An internet identifier, defined in [RFC-5322 Section 3.4.1](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1) as an `"addr-spec"`, is an email address-like identifier that contains a locally interpreted string, the `<local-part>`, followed by the at-sign character ("@"), followed by an Internet domain, the `<domain>`, resulting in `<local-part>@<doman>`.
An internet identifier, defined in [RFC-5322 Section 3.4.1](https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1) as an `"addr-spec"`, is an email address-like identifier that contains a locally interpreted string, the `<local-part>`, followed by the at-sign character ("@"), followed by an Internet domain, the `<domain>`. To avoid confusion with email addresses, it is recommended that services that support Nano Internet Identifiers use the at-sign as a prefix for both the `<local-part>` and the `<domain>`, resulting in `@<local-part>@<doman>`.
Copy link
Contributor

Choose a reason for hiding this comment

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

resulting in @<local-part>@<doman>

domain*

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@keerifox keerifox keerifox left review comments

Assignees
No one assigned
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ATXMJ @mistakia @Zosoled @keerifox