Skip to content

Latest commit

 

History

History

validation

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Readme.md
Readme.md
 
 

Readme.md

Notional Validation

Index

  1. What chains does Notional validate?
  2. The role of a validator
  3. Our validator policy
  4. Where we want to validate
  5. How we validate
  6. Validators and relayers partnerships

What chains does Notional validate?

Notional is an active set validator on:

  1. Osmosis
  2. Cosmoshub
  3. Juno
  4. Sifchain
  5. Omniflix
  6. Secret-Network
  7. Starname
  8. Regen
  9. Akash
  10. Sentinel
  11. E-Money
  12. Ixo
  13. Ki
  14. Cyber
  15. Cheqd
  16. Stargaze
  17. Chihuahua
  18. Kava
  19. BitCanna
  20. Evmos
  21. Provenance
  22. Bitsong
  23. Fetch.AI
  24. Umee
  25. Injective
  26. Passage3D
  27. Stride
  28. QuickSilver
  29. Mars

The role of a validator

We think that validators should be actively involved in supporting the communities that they serve. As we scaled, it became increasingly obvious to Jacob that he could not personally manage every piece of adequately serving all IBCGang blockchain communities, so we're moving to a model where larger vote weight %age validators have an individual rep to the community, and smaller vote weight chains have shared representatives.

We are in it for the long-haul.

We manage our organization by git issues, and if your community needs help, they can make an issue here.

Our validator policy

  1. We do not validate chains whose development teams do not prioritize user well-being
  2. We prioritize ethics and the well-being of users above all other matters. When there is a conflict of interest, we will discuss that with the community in an open fashion at: https://twitter.com/notionaldao. We discuss things on twitter, because it is a commons.
  3. We audit and test releases before public upgrade on chain that we validate.
    • As a validator on many chains, we have directly experienced chain upgrade failure when core team overlooks a bug. It is always good to have a second independent inspection from an experienced validator like Notional.
  4. While we strive for transparency, in security critical situations where disclosures could harm user well being, we're silent as a mouse.

Where we want to validate

Notional is validating, but not in the active set:

Testnet validators

  1. Axelar
  2. Stride
  3. Sei
  4. Mars

Notional wishes to validate:

  • Every IBC-enabled blockchain

Notional has decided to maintain relayers for all chains -- and document processes -- on all chains where we are in the active validator set. Presently, that means that we will maintain relayers on up to 20 * 20 = 400x2 = 800 channels. If you are a community member or team that wants to see notional relay for your community, please put an issue on this repository and we will set up a relayer.

How we validate

We aren't most validators. We're operating under the assumption that notional is joining your team, to serve your chain's community. From that point of view, we validate, relay, provide support, and soon, even develop hardware products with the blockchain communities that we serve.

  • Bare Metal
  • On-Premesis
  • Industrial Strength Internet Connections built from residential fiber lines for resilience and easy moves
  • 4G network backup
  • Love, passion, play, and fun: we want to get to know you, your software, and your users and build something better than exists today.

Validators and relayers partnerships <- this became the GMA.

Our technical partners agree to:

  • Mutual Aid Re: Uptime (eg: phone calls to one another)
  • Full commitment to open source, repeatable infrastructure (we only partner with validators who document their infrastructure)
  • Join a Twitter DM Chat, since it isn't discord.
  • Share information about chain launches