Capri_corn7

Spent the last stretch of today on the one actor in Trustless Bitcoin Vaults (TBV) that sounds least trustless on paper. A security council. I flinched at the name honestly, becuase councils are usually where trustlessness goes to quietly die.

then the actual power surprised me. the council is a 3 of 5 quorum whose only on-chain ability is broadcasting a no-payout transaction. It can BLOCK a payout in a catastrophic scenario, say a total failure of the proof system, but it cannot redirect btc anywhere. Council keys arent in any vault's destination set. Every place the btc can ever go was fixed at creation, the depositors own address or a registered arbitrageurs on liquidation, and thats enforced by bitcoin script itself.

So the worst a compromised council can do is delay someone. Not rob them. And the docs frame the whole role as transitional, a safety net meant to be retired as the protocol matures.

a backstop that can only say no feels like a different category from a multisig that holds funds. but retiring it is a promise, not a mechanism. has any protocol you follow actually dismantled its own emergency powers once things stabilized?

#baby @BabylonLabs_io $BABY

Unpopular opinion:
90% of people lose money on Binance because they chase pumps.

Real money is made by holding and waiting.

Agree or disagree? 👇
#Binance #tradingtips

No campaign this week? No problem 😎

Drop your biggest airdrop win below 👇
Mine: $142 from NEWT + GRVT

Let’s see who’s the airdrop king 👑
#Binance #Airdrop #CryptoPakistan

Le marché est vert aujourd’hui 📈
BTC 64K$ | ETH 3,2K$

Quelle est votre manœuvre en ce moment ?
A) Je conserve
B) J’achète la baisse
C) Je prends mes profits

On en discute 👇
#Binance #crypto

BTC is holding $64K right now 👀
Do you think it will hit $70K this month?

Comment YES or NO 👇
#Binance #bitcoin #CryptoPakistan

Campaigns on Binance are slow right now, so let’s keep it active with market news 😅
In your opinion, which token will pump the most in August?
Drop the name in comments 👇
#Binance #CryptoPakistan

A smaller observation today, looking at Newton's references section as a whole rather then any individual citation, since Ive noticed this pattern building across the whole newton document without naming it directly until now.
The whitepaper cites real, checkable external sources throughout, a security lab's freezing capability analysis, legislative text for the GENIUS Act, an FBI advisory on a specific exploit, peer reviewed cryptography papers on MPC throughput and threshold FHE, established standards documentation for HPKE and OPA. Twenty three references total, spanning regulatory filings, academic papers, and incident reports.
What this pattern does, cumulatively, is let claims be checked rather then just trusted. A number like "298 billion in stablecoin supply" or "16 chains with fund freezing capability" isnt just an assertion, its traceable to a specific, named, external source someone could independently verify.
Thats a meaningfully different posture then a whitepaper that makes claims and expects them accepted on the strength of the document's own authority. Having read through the citations alongside the claims they support across this whole project, I think thats actually one of the quieter, less discussed reasons the document holds up as well as it does under scrutiny.
#Newt @NewtonProtocol $NEWT

J’ai parcouru aujourd’hui la structure du flux de ticker de GRVT, principalement parce que comprendre ce que contient réellement une seule mise à jour de ticker est important pour finaliser l’image des données de marché que je construis tout au long de ce sprint.
Un ticker donne probablement le dernier prix négocié, le plus haut et le plus bas sur 24 heures, le volume sur 24 heures, et sans doute la variation en pourcentage sur la même période, mis à jour sous forme d’un instantané compact plutôt que d’exiger qu’un client calcule lui-même ces statistiques à partir de l’historique brut des transactions.
Ce que je trouve notable, c’est que c’est fondamentalement une couche de commodité placée au-dessus de données qui, techniquement, peuvent être dérivées du flux des transactions que j’ai consulté précédemment. Un client pourrait en théorie calculer le plus haut, le plus bas et le volume sur 24 heures en traitant l’historique complet des transactions, mais le fait que GRVT calcule et diffuse directement ce récapitulatif supprime une charge de calcul réelle pour chacun des clients qui devrait autrement maintenir le même calcul glissant de manière indépendante.
Cela rejoint un schéma que j’ai remarqué cette semaine dans la conception plus globale du flux de GRVT : des données brutes et granulaires existent (profondeur du carnet d’ordres, transactions individuelles), mais des vues résumées, pré-calculées, existent aussi en parallèle, pour les cas où le détail complet n’est pas nécessaire.
Je termine ce sprint avec l’observation que la surface d’API de GRVT semble être conçue de manière cohérente autour de cette même compensation : des données granulaires pour ceux qui ont besoin de précision, et des données résumées pour ceux qui ont seulement besoin d’avoir rapidement une image fiable.
@grvt_io #grvt

Went through GRVT's recent trades feed today, mostly becuase understanding exactly what data this feed carries matters for anyone building analysis tools on top of executed activity rather then just resting order data.
The trades feed surfaces individual executed trades as they happen, presumably including price, size, side, and timestamp for each fill. Unlike the orderbook, which shows resting intent, the trades feed shows actual completed activity, whats genuinely traded rather then whats merely available to trade against.
What I find notable is the distinction this creates for anyone doing analysis. Orderbook depth tells you what liquidity exists. The trades feed tells you what liquidity actually got consumed. Those are genuinely different signals, a thick orderbook with very little trade activity behind it suggests passive liquidity that isnt necessarily reflective of real trading interest, while a thin orderbook with heavy trade flow suggests something different entirely.
For anyone building volume analysis or trade flow indicators on top of GRVT, the trades feed specifically, not the orderbook, is the actual source of truth for what happened rather then what was merely available.
Still working through how far back this feed's history extends for a fresh subscription, whether a new client gets some recent trade history as an initial snapshot, or only sees trades that occur after they subscribe.
@grvt_io #grvt

A narrower follow up today on just the Market Data category within Newton's data provider ecosystem, since it uses a distinctly different integration method then the other categories I looked at broadly before.
Market Data, covering asset prices, FX rates, and NAV feeds, is the only category specifically routed through Newton's consensus mechanism, the same median reconciliation used in the two-phase evaluation flow. Every other data category either uses a real time feed with attestation, or arrives as an issued credential, neither of which requires reconciling disagreement across multiple operators the way market data does.
That distinction makes sense once you consider the nature of price data. Multiple operators independently fetching a price at slightly different moments will genuinely observe slightly different numbers, thats expected, not a failure. Sanctions data or credential data doesnt have that same observational variance, either an address is on a list or it isnt, either a credential was issued or it wasnt.
So Market Data isnt just another category using the same generic WASM plugin pattern as everything else, its specifically the category whose nature demanded Newton build a reconciliation mechanism in the first place.
Still thinking about whether other data categories could theoretically need this same consensus treatment as Newton's provider ecosystem grows, or whether price volatility is genuinely unique among the current categories in requiring it.
#Newt @NewtonProtocol $NEWT

Went through GRVT's Market Data API structure today, specifically how instruments and margin rules are exposed through it, becuase understanding what data is actually available publicly matters for anyone building analysis tools rather then just an execution system.
GRVT's Market Data API surfaces instrument definitions, current tickers, orderbook depth, recent trades, and candlestick data. Margin rules specifically appear to be queryable through this same API, meaning risk parameters arent hidden information only visible after account authentication, theyre publicly available for anyone evaluating what leverage and margin requirements apply to a given instrument.
What I find notable is that publicly exposing margin rules through market data, rather then requiring authenticated access, lowers the barrier for anyone evaluating GRVT before committing capital. A prospective trader can assess the actual risk parameters of an instrument without needing to create an account first.
This transparency also matters for anyone building third party tools on top of GRVT, since margin and risk data being publicly queryable means such tools dont need special authenticated access just to display accurate leverage information to users.
Still working through how frequently this margin rule data actually updates, whether changes to risk brackets propagate through the same real time feed structure as price data, or through some slower moving separate channel.
@grvt_io #grvt

A specific use case in Newton's whitepaper worth breaking down on its own today, institutional DeFi access, separate from the sealed bid auction mechanism that gets more attention within the same section.
Banks, asset managers, and pension funds want access to DeFi yield, lending, and trading opportunities, but participation requires compliance grade infrastructure, enforceable investor eligibility, position limits, counterparty screening, and audit trails satisfying both internal compliance teams and external regulators simultaneously.
What stands out is the dual audience requirement specifically, internal compliance AND external regulators. Many compliance solutions optimize for one or the other. Satisfying an internal risk committee is a different bar then satisfying an external regulatory examination, and building infrastructure that clears both simultaneously is a more demanding design target then either alone.
Newton's pitch is that institutions can define their own compliance policies in Rego, and Newton enforces those policies at the transaction level across whatever protocols and chains the institution actually interacts with, without requiring permissioned forks of the underlying DeFi protocols themselves.
Still working through how this scales when different institutions using the same underlying protocol have genuinely conflicting compliance requirements configured through their own separate policies.
#Newt @NewtonProtocol $NEWT

Went through GRVT's order rejection reason list today, mostly becuase understanding failure modes usually tells you more about a system's actual design constraints then the happy path documentation does.
GRVT documents a fairly extensive set of rejection categories. Margin related rejections, when an order would push an account below required margin. Self trade protection, preventing an account from matching against its own resting orders. Market maker protection, a mechanism specifically for market makers to avoid getting picked off during sudden volatility. Position size limit violations, when an order would push a position past whats allowed.
What I find notable is the sheer specificity of these categories rather then a generic "order rejected" response. Self trade protection and market maker protection specifically are not basic validation checks, theyre protective mechanisms addressing real trading scenarios experienced participants actually run into.
This granularity matters practically for anyone building an automated system on top of GRVT. A generic rejection tells you nothing actionable. A specific reason tells you exactly what to adjust, reduce size, cancel a conflicting order, wait for volatility to settle, before resubmitting.
Still working through whether these categories map to a fixed numeric error code scheme, or whether theyre primarily descriptive strings a client would need to pattern match against.
@grvt_io #grvt

A narrower detail within Newton's governance framework caught my attention today, specifically the operator admission process described as balancing quality control with decentralization.
Those two goals are in some tension by nature. Pure quality control would suggest a small, carefully vetted set of operators meeting a high bar. Pure decentralization would suggest admitting as many operators as possible to avoid concentration. Newton's framing explicitly acknowledges its balancing these rather then optimizing for either one exclusively.
In practice this likely means admission criteria that are demanding enough to filter for real operational and compliance capability, real legal entity status, uptime guarantees, an actual AML program, while still being achievable by more then a small closed circle of pre selected entities.
What I find worth noting is that this framing implicitly rejects two easier alternatives, a fully open operator set with no admission bar at all, or a small permanently fixed set of operators chosen once and never expanded. Newtons approach requires an ongoing governance process making judgment calls about where that balance sits, which is more operationally demanding then either extreme would be.
Still uncertain about how this admission process actually scales as Newton grows, whether the bar shifts as the operator set expands, or stays fixed regardless of how many operators already exist.
#Newt @NewtonProtocol $NEWT

Un détail de sécurité spécifique dans l’environnement d’exécution (sandbox) du fournisseur de données de Newton a retenu mon attention aujourd’hui, surtout la partie concernant le blocage des IP privées.
SSRF, server side request forgery (falsification de requêtes côté serveur), est une attaque réelle et assez courante : un code censé accéder à une ressource externe se fait tromper ou contraindre à accéder plutôt à une ressource interne, ce qui peut exposer une infrastructure qui n’avait jamais vocation à être accessible publiquement. Les fournisseurs de données WASM de Newton s’exécutent dans un environnement qui bloque explicitement les plages d’adresses IP privées dans le cadre du sandbox, fermant ainsi cette voie d’attaque avant même qu’un plugin compromis ou malveillant ne puisse tenter quoi que ce soit.
Combiné à des limites strictes de ressources, le sandbox protège contre deux catégories distinctes de dérives en même temps : un plugin qui tente d’atteindre un endroit qu’il ne devrait pas, et un plugin qui essaie de consommer plus de calcul ou de bande passante que ce qui lui est alloué.
Je me demande encore si ce blocage des IP privées est une règle fixe et uniforme appliquée identiquement par chaque opérateur, ou si c’est quelque chose que des opérateurs individuels configurent eux-mêmes dans le cadre de leur déploiement ; cela compterait pour évaluer à quel point la garantie de sécurité réelle de Newton reste cohérente sur l’ensemble du réseau.
#Newt @NewtonProtocol $NEWT