-
Notifications
You must be signed in to change notification settings - Fork 12
Shared X25519_PRIVATE_KEY
for Development
#22
Comments
Link below for conversation context. It was to me. Anyways you need to create a new private key for this task! |
/start |
Tips:
|
let us know when done |
* chore: add new shared evmPrivateKeyEncrypted The new evmPrivateKeyEncrypted generated for address 0x3a2E44e10AbEf5CB4a6E492c5ba93d30068d2D95 (no funds). Resolves: #22 * chore: add private key to docs * chore: add X25519 shared keys
+ Evaluating results. Please wait... |
https://github.com/ubiquibot/comment-incentives/actions/runs/7935268560 invalid input sounds unexpected @gitcoindev ?? |
+ Evaluating results. Please wait... |
In the repository secrets I think I need to change the key to match @gitcoindev's |
I just changed it to I hope that it doesn't break production for some reason (it should get it from Netlify secrets, but not sure if we implemented this correctly!) I fear that we might need to build a feature for this to support development key pair and production. Unfortunately I'm already winding down for the day so I'll leave you guys to try and investigate. |
@molecula451 I tried to override X25519_PRIVATE_KEY but it did not help. It seems that https://github.com/ubiquibot/production/blob/1937a6ba75588f51d1bf07fed1f6384f79090465/.github/ubiquibot-config.yml#L2 takes precedence over https://github.com/ubiquibot/comment-incentives/blob/main/.github/ubiquibot-config.yml#L2 (I see the first one in logs). |
+ Evaluating results. Please wait... |
+ Evaluating results. Please wait... |
@pavlovcik permitted with hard debug (tho no funds in the private key) |
I don't understand what you mean by this |
pavlovcik i re-generated the X25519 to trigger the permit, what you don't understand? using a private key i own, but also did many commits to reach the root cause |
I'll investigate more on my computer later. |
sure thing |
Will it be an issue if I revert to the commit and secret that I had before? It was the production x25519 key in the GitHub repository secrets when it was working like eight hours ago. Posting this message before checking on my computer to get you before you log off. |
Can somebody work on generating a new
X25519_PRIVATE_KEY
for the ubiquibot organization? We need to share it for development purposes.evmPrivateKeyEncrypted
(no funds!) and add to the org bot configcomment-incentives
readme.567419d
Originally posted by @pavlovcik in #19 (comment)
The text was updated successfully, but these errors were encountered: