NoFilterPublisher

Unless the chosen filter supports a "fromBlock", there is no way to control precisely at what block a subscription begins. A subscriber receives events "as they happen", and even if they subscribe very quickly after e.g. contract deployment, there can be no guarantee that they won't miss anything.

Fortunately, the most important filters (log filters) do support "fromBlock"

Unfortunately, it seems that clients don't pay attantion to an already-past "fromBlock" in the eth_getFilterChanges most implementations will rly upon.

T is the type that subscribers will receive. S is an intermediate type, that might be acquired then transformed to T. If this is not necessary, just define S to the same type as T. F is the Client.Filter type of the object usually used to specify the items that will get published. (Filter.Dummy can be acquired and left unused if no filter is necessary.)