Fix Vault Allocation Error

[prnk28]

Description

When allocating a new user vault we run into a null pointer bug. This endpoint is expected to be resolved by <API_URL>/vault/v1/allocate. This may potentially be an issue in:

• onsonr/crypto for the MPC Share Interface.

Associated Files

These files will be modified by this task.

• x/did/types/controller.go for Controller Initialization

References

Use these documents to help you complete the task.

[prnk28]

onsonr/crypto/mpc/share.go.

The share.go file in the onsonr/crypto repository defines a Share type for managing cryptographic shares. Key functions include:

• GetSignFunc(msg []byte): Returns a signing function based on the role (Alice or Bob) using the K256 curve and SHA-3 hashing.
• GetRefreshFunc(): Returns a refresh function for the share, again based on the role.
• Message(): Decodes the message part of the share.
• Role(): Determines the role (Alice or Bob) from the share.
• PublicKey(): Retrieves the public key associated with the share, decoding it differently based on the role.

The file primarily handles the creation and management of cryptographic shares and their associated operations.

[prnk28]

• Potentially offload static assets which aren't required during vault initialization into CDN (WASM, IMG)
• Update CI/CD Flow to compile WASM assets and offload to R2.