0x459948764599…45994879

ConfirmedFunding & Business537 vB80 sat/vB3 min decode

Dragonfly Reversed NEAR Decision After Next-Day Protocol Revision

Dragonfly initially planned to pass on NEAR, then co-led its seed round after Illia Polosukhin sent a revised protocol, according to Managing Partner Haseeb Qureshi.

Dragonfly Changed Course on NEAR After Next-Day Revision, Qureshi Says
WitnessDragonfly Changed Course on NEAR After Next-Day Revision, Qureshi SaysTheDigitalArtist / pixabay

Outputs

  1. Dragonfly co-led NEAR Protocol’s seed round after reversing its initial decision to pass.

  2. The reversal came one day after Dragonfly’s first meeting with the project.

  3. Co-founder Illia Polosukhin emailed a new protocol version that addressed Dragonfly’s feedback.

  4. Managing Partner Haseeb Qureshi said the revision remained imperfect but the team’s execution changed Dragonfly’s view.

  5. The source disclosed no round amount, valuation, date or terms.

Dragonfly co-led NEAR Protocol’s seed round after reversing an initial decision to decline the project, Managing Partner Haseeb Qureshi said, citing a revised protocol sent by co-founder Illia Polosukhin one day after Dragonfly’s first meeting.

The reversal followed Dragonfly’s assessment that NEAR had “fundamental flaws” and could not scale, according to Qureshi’s account on a podcast. Dragonfly had planned to pass immediately after the meeting. Polosukhin’s next-day response changed that outcome, although Qureshi said the revision was “still imperfect.”

What changed after the first meeting?

The sequence was direct. Dragonfly met with the NEAR team, formed a negative view and prepared to pass. The following day, Polosukhin emailed Dragonfly with a new version of the protocol. Qureshi said the document addressed the feedback Dragonfly had provided.

The account did not identify the specific technical shortcomings Dragonfly identified, the changes Polosukhin made or the tests used to assess the revision. As a result, the episode documents a change in Dragonfly’s investment judgment rather than independent proof that NEAR’s scalability concerns had been resolved.

What changed was clearer on process than engineering. Dragonfly went from an initial pass to further consideration and then co-leading NEAR’s seed round. The reported cause was not Qureshi’s conclusion that the revision was complete. He credited the team’s execution with changing the firm’s view.

Why did Dragonfly reverse course?

Qureshi’s account puts weight on responsiveness and follow-through. Polosukhin received Dragonfly’s concerns after the first meeting, then returned a revised protocol the next day. According to Qureshi, that response, together with the team’s execution, persuaded Dragonfly to reconsider its position.

The episode shows how a protocol review can feed directly into a funding decision. A technical assessment did not end the matter; the project team’s ability to answer criticism and resubmit the design did. For Dragonfly, the revision reopened due diligence that had otherwise ended with a decision to pass. For NEAR, the result was a seed-round co-lead.

That distinction matters because a financing commitment and a completed technical validation are different outcomes. Dragonfly’s participation shows that the firm viewed the project and team more favorably after the revision. It does not establish that NEAR’s scalability concerns had been conclusively resolved or that the revised protocol had already met production requirements.

What remains undisclosed?

Qureshi did not disclose the size, valuation, date or terms of the seed round in the account. He also did not identify the podcast or elaborate on Dragonfly’s original concerns and Polosukhin’s changes. The account specified no chain architecture, token standard, code repository or performance measure.

Those omissions limit what outsiders can conclude from the episode. The documented fact is that a next-day protocol revision preceded Dragonfly’s reversal and co-lead role. The broader judgment about NEAR’s ability to scale remains something the project must demonstrate, rather than something the investment decision alone settles.

The financing structure has already shifted from a planned Dragonfly pass to a seed-round co-lead; the next checkpoint is whether the revised protocol and team’s execution address the scalability concerns that initially stopped the firm.

via tokenpost.com (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,514 articles