Improve IovReader/IovWriter achitecture

Dependencies

The currently documented way to create an IovReader is complicated:

const knownChains = await withConnectors([await bnsConnector("ws://localhost:22345")]);
// reader is already there: knownChains[0].client, no writer required

const writer = new IovWriter(profile, knownChains);
const chainId = writer.chainIds()[0];
const reader = writer.reader(chainId);

So that the moment we need a reader to make a writer but need a writer to make a reader.

IovReader is responsible for writing to the blockchain

The term “reader” is irritating as IovReader is not only reading from the blockchain but also write signed transactions to it. It serves more as a networking component.

This becomes important when thinking about disconnect(). Right now, in order to disconnect a writer, you need to disconnect all the readers and as soon as you disconnect a reader, the writer does not work anymore. This behavior would make more sense, if it was clear, that IovReader is IovWriter’s networking component.

[Isabello]

MultiChainSigner seems pretty good and explicit about what it does. I like it.

[webmaster128]

I can live with IovWriter for now until we find a natural fit. It is unique and not misleading. From the ideas that exist now, I like MultiChainSigner most.