From f1d3565590c5744e5ab0ae7cbc85e5d56ef22be3 Mon Sep 17 00:00:00 2001 From: David Nicholas <34694793+DavidNic11@users.noreply.github.com> Date: Tue, 27 Aug 2019 14:53:33 -0700 Subject: [PATCH] Added --- docs/spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/spec.md b/docs/spec.md index 685d6c6..21d850f 100644 --- a/docs/spec.md +++ b/docs/spec.md @@ -11,7 +11,7 @@ Requests without an `in3` property will also get a response without `in3`. This * **chainId** `string` - The requested [chainId](#chainid). This property is optional, but should always be specified in case a node may support multiple chains. In this case, the default of the node would be used, which may end up in an undefined behavior since the client cannot know the default. -* **includeCode** `boolean` - Applies only for `eth_call`-requests. If true, the request should include the codes of all accounts. Otherwise only the the codeHash is returned. In this case, the client may ask by calling eth_getCode() afterwards. +* **includeCode** `boolean` - Applies only for `eth_call`-requests. If true, the request should include the codes of all accounts. Otherwise only the the codeHash is returned. In this case, the client may ask by calling `eth_getCode()` afterwards. * **verifiedHashes** `string[]` - If the client sends an array of blockhashes, the server will not deliver any signatures or blockheaders for these blocks, but only return a string with a number. This allows the client to skip requiring signed blockhashes for blocks already verified.