Block Listener

We expose a block listener which fires when a new block is mined. This normally is a huge pain point for dApps as they have to monitor transactions by polling every x seconds fetching the latest block, essentially guessing when a new block will be mined and also doing a lot of unnecessary HTTP requests. With the use of blooms with the block listener, it allows your dApp to be able to do some really powerful super-efficient stuff with minimal code.

The block listener also handles any disconnects and missing blocks for you. For example, say the client (your user) loses Internet for 1 minute and your dApp misses 4 blocks, once the Internet reconnects the client will emit all the blocks which were missed back in the correct order for you.

This block listener can be hooked in, even if the user is not authenticated, or even if your dApp handles > 1 wallet provider. You can still use this block listener if the user is using another wallet.

The block listener tech documentation can be found here.

If you want to found out how you can benefit from using blooms take a read here.