Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I decided to remove makeProxyTx() and proxy() from the KMaaS base functionality. I initially included it because I thought that it would allow the KMaaS account to also function as a gas relayer, but comments made me reconsider. If
proxy
is separated into another contract for use on other EVM chains, then 1.makeProxyTx
doesn't work because it doesn't know where to point to and 2. nonce management doesn't make sense because the same keypair can sign transactions on multiple different chains. ThenmakeProxyTx
just replicatessignEIP155
functionality with more parameters hard-coded. After trying to approach it a couple different ways I decided it just makes more sense to let developers define how they would want relaying to work.Instead I decided to include that functionality in the sample application instead. The sample application previously didn't rely on gas relayers so required the public keys stored by the KMaaS application to be funded. Instead, I'm in the process of updating it so that user accounts don't have to pay gas to submit transactions.