Join the Team · Roles & Standards
CVIN is in co-creation stage: the product runs, the data grows, revenue has just started. We are looking for two kinds of people: revenue-share partners (closed deals, agreed split) and pure contributors / volunteers (time in exchange for bylines, track record, and position in the ecosystem). Both are welcome. Rules first, in writing.
Two ways to participate
A · Revenue share
For people who can directly bring deals or supply (BD, channels, data-source operators). You close, we split as agreed in writing; annual renewals count on the same terms.
B · Contributor / volunteer
For people who believe in the project and want a byline and a track record (content, translation, community). Contributions are ledgered, and if your area later produces paid usage, attribution enters the share pool. Join and leave anytime.
Open roles (5 directions, all open)
BD / Channel Partner (regional)
revenue shareAcquisition is the only bottleneck. The registry, the price index, the verification reports — all live. What is missing is people to put them in front of data centers and buyers. A machine cannot knock on a door.
- Can get directly to decision-makers at GPU data centers / rental platforms / bulk buyers (not via public support channels)
- Bring at least 3 local contacts you can actually meet (a list is enough to start — no prior deal required)
- Can explain cvin.org's three products (registry / price index / verification report) in your own words
- Comfortable with a deal-first, share-on-close collaboration (see reward terms below, agreed in writing)
GEO content contributor (Chinese platforms)
contributor / volunteerChinese LLMs (Doubao, Kimi, Yuanbao) already cite cvin.org, but the Chinese corpus is still owned by stale CSDN/Zhihu content. We have the data and the material; we need people with account reach to publish it.
- At least one account on these platforms with a content history and no violations
- Fact-based writing only: cite site pages and real numbers; no "best / No.1" superlatives
- At least 2 posts per month (topics come from /answers and the weekly snapshot — no need to invent them)
- Byline model: articles belong to the author; cvin.org only requires citation
English content / localization
contributor / volunteerAll 30+ zh/en page pairs so far were translated by the initiator alone — coverage has plateaued. English pages face the dollar world directly (x402 payments, enterprise procurement): the most valuable corpus we have.
- Native-level English or long-term working proficiency (judged by a 200-word trial translation, not credentials)
- Solid grasp of GPU / compute / blockchain terminology (H100, SXM, lien, UCC-1 — translated correctly)
- Follow the site glossary: terms stay consistent across pages, no freelance rewrites
- At least 2 pages translated or proofread per month
Data-source operator (data center / rental platform / reseller)
revenue shareAutomated collection has hit its ceiling (20+ platforms). Incremental supply can only come from operators listing prices and registering devices themselves — the single growth channel on the supply side.
- Real operating devices or real quotes on hand (serial numbers or platform links we can verify)
- Listings are public: price data visible to everyone, no dark pools
- Register at least 10 devices to start (L1 or above, see /en/levels)
- Update quotes at least weekly
Standards Council — 7 seats (independent)
council seat · unpaidThe Council is where "neutrality must be structure, not statement" lands. All 7 seats are vacant. Charter v1.0 is to be amended by the first members who join — they are not being asked to sign it.
- No equity / employment / non-compete ties to the initiator (disclose and recuse if any)
- A publicly verifiable track record in any of: cryptography, standardization, compute supply/demand, asset finance, ITAD, public interest
- Seats are independent of commercial interests: they cannot be bought, carry no compensation, and the initiator is capped at 1/7 forever
- Participate in at least one RFC vote per quarter
How to apply
Email hi@cvin.org (subject: "Co-creation · role name") or Telegram @briantian. Three things only:
Applications enter the decision log (anonymized); everyone gets an answer either way — co-creation starts at the application step.