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: Fixed broken link #1479

Merged
merged 1 commit into from
Sep 4, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions book/writing-programs/precompiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Inside the zkVM, precompiles are exposed as system calls executed through the `e
Each precompile has a unique system call number and implements an interface for the computation.

SP1 also has been designed specifically to make it easy for external contributors to create and extend the zkVM with their own precompiles.
To learn more about this, you can look at implementations of existing precompiles in the [precompiles](https://github.com/succinctlabs/sp1/tree/main/core/src/syscall/precompiles) folder. More documentation on this will be coming soon.
To learn more about this, you can look at implementations of existing precompiles in the [precompiles](https://github.com/succinctlabs/sp1/tree/main/crates/core/executor/src/events/precompiles) folder. More documentation on this will be coming soon.

**To use precompiles, we typically recommend you interact with them through [patches](./patched-crates.md), which are crates modified
to use these precompiles under the hood, without requiring you to call system calls directly.**
Expand All @@ -20,4 +20,4 @@ Here is a list of all available system calls & precompiles.

```rust,noplayground
{{#include ../../zkvm/lib/src/lib.rs}}
```
```
Loading