[PROPOSAL #947] [VOTING] CHIPs signaling phase: Permissionless ICS Frontend

Informal is developing a user-facing frontend for Permissionless ICS. This application aims to address several issues: • With the launch of permissionless ICS, ATOM delegators need a single platform to discover new consumer chains, explore staking rewards, delegate to validators, and engage with the chain’s community, including airdrops and liquidity provision. • The process of navigating a Cosmos chain through devnet, testnet, and mainnet launch phases can be challenging. A comprehensive resource to guide developers through the entire launch process is essential. • Putting together a validator set is often complex and opaque for projects. What’s needed is a single platform where chains could come together with validators to run their chain. Forge offers three main user experiences- for delegators, validators,and chain developers. We are focusing on the delegator experience for the launch. The delegator experience Chain listing screen image 2000×2129 372 KB The chain listing screen will list consumer chains, along with basic information. At launch, users will be able to filter chains by project phase, with additional filtering and search functionality planned…

Excerpt (1197 of 6197 characters). Read the whole post on the forum ↗

This is much more feature-rich than I expected - cudos!

Looking forward to this launching + integrating the PSS calculator to it at some point soon.

Syed:

Looking forward to this launching

Seems to have a hard dependency on hydro, looking forward to that too?

I don’t think it’s a hard dependency - I think Hydro-relation is just that box on the side of one screen.

The rest of the website is coming from onchain data / manual entry, e.g. for the phase 1 Delegator functions:

• Ability to see current/upcoming chains
• See each chains info
• Seeing which vals are validating a particular chain
• and then switching my delegations on the site as a result

jacobgadikian:

Seems to have a hard dependency on hydro, looking forward to that too?

I’ve done UX for both platforms, so can speak to this.

That’s a badge that may only be present on projects that are participating in Hydro.

The page is designed in a way that the badge could be present when applicable and not there when not applicable.

There is no dependency for Hydro in order to launch FORGE and there is no requirement for ICS chains to participate in Hydro.

We will hold an ATOM Zone in a few weeks where I can answer further questions on this platform and we’re open to more feedback, ideas and input via the forum in the interim.

Syed:

This is much more feature-rich than I expected - cudos!

Appreciate that ser!

Great work! Can’t wait for all of this to be finalized, having few successful consumer chains launch and starting biding on Hydro

This looks to be a good UI project.

• I would suggest adding a list of key opinion leaders who can be contacted and used a s channels to distribute information about the upcoming chains off-chain (twitter, TG etc) to help them with traction.
• Could also be useful to add a token section per chain. So that forge offers more granular approach to delegators. The token section could list tokenomics, price and purchase venues for example.

Very interesting concept. I like the idea of having a frontend/platform where delegators, validators and aspiring ICS consumer chains can meet and learn about each other.

I’ve a question regarding this:

jtremback:

Validators

ATOM delegators cannot receive staking rewards from a consumer chain without delegating to a validator who runs that chain. At the bottom of the chain detail screen, delegators can see a list of validators opted in to each chain, and delegate to them right in the interface.

So is it basically ATOM restaking what delegators have to do here, or is liquid ATOM required to be delegate to a consumer chain validator in order to earn staking rewards?

• Let’s suppose I delegated some ATOM to StakeCito on the Hub. Thus, does StakeCito also have to validate the respective consumer chain for me to restake/delegate ATOM on the consumer chain, or could I simply delegate ATOM to an alternative validator that is running this specific consumer chain?

@Seppmos This is purely a frontend to functionality that exists on-chain. The delegate and redelegate functionality in the validator list is just regular Cosmos delegation stuff.

Seppmos:

Let’s suppose I delegated some ATOM to StakeCito on the Hub. Thus, does StakeCito also have to validate the respective consumer chain for me to restake/delegate ATOM on the consumer chain, or could I simply delegate ATOM to an alternative validator that is running this specific consumer chain?

For a given delegation from a delegator to a validator, the delegator will receive rewards for all consumer chains the validator is validating on.

There is currently no concept in ICS of a delegator’s tokens being delegated to different validators on different consumer chains, so the functionality exposed in Forge is just vanilla delegate and redelegate.

We fully support this proposition and love the envisioned design and features. We also endorse the name being chosen “Forge” as well as the early logo design associated with the branding. Additionally, the notification ability is very welcomed. Our only suggestion relates to the “idea phase”: jtremback: Idea phase: In this phase, the developer reads documentation on Cosmos and bootstraps their chain. The ICS integration with Spawn (a chain bootstrapping tool) is important here. Part of every consumer chain’s repo will be a JSON file defining their Forge chain detail screen, including stats, ICS settings, and badges. While developing their chain, a preview of the Forge detail screen can be generated by inputting a link to the chain’s Github repository. A coordinated effort is currently underway within the AADAO to develop an interactive front-end experience for engaging with the ICS Financial modeling we released earlier this year: ICS 2.0 Economics: Partial Set Security (PSS) Financial Model . We strongly recommend merging this initiative with your ongoing efforts with Forge, as they have significant synergies. Selecting the right ICS parameters for a…

Excerpt (1192 of 1928 characters). Read the whole post on the forum ↗

Thanks for these suggestions. I like both of them.

Shotanate:

I would suggest adding a list of key opinion leaders who can be contacted and used a s channels to distribute information about the upcoming chains off-chain (twitter, TG etc) to help them with traction.

This doesn’t feel right for Forge, but perhaps for another website. The initial thought is that this list must be community-managed, though. It sounds prone to drama. I could foresee potential controversy if a KoL is accidentally forgotten to be included, or there will be discussions/frustrations over why some were included because people disagree with their work/funding/impact. It’s not a bad idea, though, as it would be useful for all of Cosmos. It’s just not right for Forge.

Shotanate:

Could also be useful to add a token section per chain. So that forge offers more granular approach to delegators. The token section could list tokenomics, price and purchase venues for example.

This is already designed. These layers are just hidden in the screenshot above. We will go to market as is and then iterate based on feedback. We had the same thinking as you.