Orchestration Account - Query Balances

[0xpatrickdev]

What is the Problem Being Solved?

This ticket captures three related items:

1. CosmosOrchestrationAccount and LocalOrchestrationAccount do not have the getBalances interface implemented (only getBalance).

2. LocalOrchestrationAccount uses the getBalance method from vats/localchain.js, which calls out to vbank. This presents a challenge if the caller is trying to work with an asset that's not recognized by vbank:
   

   agoric-sdk/packages/vats/src/localchain.js

   Lines 113 to 117 in b5cf8bd

   	async getBalance(brand) {
   	const { bank } = this.state;
   	const purse = E(bank).getPurse(brand);
   	return E(purse).getCurrentAmount();
   	},

   
   Also, it doesn't seem Bank (vbank) has an interface for enumerating purses. The implementation may require iterating over every known asset, which is not ideal.

Description of the Design

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations