Datafeeds

Morpheus Datafeeds provide high-integrity price records synchronized directly to Neo N3 Mainnet. Feed publication is isolated onto the dedicated DataFeed CVM so market updates are not delayed by slower request/response workloads.

Operational Architecture

Unlike the request-callback Oracle model, Datafeeds are pre-synchronized state. They operate on an automated operator pipeline:

1. The control plane or scheduler triggers a feed tick.
2. The dedicated DataFeed CVM fetches and normalizes source quotes.
3. Only materially changed quantized values are prepared for publication.
4. The relayer pushes the update to the on-chain MorpheusDataFeed registry.

Supported Assets

Data Storage Format

All prices are stored as scaled USD integers with a global precision of 1 USD = 1,000,000 units.

• A price of $12.50 is stored as 12500000.
• A price of $65,000.00 is stored as 65000000000.
• A price of $0.002437 is stored as 2437, which is enough to represent low-priced assets such as FLM directly.
• The 0.1% sync threshold is evaluated against the quantized on-chain integer value. The canonical storage key keeps the source prefix, for example TWELVEDATA:FLM-USD and TWELVEDATA:JPY-USD.

Canonical Pair Meanings

Contracts and users should use the pair keys exactly as written below. The canonical key format is provider-scoped, so the standard catalog uses identifiers such as TWELVEDATA:NEO-USD and TWELVEDATA:BTC-USD.

Contract Integration

Neo N3 (C#)

Use the contract hash 0x03013f49c42a14546c8bbe58f9d434c3517fccab or resolve the NeoNS alias pricefeed.morpheus.neo to the same script hash.

// Read the latest verified price from contract storage
public static void CheckLiquidation() {
    object[] record = (object[])Contract.Call(
        DataFeedHash,
        "getLatest",
        CallFlags.ReadOnly,
        "TWELVEDATA:NEO-USD"
    );
    
    BigInteger priceUnits = (BigInteger)record[2];
    BigInteger lastUpdate = (BigInteger)record[3];
    
    // Process logic...
}