Repository navigation
Conversation
haimbj1
force-pushed
the
docs/confidential-payment
branch
from
October 20, 2026 09:06
71d62de to
bb6c655
Compare
…ocks, wrong titles; repo-root paths
…e pins in check-versions
…or note, house diagram, prerequisites
haimbj1
force-pushed
the
docs/confidential-payment
branch
from
October 29, 2026 15:05
a14d792 to
3813a75
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TL;DR
No tutorial shows a full confidential token transfer from start to end. New developers cannot see how little code CoFHE needs.
Add one tutorial page with a project that CI tests. Alice pays Bob, Bob reads his balance, and Eve cannot.
Jira: DOC-77. Stacked on #126: merge that first, then this PR moves to
main.What
cofhe/tutorials/confidential-payment: Alice pays Bob 100 tokens. Bob reads his balance, and Eve cannot.cofhe/tutorials/examples/confidential-transfer/:npx degit FhenixProtocol/fhenix-docs/cofhe/tutorials/examples/confidential-transfer.How the page stays correct
Tutorial examples. It runsnpm ci && npm testin every example project from a clean checkout.check-example-regions.py. Each code block on the page has an invisible marker naming a region in a project file. The check fails if the block and the region differ. So the code on the page is the code CI tested.check-versions.pynow also checks the example'spackage.jsonpins against the compatibility page.Checks
npm ci && npm testfrom a clean copy: 2 passing.check-versions --docsfail. With the pin restored, it passes.mint validateandmint broken-links --check-anchors --check-redirectspass.Sepolia run (2026-10-20)
npm run sepoliapassed, with only Alice's key. Bob was a fresh random wallet.Bob's balance: 100,Alice's balance: 900Gas on Sepolia, 1.0.0 (not in this PR)
confidentialTransferto a new holderconfidentialTransferto an existing holderconfidentialTransferFromby an operatorsetOperatorsetOperatorruns no FHE and writes one storage slot, but it also costs 2.75 times the page value. So the gap does not come from 1.0.0. Sepolia's gas pricing has changed since the page was measured. The page needs a separate decision: which network it describes, and a new measurement.