-
Notifications
You must be signed in to change notification settings - Fork 12
Broken Permit Format #3
Comments
@whilefoo the deadline is at 2024-01-25T19:04:25.638Z |
It appears the permit was not generated with new format. I think you haven't merged 0x4007/.ubiquity-os#7 to this repo |
Perhaps you can open another pull request to @ubiquibot organization's config? |
Won't we use this repo ( |
I can't load the pull request file changes view from my phone it just breaks so I don't understand the implementation details. Anyways it probably makes sense to just merge in this repository then! |
That's weird what about trying to merge to development? I'm inclined to think user error cause git has been around for awhile. |
I think it's because the two repositories don't have a common root commit (https://stackoverflow.com/a/23350970), so the only way is to force push or create new repo |
Just commit on development and in the commit message you can add a new line Resolves #3 Although a few days ago I merged unrelated histories by adding a flag. Something like git merge --allow-unrelated-histories |
+ Evaluating results. Please wait... |
Hey @rndquu @wannacfuture we need to fix the payment permit wallet because these rewards are coming from a non funded wallet. I want to make a new wallet and start issuing these payments again. @wannacfuture looks like relevance is not multiplying against the formatting score. This is incorrect. |
You just need to change the X25519_PRIVATE_KEY and evmKey in the config. |
I was never able to successfully regenerate the evm encrypted private key. I might need some help with this but I'll try again tonight. @diamondnegroni will keep you posted on if this is stable |
If you want to use a new wallet then you need to:
|
Please match the permit encoding format in this codebase.
The text was updated successfully, but these errors were encountered: