ethereum-attestation-service / eas-docs-site Goto Github PK

The documentation at https://docs.attest.sh/docs/developer-tools/sdk-wagmi links to a gist at https://gist.github.com/slavik0329/2e5b6fc31cb745b65d3d37f7cf1d7b36 for hooks to use to convert wagmi objects for use with the EAS SDK (ethers).

However, the EAS SDK uses ethers v6, and that gist is written for ethers v5 (it references a providers export of Ethers, which was moved in v6).

Attempting to install ethers v5 for that script results in an error in the SDK ("Incompatible ethers version detect. Make sure to use the SDK with ethers v6 or later"), so v6 has to be used.

Therefore, those hooks should be updated for ethers v6 and the documentation updated to include the newer option.

[WHAT]:
Link from EAS to docs site returns error "This site can’t be reached".

[WHY]:
The Link links to an inaccurate domain "https://docs.attest.**org**/docs/welcome"

[HOW]:
The URL/href needs to redirect to ".sh" instead.
Correct link: "https://docs.attest.**sh**/docs/welcome"

Video of issue:

The Attestations vs X page says that Ethereum addresses are DIDs, but this is not accurate according to the W3C specification.

From ChatGPT:

No, an Ethereum address by itself is not considered a decentralized identifier (DID) according to the W3C specification for DIDs. While Ethereum addresses are decentralized and unique identifiers within the Ethereum blockchain, they do not meet the full criteria of a DID as defined by the W3C.

Decentralized Identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID refers to any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the DID. According to the W3C DID specification:

1. DID Document: A DID must resolve to a DID Document. This document contains the metadata necessary to interact with the DID subject, including public keys, authentication protocols, and service endpoints.
2. Control: DIDs are fully under the control of the DID subject or a delegated trusted entity, allowing the DID subject to prove control over it without requiring permission from any centralized authority.
3. Decentralized Systems: DIDs are typically associated with cryptographic material, such as public keys, and are anchored on a blockchain or other decentralized networks.

While an Ethereum address functions as a unique identifier within the Ethereum network and can be used to verify transactions using cryptographic keys, it does not natively include the broader functionality required by the DID specification, such as a resolvable DID document that provides metadata about the identity.

However, DIDs can be created on the Ethereum blockchain through various implementations that utilize Ethereum's smart contract capabilities to create and manage DID documents according to the DID specification. These are often referred to as "Ethereum-based DIDs" or "Blockchain-based DIDs," where the Ethereum network serves as the infrastructure for these decentralized identifiers.

Points to: https://docs.attest.sh/docs/category/use-cases

Which doesn't seem to exist. :)