controllinghand
commented
5 years ago Another alternative to the BP.json file could be a smart contract that BPs can use to register said tool/app/education/resource etc. I'm thinking this could be something in the vain of how proxy account register today I would like to see something like
- EOS account name: Your EOS account name. If a BP should be the one that they use to produce blocks so they get the credit.
- Project Name: This could be the name of the tool,app,topic etc...
- Description: A short description of your project intended to be shown in listings.
- Website: An http or https URL to a website, Reddit post, etc. with more information about your Project.
- Logo: An http or https URL to an image with the size of 256 x 256 px. This should be the logo for the project not the BP's main logo
- Project Status: Is this in Dev, Beta or Production
- Category: This is optional I have some categories I have already created located here https://eosratings.com/top-tools/ for example, explorers, wallets, voting, resources, outreach, education, testnet, key managment, identity, account creation, chain contracts, and a host of monitors and trackers.
lukestokes
igorls
Based on a recent conversation with a BP ratings group, the idea of linking to useful projects came up which makes a lot of sense to me. It would still be up to the community to evaluate that BPs level of involvement in the project or how beneficial that project really is to the greater ecosystem, but I think it might be an interesting way for BPs to quickly communicate to others what they are into. Yes, their website will probably do this also, but having it part of the BP.json standard would help others quickly aggregate this information in a useful way for voters.
What do you think?