feat: add bloom wallet

[MarkNerdi]

Description

This PR add Bloom wallet to the list of supported wallets

PLEASE NOTE- Checklist must be complete prior to review.

Checklist

• Increment the version field in package.json of the package you have made changes in following semantic versioning and using alpha release tagging
• Check the box that allows repo maintainers to update this PR
• Test locally to make sure this feature/fix works
• Run yarn check-all to confirm there are not any associated errors
• Confirm this PR passes Circle CI checks
• Add or update relevant information in the documentation

Docs Checklist

• Include a screenshot of any changes (see docs README on running locally)
• Add/update the appropriate package README (if applicable)
• Add/update the related module in the docs demo (if applicable)
• Add/update the related package in the docs/package.json file (if applicable)

If this PR includes changes to add an injected wallet or SDK wallet module:

Please complete the following using the internal demo package.
To run this demo use the command yarn && yarn dev to get the project running at http://localhost:8080/

Tests with demo app (injected)

• send transaction
• switch chains
• sign message
• sign typed message
• disconnect

Tests with demo app (SDK)

• send transaction
• switch chains
• sign message
• sign typed message
• disconnect

[Adamj1232]

Suggested change

	"version": "2.1.2",
	"version": "2.0.0-alpha.1",

[Adamj1232]

Hi @MarkNerdi it looks like the build is failing within the PR status checks - can you have a look when you get a moment?

[MarkNerdi]

@Adamj1232
Updated the code, can you run the workflow again pls? 🙏

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub ↗︎

👍 No dependency changes detected in pull request

[Adamj1232]

@MarkNerdi local testing and build went well. I formatted the files and added the bloom module to the internal demo - packages/demo/package.json where it wasnt added. Was bloom wallet functionality tested using the internal demo on your end?

[MarkNerdi]

@Adamj1232
Yes i tested it locally, for that i had to remove @web3onboad/bloom from the package.json, as that isnt published yet

[Adamj1232]

@MarkNerdi code is looking good! When testing locally I am getting the following error:

[MarkNerdi]

@Adamj1232 This error occurs when you dont have bloom installed on you machine. Do you have an example in your project where a wallet prompts the user to download it? i could add that

[Adamj1232]

@Adamj1232 This error occurs when you dont have bloom installed on you machine. Do you have an example in your project where a wallet prompts the user to download it? i could add that

@MarkNerdi ah gotcha, yeah we would def want to display a download message so users can add Bloom if they want - here is an example to display that message formatted using a helper function -

web3-onboard/packages/okx/src/index.ts

Line 35 in eb205fb

throw new Error(createDownloadMessage('OKX Wallet', downloadUrl))

[MarkNerdi]

@Adamj1232
Sadly there is no consistent way to determine if an application is installed via the browser. The code in the newest PR checks if updating location.href to a specified protocl throws an error or not, which happens on Windows (and Mac) i think.

[Adamj1232]

Looks good! Thanks for contributing to W3O!