tfgrid/circle_engineering
22
0
Fork 0
Code Issues 61 Pull Requests Packages Projects 1 Releases Wiki Activity
677fade281
circle_engineering/meetings_notes/engineering_meeting_24-08-12.md
Mik-TF 44efe31a8e added 08-12 meeting
2024-08-12 11:17:38 -04:00

4.9 KiB
Raw Blame History

Developers Meeting: 24-08-12

Table of Contents

Introduction

We provide information on developers meeting.

Attendees

  • Ahmed
  • Kristof
  • Scott
  • Mik

Main Content

INCA Project

  • inca project
    • inspiration from hashgraph website
    • clear agreement between participants
    • tokenomics
      • Kristof finished a tokenomics version
      • 75% TFT to community
      • 25% to team, investors
    • conversion
      • all vesting
        • at first gets 60% of INCA
        • rest is unlock over time
      • farmers over 3 years
      • ecosystem over 4 years
      • investors
        • 1 quarter later
      • conversion: 1 TFT --> 1 INCA
      • first 1 billion is TFT
      • 3 next billions are INCA
    • liquidity pool
      • INCA, TFT, fiat currencies
        • how we convert in-between
      • e.g. someone pays capacity
        • can pay in USD
          • buy from the liquidity pool
      • todo with liquidity pool
        • define how liquidity pool
          • accelerated liquidity pool
        • define how farmers will be paid in INCA
          • leave this to the COOP
    • utilization
      • 80% of utilization goes to farmers
      • 20% goes to cooperative
        • or 10% coop, 10% validator
      • rewards locked
        • coop decides how they want to use them
        • e.g. can say
          • rewards coming available
            • can use it for emerging country
            • can use for specific use case
            • use to drive demand

Cloud and Hero

  • cloud threefold
    • focus on pulumi
      • create and delete steps
  • hero
    • bring first version of hero live
    • do for specific use cases
      • alternative to calendly

Manual Updates: Pulumi and Terraform

  • Manual updates overview
    • pulumi
      • section in manual cleaner than terraform
      • can use code
      • TF strong with infrastructure as code
        • UI, not really our strenght
      • todo: explain more for people who don't know about it
    • python and pulumi
      • once we have it we add it to the manual
  • manual mycelium
    • updates from planetary to mycelium
      • OK for dev branch for now (manual.dev.grid.tf)
  • manual python with pulumi
    • needs some configurations to be updated
      • Thabet will work on this and we can improve the manual when we get more python/pulumi info+content
    • more examples
      • threefoldtech/pulumi-threefold
        • link to examples
      • lead people to Python
        • Ahmed is working on this
    • explain better what the properties are
      • e.g. sizes
      • link to Pulumi docs
    • move pulumi above terraform
  • terraform
    • terraform_full_vm
      • explain HRU, HDD
      • variable size, what is size
    • emphasis on example
    • add examples

Responsibility and Stories

  • responsibility of a story needs to be to someone who will own it
    • e.g. call the assigner evey day and see if it's being worked on
    • coordinator needs to find someone to take ownership
    • members
      • owner of a story
      • assigning
    • in a story
      • who owns it
        • takes responsibility that it gets done
      • person who needs to execute
        • if someone not doing the work, escalate to higher level, e.g. Kristof

Threefold.io Caddy Issue

  • threefold.io caddy issue
    • it has been fixed

Community Meeting

  • community meeting
    • more details on cyber security
      • no longer going to work
      • that is what we're going to do
    • Scott can discuss it but needs more info
      • what types of workloads won't work anymore
      • is it for all nodes or some nodes
      • could be good if farmers could opt-in or opt-out
  • uniqueness identification
    • civic.com, shufti pro

To discuss next meeting

  • discuss if we change farming rewards for HDD-only node
  • violation of minting for some nodes
    • Scott checks the differences
    • discuss with Lee and Jan
  • 3.15
    • discuss with the team the specs
  • define all products
    • discuss and get feedback from other members
  • gep update
    • discuss how we decide the 80% consensus
  • protection against cyber treats
    • priority for next meeting
    • discuss how we proceed
  • hack/ddos attack of threefold.io

Some Related Links