Add Ink xStocks proof of concept#1934
Draft
fricoben wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 this PR is
This PR adds the technical artifact behind our Ink Spark application: an Ink xStocks proof of concept for Verity. It shows how a reusable formal-verification spec pack for Ink builders could work, starting with contracts built on top of xStocks.
The broader project is the Ink Verified Finance Spec Pack: reusable Verity models, specs, examples, and docs for Ink builders integrating with xStocks first, then extending the same pattern to Tydro and Nado-style integrations.
Non-technical overview
Short Loom walkthrough for Spark/Ink reviewers:
https://www.loom.com/share/3fd4d83ad7cc4c1caebd6ad5cc396a6f
The video is meant as a non-technical presentation of the overall project: what Verity is, why Ink DeFi/RWA builders need reusable verification support, why xStocks are the first practical example, and how the same approach could later help teams building around Tydro and Nado.
This PR is the inspectable technical companion to that video.
Why this matters
xStocks are not ordinary ERC-20 tokens. They represent tokenized equities and ETFs, so integrating contracts may need to reason about corporate actions such as dividends, splits, reverse splits, rebasing/multiplier behavior, stale epochs, and transfer/compliance edge cases.
If every Ink builder has to model those assumptions from scratch before verifying its own vault, adapter, wrapper, or strategy contract, formal verification becomes slower and more expensive than it needs to be. This PR demonstrates how Verity can package those assumptions into reusable specs and examples.
Scope
This POC focuses on an example xStock vault and reusable xStocks-facing specifications. It is meant to help developers prove properties about their own contracts that integrate xStocks.
It does not claim to audit or formally verify the xStocks core protocol itself. The xStocks behavior is modeled at the integration boundary, and the docs/specs separate what is proved from what remains an external assumption.
Review focus
Please review whether the structure is understandable as an Ink builder-facing example:
Related links