akash-network / community

Starting point for joining and contributing to building Akash Network
MIT License
55 stars 28 forks source link

[Provider Audit] provider.brixzen.my.id #658

Closed brixzen closed 3 months ago

brixzen commented 3 months ago

Prerequisite Steps:

1. Make sure your provider has community provider attributes and your contact details (email, website):

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

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

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

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 : Ali Usman
  2. Discord : usman.brixzen AND Telegram : brixzen
  3. Contact email address : admin@brixzen.com
shimpa1 commented 3 months ago

hi @brixzen ,

Provider responding to https status endpoint: yes Provider responding to grpc status endpoint: yes Provider responding to orders: no - The auditor did not get a response from the provider when placing an order. The Provider account does show activity. Requires further testing.

Currently set attributes: provider-services query provider get akash1ylcl54t38pw8hg2ehvs84r9jnwlfrxd7e889wk attributes:

**Attributes correct: no

Add the following to the bottom of the ~/provider/provider.yaml file email: admin@brixzen.com website: https://brixzen.com

Then run helm upgrade --install akash-provider akash/provider -n akash-services -f provider.yaml --set bidpricescript="$(cat ~/provider/price_script_generic.sh | openssl base64 -A)"

Please fix these issues then we can continue.

thank you!

Shimpa

brixzen commented 3 months ago

Hi @shimpa1

update of attribute done, how to test : Provider responding to orders: no

brixzen commented 3 months ago

i think found something here, why provider responding to orders: no,

Screenshot 2024-08-20 at 02 05 57

because of my wallet used as deployment orders before. i will try to update first. an re-run the setup.

thanks @shimpa1

brixzen commented 3 months ago

done now, hopefully will be working now @shimpa1 i also changed the key using new wallet. thanks..

provider-services query provider get akash142cqa0uzcmjk8dpfd2lmcvpkr4jdxtstnguh48 attributes:

shimpa1 commented 3 months ago

@andy108369 Provider akash142cqa0uzcmjk8dpfd2lmcvpkr4jdxtstnguh48 ready to be signed

andy108369 commented 3 months ago

Tested (with dseq 17693194)

Signed

FWIW: the email & website do not need to be provider attributes, but just the info fields only.