-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account provisioning: charge BLD for smart wallet #4654
Comments
@michaelfig and I think we have a design: Scenario: User Una wants to accept (make) an offer (for example, to getRUN or to trade on the AMM or to take out a Vault). How does Una communicate with Zoe or any other object in the Agoric blockchain VM? @michaelfig and I concluded that some introduction mechanism is necessary to join the Agoric society where members enjoy the benefits of offer safety etc. Una must have 1 BLD. Una uses a wallet web UI to send a "please provision" message that (1) liens gp=1 BLD and (2) creates a c-list and on-chain wallet. Una can then proceed using or RUN? gp is a governable parameter p.s. Alice... |
cost? option: free if they already have BLD? nearby issue: how to get my friend in Agoric when my BLD is locked? how much does it take to earn 1 BLD in 1 month from staking rewards? |
@samsiegart writes in #5860 (review) :
The Feb 24 design above is one answer. But I wonder if it's overkill. In order for the cosmos layer to check a signature, an account has to exist; that is: some tokens must have been sent there. Perhaps that's enough, initially? Yes, somebody could send a worthless token over IBC to get an account created... but maybe that's an acceptable risk, initially? |
SMART_WALLET option for instagoric faucet@samsiegart 's Smart Wallet AMM Trade notes include:
where agoric-sdk/packages/cosmic-swingset/Makefile Lines 216 to 220 in 6b7b997
For end-to-end testing of an AMM swap (#5073), I'm inclined to add a corresponding p.s. |
@dtribble @rowgraus as we have discussed, I added a couple questions to the problem statement:
|
Today's design: charge 10BLD for a SMART_WALLET account; put proceeds in community fund. I plan to make a stretch-goal issue to make the 10BLD a cosmos governance parameter. |
Since we're charging execution fees in IST based on message size (#5817), for bootstrapping, should we issue 1IST in exchange for the 10BLD? (or 0.25 IST or whatever) |
What is the Problem Being Solved?
In #4402 we discuss fee aspects of
RUNIST onboarding, but there is also a question of provisioning accounts; that is: for creating an on-chain c-list and associating it with a cosmos account (key pair). How do we appropriately recover the cost of this operation?Our devnet account provisioning process depends on a discord faucet bot on our discord service to mitigate griefing and sybil attacks.
Additional open questions:
SMART_WALLET
accounts, while we gather confidence in system performance?REMOTE_WALLET
) accounts is higher risk. how to manage that risk?Description of the Design
?
note Feb 24 proposal
Security Considerations
see problem statement above
Test Plan
IOU
cc @Tartuffo @michaelfig @dtribble @warner
The text was updated successfully, but these errors were encountered: