-
Notifications
You must be signed in to change notification settings - Fork 1k
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
auto-claim gas on tx submission #1078
Comments
One practical example for Gas gateways: neo-project/proposals#101 |
@igormcoelho I think Rick login here is @lock9 So, you are suggesting that the blockchain calculates the unclaimed GAS and sand it to the wallet every time it makes a transaction, aren't you? What if a wallet receives 10 NEO and no gas? If every transaction needs gas, including the claim it wouldn't be able to claim it. |
He must wait or buy some gas |
I propose closing this one:
|
What about modify the |
It's NEP-17, I don't think it can do these tricks without breaking compatibility. We also have |
We can use hardforks to ensure the compatibility. |
HF can do anything technically, but I mean conceptually, per NEP-17, |
If you are able to spend this balance, and we increase totalsupply as well, we can do more or less the same as Aave. |
@lock9 has raised some questions related to points, which we have previously debated by community, on several threads (although I cannot find them all here now...)
The challenge is: how to prevent people from requiring Gas, in order to operate Neo.
Since every tx is paid, even claiming would cost a little bit of gas, and Neo would be stuck for a while...
In my opinion, solution is simple: now that we have Native NEP-5 for GAS, it's possible to pre-calculate how much gas user would have unclaimed for that Neo, and allow that as network fee in that transaction.
Other point was discussed on other thread, I guess by @MorganDream too, where a GAS gateway could help in other operations... this same GAS gateway could operate Neo to GAS on runtime (as long as we define a NEP for it), and the same would apply for any other NEP-5 that wants to subsidize user operations.
Please comment here if I forgot threads or names... it's an important issue.
The text was updated successfully, but these errors were encountered: