The verifiable dossier behind every listing.
Every Node on TrafficNodes carries a Passport: identity, type-specific attributes, monetization and commercial terms, transfer terms, verification evidence and a full event history — the structured record a Node Score is computed from, and the record a buyer reviews before making an offer.
Interactive Passport demo
Crypto Signals — EU/EN
Crypto · European Union, Global
Asking price
$58,000
What's actually in a Passport
A Passport is structured, not a free-text description. Identity fields (type, platform, vertical, geo, language) are typed per Node type — a Telegram channel and an ad account carry different attribute sets, because they're different things. Monetization and commercial terms (price model, access model, sales model, quantity where finite) sit alongside audience and performance metrics, verification evidence at whatever level the listing has reached, and an immutable Node History log of every meaningful change: listing, offers, transfer, disputes.
Why structure beats a description
A free-text listing description can say anything. A Passport's fields are the same shape across every seller and every Node of that type, which is what makes a Node Score computable at all, what makes Rankings comparable, and what makes a buyer's diligence pass faster — you're reading the same fields in the same order every time, not parsing a paragraph for the numbers that matter.
What a buyer sees vs. what stays private
Everything shown here and on a live /node/[id] page is what a buyer actually gets — no private seller fields, no hidden Passport sections. What's NOT shown publicly (payout details, internal audit notes) simply isn't part of the public Passport shape; it isn't a redacted version of a bigger private one.
Capabilities
What this is backed by: Rendered on every /node/[id] page from lib/types.ts's Node/NodePassport shape and node_history rows.
On the Marketplace
Related Platform features