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

Docs: Updated Foundational Concepts page #3715

Closed
Tracked by #2658 ...
critesjosh opened this issue Dec 15, 2023 · 0 comments · Fixed by #4143
Closed
Tracked by #2658 ...

Docs: Updated Foundational Concepts page #3715

critesjosh opened this issue Dec 15, 2023 · 0 comments · Fixed by #4143
Assignees
Labels
A-documentation Area: relates to documentation

Comments

@critesjosh
Copy link
Contributor

The goal is to make the foundational concepts page more accessible and understandable without going directly into code. In the explanation, we can link out to more detailed pages, but this page should give a "protocol researcher" a good understanding of what Aztec does (and hopes to achieve).

Major concepts (keep it to the 3 top level, data privacy, confidentiality, trustlessness, but can add more detail and subsections.) This in an inexhaustive list.

  • Trustless privacy
    • Data privacy (private state)
      • Note tree / nullifier tree
        • Notes
        • UTXOs
      • Private state is isolated per key
  • Confidentiality (private execution)
    • PXE
      • Stores local db of every private note (that you own) + current public state
      • Txn
        • Simulates first to assure success
        • Then runs it through circuit and generates proof
        • It then creates new commitments to new data and nullifies old data
      • Then you send:
        • Proof
        • Set of new commitments
        • Set of nullifiers
      • All 3 sent to sequencer
        • Sequencer checks them (meaning, submits commitments, nullifiers and proof, to the kernel circuit)
        • Updates the trees for the whole block
      • Proofs are then sent to proving network for recursive proving (?)
        • One final rollup proof sent to Ethereum for verification
  • Trustlessness (censorship resistance, network decentralization)
@critesjosh critesjosh added the A-documentation Area: relates to documentation label Dec 15, 2023
@critesjosh critesjosh self-assigned this Jan 19, 2024
signorecello pushed a commit that referenced this issue Jan 23, 2024
This PR adds clearer entry points to the docs homepage so people have a
better idea of where to go. It incorporates the thinking behind the
Solidity Dev and Aztec Dev personas
([mindmap](https://www.mindmeister.com/app/map/3110603953?t=oWDwlsESBd)),
but doesn't explicit say "Solidity devs go here" or "Aztec devs go
here".

Adds a higher level introduction to the main Foundational Concepts page,
related to issue 3715 linked below.

Removes the History of blockchain privacy page.

This is not meant to be a final version, merely an incremental
improvement on what we currently have.

closes: #3715  #2652
closes: AztecProtocol/dev-rel#112
michaelelliot pushed a commit to Swoir/noir_rs that referenced this issue Feb 28, 2024
This PR adds clearer entry points to the docs homepage so people have a
better idea of where to go. It incorporates the thinking behind the
Solidity Dev and Aztec Dev personas
([mindmap](https://www.mindmeister.com/app/map/3110603953?t=oWDwlsESBd)),
but doesn't explicit say "Solidity devs go here" or "Aztec devs go
here".

Adds a higher level introduction to the main Foundational Concepts page,
related to issue 3715 linked below.

Removes the History of blockchain privacy page.

This is not meant to be a final version, merely an incremental
improvement on what we currently have.

closes: AztecProtocol#3715  AztecProtocol#2652
closes: AztecProtocol/dev-rel#112
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-documentation Area: relates to documentation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant