Rigidity

You will usually use `RequestPuzzleState` and `RequestCoinState` as an entrypoint for subscribing, since it's more resilient to reorgs and more concise. There's a case to be made for removing the...

> > We don't have any precedent for doing it this way, and this increases the size of the protocol messages and requires differentiating between the response types just the...

> > Some major differences is that in his protocol you subscribe and request coin states in bulk, with many coin IDs and puzzle hashes. Also, subscriptions aren't given shorter...

> > > > We don't have any precedent for doing it this way, and this increases the size of the protocol messages and requires differentiating between the response types...

This is ready for initial reviews, though rate limits have not been set, so it is not ready for merge yet. That is what I will work on next.

> My understanding was that there was consensus (or at least some agreement) on altering the protocol to essentially merge the request for subscription with requesting coin states. and the...

I have also updated [CHIP-0026](https://github.com/Chia-Network/chips/pull/100) according to the new changes.

I think we should either get rid of the duplicated check above if it's not important enough, or add `# pragma: no cover` to it. Since it's an almost impossible...

I'd like to note that with [CHIP-0026](https://github.com/Chia-Network/chips/pull/100) once adopted, hitting the subscription limit will result in a rejection instead of silently failing. The wallet can then respond appropriately, such as...

We don't yet use CHIP-0026 in the wallet , though it will be in the full node in the upcoming release if things go according to plan. So for now...