[Feature] Switch to job account for new jobs going forward #74
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.
Last part of #63
Changes included
create_account
endpoint, merge it to controller'screate_job
.create_job
, it will always try to create job using a job account, if user doesn't have a job account tracker, create it then create account then create job (2 reply), if user has a job account tracker but no free job account, then create job account then create job (1 reply), if user has both job account tracker and a free job account, create job right increate_job
.job-account-tracker
contract, it's like putting the oldACCOUNTS
from controller to this contract, it tracks job account availability for all users.account
tolegacy-account
.account
tojob-account
.create_job
,update_job
anddelete_job
, we used to deduct fee from user's main warp account inupdate_job
anddelete_job
, i think it's cleaner to make user pay when they call the function, consider user already created jobs, it's common that user has warp fee denom in their wallet.Test
Migration required