Closed TrevorJTClarke closed 1 year ago
I thought that might be because we have this in the config.local.yaml
:
But after changing that to:
- denom: "ujunox"
+ denom: "stake"
- prefix: "juno"
+ prefix: "local"
chain_id: "testing"
rpc_endpoint: "http://localhost:26657/"
grpc_endpoint: "http://localhost:9090/"
wsrpc_endpoint: "ws://localhost:26657/websocket"
contract_address: null # This can be set via CRONCAT_CONTRACT_ADDRESS, committing this is a pain.
gas_prices: 0.07
gas_adjustment: 1.5
polling_duration_secs: 2
am still seeing this
Added new cmd:
cargo run -- get-agent-accounts --sender-name mainnet
- gets all generated addrs for keypair
cargo run -- get-agent-accounts --sender-name mainnet --chain-id juno-1
- gets addr for network
Now upon generating new account, spits out supported addresses for easier funding
Merging #91 (67668b3) into main (f69d691) will not change coverage. The diff coverage is
0.00%
.
@@ Coverage Diff @@
## main #91 +/- ##
=====================================
Coverage 0.00% 0.00%
=====================================
Files 23 23
Lines 776 794 +18
=====================================
- Misses 776 794 +18
Impacted Files | Coverage Δ | |
---|---|---|
croncat/src/store/agent.rs | 0.00% <0.00%> (ø) |
|
croncat/src/utils.rs | 0.00% <ø> (ø) |
|
croncatd/src/main.rs | 0.00% <0.00%> (ø) |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Hmm found an issue now:
status: Unknown, message: "empty address string is not allowed", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "5411507"} }
croncat-rs/croncat/src/client/query_handlers/wasm_query.rs:29:19
Fixes #90