Governance System

Governance System

Community Meetings and Updates

All Miner Councils must schedule recurring meetings every two weeks with the community to provide updates, interview and debate proposal authors, and answer questions from the community related to their domain. Meetings take place in the Recurring Council Meetings channel on the Telcoin Association Discord.

Recurring Meetings

Overview

All Miner Councils must schedule recurring meetings every two weeks with the community to provide updates, interview and debate proposal authors, and answer questions from the community related to their domain.

Meetings take place in the “Recurring Council Meetings” channel on the Telcoin Association Discord.

Frequency and Channels

  • Frequency: Meetings must be held least every two weeks, with two weeks notice of the day and time.
  • Channels
    • Scheduling: Meeting schedules and agendas must be posted in the “Council Meetings Updates” channel of the Telcoin Discord.
    • Meeting Location: All recurring meetings must take place in the “Recurring Council Meetings” voice channel on the Telcoin Discord.

    • Agenda, Frequency, Attendees

  • Global Councils: Platform and Treasury Council schedule and host recurring meetings together.
    • Agenda: Update the community on platform-wide and treasury activities and outcomes, interview debate TIP & TELIP proposals with the author and the community, and answer general questions related to Platform-wide facilities, Telcoin Network, and the TEL Treasury.
    • Attendees: All Platform and Treasury council members must attend every recurring meeting or provide the community with an explanation and summary of their opinions related to TIP, TELIP proposals on the agenda, or else the Compliance Council may direct the Telcoin Association Operations UAB (TAO) to revoke absent members governance NFT and vote on their behalf until a new candidate is selected.
  • Local Councils: TAN and TELx Council schedule and host recurring meetings related to their domains. Councils may choose to schedule meetings with both Councils or separately. In other words, network councils are autonomous in their periodic communications with the community related to their domain, but may choose to coordinate meetings together to solve shared problems or share preferences.
    • Agenda: Update the community on TAN or TELx activities and outcomes, interview and debate TANIP or TELxIP proposals with the author and the community, and answer general questions related to TAN or TELx facilities, inventories, and other related systems.
    • Attendees: All TAN and TELx council members must attend every recurring meeting or provide the community with an explanation and summary of their opinions related to TANIP(TAN Council) or TELxIP(TELx Council) proposals on the agenda, or else the Compliance Council may direct the TAO to revoke absent members governance NFT and vote on their behalf until a new candidate is selected.
  • Compliance Council: At least one Compliance Council member must attend all recurring meetings, and must share updates related to their domain in system-wide council meetings each time a CCIP proposal has been submitted.

    • Proposal Updates

    Overview

    Proposal authors and voters must submit updates to the proper channels, or else the Compliance Council may request the TAO revokes the absent Council Members’ governance NFT and vote on their behalf until a new member is selected by Miners.

    Positions, Required Actions, Examples

    Proposal Authors: Council members who submit improvement proposals to council snapshots for voting.

  • Required Actions: Miner Council proposal authors must submit updates to the relevant proposal updates channel after the proposal each time the proposal is submitted to a council for voting, after each voting period concludes, and after the proposal has been implemented.
    • Proposal Initiation: At the time of submission, the proposal author is required to submit a link to their snapshot proposal in the relevant improvement proposal updates channel.
      • Example: After submitting a TELIP proposal to a snapshot, the TELIP proposal author must submit the proposal, including the snapshot link to the TELIP proposal, to the ‘TELIP updates channel’ on the Telcoin Discord.
    • Voting Outcome: After each voting period by a Miner Council concludes, the proposal author is required to submit the outcome to the relevant improvement proposal updates channel.
      • Example: After a proposal has been voted on by a Council, the TELIP proposal author must submit the outcome of a proposal, including the snapshot link to the TELIP proposal, to the ‘TELIP updates’ channel on the Telcoin Discord.
    • Implementation: After the improvements planned in the improvement proposal have been completed, the proposal author is required to share the link to the documentation, code, and/or other pertinent information related to the now completed improvement to the relevant proposal updates channel.
      • Example: After their proposed TELIP has been implemented, the proposal author must submit information related to the upgrade after it has been implemented to the ‘TELIP updates channel’ on the Telcoin Discord.

    • Voters: Council members who vote on proposals that have been submitted to their snapshot.

  • Required Actions: After voting, all Council Members must share whether they voted yes or no on a given proposal and their rationale to the updates channel on discord associated with the proposal type.
    • Example: TIP voting outcome and rationale should be submitted by the Platform Council voter to the TIP proposal updates channel)
    • Telcoin Association Discord: Proposal Update Channels