Oracles & Verification
Vellichor deliberately doesn't use a price-feed oracle for core buy/sell — prices are set directly (by the team at listing, by sellers on resale), not computed from an external index. This avoids a manipulable price dependency, especially while secondary liquidity is thin.
Two other pieces of the "digital twin" model — formalized authenticity attestation and environmental monitoring — have real, working contracts in the repo (VellichorAuthenticityRegistry.sol, VellichorEnvironmentalOracle.sol), and are live on Robinhood Chain mainnet with a gated internal admin UI at /admin/list-bottle. Neither is connected on-chain to VellichorVault.sol— "authenticated before minted" is enforced as a UI-level rule in that admin tool, not a contract-level requirement.
Both are, today, entirely human-entered.A person on Vellichor's curation team inspects the bottle or reads a thermometer/hygrometer, then submits that data through the internal admin tool, which calls recordAttestation() or recordReading()on-chain. Neither contract currently receives data from any automated source — the "oracle" in both names describes the on-chain interface, not an automated feed.
Two different long-term paths
Environmental readings
Can realistically become automated once real IoT sensors are installed in storage facilities — the sensor would call
recordReading()directly, replacing the manual entry step entirely.Authenticity attestation
Likely to stay human-driven permanently, not just until some future hardware ships. Verifying provenance, purchase history, and condition is a judgment call — it isn't the kind of thing a sensor reads.
What is real today, independent of either contract above: Vellichor's curation process itself — verified provenance and condition assessment before a bottle is vaulted — functioning as that same human-driven authentication step, even before it was formalized as an on-chain attestation.