Auth should be an EventTarget and emit events

[sgwilym]

What's the problem you want solved?

There is no way to observe whether an Auth has added new keypairs or capabilities without being directly responsible for adding those keypairs or capabilities.

Is there a solution you'd like to recommend?

Auth should extend EventTarget and emit events for:

• Identity keypairs being added
• Share keypairs being added
• Capabilities being added

[Vicente015]

Hello, I would like to implement this, what do you think about the following structure?

Auth Events Reference

Name	Description	Payload
CAP_ADDED	Cap added	ReadCapPack | WriteCapPack
KEYPAIR_ADDED	Keypair added	{ type: 'IDENTITY' | 'SHARE', keypair: ShareKeypairRaw | IdentityKeypairRaw }

More events to consider?:
Reading the code I came up with more events ideas, not sure if they are useful

Name	Description	Payload
CAP_CREATED	Cap created	ReadCapPack | WriteCapPack
CAP_DELEGATED	Cap delegated	ReadCapPack | WriteCapPack
KEYPAIR_CREATED	Keypair created	{ type: 'IDENTITY' | 'SHARE', keypair: ShareKeypairRaw | IdentityKeypairRaw }
READY	Auth is ready (encryptionKey resolved)	Auth

[sgwilym]

Great! I like the DELEGATED, and READY events, they seem useful.

I feel like the CREATED vs ADDED events may be too fine-grained? What do you think? Did you find some use for these?