Pruned peers do not have the full blockchain history and therefore have only limited value for SPV clients.

With Bitcoin Core 0.16, pruned peers will announce its service via NODE_NETWORK_LIMITED (see BIP159 https://github.com/bitcoin/bips/blob/master/bip-0159.mediawiki). BIP159 is a non consensus change.

This will allow SPV clients to connect to pruned peers. But, since they only signal for the last 288 blocks, SPV/BIP37 clients interested to load history older then 1 day of blocks would still require to connect to traditional peers.

In future, pruned nodes may have a way to signal how many blocks they will keep on disk (without adding a fingerprinting vulnerability).

Not to forget is that BIP37 is a controversial concept. It has significant privacy downsides (see Jonas Nicks research).

A far better concept is "Client side filtering". See the upcoming BIP: https://github.com/bitcoin/bips/pull/636

Pruned peers do not have the full blockchain history and therefore have only limited value for SPV clients.

With Bitcoin Core 0.16, pruned peers will announce their service via NODE_NETWORK_LIMITED (see BIP159). BIP159 is not a consensus change.

This will allow SPV clients to connect to pruned peers. But, since they only signal for the last 288 blocks, SPV/BIP37 clients interested to load history older than 1 day of blocks would still require to connect to traditional peers.

In the future, pruned nodes may have a way to signal how many blocks they will keep on disk (without adding a fingerprinting vulnerability).

Note that BIP37 is a controversial concept. It has significant privacy downsides (see Jonas Nick's research).

A far better concept is "Client side filtering". See the upcoming BIP157 and BIP158.