feat(connect): introduce ignite connect

[julienrbrt]

Introducing the Ignite Connect App. This app allows interacting with any cosmos chain for making queries and transactions.
This is the replacement of ignite node, a command in ignite that did basically the above but only for bank queries and transactions, as well as querying transaction hashes. Once this is released, ignite node will be deprecated.

This app is shares the same concepts as Hubl.
However, it doesn't share the same codebase and is better integrated in Ignite for a better UX (supporting ignite account for key management and replacing an existing ignite feature).

[julienrbrt]

Getting back to this 😅

[julienrbrt]

R4R! In a follow-up I'll upgrade the app to use ignite 29 and wired keyring (it is a bit annoying to do that with 0.50 client/v2).

[Pantani]

I got an error connecting to Archway (archway.lavenderfive.com:443):

➜  apps git:(julien/connect) ignite connect archway
2025-02-05T21:10:38.454-0300 [ERROR] app /Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect: plugin process exited: plugin=/Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect/connect.ign id=53918 error="exit status 2"
✘ Error reading from server: EOF

[Pantani]

the same for atomone

ignite connect atomone                                                                  
2025-02-05T21:15:15.372-0300 [ERROR] app /Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect: plugin process exited: plugin=/Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect/connect.ign id=54296 error="exit status 2"
✘ Error reading from server: EOF

I got an error connecting to Archway (archway.lavenderfive.com:443 and grpc.mainnet.archway.io:443):

➜  apps git:(julien/connect) ignite connect archway
2025-02-05T21:10:38.454-0300 [ERROR] app /Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect: plugin process exited: plugin=/Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect/connect.ign id=53918 error="exit status 2"
✘ Error reading from server: EOF

[Pantani]

Sometimes, it takes too long after Selected endpoint: ..... Can we add a spinner?

[julienrbrt]

the same for atomone

ignite connect atomone                                                                  

2025-02-05T21:15:15.372-0300 [ERROR] app /Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect: plugin process exited: plugin=/Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect/connect.ign id=54296 error="exit status 2"

✘ Error reading from server: EOF

I got an error connecting to Archway (archway.lavenderfive.com:443 and grpc.mainnet.archway.io:443):

➜ apps git:(julien/connect) ignite connect archway

2025-02-05T21:10:38.454-0300 [ERROR] app /Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect: plugin process exited: plugin=/Users/danilopantani/Desktop/go/src/github.com/ignite/apps/connect/connect.ign id=53918 error="exit status 2"

✘ Error reading from server: EOF

Yeah, not all endpoints work from the chain registry unfortunately. We should eventually pick preferred ones to show first to improve the UX. Right not you need to try a bit until you find one that works :/
You can try with a local chain as well, if you do connect add simapp localhost:9080.

[Pantani]

Some interactions we can improve

If we try to delete a nonexisting chain, it always shows success, maybe we should show that the chain was not there:

Ignite connect remove shows an error:

Ignite connect add only, tries to add a empty chain:

[julienrbrt]

The last one is expected. I'll improve the other two yes 👍🏾

[julienrbrt]

R4R again @Pantani.
About this: #102 (comment), given the uncertainty over 0.52, I am just going to pull in the latest client/v2 in that app, to have the whole logic there. Gives us beter control as well. I'll do that in a follow-up.

[Pantani]

LGMT!!! amazing feature