Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 18 additions & 4 deletions ERCS/erc-7730.md
Original file line number Diff line number Diff line change
Expand Up @@ -1209,7 +1209,7 @@ In the following references, the format title is the value to use under the `for

#### Integer formats

Formats usable for uint/int solidity types.
Formats applicable to `uint`/`int` solidity types.

| **`raw`** | |
|---------------|-----------------------------------------------------------------------|
Expand Down Expand Up @@ -1283,7 +1283,7 @@ Formats usable for uint/int solidity types.

#### String formats

Formats usable for strings.
Formats applicable to for `string` solidity type.

| **`raw`** | |
|---------------|-----------------------------------------------|
Expand All @@ -1294,7 +1294,7 @@ Formats usable for strings.

#### Bytes formats

Formats usable for bytes
Formats applicable to `bytes` solidity type.

| **`raw`** | |
|---------------|------------------------------------------------|
Expand All @@ -1316,7 +1316,7 @@ Formats usable for bytes

#### Address

Formats usable for address
Formats applicable to `address` solidity type.

| **`raw`** | |
|-----------------|----------------------------------------------------------------------------------------------|
Expand Down Expand Up @@ -1346,6 +1346,20 @@ Formats usable for address
| `MYTOKEN` | Field Value 0xaabbccddeeff.... |


#### Interoperable addresses

Interoperable address format applicable to solidity type `bytes` (especially `bytes32`) and `uint256`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Interoperable address format applicable to solidity type `bytes` (especially `bytes32`) and `uint256`.
Interoperable address format applicable to solidity type `bytes`.

It's not actually related to bytes32 and uint256. That's why It might be better to remove this part.


| **`interoperableAddressName`** | |
|-------------------------|--------------------|
| *Description* | Display bytes as an [ERC-7930](./eip-7930.md) Interoperable Name. The wallet SHOULD parse the binary format, extract the target address and chain, and display it in the standard `<address> @ <chain> # <checksum>` format. |
| *Parameters* | --- |
| `types` | An array of expected types of the address (see [next section](#address-types-and-sources)). If set, the wallet SHOULD check that the address matches one of the types provided |
| `sources` | An array of acceptable sources for names (see [next section](#address-types-and-sources)). If set, the wallet SHOULD restrict name lookup to relevant sources |
| `senderAddress` | Either a string or an array of strings. If the address pointed to by `addressName` is equal to one of the addresses in `senderAddress`, the addressName is interpreted as the sender referenced by `@.from` |
| *Examples* | --- |
| `0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045@eip155:1#4CA88C9C` | Field Value = `0x00010000010114D8DA6BF26964AF9D7EED9E03E53415D37AA96045` |

#### Address types and sources

Address names trusted sources specify which type and source of trusted names SHOULD be used to replace an address with a human-readable names.
Expand Down
Loading