`on` vs `bind`

It's odd that `Socket` inherits from EventEmitter but implements its own event cycle with `bind`

https://github.com/bcoin-org/bsock/blob/master/lib/socket.js#L19

https://github.com/bcoin-org/bsock/blob/master/lib/socket.js#L837-L887

I raise this issue because I was mistakenly using `on` and not `bind` so events we're firing, but there is something odd about the implementation as such, its managing two lifecycles one on the Socket, one internally on Events.

Perhaps as a solution, `on` could proxy to `bind` when sensible to maintain a consistent event emitter implementation

Read lib/socket.js at lines 19 and 837-887, then compare Socket's inherited EventEmitter behavior with its internal bind-based event lifecycle. Clarify whether on should proxy to bind and define how event registration and emission should remain consistent; validate the chosen behavior against the existing socket event flow.

Written by the indexing model from the issue text.