From 914fb7c40cc0f34cf78b123c2be97a724bc8fe7f Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 7 Mar 2024 16:38:43 +0100 Subject: [PATCH] Fix inline code --- bip-0040.mediawiki | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bip-0040.mediawiki b/bip-0040.mediawiki index fb09b66c..8afbefe0 100644 --- a/bip-0040.mediawiki +++ b/bip-0040.mediawiki @@ -36,9 +36,9 @@ Later in 2012, Marek Palatinus introduced Stratum also for mining pools: The Str Stratum leverages [https://www.jsonrpc.org/ JSON-RPC]. Both versions 1.0 and 2.0 are allowed. Rules of that version apply accordingly. -Additionally, it is a convention to give all Stratum methods in the `method` property a name in the following form: `.`, where `` is allowed to have dots and `` isn't. For example, the the value `blockchain.block.subscribe`. +Additionally, it is a convention to give all Stratum methods in the method property a name in the following form: ., where is allowed to have dots and isn't. For example, the the value blockchain.block.subscribe. -Note: In JSON-RPC 1.0, the `param` property is an array, so everything should be passed in the right order. In JSON-RPC 2.0, also named parameters are allowed. In that case, the parameter names that are documented should be used. If not, the method can fail. It is maybe also possible that a specific method (or server) only does support `params` being an array, because it doesn't know how to handle the named ones, even if it supports JSON-RPC 2.0. +Note: In JSON-RPC 1.0, the param property is an array, so everything should be passed in the right order. In JSON-RPC 2.0, also named parameters are allowed. In that case, the parameter names that are documented should be used. If not, the method can fail. It is maybe also possible that a specific method (or server) only does support params being an array, because it doesn't know how to handle the named ones, even if it supports JSON-RPC 2.0. ==Specification: Transport Protocols==