Skip to content
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

chore: making a symlink to the new whitepaper #711

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bcm-at-zama
Copy link
Contributor

For https://github.com/zama-ai/planning-blockchain/issues/433, make a symlink on old fhEVM WP (v1) to the new one (v2)

@bcm-at-zama bcm-at-zama requested a review from a team as a code owner February 18, 2025 10:43
@cla-bot cla-bot bot added the cla-signed label Feb 18, 2025
@bcm-at-zama
Copy link
Contributor Author

At the end:
md5 fhevm-whitepaper*
MD5 (fhevm-whitepaper-v2.pdf) = 89c404fafda8c3dfca33a93657dc29e7
MD5 (fhevm-whitepaper.pdf) = 89c404fafda8c3dfca33a93657dc29e7

so the same pdf.

@bcm-at-zama
Copy link
Contributor Author

While in main

md5 fhevm-whitepaper*
MD5 (fhevm-whitepaper-v2.pdf) = 89c404fafda8c3dfca33a93657dc29e7
MD5 (fhevm-whitepaper.pdf) = 2a9f974d5eb2b81fff249e4aa7a0581c

so that's a link to the v2 paper, all good.

@bcm-at-zama bcm-at-zama changed the title chore: making a link to the new whitepaper chore: making a symlink to the new whitepaper Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants