The Keychain Multichain Explorer Challenge - Open Beta Testing Adventure
Intro..
Really got quite excited about the @keychain Open Beta. Even though i've not been on Hive that long compared to seasoned Vets I would definitely call mysel a Keychain 'Maxi', use the thing pretty much every day, in fact I can't remember when I last didn't use it! lolz.
The gauntlet being thrown down to end users to take part in the Keychain Multichain Explorer Challenge was the icing on the cake.. How exciting, Keychain was spreading it's wings and supporting more chains and tokens, couldn't help but get onboard! :0)

The Open Beta Test Setup..
Having the new Beta version available to install as a standalone Extension I think in the end was a bit of a master stroke, it actually allowed for some quick and painless comparative testing, without the need to panic about removing the original extension etc.
As directed, extract existing Keychain extension Creds via the suggested .kc file method, create a new login on the new Extension with the same password, import the .kc file Creds and badda bing badda boom, up and running.. :)
Door No. 1, first things first, the general UX experience
Blink and you'll miss it, the changes are subtle on the landing page when comparing the floating Keychains but there are a few notable differences (I'm going to stick with dark theme btw, It's my mantra):

- Notification and Claims have moved, basically swapped around with user accounts but it still feels like home for the most part
- Some layout tweaks elsewhere but nothing crazy
Noticed a few niggle items on the Open Beta
- When actioning 'claims' the popup dialog is slow to display in comparison to the existing Keychain, so the user is left wondering if the dialog will display at all, definitely much quicker on the existing Keychain
- Oddly scroll wheel usage on the new Open Beta when sailing through the users list of tokens below Hive /HBD/HP is overly too quick, it's quite difficult to land on the token you want first time, unlike the existing Keychain, much smoother/slower in this respect
Door No. 2, general Signing operations
Genuinely been all over creation here, used heavily in all aspects of Splinterlands, all good nothing to report
- Battle
- Brawl
- Market Buy/Sell
- SPS/DEC Operations
- Tournament
- Proposal Voting
- Tournaments
Couldn't help but share a win lol ;)

https://splinterlands.com/battle/sl_4cdc7a1c2d7065376267675e95470864
In terms of Social Platform Chain operations, again all facets checked and nothing went sideways (HIVE BLOG & PEAKD):
- Comments/Posts
- Upvotes/Downvotes
- Community creation, yes really pushed the boat out, looking forward to finally getting this underway soon with an inaugural post.. watch this space C/Northern Ireland, excited!

Door No. 3, Accounts
This is where the fun starts, lots of shiny new options to play with. I mean clearly standard Hive Account creation is fine as the .kc file import was smooth as silk, but really here talking more about the EVM chain funsies:
Would like to point out that during this process I didn't do any pre-reading, I simply took the menu's as I saw them at face value, to evaluate how intuitive they really were, and was pleasantly surprised.
In terms of the new EVM Chain support, had a small native Wallet in Brave sitting around complete with obviously required EVM support, it was also using Polygon Mainnet and had some custom tokens involved, GLM, so perfect for testing and then took a crack at importing via seed phrase, all good!

Once the EVM Account was added it wasn't difficult to navigate to the Manage Chains Menu and add a custom Chain, in this case the Polygon Mainnet that I had discussed with @stoodkev who confirmed that it would be added by default in due course..
Again nothing in here overly difficult, all just played ball..

And voila, all of a sudden @keychain is rocking Polygon Mainnet support
Last piece of the puzzle to access the aforementioned GLM tokens was to add a new custom token, again in exactly the same manner as the custom Chain eg.

- One bit of niggle here, the Custom token added does not have any attributed value, so only the 5.1 POL is making up the estimated account value which is annoying, I mean if Polyscan can list the GLM value live, maybe a similar mechanism can be used here if possible?
Door No. 4 EVM Chain usage in Web3
Didn't go massively overboard here, just wanted to check if the new EVM support added would behave, so sailed straight to Polygon Portal to try and connect up the wallet..
Pretty damn snazzy seeing the Keychain Icon in the suggested wallets box! ;)

No complaints did what it said on the tin,

Gave Uniswap a rattle as well, no issues to report, both wallet connect and token swapping was 100% :)

Pretty neat, @keychain underpinning the token swappage of two tokens nothing to do with Hive!

Moving back to the Keychain extension itself. Had a bit of a play around with the Inbuilt swap bridge efforts thus far, also a great step in the right direction,

Roundup..
All in all had a great time testing the Open Beta Extension, currently based on experience over the last 14 days or so, I see no need for me personally to go back to the existing Keychain, as the new Beta version is performing admirably. Likely just continue using the Open Beta and see what it can do for me! Take my hat off to the Devs, nice work ;)
Disclaimer:
I'm a Brave user, have been for years, no other Browser comes close IMHO so everything I've proceeded to share here was carried out on Brave 1.91.180 (Official Build)(64-bit)
Congratulations @urielkinnear! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 1500 upvotes.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
Thank you for all the feedback! It is really useful to see you testing every new aspect of the Open Beta.
Just realised I forgot to talk about the side panel UX option.. oops lol