UPDATE arc60 README, clarify

Signed-off-by: ehanoc <[email protected]>

ARCs/arc-0060.md

@@ -51,18 +51,19 @@ When connected to a specific `domain` (i.e app or other identifier), the wallet
 
 Supported scopes are:
 
-- `AUTH` (1): This scope is used for authentication purposes. It is used to sign data that will be used to authenticate the user. The `data` field **MUST** be a JSON object with the following fields:
-    - `type`:  the type of operation (e.g., "SIWA", “webauthn.create”, “webauthn.get”, etc)
-    - `origin`: The origin / domain of the request or the URL of the relying party (RP) that initiated the authentication.
-    - `challenge`: 32 bytes of entropy.
+- `AUTH` (1): This scope is used for authentication purposes. It is used to sign data that will be used to authenticate the user to a specific domain. The `data` field **MUST** be a JSON object that represents the content to be signed. The `authenticatedData` field **MUST** include, at least, the `sha256` hash of the `domain` requesting a signature. The wallet **MUST** do an integrity check on the first 32 bytes of `authenticatedData` to match the hash. The `hdPath` field is **optional** and **MUST** be a BIP44 path in order to derive the private key to sign the `data`. The wallet **MUST** validate the path before signing.
+
 
 Summarized signing process for `AUTH` scope:
 ```plaintext
 EdDSA(SHA256(data) + SHA256(authenticatedData))
 ```
 
+- **`note`**: Other scopes could be added in the future.
+
+#### Parameters
 
-#### `StdSigData`
+##### `StdSigData`
 
 Must be a JSON object with the following properties:
 
@@ -75,7 +76,7 @@ Must be a JSON object with the following properties:
 | `authenticatedData` | `bytes` | It **MUST** include, at least, the `sha256` hash of the `domain` requesting a signature. The wallet **MUST** do an integrity check on the first 32 bytes of `authenticatedData` to match the hash. It **MAY** also include signature counters, network flags or any other unique data to prevent replay attacks or to trick user to sign unrelated data to the scope. The wallet **SHOULD** validate every field in `authenticatedData` before signing. Each `Scope` **MUST** specify if `authenticatedData` should be appended to the hash of the `data` before signing. |
 | `hdPath` | `string` | This field is **optional**. It is required if the wallet supports BIP39 / BIP32 / BIP44. This field **MUST** be a BIP44 path in order to derive the private key to sign the `data`. The wallet **MUST** validate the path before signing. |
 
-#### `metadata`
+##### `metadata`
 
 Must be a JSON object with the following properties:
 
@@ -84,7 +85,7 @@ Must be a JSON object with the following properties:
 | `scope` | `integer` | Defines the purpose of the signature. It **MUST** be one of the following values: `1` (AUTH) |
 | `encoding` | `string` | Defines the encoding of the `data` field. `base64` is the recommended encoding. |
 
-#### `Errors`
+##### `Errors`
 
 These are the possible errors that the wallet **MUST** handle: