1,014 or 1.014: what breaks in tokenized asset feeds

Duration: NaN:NaN:NaN

Speaker: Bianca Buzea

Type: Lightning Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

The most common way a tokenized asset can get mispriced onchain is not an attacker. It is a misplaced decimal in a fund administrator sheet: 1,014 where someone meant 1.014, and everything downstream inherits it until a circuit breaker kicks in. Tokenized assets sit in DeFi as collateral, as derivatives margin, and in AMM pools, mostly since last year. Onchain they look like any other token, so the instinct is to apply oracle checks built for onchain-native assets. Those checks do not all carry over. Sourcing: data for onchain-native assets comes from many independent venues; for a tokenized asset it comes from the custodian. Monitoring: heartbeat and deviation don't make sense when only one price is published a day. The model for freshness has to change. Failure handling: a halted feed can be a security precaution, not a bug. Protocols need to define the appropriate behavior in advance. Builders leave knowing which of their assumptions break before integrating a tokenized asset.