ICON P-Rep Weekly Meetings

February 16, 2020

ICON P-Rep Weekly Meeting #1

<p>Date: 2020-02-15 11:00 PM UTC</p> <p>Attendees: Blockmove, Catalyst, Everstake, ICON BOOM, ICONation, Parrot9, POS Bakerz, RHIZOME, UBIK Capital</p> <h2>Meeting Main Topics</h2> <ul> <li>Top request from the community is a list of contributions of the P-Rep teams visible on the voting screen. It doesn’t have to be perfect. It just needs to be there.</li> <li>Inactive nodes collecting rewards.</li> <li>Dynamic node registration fee.</li> <li>ICONex Mobile Wallet Fee Issue.</li> <li>icon.foundation telegram channel list additions/updates</li> </ul> <h2>Meeting Sub-Topics</h2> <ul> <li>Ledger Support for Staking from Mobile App</li> <li>Ongoing issues with Ledger.</li> <li>Trezor wallet support completion.</li> <li>User request for an auto-restake function.</li> </ul> <h2>Post-Meeting Notes</h2> <h3>P-Rep Contributions on the Voting Screen</h3> <p>The overall consensus is that the voting process needs to be improved. The current voting interface does not include a feature that educates voters on the various teams. Initially, this was not too big of an issue. Recently, the number of P-Rep teams have risen to 100+, so there needs to be a overhaul of the voting UI.</p> <p>Some ideas that were presented in the meeting...</p> <ul> <li>Add some kind of notifaction and other "helper texts" that walk new voters through some basic facts about the ICON network (e.g. voters will receive the same rewards regardless of what P-Rep they vote for).</li> <li>Add additional registration variable to point to a list of contributions on the ICON tracker.</li> <li>Allowing P-Reps to specify the niche they are in (e.g. business dev, marketing, development, etc.) and making those niches visible on the voting interface. If any ICONist is interested in voting for a business development P-Rep, then they can click on the business development niche and select a team.</li> <li>Anything we can do will be an improvement over the current interface which does not provide any context to the voting process.</li> <li>Parrot9 mentioned they are working with ICON Foundation to improve UX. Let's keep discuss this and push for a UI improvement to address the voting flow.</li> </ul> <p>Next Steps: Discuss below, and involve ICON Foundation in the conversation.</p> <p>Discussion: <a href="https://forum.icon.community/t/p-rep-contributions-on-the-voting-screen-in-iconex/441">https://forum.icon.community/t/p-rep-contributions-on-the-voting-screen-in-iconex/441</a></p> <h3>Inactive Nodes Collecting Rewards</h3> <p>Teams had a mixed opinion on this topic.</p> <p>Some ideas that were presented in the meeting...</p> <ul> <li>For the most part Sub P-Rep nodes function as citizen nodes at this time. The ICON network is not under heavy usage at the moment, so a large number of citizen nodes provides unnecessary buffer to relay requests to P-Rep nodes.</li> <li>Many teams are not technical, and forcing teams to run a node will take away their time/effort, which can be used to work on what they're good at (e.g. marketing, bizdev, etc.)</li> <li>The debate is between practicality and philosophy. Some believe that running a node is a core requirement to be a P-Rep (philosophical), some believe that running a node is a soft requirement that can be fulfilled if the team can do so without wasting time/effort (practical).</li> <li>Many Sub P-Rep nodes are operated by OAKNODE. Depending on your views, this is a layer of centralization as without OAKNODE, these teams may not have the technical expertise or interest in securing a node.</li> <li>Blockmove suggested a more practical solution like onboarding more active Sub P-Rep nodes rather than taking a governance-level action.</li> </ul> <p>Next Steps: Discuss below, and put together a governanc</p>