how to limit excess authority when registering a vbank asset #10722
Labels
Comments
mergify bot
added a commit
that referenced
this issue
Dec 18, 2024
closes: #10703 ## Description - add `FastLP` / `ufastlp` to vbank ### Security Considerations Adds `bankManager` to the FastUSDC core eval permit, which introduces an audit burden to see that is used only for the relevant `addAsset` call. - #10722 ### Scaling Considerations eliminates up-calls from go to JS on each FastLP balance update ### Documentation Considerations Existing docs suffice; to wit: [VBank Assets and Cosmos Bank Balances](https://docs.agoric.com/guides/getting-started/contract-rpc.html#vbank-assets-and-cosmos-bank-balances) ### Testing Considerations - update tests that relied on getting FastLP balances from `published.wallet.${addr}.current`. ### Upgrade Considerations unreleased
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
#10709 uses the usual
E(bankManager).addAsset(...)idiom to register FastLP. ButbankManagerhas much more authority than this: it can create a vbank purse for any address and then withdraw from it.Description of the Design
TBD
Security Considerations
yes
Scaling Considerations
?
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: