Run of Show created

• Adding guest questions

Research options for being able to manage incentives programmatically - scripts or smart contracts or something else.

End of year tshirt gift for Vanguards

Audit request for provider.akash-ott.zapto.org. All prerequisites are complete, please reply on this issue if I need to change anything. Thanks very much.

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Name
2. Discord handle or Telegram handle
3. Contact email address

• sig-analytics #169

@envy-cosmos

• sig-education meeting 1
• sig-education meeting 2
• sig-community meeting 2
• wg-crew3 meeting 1
• wg-events-2023 meeting 1
• wg-akash-hackathon meeting 1

Upcoming meeting details and links need to be added.
Descriptions need to be updated.

When deploying for a GPU, the bid engine doesn't return the GPU model or vendor. This is crucial for users to know which provider to choose for which model, especially when deploying with a wildcard in the SDL.

Details:
akash-network/support#124

Drafting Overview/Agenda

Three new courses

• CLI Provider deployment
• Terraform
• Akash Console

Date & Time:
3/1 @ 12pm MST

Hosted by Akash

Guests: TBD

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Name
2. Discord handle or Telegram handle
3. Contact email address

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Name
2. Discord handle or Telegram handle
3. Contact email address

Support for managing secrets helps unlock multiple use cases, including but not limited to:

• Private container registry support
• Storing of secrets for use with other applications (like validator keys etc)

The exact solution is TBD with engineering but the initial thought is to integrate with HashiCorp Vault for the first version

Add meeting notes to sig-documentation.
This should be completed shortly (speaking with a community member to take the note bounties).

Hello !

Please can you pass the audit for provider.akth-cryptobabou.com ?

Discord handle : CryptoBabou
Contact email address : [email protected]

thank in advance,

Messaged sponsorship team

chore: add meeting notes and transcripts to wg-content-moderation for meetings 1, 2, and 3.
This should be completed shortly (speaking with a community member to take the note bounties).

We have completed all the prerequisite steps as outlined below. If you could review/audit our provider we'd be appreciative.

Our contact information follows

Name : CryptoBabou
Discord handle or Telegram : CryptoBabou
Contact email address : [email protected]
Provider details are : provider.akth-cryptobabou.com

• Identify sources for each GPU type
• Compare/ contrast pricing
• Negotiate and establish 1y contracts

Should be completed shortly with a community member picking up this bounty.

Hi,

I'd like to request that my provider is audited please.

Email Address: [email protected]

Thanks,

Liam

Having access to the IP lease from the deployment is important in cases where the deployment needs to use the IP address for communication once the application comes up.

Details: akash-network/support#84

Reached out regarding sponsorship and speaking engagement

Content moderation work is currently scoped to two areas as outlined in this PRD https://github.com/akash-network/community/blob/main/wg-content-moderation/prd.md

• Management API
• Moderation API

Hello !

Please can you pass the audit for provider.www.akt-cryptobabou.com ?

Discord handle : cryptobou

thank in advance,
CryptoBabou

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

node1:~$ provider-services query provider get akash1<redacted> -o text
attributes:
- key: region
  value: us-east
- key: host
  value: akash
- key: tier
  value: community
- key: organization
  value: akash-cloud.com
- key: statusPage
  value: status.akash-cloud.com
- key: hardwareCpuArch
  value: x64
- key: hardwareGpuVendor
  value: Nvidia
- key: featPersistentStorageType
  value: beta1
- key: capabilities/storage/1/class
  value: beta1
- key: capabilities/storage/1/persistent
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/tu117
  value: "true"
host_uri: https://provider.akash-cloud.com:8443

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

ubuntu:~$ host anything.ingress.akash-cloud.com
anything.ingress.akash-cloud.com has address 71.65.232.20

3. Please make sure your Akash provider doesn't block any Akash specific ports.

Confirmed

Audit Steps:

1. Title the issue: " [Provider Audit]: provider.akash-cloud.com"

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Name
   Pete
2. Discord handle or Telegram handle
   bigdahog
3. Contact email address
   [email protected]

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

Name - Abraham
Discord handle or Telegram handle: freakin | blkbox
Contact email address: [email protected]

Parameter change for bid deposit and provider deposit will be changed from 5akt to 0.5AKT.

This requires a proposal on chain.

Georgepro will handle add detailed notes and actions items to sig-design monthly meeting 2 notes: https://github.com/akash-network/community/blob/main/sig-design/meetings/002-2023-02-21.md

• sig-education meeting 3 (/003-2023-04-11.md)
• sig-education readme #164
• sig-community meeting 3 (/003-2023-04-11.md)
• sig-community readme
• wg-events-2023 (002-2023-04-19.md)
• wg-akash-hackathon (002-2023-04-21.md)

@iamGeorgePro

Add meeting notes to sig-documentation.
This should be completed shortly (speaking with a community member to take the note bounties).

Run of Show drafted

• Adding Questions

• wg-akash-hackathon
• wg-docs 2.0 working sessions
• sig-community readme
• sig-education readme
• wg-akash-website - #177

Validate whether Akash is able to orchestrate native windows containers on windows machines as a PoC for a potential partnership and work on changes to support it if needed.

Kubernetes does support Windows native containers but seems like only for Windows server 2019: https://kubernetes.io/docs/concepts/windows/intro/

• wg-akash-hackathon meeting 2023-05-08.md
• sig-education meeting 2023-05-09.md
• sig-community meeting 2023-05-09.md
• sig-design meeting 2023-05-10.md
• wg-events-2203 meeting 203-05-10.md

@iamGeorgePro

ICS-27 Interchain Accounts outlines a cross-chain account management protocol built upon IBC. ICS-27 enabled chains can programmatically create accounts on other ICS-27 enabled chains & control these accounts via IBC transactions (instead of signing with a private key).

Details: https://github.com/cosmos/ibc/blob/main/spec/app/ics-027-interchain-accounts/README.md

Need to become member of Cloud Native Computing Foundation to get 8k level sponsorship.

Otherwise lowest sponsorship tier is 28k

Reviewing options

https://docs.google.com/forms/d/e/1FAIpQLSd4djPpUNfABmv65fw1Vp21U4OsQO8zkTp3roTfg625D0Jy_g/viewform

@figurestudios will add detail notes for sig provider meeting 2: https://github.com/akash-network/community/blob/main/sig-providers/meetings/002-2023-02-22.md

The file for yesterday's meeting for sig-docs need to be updated with the following information:

1. Notes
2. Participants
3. Transcript
4. Meeting Details (including recording)

@brewsterdrinkwater are you able to do points 2-4, or do you know who can? After this, I can add the notes as usual.

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host ingress.aresakash.tech (ip 46.173.164.46)

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Name (Vladyslav)
2. Discord handle or Telegram handle (Dis Jolandemo#7347
3. Contact email address [email protected]

Prerequisite Steps:

1. Make sure your provider has community provider attributes:

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Name - Abraham
2. Discord handle or Telegram handle: freakin | blkbox
3. Contact email address: [email protected]

Own and produce notes for sig-design and sig-community starting the next scheduled meetings according to the standards and formatting as illustrated in the sig-client meeting notes.

Owner: community contributor iamGeorgePro

Important parameters:

• Clear and concise
• Use full sentences and proper grammar
• Posted within 48 hours of sig meetings' completion

Setting call with sponsorship manager