Skip to content

add ed25519 sig-verification #355

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

Closed
wants to merge 11 commits into from
Closed

add ed25519 sig-verification #355

wants to merge 11 commits into from

Conversation

mubarizkyc
Copy link

Code for an onchain program that unlocks a vault when the token price hits a certain target after valdiating that the data send to Ed25519 program was correct via Solana sys_var instruction
.
This pull request was created for https://app.gib.work/bounties/65246598-dc39-4d3c-9928-42ae766abec8 in an attempt to solve a bounty #348 . Payment for the bounty is immediately sent to the contributor after merge.

@ngundotra
Copy link
Contributor

@mubarizkyc Hey this looks like the best overall submission! Thank you!

Before accepting, can you follow repository conventions?

  • Wrap the solana-signature-verification/programs directory into solana-signature-verification/anchor/programs
  • Setup local testing (okay to have a .skipped test suite that runs on mainnet-beta)
  • Remove unused TS imports from files
  • Add your program to top-level Cargo.toml workspace

@mubarizkyc
Copy link
Author

mubarizkyc commented Feb 13, 2025

@ngundotra Pyth oracle feeds are available on Devnet and Mainnet, so the escrow work could'nt be done on localnet. However, the signature verification logic will be the same across all networks.

Copy link
Contributor

@ngundotra ngundotra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup makes sense. Can you please make the requested changes? Almost there

@@ -0,0 +1,21 @@
use anchor_lang::prelude::*;
pub const ESCROW_SEED: &[u8] = b"get the best weed from us";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: can we get a normal seed?

@@ -0,0 +1,21 @@
use anchor_lang::prelude::*;
pub const ESCROW_SEED: &[u8] = b"get the best weed from us";
//pub const SOL_USDC_FEED: &str = "GvDMxPzN1sCj7L26YDK2HnMRXEQmQ2aemov8YBtPS7vR";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: remove

@mubarizkyc
Copy link
Author

Yup makes sense. Can you please make the requested changes? Almost there

@ngundotra sure

@ngundotra
Copy link
Contributor

Can you add a script to test this automatically please?

@mubarizkyc
Copy link
Author

mubarizkyc commented Feb 17, 2025

@ngundotra I just ran anchor run test in my repo

Screenshot From 2025-02-13 17-34-00

@mubarizkyc mubarizkyc requested a review from ngundotra February 23, 2025 13:53
@ngundotra
Copy link
Contributor

anchor test does not work for me, do you mind checking if you have any uncommitted files?

Also can you please fix the CI errors?

@ngundotra
Copy link
Contributor

Thank you for your contributions! I'm going to help you close this out. Great work so far. Will get this cleaned up & merged in EOD

@ngundotra
Copy link
Contributor

@heyAyushh can you help us fix the CI? Looks like basics/counter tests are failing & this repo is failing to build, despite being valid anchor.

@heyAyushh
Copy link
Member

let me get back to you soon.

@ngundotra
Copy link
Contributor

@mubarizkyc we are going to close this PR in favor of a simpler approach. Thank you for your contribution. You will be awarded partial bounty from Gibwork directly. They will reach out to you.

@ngundotra ngundotra closed this Mar 4, 2025
@mubarizkyc
Copy link
Author

@ngundotra Was it decided at the beginning of the task whether I should manage the whole CI/CD within this budget? I will be careful before wasting my time again.

@ngundotra
Copy link
Contributor

ngundotra commented Mar 4, 2025

Sorry, the CI/CD issue was not your fault. It is normal to expect contributors to work through CI/CD issues for contributions, but this time this was not fair since CI/CD was not setup for external contribution

We will fix this before issuing another bounty. Thank you @mubarizkyc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants