# Bring Gonka to EBC12 as a Gold Sponsor

Proposal type: Активация спроса
Review source: AI_DRAFT
Recommendation: Needs revision
Community stance: Needs changes
Exported: 2026-06-25T21:36:50.372Z

> This is generated from the latest AI draft and has not been published by a human reviewer.

## Community Review

Recommendation: Needs revision
Evidence confidence: medium

Summary:
This is a plausible demand-activation sponsorship opportunity, but it is not yet fundable as a Community Fund grant. The evidence supports that EBC12 is a real Barcelona event positioned around digital-asset decision-makers, meetings, and sponsor visibility. However, the proposal does not define verifiable Gonka outcomes, a Gonka-side owner for representation and follow-up, a real budget breakdown, tranches, acceptance criteria, opportunity cost, or post-event reporting. The current success metric is a tender vote tally, which is governance context, not evidence of network impact.

Top reasons:
- The event and audience appear relevant, but network impact is not yet measurable or Gonka-specific.
- The 62,000 USDT ask lacks budget breakdown, tranches, opportunity-cost analysis, and contract/payment safeguards.
- Accountability is incomplete because the proposer represents EBC while the Gonka-side owner and representatives are not confirmed.
- The proposal should be revised into a procurement-style sponsorship plan with KPIs, acceptance criteria, reporting, and conflict controls before Community Fund capital is allocated.

Conditions:
- Name a Gonka-side accountable owner and confirmed representatives who can speak for Gonka, book meetings, staff the booth, approve messaging, and own follow-up after the event.
- Attach an official EBC sponsor quote or contract showing the exact Gold Sponsor deliverables, price, payment recipient, cancellation/refund terms, taxes/fees, and deadlines.
- Replace the vote-tally metric with outcome metrics such as target accounts contacted, qualified meetings booked before the event, meetings completed, qualified leads, follow-up owners, partnership/listing/integration opportunities opened, media/content deliverables, and post-event conversion targets.
- Provide acceptance criteria and verification artifacts: booth proof, speaking-slot proof, sponsor listing screenshots, agenda links, meeting log, lead register, post-event report, and follow-up status report.
- Provide a budget breakdown and opportunity-cost comparison against lower sponsorship tiers, booth-only attendance, targeted side event, delegation-only attendance, or other European growth channels.
- Use tranches or escrow: for example, deposit only after contract review, remaining payment after sponsor deliverables are confirmed, and any travel/activation spend separated from sponsorship fee.
- Disclose and manage the EBC/proposer conflict explicitly, including whether the proposer or affiliated entity receives the funds and whether any commission or sales incentive exists.
- Define risk handling for cancellation, non-delivery of speaking slots/booth, poor representative availability, compliance/brand approval, data handling for leads, and post-event reporting.

Blocking issues:
- No measurable outcome (blocker): The only success metric is a tender vote signal. It does not measure meetings, qualified leads, partnerships, integrations, listings, validator/operator interest, developer adoption, media reach, or any other Gonka network outcome.
- No budget or tranche logic (blocker): The ask is a lump-sum 62,000 USDT sponsorship with no itemized quote, tranche, escrow, cancellation/refund, or milestone logic.
- Unverified core claims (major): The event’s existence and audience positioning are corroborated, but the exact Gold Sponsor package, price, sponsor contract terms, and expected Gonka-specific outcomes are not independently verified in the usable materials.
- Material conflict or compliance risk (major): The proposer says he represents EBC, so the proposal appears to be vendor-originated. This is not automatically disqualifying, but it needs explicit conflict disclosure, procurement comparison, payment recipient details, and contract protections before funding.

Team confidence:
Team confidence is low for this exact ask. A proposer is named and appears to represent EBC, but the proposal does not establish who inside Gonka will own attendance, messaging, meetings, lead follow-up, reporting, and outcome delivery. The accessible corpus does not verify the proposer’s credentials or relevant delivery record beyond event-page claims.

Team checks:
- Owner - concern: Heydar Naghiyev is named as proposer and says he represents EBC, but the Gonka-side owner for representing the project and delivering outcomes is undecided.
- Relevant proof - concern: The EBC webpage supports event existence and audience positioning, but no usable evidence verifies the proposer’s individual delivery record, sponsorship fulfillment history, or prior outcomes for similar protocol sponsorships.
- Capacity - unknown: No staffing, time commitment, pre-event preparation, onsite schedule, meeting-booking resources, or follow-up capacity is specified for either EBC or Gonka representatives.
- Accountability path - fail: No reporting cadence, post-event report, lead register, meeting log, acceptance review, refund/cancellation path, or escalation path is defined.

Dimension notes:
- Network value 2/4: The network-value thesis is plausible: European market visibility and access to exchanges, institutions, infrastructure firms, allocators, and policy/digital-asset decision-makers could benefit Gonka. The EBC event page corroborates that the event is designed for decision-makers and meetings. But the proposal does not convert this into specific Gonka adoption, partnership, liquidity, builder, validator, compute, or commercial outcomes, so the network leverage remains speculative.
- Plan clarity 1/4: The sponsorship package is described at a high level, but the proposal lacks normalized acceptance criteria, explicit exclusions, milestone dates, pre-event workplan, target account list, speaker/booth staffing plan, lead qualification criteria, and post-event verification. The only listed success metric is a community vote tally, which is not a network outcome metric.
- Team confidence 1/4: There is a named proposer, Heydar Naghiyev, who says he represents EBC, and the EBC page supports the event's existence. However, the proposal does not provide usable evidence of the proposer’s relevant delivery record, the LinkedIn evidence failed to fetch, and the actual Gonka representatives are not assigned. For this exact ask, accountability is split between EBC providing a package and an unspecified Gonka/core/community representative delivering the network outcomes.
- Funding discipline 0/4: The request is a 62,000 USDT lump sum with no itemized package quote, no comparison to alternative sponsorship levels or events, no tranche/escrow logic, no payment safety conditions, and no opportunity-cost analysis. The only budget line is explicitly described as an inferred imported ask.
- Risk & stewardship 1/4: Material risks are underdeveloped. The proposer is affiliated with EBC, the likely payment recipient/vendor, which is a disclosed but important incentive conflict requiring explicit handling. There is no cancellation/refund plan, contract/payment recipient detail, compliance review, lead-data handling plan, post-event handover, or reporting cadence. Maintenance is not a maintained software asset issue, but follow-up ownership after the event is still missing.

## Conditions
- Name a Gonka-side accountable owner and confirmed representatives who can speak for Gonka, book meetings, staff the booth, approve messaging, and own follow-up after the event.
- Attach an official EBC sponsor quote or contract showing the exact Gold Sponsor deliverables, price, payment recipient, cancellation/refund terms, taxes/fees, and deadlines.
- Replace the vote-tally metric with outcome metrics such as target accounts contacted, qualified meetings booked before the event, meetings completed, qualified leads, follow-up owners, partnership/listing/integration opportunities opened, media/content deliverables, and post-event conversion targets.
- Provide acceptance criteria and verification artifacts: booth proof, speaking-slot proof, sponsor listing screenshots, agenda links, meeting log, lead register, post-event report, and follow-up status report.
- Provide a budget breakdown and opportunity-cost comparison against lower sponsorship tiers, booth-only attendance, targeted side event, delegation-only attendance, or other European growth channels.
- Use tranches or escrow: for example, deposit only after contract review, remaining payment after sponsor deliverables are confirmed, and any travel/activation spend separated from sponsorship fee.
- Disclose and manage the EBC/proposer conflict explicitly, including whether the proposer or affiliated entity receives the funds and whether any commission or sales incentive exists.
- Define risk handling for cancellation, non-delivery of speaking slots/booth, poor representative availability, compliance/brand approval, data handling for leads, and post-event reporting.

## Blocking Issues
- No measurable outcome (blocker): The only success metric is a tender vote signal. It does not measure meetings, qualified leads, partnerships, integrations, listings, validator/operator interest, developer adoption, media reach, or any other Gonka network outcome.
- No budget or tranche logic (blocker): The ask is a lump-sum 62,000 USDT sponsorship with no itemized quote, tranche, escrow, cancellation/refund, or milestone logic.
- Unverified core claims (major): The event’s existence and audience positioning are corroborated, but the exact Gold Sponsor package, price, sponsor contract terms, and expected Gonka-specific outcomes are not independently verified in the usable materials.
- Material conflict or compliance risk (major): The proposer says he represents EBC, so the proposal appears to be vendor-originated. This is not automatically disqualifying, but it needs explicit conflict disclosure, procurement comparison, payment recipient details, and contract protections before funding.

## Evidence Gaps
- Source-linked material (fetch_failed, failed) - https://www.linkedin.com/in/heydarnaghiyev/. init["status"] must be in the range of 200 to 599, inclusive.

## Source Links
- VOTE_GONKA 29baf37b-811f-4c36-b517-66a578383f1c (expired) - https://vote.gonka.vip/tenders/29baf37b-811f-4c36-b517-66a578383f1c

## AI Score
- Model: gpt-5.5
- Prompt: framework-review-v7
- Final score: 22.25
- Detailed recommendation: NO