Celestia testnet explorer tracker

[rach-id]

This will track the remaining issues to be handled before testnet deployment:

• [x] https://github.com/celestiaorg/big-dipper-2.0-cosmos/issues/5
• [x] https://github.com/celestiaorg/big-dipper-2.0-cosmos/issues/15
• [x] https://github.com/celestiaorg/big-dipper-2.0-cosmos/issues/17
• [x] https://github.com/celestiaorg/bdjuno/issues/7
• [x] https://github.com/celestiaorg/bdjuno/issues/12
• [x] https://github.com/celestiaorg/juno/issues/4
• [x] https://github.com/celestiaorg/juno/issues/5

Stretch goals

• [ ] https://github.com/celestiaorg/big-dipper-2.0-cosmos/issues/14
• [ ] https://github.com/celestiaorg/big-dipper-2.0-cosmos/issues/13
• [ ] https://github.com/celestiaorg/big-dipper-2.0-cosmos/issues/6

[lzrscg]

Progress update:

• Made progress setting up infrastructure on AWS
• Juno upstream pulled
• Juno cosmos-sdk version update, but bdjuno has issues
• Bdjuno upstream pulled

[lzrscg]

Current status

• [x] Fix testnet/mainnet config to reflect the correct celes/uceles units #5
• [x] Pull upstream and update the explorer #15
• [x] Rename PayForMessage to PayForData #17
• [x] Fix testnet/mainnet config to reflect the correct celes/uceles units bdjuno#7
• [x] Pull upstream changes bdjuno#12
• [x] Pull upstream changes juno#4
• [x] Depend on the latest version of Cosmos-SDK juno#5

[rach-id]

Great job :tada:

[rach-id]

Can you please open PRs to our repos containing the changes ?

[lzrscg]

@SweeXordious I definitely will, but I haven't fully tested and there still are likely some issues. I will do that once I can confirm everything is polished and ready

[lzrscg]

ok everything is complete. next steps (in order)

1. deploy everything and find/fix bugs
2. contribute changes upstream
3. set up staking ui
4. try for stretch goals

[rach-id]

Sounds awesome. Thanks a lot for your help :D