Extract client instantiation into a separate tutorial

[thephez]

You could also extract the entire client instantiation into a separate tutorial segment and replace it with a single line client import in all subsequent segments.

Originally posted by @riongull in #34 (comment)
Also see: #34 (comment) and #34 (comment)

[thephez]

Originally posted by @riongull in #34 (comment)

I would have one client configuration with most or all of the client option keys documented in the passed-in object - scrap the separate clientOpts object:

const client = new Dash.Client({
  network: 'testnet',
  wallet: {
    mnemonic: 'a Dash wallet mnemonic with testnet funds goes here',
    unsafeOptions: {
      skipSynchronizationBeforeHeight: 875000, // only sync from mid-2023
    },
  // all other keys, or most if there are too many
  },
});

You could start each comment with "required for reads", "required for writes" or some convention like that. Might also make sense to document what the defaults are.

A dev wants to know what is optional, required, and default. If that can be done right in copy-pastable code that's ideal in my opinion. Easiest to have it all in one code block and then let the dev delete or comment out from there.

@ajcwedev is translating your docs into a complete quick start that devs can literally follow step by step in a copy paste way. To me, this tutorial presumes that you want to learn how to do reads and writes, so I would structure it that way.

Adding this extended info will be more reason to have the client configuration be a separate segment of the tutorial where you just import the configured client instance in each subsequent segment.