App spec v9 enforced at block 3,050,000 (late Oct 2026): duration in seconds, payment memo, machine-type field

[2ndtlmining]

What

Version 9 of the Flux application specification is enforced at block 3,050,000, expected late October 2026, with existing applications migrated automatically in the same quarter. It adds three fields:

1. Duration in seconds instead of blocks — so lifetimes stop moving when block timing changes. This is the one most likely to break existing parsing: any code reading a spec's duration as a block count will silently misinterpret a seconds value.
2. Payment memo — binds a payment to the application it funds (this is what lets PNR attribute revenue).
3. Machine type — lets a spec request accelerated hardware.

Why this repo cares

client/src/appSpecs.js and the categorization path consume api.runonflux.io/apps/globalappsspecifications. api/src/services/chain_activity.rs's fetch_deployment_heights reads each spec's height field for the Chain Activity utility classifier.

Two concrete opportunities and one risk:

• Risk: duration-as-seconds vs duration-as-blocks in any spec-lifetime display or "expiring today" calculation.
• Opportunity: the machine-type field could back a real GPU / accelerated app category, which today has no signal at all to derive from.
• Opportunity: the payment memo is a genuine app-to-payment link that does not exist in the data model today.

Important caveat from the whitepaper

"The fields are in the schema and not yet in the code that would act on them: as of the survey, the payment memo, referral code and machine-type fields appear nowhere in the placement path. The enforcement height is constrained to follow the implementation, not precede it."

So the enforcement height may move, and the fields may be present-but-unpopulated for a while after enforcement. Treat this as: watch for the fields appearing in real spec data, do not build against the schema alone.

Next step

Sample globalappsspecifications for the new fields and see whether any are populated yet. That is cheap and decides whether there is anything actionable.

Source

Flux whitepaper v9, §3.3, https://whitepaper.app.runonflux.io/