Add wallet authentication documentation to scenarios 26-35, 41, 43-45
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Successful in 2s
Deploy to Testnet / deploy-testnet (push) Successful in 1m7s
Documentation Validation / validate-docs (push) Failing after 11s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Multi-Node Stress Testing / stress-test (push) Successful in 3s
Node Failover Simulation / failover-test (push) Successful in 4s
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Successful in 2s
Deploy to Testnet / deploy-testnet (push) Successful in 1m7s
Documentation Validation / validate-docs (push) Failing after 11s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Multi-Node Stress Testing / stress-test (push) Successful in 3s
Node Failover Simulation / failover-test (push) Successful in 4s
- Add wallet authentication section to scenarios 26-35, 41, 43-45 - Document three authentication methods: interactive prompt, password file, and environment variable - Include security best practices for password handling - Add code examples for each authentication method with scenario-specific commands - Recommend password files with restricted permissions for scripts
This commit is contained in:
@@ -65,6 +65,26 @@ An hermes agent acts as a validator to:
|
||||
- Mining node configured
|
||||
- Wallet configured with staking balance
|
||||
|
||||
### **Wallet Authentication**
|
||||
For validator operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc validator init --wallet my-wallet --stake-amount 1000
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc validator init --wallet my-wallet --stake-amount 1000 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc validator init --wallet my-wallet --stake-amount 1000
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An Hermes agent acts as a cross-chain trader to:
|
||||
- Marketplace accessible on all chains
|
||||
- Wallets configured on each chain
|
||||
|
||||
### **Wallet Authentication**
|
||||
For cross-chain trading operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc cross-chain swap --from my-wallet --to-chain ait-mainnet --amount 100
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc cross-chain swap --from my-wallet --to-chain ait-mainnet --amount 100 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc cross-chain swap --from my-wallet --to-chain ait-mainnet --amount 100
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as a monitoring agent to:
|
||||
- Messaging service available
|
||||
- Blockchain node accessible
|
||||
|
||||
### **Wallet Authentication**
|
||||
For monitoring operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc monitor start --wallet my-wallet --interval 60
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc monitor start --wallet my-wallet --interval 60 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc monitor start --wallet my-wallet --interval 60
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as a plugin marketplace agent to:
|
||||
- Marketplace service running
|
||||
- Plugin development environment
|
||||
|
||||
### **Wallet Authentication**
|
||||
For plugin marketplace operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc plugin publish --wallet my-wallet --plugin-id custom-llm-plugin
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc plugin publish --wallet my-wallet --plugin-id custom-llm-plugin --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc plugin publish --wallet my-wallet --plugin-id custom-llm-plugin
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as a database service provider to:
|
||||
- Marketplace service accessible
|
||||
- Security service configured
|
||||
|
||||
### **Wallet Authentication**
|
||||
For database service operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc database init --wallet my-wallet --name my-db-service --capacity 100GB
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc database init --wallet my-wallet --name my-db-service --capacity 100GB --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc database init --wallet my-wallet --name my-db-service --capacity 100GB
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as a federation bridge to:
|
||||
- Cross-chain bridge running
|
||||
- Messaging service available
|
||||
|
||||
### **Wallet Authentication**
|
||||
For federation bridge operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc island bridge create --wallet my-wallet --source-island island-001 --target-island island-002
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc island bridge create --wallet my-wallet --source-island island-001 --target-island island-002 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc island bridge create --wallet my-wallet --source-island island-001 --target-island island-002
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An Hermes agent acts as an AI power advertiser to:
|
||||
- Marketplace service running
|
||||
- Analytics service available
|
||||
|
||||
### **Wallet Authentication**
|
||||
For AI power operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc ai test --wallet my-wallet --model llama2 --prompt "Test prompt"
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc ai test --wallet my-wallet --model llama2 --prompt "Test prompt" --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc ai test --wallet my-wallet --model llama2 --prompt "Test prompt"
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as a multi-chain validator to:
|
||||
- Staking service running
|
||||
- Monitoring service available
|
||||
|
||||
### **Wallet Authentication**
|
||||
For multi-chain validator operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc validator multi-init --wallet my-wallet --chains ait-mainnet,ait-testnet --stake-amount 500
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc validator multi-init --wallet my-wallet --chains ait-mainnet,ait-testnet --stake-amount 500 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc validator multi-init --wallet my-wallet --chains ait-mainnet,ait-testnet --stake-amount 500
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as a compliance agent to:
|
||||
- Security service running
|
||||
- Analytics service available
|
||||
|
||||
### **Wallet Authentication**
|
||||
For compliance operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc compliance init --wallet my-wallet --policies security,governance
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc compliance init --wallet my-wallet --policies security,governance --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc compliance init --wallet my-wallet --policies security,governance
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -65,6 +65,26 @@ An hermes agent acts as an edge compute provider to:
|
||||
- Island network configured
|
||||
- Database service running
|
||||
|
||||
### **Wallet Authentication**
|
||||
For edge compute operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc island join --wallet my-wallet --island-id island-001 --role compute-provider
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc island join --wallet my-wallet --island-id island-001 --role compute-provider --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc island join --wallet my-wallet --island-id island-001 --role compute-provider
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -66,6 +66,26 @@ An hermes agent uses the bounty system to:
|
||||
- Wallet with sufficient AIT tokens for bounty payments
|
||||
- Agent SDK configured
|
||||
|
||||
### **Wallet Authentication**
|
||||
For bounty operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc agent bounty create --title "GPU Optimization" --reward 1000
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc agent bounty create --title "GPU Optimization" --reward 1000 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc agent bounty create --title "GPU Optimization" --reward 1000
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow
|
||||
|
||||
@@ -67,6 +67,26 @@ An hermes agent uses the knowledge graph marketplace to:
|
||||
- Agent SDK configured
|
||||
- IPFS client configured
|
||||
|
||||
### **Wallet Authentication**
|
||||
For knowledge graph operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc agent knowledge create --name "AI-Models-Graph" --description "Knowledge graph for AI models"
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc agent knowledge create --name "AI-Models-Graph" --description "Knowledge graph for AI models" --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc agent knowledge create --name "AI-Models-Graph" --description "Knowledge graph for AI models"
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -66,6 +66,26 @@ An hermes agent uses the dispute resolution system to:
|
||||
- Wallet with sufficient AIT tokens for staking
|
||||
- Agent SDK configured
|
||||
|
||||
### **Wallet Authentication**
|
||||
For dispute resolution operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc agent dispute file --transaction-id <tx-id> --reason "Service not delivered" --stake 100
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc agent dispute file --transaction-id <tx-id> --reason "Service not delivered" --stake 100 --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc agent dispute file --transaction-id <tx-id> --reason "Service not delivered" --stake 100
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
@@ -68,6 +68,26 @@ An hermes agent uses zero-knowledge proofs to:
|
||||
- Agent SDK configured
|
||||
- IPFS client configured
|
||||
|
||||
### **Wallet Authentication**
|
||||
For zero-knowledge proof operations requiring wallet signing, use one of these methods:
|
||||
|
||||
```bash
|
||||
# Interactive prompt (default)
|
||||
aitbc agent zk generate-proof --circuit groth16 --input ./input.json
|
||||
|
||||
# Password file (recommended for scripts)
|
||||
aitbc agent zk generate-proof --circuit groth16 --input ./input.json --password-file /path/to/password.txt
|
||||
|
||||
# Environment variable
|
||||
export KEYSTORE_PASSWORD=mypassword
|
||||
aitbc agent zk generate-proof --circuit groth16 --input ./input.json
|
||||
```
|
||||
|
||||
**Security Best Practices:**
|
||||
- Use password files with restricted permissions (chmod 600)
|
||||
- Store password files outside the repository
|
||||
- Avoid hardcoding passwords in scripts
|
||||
|
||||
---
|
||||
|
||||
## 🔧 **Step-by-Step Workflow**
|
||||
|
||||
Reference in New Issue
Block a user