You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Objective:** Verify oracle is providing AKT/USD price feeds with recent timestamps
53
59
54
-
**Important Note:** The oracle module stores prices using the **base denom**`akt`, not the micro-denom `uakt`. The `--asset-denom` flag, if used, must specify `akt` — using `uakt` or `uact` will return empty results.
55
-
56
60
**User Actions:**
57
-
1. Query oracle prices (pipe through `head` to limit verbose output):
58
-
```bash
59
-
akash query oracle prices | head -n 50
60
-
```
61
-
2. Examine the output — confirm price entries exist for `denom: akt` with `base_denom: usd`
62
-
3. Check the `timestamp` field on the most recent price entry (first entry in output)
63
-
4. Compare the timestamp against current time — it should be within 60 seconds:
61
+
1. Query oracle prices and current time:
64
62
```bash
63
+
akash query oracle prices | head -n 15
65
64
date -u +"%Y-%m-%dT%H:%M:%S"
66
65
```
67
-
5. Verify the price value is reasonable (e.g., AKT ~$0.30-$5.00 range depending on market)
66
+
2. Confirm price entries exist for `denom: akt` with `base_denom: usd`
67
+
3. Check the `timestamp` field — should be within 60 seconds of current time
68
+
4. Verify the price value is reasonable (e.g., AKT ~$0.30-$5.00 range)
68
69
69
70
**Expected Results:**
70
71
- Oracle returns price entries (prices list is NOT empty)
71
72
- Entries show `denom: akt` and `base_denom: usd`
72
-
- Price value is a reasonable AKT/USD value (non-zero, non-negative)
73
+
- Price value is reasonable (non-zero, non-negative)
73
74
- Most recent timestamp is within 60 seconds of current UTC time
74
75
75
-
**If This Test Fails:**
76
-
- Empty results → Oracle price feeder may not be running
77
-
- Stale timestamps (>60s old) → Price feeder may have stopped submitting
78
-
- Unreasonable prices → Check Pyth feed ID configuration
76
+
**Proof to Submit:**
77
+
- Oracle prices output showing recent timestamp
78
+
- Current UTC time for comparison
79
79
80
80
---
81
81
@@ -88,77 +88,66 @@ Before running functional tests, verify the BME module and dependencies are heal
88
88
```bash
89
89
akash query bme vault-state
90
90
```
91
-
2. Record baseline values:
92
-
- Balances (VaultAKT)
93
-
- TotalBurned
94
-
- TotalMinted
95
-
- RemintCredits
91
+
2. Record baseline values for later comparison
96
92
97
93
**Expected Results:**
98
94
- Query succeeds
99
-
- All fields returned (may be zero on fresh testnet)
100
-
- Document baseline for later comparison
95
+
- All fields returned: balances, total_burned, total_minted, remint_credits
96
+
97
+
**Proof to Submit:**
98
+
- Full output of `akash query bme vault-state`
101
99
102
100
---
103
101
104
102
### Test 0.5: Collateral Ratio Check
105
103
106
104
**Objective:** Verify collateral ratio calculation is working
107
105
106
+
**Note:** Tests 0.5 and 0.6 use the same command. This test focuses on the `collateral_ratio` value; Test 0.6 focuses on the `status` field and flags.
107
+
108
108
**User Actions:**
109
-
1. Query BME status (collateral ratio is included in output):
109
+
1. Query BME status:
110
110
```bash
111
111
akash query bme status
112
112
```
113
113
2. Locate the `collateral_ratio` field in the response
114
+
3. Verify value is reasonable (typically 0.9 - 2.0+ range when healthy)
114
115
115
116
**Expected Results:**
116
117
-`collateral_ratio` field is present with a decimal value
117
-
-On fresh testnet with no activity, may return `0.000000000000000000`
118
-
-Non-error response confirms module is calculating correctly
118
+
-Value is > `halt_threshold` (0.90) for healthy operation
119
+
-Value is > `warn_threshold` (0.95) for normal operation
119
120
120
-
**Example output:**
121
-
```yaml
122
-
collateral_ratio: "0.950000000000000000"
123
-
halt_threshold: "0.900000000000000000"
124
-
mints_allowed: true
125
-
...
126
-
```
121
+
**Proof to Submit:**
122
+
- Output showing `collateral_ratio` value
127
123
128
124
---
129
125
130
126
### Test 0.6: Mint Status Check
131
127
132
128
**Objective:** Verify BME mint status is Healthy (required for most testing)
133
129
130
+
**Note:** Uses same command as Test 0.5. This test focuses on the `status` field and boolean flags.
131
+
134
132
**User Actions:**
135
-
1. Query BME status:
133
+
1. Query BME status (if not already captured in 0.5):
136
134
```bash
137
135
akash query bme status
138
136
```
139
137
2. Check the `status` field and related flags
140
138
141
-
**Example Output:**
142
-
```yaml
143
-
collateral_ratio: "0.999328857700195767"
144
-
halt_threshold: "0.900000000000000000"
145
-
mints_allowed: true
146
-
refunds_allowed: true
147
-
status: mint_status_healthy
148
-
warn_threshold: "0.950000000000000000"
149
-
```
150
-
151
139
**Expected Results:**
152
140
-`status`: `mint_status_healthy` (required to proceed with most tests)
153
141
-`mints_allowed`: `true`
154
142
-`refunds_allowed`: `true`
155
-
- `warn_threshold`: `0.95`(status changes to warning below this)
156
-
- `halt_threshold`: `0.90`(mints halt below this)
157
143
158
144
**If status is NOT `mint_status_healthy`:**
159
-
- `mint_status_warning`: Collateralization Ratio dropped below 0.95 — investigate
160
-
- `mint_status_halt_cr`: Collateralization Ratio dropped below 0.90 — mints blocked, investigate before proceeding
161
-
- `mint_status_halt_oracle`: Oracle failure — investigate oracle health (Test 0.3)
145
+
-`mint_status_warning`: Collateral Ratio below 0.95 — investigate
146
+
-`mint_status_halt_cr`: Collateral Ratio below 0.90 — mints blocked
147
+
-`mint_status_halt_oracle`: Oracle failure — check Test 0.3
148
+
149
+
**Proof to Submit:**
150
+
- Output showing `status: mint_status_healthy` and `mints_allowed: true`
- AKT supply returned (note for inflation tracking in later tests)
169
+
- AKT supply returned (baseline for inflation tracking)
182
170
- ACT supply returned (may be 0 on fresh testnet)
183
171
172
+
**Proof to Submit:**
173
+
- Both supply values (uakt and uact amounts)
174
+
184
175
---
185
176
186
177
### Test 0.8: Vault State Baseline (Pending Operations Check)
187
178
188
-
**Objective:** Record vault state baseline and verify no unexpected pending operations
179
+
**Objective:**Verify no unexpected pending operations
189
180
190
-
**Note:** There is no direct `pending-records` CLI query. Pending operations are inferred by comparing vault-state before and after operations, and by observing state changes across epoch boundaries.
181
+
**Note:** Pending operations are inferred by comparing `balances.uakt` vs `remint_credits`. If `balances.uakt` > `remint_credits`, there are pending mint operations.
191
182
192
183
**User Actions:**
193
184
1. Query current vault state:
194
185
```bash
195
186
akash query bme vault-state
196
187
```
197
-
2. Record the current values as a baseline
198
-
3. Query again after ~1-2 minutes (one epoch) to verify state is stable:
199
-
```bash
200
-
sleep 90
201
-
akash query bme vault-state
202
-
```
188
+
2. Compare `balances.uakt` to `remint_credits`
203
189
204
190
**Expected Results:**
205
-
- Vault state query succeeds
206
-
- If vault state is changing unexpectedly between queries (without you initiating operations), there may be stale operations from prior testing — investigate before proceeding
207
-
- Stable state indicates clean baseline for testing
191
+
- Query succeeds
192
+
- If `balances.uakt` ≈ `remint_credits`: no significant pending operations
193
+
- If `balances.uakt` > `remint_credits`: pending mints exist (may be from prior testing)
0 commit comments