Remove non-production assertion examples and enhance ERC4626 docs#179
Merged
Remove non-production assertion examples and enhance ERC4626 docs#179
Conversation
Contributor
czepluch
commented
Jan 7, 2026
czepluch
commented
- Remove Farcaster protocol integrity example (ass22) - hypothetical example not suitable for production documentation
- Remove orphaned Bedrock staking snippet (ass3)
- Expand ERC4626 vault operations docs to cover all operations (deposit, withdraw, mint, redeem) with batch handling
- Update navigation and cross-references
- Remove Farcaster protocol integrity example (ass22) - hypothetical example not suitable for production documentation - Remove orphaned Bedrock staking snippet (ass3) - Expand ERC4626 vault operations docs to cover all operations (deposit, withdraw, mint, redeem) with batch handling - Update navigation and cross-references
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
1 participant
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.