SShortSingh.
Back to feed

Your Protocol Has Consensus. The Committee Reviewing It Doesn't.

0
·1 views

Somewhere right now, five people at an asset manager are discussing a DeFi protocol whose builders will never hear the verdict. The risk lead read the docs. Compliance found a blog post from last year. Legal skimmed an audit of a version that is no longer deployed, the portfolio manager remembers a founder's thread, and finance pulled numbers off a dashboard. Twenty minutes in, they realize they do not agree on what the protocol actually is, so the item gets parked and nobody sends the team a reason.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How to organize a large OpenAPI spec: multi-file structure, $ref rules, and CI checks

Every OpenAPI document starts as one clean file. Then it reaches forty operations and the file is 2,000 lines, then a hundred operations and pull requests conflict on every merge, then nobody edits it without a full afternoon of context. The standard advice is "split it with $ref," which is true and unhelpful — split how, along which boundaries, and what breaks in tooling when you do? This is the layout and rule set that survives 200+ operation APIs. Organize by artifact kind first, domain second.

0
ProgrammingDEV Community ·

Gev: Gmail label suggestions with an embedded inference engine.

I wanted a simpler way to sort email without sending message text to an AI service. So I started building Gev: a browser extension that reads my Gmail messages and automatically labels them into categories like Receipts, Personal, Updates, or Newsletters. https://github.com/receptron/laya model. The model and ONNX runtime are bundled with the extension. There’s no inference API or hosted model involved and no data is ever sent to an external service or host(except gmail).