Skip to content

Add EIP: Identity aggregated NFT #10035

Add EIP: Identity aggregated NFT

Add EIP: Identity aggregated NFT #10035

Triggered via pull request June 25, 2023 16:36
Status Cancelled
Total duration 35s
Artifacts 1
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
Save PR Number
2s
Save PR Number
HTMLProofer
25s
HTMLProofer
Link Check
19s
Link Check
CodeSpell
13s
CodeSpell
EIP Walidator
6s
EIP Walidator
Markdown Linter
5s
Markdown Linter
Fit to window
Zoom out
Zoom in

Annotations

15 errors
Markdown Linter
Process completed with exit code 1.
the first match of the given pattern must be a link: EIPS/eip-XXXX.md#L16
error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-XXXX.md | 16 | This standard extends ERC-721 by binding individuals' Web2 and Web3 identities to non-fungible tokens (NFTs). By binding multiple identities, aggregated and composible identity infomation can be verified, resulting in more beneficial onchain scenarios for individuals, such as self-authentication, social overlapping, commercial value generation from user targetting, etc. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-link-first/
Markdown Linter
Unable to process file command 'env' successfully.
the first match of the given pattern must be a link: EIPS/eip-XXXX.md#L140
error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-XXXX.md | 140 | 3. Verify the binding relationship between data on-chain and off-chain data through signature based on ERC-1271 | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
Markdown Linter
Invalid value. Matching delimiter not found 'EOF'
the first match of the given pattern must be a link: EIPS/eip-XXXX.md#L141
error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-XXXX.md | 141 | Through the signature method based on the ERC-1271 protocol, the verifyIdentiesBinding function of this EIP realizes the binding of the userID and NFT owner address between on-chain and off-chain. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: EIPS/eip-XXXX.md#L151
error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-XXXX.md | 151 | As mentioned in the specifications section, this standard can be fully EIP-721 compatible by adding an extension function set. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: EIPS/eip-XXXX.md#L152
error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-XXXX.md | 152 | In addition, new functions introduced in this standard have many similarities with the existing functions in EIP-721. This allows developers to easily adopt the standard quickly. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`): EIPS/eip-XXXX.md#L21
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`) --> EIPS/eip-XXXX.md | 21 | Exisiting solutions such as ENS, although open, decentralized, and make it more convenient for Ethereum-based applications, lack of data standardization and athentication of itentity due to inherent anominity. Other solutions such as SBTs rely on centralized attestors, can not prevent data tampering, nor inscribe data into the ledger itself in a privacy enabling way. Previous work such as ERC6066 does not bind nor verify user identity data, thus unable to meet the user identity aggregation, user Kyc verification and other application scenarios related to user data sovereignty | = info: the pattern in question: `(?i)erc[\s]*[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-re-erc-dash/
references to proposals with a `category` of `ERC` must use a prefix of `ERC`: EIPS/eip-XXXX.md#L151
error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC` --> EIPS/eip-XXXX.md | 151 | As mentioned in the specifications section, this standard can be fully EIP-721 compatible by adding an extension function set. | = help: see https://ethereum.github.io/eipw/markdown-refs/
references to proposals with a `category` of `ERC` must use a prefix of `ERC`: EIPS/eip-XXXX.md#L152
error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC` --> EIPS/eip-XXXX.md | 152 | In addition, new functions introduced in this standard have many similarities with the existing functions in EIP-721. This allows developers to easily adopt the standard quickly. |
authors in the preamble must match the expected format: EIPS/eip-XXXX.md#L4
error[preamble-author]: authors in the preamble must match the expected format --> EIPS/eip-XXXX.md:4:8 | 4 | author: Chloe Gu (@xy_gu), Navid X. ([email protected]), Victor Yu ([email protected]), Archer H. | ^^^^^^^^^^^^^^^^^^ unrecognized author | = help: Try `Random J. User (@username) <[email protected]>` for an author with a GitHub username plus email. = help: Try `Random J. User (@username)` for an author with a GitHub username. = help: Try `Random J. User <[email protected]>` for an author with an email. = help: Try `Random J. User` for an author without contact information. = help: see https://ethereum.github.io/eipw/preamble-author/
authors in the preamble must match the expected format: EIPS/eip-XXXX.md#L4
error[preamble-author]: authors in the preamble must match the expected format --> EIPS/eip-XXXX.md:4:27 | 4 | author: Chloe Gu (@xy_gu), Navid X. ([email protected]), Victor Yu ([email protected]), Archer H. | ^^^^^^^^^^^^^^^^^^^^^^^^^ unrecognized author | = help: Try `Random J. User (@username) <[email protected]>` for an author with a GitHub username plus email. = help: Try `Random J. User (@username)` for an author with a GitHub username. = help: Try `Random J. User <[email protected]>` for an author with an email. = help: Try `Random J. User` for an author without contact information.
HTMLProofer
Canceling since a higher priority waiting request for 'Continuous Integration-7231' exists
HTMLProofer
The operation was canceled.

Artifacts

Produced during runtime
Name Size
pr_number Expired
87 Bytes