Published working playbook — not listing policy, legal advice, investment advice, or a token recommendation. Prepared for Rohan Deshmukh, Head of Listing Research, Sagar Digital Assets Exchange, Navi Mumbai, for a nine-person desk and the 11 January 2027 screening kickoff. Draft prepared 18 November 2026.
Answer status: Rohan approved the four Stack Exchange question drafts in Appendix A on 18 November 2026. They are ready for manual submission; no live question URLs or answers to those new questions were available at publication. The “prior reading” below summarizes existing, attributed Stack Exchange answers; it does not present them as answers to the new drafts.
1. Operating protocol
Create one timestamped evidence record per candidate. At minimum, record:
- Token name, contract address(es), chain(s), token standard, decimal/supply model, mint/burn functions, proxy/upgrade history, and any ticker or contract migration.
- Category, researcher, independent reviewer, compliance liaison, evidence URLs, data-retrieval time, and unresolved PostHog
question_keyvalues. - Entity/foundation and beneficial-ownership documents where applicable; governance and privileged-control documentation; counsel/compliance sign-off status.
- Market-data window, venues/pairs covered, executable-depth results, unlock/emission schedule, treasury/market-maker disclosures, and manipulation review.
- Community methodology, including sybil/bot filtering, incentive adjustment, developer retention, governance participation, and incident-disclosure history.
- Decision and dissent: evidence accepted, evidence rejected, rationale, reviewer, and conditions for reassessment.
Use maker-checker review: a category owner produces the record, an independent reviewer reproduces the important checks, and only authorized compliance/legal personnel make legal determinations. Do not convert the illustrative metrics below into pass/fail thresholds without desk approval.
2. Common and category-specific checklist
| Category | Compliance-supporting evidence | Liquidity quality | Community quality |
|---|---|---|---|
| DeFi | Verified source; issuer/governance records; admin, pause, upgrade and timelock controls; oracle dependencies; legal review of the actual lending, yield, derivatives or reward mechanics as applicable. | CEX/DEX executable depth at desk-approved notionals; holder and LP concentration; lock-ups, emissions and unlocks; cross-venue price/volume consistency; wash-trading and incentive-adjusted activity; liquidation/oracle stress. | Retained users rather than only wallet counts; developer and governance participation; voter concentration; incident response; sybil and airdrop/incentive filtering. |
| L2 | Bridge, sequencer/proposer, proof system, data availability, upgrade keys, forced inclusion/withdrawal and escape-hatch documentation; token utility and migration records; counsel review of claims and controls. | Bridge/withdrawal friction and finality; canonical versus wrapped representations; incentive-driven TVL; unlocks; depth across L1/L2 and CEX venues; migration-adjusted histories. | Real developers and users; sequencer/operator/governance concentration; independent ecosystem projects; sybil/incentive adjustment; incident and upgrade communication. |
| Gaming | IP/asset licences; studio and mint/admin rights; royalty and metadata controls; player terms; qualified review of rewards, loot boxes, chance mechanics, consumer protection and marketing as applicable. | Separate fungible-token and NFT tests; executable token depth; NFT floor depth and unique buyers/sellers; wash trading; treasury support; unlocks and studio-related selling. | Retained players and creators; bot-adjusted activity; repeat spend/usage rather than only sign-ups; developer output; community moderation and incident history. |
| Infrastructure | Entity/operator records; service agreements; node/operator rules, slashing and rewards; privileged controls; any licensing or data-provenance issues requiring qualified review. | Emissions and operator rewards; treasury sales; real service revenue versus subsidies; executable depth; holder/operator concentration; unlocks and venue consistency. | Independent node operators, developers and paying users; uptime and service quality; concentration; governance; subsidy-adjusted growth and outage disclosure. |
Suggested escalation conditions, pending approval: an actual legal prohibition or unresolved sanctions concern; unverifiable contract ownership/control; no credible withdrawal/settlement path; evidence of manipulated volume; undisclosed privileged minting; or a material claim that cannot be independently substantiated. Whether each is a hard stop or an enhanced-review trigger is a policy decision for Rohan, compliance and counsel.
3. Prior Stack Exchange reading — attributed and qualified
These are background sources retrieved from Ethereum Stack Exchange. Summaries below are paraphrases; source answers are available under CC BY-SA 4.0. Votes and acceptance are not substitutes for independent verification.
- DeFi: Mikko Ohtamaa’s answer to “Evaluating Arbisoo risks” treats technically incoherent, buzzword-heavy project documentation as a serious risk signal. Desk control: escalate unclear claims for evidence review, but do not allege fraud from writing quality alone.
- L2: Henry Gagnier’s accepted answer to “Blockchain Layer 2 Attacks” notes that EVM contracts on L1 and major L2s use the same Solidity environment. Desk limitation: contract-language similarity does not remove L2-specific bridge, proof/finality, data-availability, sequencer or upgrade risks; review those layers separately. Doğa Özcan’s answer to “What are the drawbacks of layer 2?” also highlights data-availability risk, but every dated technical claim must be checked against the candidate’s current architecture.
- Gaming: Nicolas Massart’s answer about building a game around an existing NFT collection explains that a game can read NFT ownership/metadata, while contract changes may require the original authors and wallet ownership should be verified. Desk addition: technical interoperability is not proof of an IP licence.
- Infrastructure: DevCrypto’s answer on Chainlink/oracle safety notes that Ethereum itself does not guarantee off-chain data safety. Lauri Peltonen’s accepted answer on oracle timestamps discusses oracle trust, availability and latency. Desk control: document oracle/operator trust assumptions, heartbeat and deviation parameters, fallbacks, audits, uptime and incident history rather than treating “uses an oracle” as a safety conclusion.
Unanswered by these sources: current Indian legal treatment, desk-specific liquidity thresholds, and validated community-quality benchmarks. Those remain open rather than being inferred from old answers.
4. Reproducible Polygon market-data examples
Illustrative proxy pairs: AAVE/USD for DeFi, POL/USD for L2, IMX/USD for gaming, and LINK/USD for infrastructure. They are examples only, not a candidate shortlist or ranking.
Pull specification: Polygon daily aggregates, multiplier=1, timespan=day, from=2026-10-19, to=2026-11-17, adjusted=true, sort=asc; 30 bars per pair, dates in UTC, retrieved 18 November 2026.
| Category | Pair | Last close (USD) | Median daily USD-notional proxy | 30-bar close return | Annualized log-return volatility | Max close drawdown |
|---|---|---|---|---|---|---|
| DeFi | X:AAVEUSD |
112.55 | $6,913,489 | -24.65% | 90.9% | -35.00% |
| L2 | X:POLUSD |
0.08300 | $834,366 | -10.40% | 66.5% | -18.06% |
| Gaming | X:IMXUSD |
0.09983 | $186,706 | -34.30% | 71.8% | -38.01% |
| Infrastructure | X:LINKUSD |
9.32 | $10,900,178 | -22.63% | 76.9% | -28.88% |
Method:
- Daily USD-notional proxy = Polygon base volume
v× volume-weighted average pricevw; the table reports the median of the 30 daily values. - Close return = last close ÷ first close − 1. The 30 bars provide 29 close-to-close return intervals.
- Volatility = sample standard deviation of those log returns × √365. This is an illustrative historical annualization, not a forecast.
- Max close drawdown = minimum of close ÷ running peak close − 1 within the window.
- All four series had 30 bars and zero zero-volume bars. Polygon request IDs, in table order:
a61460a021dd63ae4b0bf5361aed0580,b3b103842f7c7501e814d74f1dda3992,0b80645fdf2c0c7000ad80a674df3acf, and5b738180db64158b8c682122f834ab0a.
Critical limitations: OHLCV notional is not executable depth, bid/ask spread, slippage, global market share, or proof of genuine volume. Polygon venue coverage and pair mappings must be documented; validate with order-book depth, venue-level data and wash-trading analysis. Do not compare raw token units across assets. X:MATICUSD remained discoverable as active but returned zero bars for this window, so X:POLUSD was used. Reconcile MATIC→POL migration history and avoid silently splicing incompatible series. A snapshot request also returned only fallback AAVE data, so this draft relies on the four complete aggregate series instead.
5. PostHog open-question register
The 12 opening events were verified after ingestion: three each for DeFi, L2, gaming and infrastructure in PostHog project 738640. The saved insight is Sagar 2027 screening — unresolved research questions (OnWAeGvZ).
| Category | Compliance | Liquidity | Community |
|---|---|---|---|
| DeFi | defi_compliance |
defi_liquidity |
defi_community |
| L2 | l2_compliance |
l2_liquidity |
l2_community |
| Gaming | gaming_compliance |
gaming_liquidity |
gaming_community |
| Infrastructure | infra_compliance |
infra_liquidity |
infra_community |
Each listing_research_question_opened event includes cycle_id=sagar_2027_01_11, category, check_type, question_key, full question text, status=open, unassigned owner/reviewer, and publication_status=draft_pending_rohan_approval.
To resolve an item, capture exactly one listing_research_question_resolved event with the same cycle_id, category, check_type, and question_key, plus resolution_url, resolution_note, owner, and reviewer. The saved insight calculates opened − resolved, broken down by category. An answer arriving is not enough; a reviewer must approve the resolution.
Publication update: the later listing_research_question_status_changed events record publication_status=approved_pending_manual_submission while retaining status=open. A listing_research_playbook_published event records this article’s public DEV URL.
Tracking discipline: do not retry opening or resolution batches blindly—duplicates distort the formula. Define an idempotent event UUID/reopening convention before live use. Keep privileged legal findings and personal analyst data out of PostHog; store only non-sensitive research metadata and links to the controlled evidence record. The current “Default project” contains unrelated event streams, so retain the cycle filter and consider a dedicated project.
Appendix A — exact Stack Exchange question drafts
All four target Ethereum Stack Exchange and use existing tags, which matters because the connected account has 1 reputation and cannot be assumed to have tag-creation privileges. These are process questions, not requests for token picks or legal advice. Site scope still needs moderator/community-fit confirmation.
A1. DeFi
Title: What verifiable evidence should a token-listing review collect for a DeFi token?
Tags: defi, security, audit, tokens, liquidity
Body:
I am building a repeatable token-listing review for a nine-person research desk. This is a process question, not a request for token recommendations or legal advice.
For a DeFi token and its associated protocol, what verifiable evidence should be collected before listing? Please address these three evidence groups:
- Compliance-supporting artifacts: verified contract source, issuer/governance documentation, admin/pause/upgrade/timelock controls and oracle dependencies. Which technical, contract and governance records should qualified counsel/compliance personnel review?
- Liquidity quality: executable CEX/DEX depth at predefined trade sizes, holder/LP concentration, emissions and unlocks, cross-venue consistency, and tests for wash trading or temporary incentive-driven liquidity.
- Community quality: retained users, developers and governance participants; voter concentration; incident disclosure; and methods for adjusting wallet, vote and activity counts for sybil accounts or incentives.
Please prioritize measurable checks, reliable data sources and red-flag/failure conditions, with limitations. How should oracle failure, liquidation cascades, composability, privileged keys and recursive or leveraged liquidity change the review? An ideal answer distinguishes reported activity from executable liquidity and organic participation.
A2. Layer 2
Title: What verifiable evidence should a token-listing review collect for an L2 token?
Tags: layer-2, security, decentralization, scalability, liquidity
Body:
I am building a repeatable token-listing review for a nine-person research desk. This is a process question, not a request for token recommendations or legal advice.
For a layer-2 token, what verifiable evidence should be collected before listing? Please address:
- Compliance-supporting artifacts: current bridge, sequencer/proposer, proof, data-availability, upgrade-key, forced-inclusion/withdrawal and escape-hatch documentation, plus token utility and migration records. Which artifacts should qualified counsel/compliance personnel review?
- Liquidity quality: executable depth across relevant L1/L2 and centralized venues; canonical versus wrapped supply; bridge/finality/withdrawal friction; emissions, unlocks and incentive-driven TVL; and migration-safe price/volume histories.
- Community quality: developers, retained users and governance participation; operator/voter concentration; independent ecosystem usage; and sybil/incentive-resistant measurement.
Please give measurable checks, reliable sources, red flags and limitations. How should proof/finality assumptions, data availability, sequencer censorship or downtime, upgrade controls and bridge/escape-hatch design alter the review? Please distinguish raw TVL or transaction counts from durable liquidity and organic use.
A3. Gaming
Title: What verifiable evidence should a token-listing review collect for a gaming token?
Tags: games, nft, tokens, security, liquidity
Body:
I am building a repeatable token-listing review for a nine-person research desk. This is a process question, not a request for token recommendations or legal advice.
For a gaming token, including a game using ERC-20, ERC-721 or ERC-1155 assets, what verifiable evidence should be collected before listing? Please address:
- Compliance-supporting artifacts: IP/asset licences, studio and mint/admin controls, royalty and metadata mutability, player terms, and the technical records qualified counsel would need to assess rewards, loot boxes/chance mechanics, consumer protection and marketing as applicable.
- Liquidity quality: separate fungible-token and NFT tests; executable depth; NFT unique buyers/sellers and floor depth; wash-trading detection; treasury support; unlocks; and studio-related selling.
- Community quality: retained players and creators, bot-adjusted activity, repeat usage rather than sign-ups, developer output, moderation and incident history.
Please provide measurable checks, reliable sources, red flags and limitations. How should studio keys, metadata changes, asset interoperability and bot- or incentive-driven activity change the review? Technical interoperability alone should not be treated as evidence of IP permission.
A4. Infrastructure
Title: What verifiable evidence should a token-listing review collect for an infrastructure token?
Tags: oracles, off-chain, security, tokens, liquidity
Body:
I am building a repeatable token-listing review for a nine-person research desk. This is a process question, not a request for token recommendations or legal advice.
For an oracle, RPC, storage, compute or DePIN infrastructure token, what verifiable evidence should be collected before listing? Please address:
- Compliance-supporting artifacts: entity/operator records, service agreements, node rules, slashing/reward mechanics, privileged controls and data-provenance records that qualified counsel/compliance personnel should review.
- Liquidity quality: executable depth, emissions and operator rewards, treasury sales, unlocks, holder/operator concentration, venue consistency, and real service revenue versus token-subsidized demand.
- Community quality: independent node operators, developers and paying users; uptime/service quality; operator and voter concentration; governance; outage disclosure; and subsidy-adjusted growth.
Please provide measurable checks, reliable sources, red flags and limitations. How should oracle/operator centralization, service availability, data provenance and reward-driven supply change the review? An ideal answer distinguishes paying usage and executable liquidity from incentivized node counts, transfers or reported volume.
Appendix B — confirm before the 11 January 2027 cycle
-
Author identity and permission: the connected Stack Exchange and DEV profiles display
1DS22CS119_Manish, not Rohan. Confirm permission to use these accounts, the desired public author/organization, and whether the exchange name and internal workflow may be public. -
Posting route and site fit: the Stack Exchange API available here returned
no_methodfor question creation. The four drafts therefore require manual posting or another authorized route. Confirm Ethereum Stack Exchange scope; broad best-practice questions may need further narrowing or migration. - Answers and timing: set an answer-harvest/review date before kickoff and criteria for accepting community input. Do not wait for or imply unanimous community consensus.
- Ownership: supply the nine desk members’ names/roles, category owners, independent reviewers, compliance liaison, escalation path, and whether the nine includes Rohan.
- Legal/compliance sign-off: obtain qualified Indian counsel/compliance confirmation of the current VDA/regulatory perimeter, AML/KYC and sanctions controls, Travel Rule and recordkeeping obligations, tax/reporting treatment, advertising/consumer requirements, and any gaming/chance/derivatives issues that apply. Analysts should collect evidence, not make unsupported legal conclusions.
- Policy thresholds: approve hard stops versus scored factors, liquidity notionals and slippage limits, concentration/unlock limits, lookback windows, sybil thresholds, missing-data treatment, and reassessment triggers.
- Market-data governance: approve Polygon and secondary sources, venue coverage, pair mapping, time zone/cut-off, corporate/token-action handling, and the MATIC→POL treatment. Re-run all examples near kickoff.
- Publication scope: the account owner approved this working playbook for publication on 18 November 2026. Obtain legal/compliance review before treating it as official policy, and review future revisions and redactions. Token examples must remain clearly illustrative.
-
PostHog governance: confirm use of Default project
738640or move to a dedicated project; confirm access, retention, event idempotency/reopening rules, and the prohibition on privileged or personal research data. - Kickoff definition: confirm the exact Asia/Kolkata start time, candidate universe, jurisdictions served, and whether any category definitions overlap (for example, an L2 gaming token) plus the required multi-label review rule.
Top comments (0)