Example Use Cases
Example use cases for vBase across financial and non-financial domains
vBase creates independently verifiable, point-in-time audit trails for data, models, trading strategies, research outputs, and other digital content.
Individual audit trail records, or Stamps, can be grouped into Collections, allowing users to verify the history of an entire dataset, strategy, portfolio, or other body of work.
Below are some common financial and non-financial applications.
Financial applications
Financial products are often evaluated by looking at historical data, predictions, or decisions. vBase helps make those histories independently verifiable.
Alternative data providers
Stamp dataset deliveries such as sentiment scores, macro indicators, developer activity, mobility data, or other predictive data to make them verifiably point-in-time.
Purpose: Create a point-in-time history that buyers can verify for evaluation and backtesting.
Example: A provider stamps each daily delivery into a Collection. A client can later compare the dataset with the corresponding audit trail to verify the point-in-time integrity and completeness of the data.
Trading strategies, signals & models
Stamp trading signals, model forecasts, portfolio weights, or rebalance files as they are produced.
Purpose: Build a verifiable history showing what a model or strategy produced and by when.
Example: A model builder stamps each weekly signal file in a Collection, creating a continuous point-in-time record that future investors can independently verify.
Investment managers
Create verifiable histories for model portfolios, fund sleeves, SMAs, or other investment strategies.
Purpose: Support independent substantiation of reported strategy or portfolio histories.
Example: An investment manager stamps each portfolio update as it occurs. Investors can later compare reported historical positions or performance with the point-in-time record.
Forecasts & research
Stamp forecasts, recommendation histories, research models, valuation frameworks, or investment memos as they are produced.
Purpose: Document when predictions, recommendations, or research outputs existed and whether they were subsequently revised.
Example: An analyst stamps each published recommendation into a Collection, creating a verifiable history that can later be evaluated against subsequent outcomes.
Index providers & calculation agents
Stamp index methodologies, constituent files, weights, and rebalance outputs.
Purpose: Create an independently verifiable history of index construction, constituent changes, weights, and methodology versions.
Example: An index provider stamps each rebalance file and relevant methodology version, allowing future users to verify the index's recorded history.
Backtests and live performance
Stamp model specifications, configuration files, or backtest results before subsequent performance occurs.
Purpose: Document what research, parameters, or strategy definitions existed at a particular point in time and create a clear boundary between historical research and later forward performance.
Example: A researcher stamps a model specification and backtest before beginning a live evaluation period. Later performance can then be assessed relative to the model definition that was recorded at the start of the period.
Non-financial applications
vBase is domain-agnostic. Any field that produces data, predictions, research, or other digital records over time can benefit from independently verifiable history.
AI & machine learning
Stamp model outputs, prediction batches, evaluation results, or model versions over time.
Purpose: Create a point-in-time history of model behavior for evaluation, auditability, and reproducibility.
Example: A model developer uses a Collection to record successive evaluation outputs across model versions or retraining cycles.
Research & academia
Stamp datasets, manuscripts, experimental results, or research outputs.
Purpose: Document when research materials or results existed and create a verifiable history of subsequent revisions.
Example: A research team stamps datasets and experimental outputs as they are produced, creating an independently verifiable record of the research process.
Media & publishing
Stamp articles, images, reports, press releases, or other original content.
Purpose: Document that specific content existed by a particular time and under a particular identity.
Example: A publisher stamps an original research report before distribution, allowing its publication history to be independently verified later.
Legal, compliance & recordkeeping
Stamp contracts, filings, policies, risk reports, valuation reports, or other important records.
Purpose: Create an independently verifiable record of document integrity and timing.
Example: An organization stamps recurring compliance or risk reports into a Collection, creating a point-in-time history of what was recorded at each reporting interval.
Project & client deliverables
Stamp datasets, analyses, reports, or other deliverables as they are completed or handed off.
Purpose: Create a shared, independently verifiable history of project outputs between teams, clients, or other counterparties.
Example: A service provider stamps each major client deliverable into a Collection, creating a record of what was delivered and by when.
Summary
vBase can be useful anywhere historical data, predictions, or digital records need to be evaluated based on what existed and by when.
The underlying content can remain private while its history becomes independently verifiable.
Next steps
Last updated