-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
CLI Multiple Coins #24
Comments
what about this as a format: |
What if we even limit the coin names not to include numbers so we could do |
Great idea!
…On Thu, Feb 9, 2017 at 5:21 PM, ᴍᴀᴛᴛ ʙᴇʟʟ ***@***.***> wrote:
What if we even limit the coin names not to include numbers so we could do
this: 10atom,100btc,666silver. Add we could support spaces so if you
quote your CLI arg you could do this: "10 ATOM, 100 BTC".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/tendermint/basecoin/issues/24#issuecomment-278793279>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACMb70G5IuGQzkhCz8rKX0HuRhYxZKZ4ks5ra5FNgaJpZM4L8sv->
.
|
Merged
liamsi
pushed a commit
to liamsi/cosmos-sdk
that referenced
this issue
Jun 26, 2018
Add a godoc reference to delegate indexing and references to that service, thus keeping our library and usages upto date, instead of relying on generated markdown that goes stale especially for changing API signatures, and becomes tedious where someone has to remember to always regenerate the README markdown and then commit it. Fixes cosmos#24
sosedoff
referenced
this issue
in figment-networks/cosmos-sdk
May 16, 2022
* use memdb for cachekv * Remove remaining n^2 nature of CacheKV (Speedup dirtyItems) * Delete deadcode, fix lint Co-authored-by: mconcat <[email protected]>
luchenqun
pushed a commit
to luchenqun/cosmos-sdk
that referenced
this issue
Sep 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is intended to be a discussion space surrounding sending transaction coins through the CLI. Currently there are three transaction fields using coins:
Problems with this current setup:
Initial proposed solution: hack it with slashes. Rather than having fee and amount be integer types, we could make them strings which we parse at execution, this would of course limit the use of the slash character within the coin-type name if operating from the CLI. This would also eliminate the need for the coin flag, as it would be built right into fee or amount. Here are some examples that could be valid strings to send into the proposed fee or amount flags:
blank/1/btc/2
gold/10
atoms/10/btc/100/silver/666
etc.
The intention of using this is to simplify use of the CLI so the user doesn't need to point to a .json file nor type any json code. Thoughts?
The text was updated successfully, but these errors were encountered: