* one outstanding buig peer list only records a single node * Cullen - Billy invited to get more involved with IBC related topics get the lay of the land
* Sunny really wants batched RPC requests on 9090, similar to GraphQL would be super useful, since for osmosis a lot of requests are necessary. * having a list of 5-6 publicly (i think he means all available ports?) available nodes really helps for ux. * 9090 GRPC mostly used for backends querying nodes, but needs batched requests * 26657 usually not exposed because easily DoSed, but useful for any browser/webapp that needs to query stuff * 26656 is usually the only port exposed. * Adam: relatively easy to get blacklisted by nodes on the P2P port * Some tools are already out built by the community # Discusssion: Best approaches for crawling the network, check if nodes are really active * ETH TokenLists for Cosmos is needed too * take everything from Sunny's tm-network json
* version number, binary location, genesis may seem superfluous but are important if you want to run a node (nowhere else to get all this info in one place) Especially automated deployment of new nodes. Registry not just useful for verifying chain identity. * Discuss what further items to include in the Registry (Sunny) This is part User Interface questions (how to display an IBC connected asset? What level of transparency or insight on security should be my responsibility as an interface developer?) as well as developer experience questions (how do I query the balance of a user with mutli-chain assets and display those assets in a clear and friendly manner?). Highlight, discuss and solve the emerging challenges that need to be addressed by application level developers to ensure a high quality user experience when dealing with an IBC connected Internet of Blockchains.
0 kommentar(er)
