Register Oblivion Protocol - #150
Closed
ScriptedBro wants to merge 1 commit into
Closed
Conversation
github-actions Bot
added a commit
that referenced
this pull request
Aug 21, 2026
Applied from #150 by @ScriptedBro, rebuilt on top of whatever else landed while it was open. Co-authored-by: ScriptedBro <45717428+ScriptedBro@users.noreply.github.com>
Contributor
|
Applied to main as Closed rather than merged because the entry was rebuilt on top of everything else that landed while this was open. That is what stops registrations from deleting each other, and it means you never had to resolve a conflict. The commit is credited to you. |
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.
What are you building?
Oblivion Protocol is a privacy-first dark liquidity and confidential DeFi engine on Starknet. It enables users and institutions to:
Privacy is needed because transparent LP positions and large swaps on public AMMs suffer from front-running, sandwich attacks, copy-trading, and regulatory friction for institutions.
The hard part will be orchestrating Cairo
privacy_invokeadapters to handle multi-step atomic settlement (internal CoW netting -> Ekubo route -> note minting) while keeping proof sizes compact and maintaining sub-second UX for batch auctions.Who's building it?
Built by ScriptedBro (GitHub) — Full-stack Starknet & Cairo developer building privacy-preserving financial infrastructure and zero-knowledge tooling on Starknet.
Checklist
registry.jsonand did not modify anyone else's entryslugis lowercase, hyphenated, and not already takenrepo_urlis publictelegramhas a bare username for everyone on the team