..

[.. @superfi000777]

Dusk's own bridge post-mortem: one signing wallet handled signing + event handling + connectivity in a single path. Compromised Jan 16, 8M+ DUSK moved before shutdown. Pitch is trust-by-design settlement for regulators.
Paid Partnership #dusk $DUSK @DuskFoundation

[.. @superfi000777]

Dusk lists four products with status tags: DuskDS is Live. DuskEVM and Hedger are Testnet. Dusk Trade — the actual application layer NPEX's €200M+ would run through — is still Building.
Paid Partnership #dusk $DUSK @DuskFoundation

[.. @superfi000777]

Dusk's homepage lists €300M+ "confirmed issuance with institutions" up top. The NPEX case study further down cites €200M+ specifically for NPEX.
Paid Partnership #dusk $DUSK @DuskFoundation

[.. @superfi000777]

Dusk's homepage lists €300M+ "confirmed issuance with institutions" up top. The NPEX case study further down cites €200M+ specifically for NPEX. No footnote connects the two numbers.
Paid Partnership #dusk $DUSK @DuskFoundation

[.. @superfi000777]

Dusk’s bridge incident shows why isolation matters: a single signing wallet handling too many jobs turned one compromise into a major loss. Separating signing, event handling and fund release reduces that blast radius.
Paid Partnership #dusk $DUSK @DuskFoundation

[.. @superfi000777]

Newton's cross-chain operator sync uses "permissionless relayers" to carry signed updates between chains. Signature stops forgery — doesn't guarantee delivery.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

No UX changes" — but underneath that, every transaction now runs a full operator consensus round: independent policy evaluation, TEE execution, BLS signature aggregation, before settlement.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton's operators independently fetch sanctions data — but if they're all querying the same upstream source (OFAC, one commercial feed), that's decentralized fetching, not decentralized truth.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton cites the $1.5B Bybit hack as the threat its runtime invariants solve. But Bybit wasn't a key-theft — it was a compromised signer UI tricking a legitimate signer.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton's identity checks run "within TEE enclaves —that's not decentralized infra, that's one hardware vendor's chip.TEEs have real documented side-channel exploits."No single point of trust" has a silicon-shaped asterisk in the identity Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton: "any Rego policy is automatically ZK-provable." True — but compiling a full interpreter into a general zkVM (SP1/RISC0) is historically slow vs. bespoke circuits, and the whitepaper never states a proving-time number.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton calls its operator network "decentralized for neutrality... permissioned for quality." Both in one sentence. Vetted legal entities running decentralized consensus among themselves isn't the same trust model as open, anyone-stakes Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton's whitepaper cites research on 16+ chains with fund-freezing built in as a problem — then lists its own "stolen asset blocking" a few sections later. Same mechanism, better paperwork? Transparent ≠ opaque Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Newton's operators are slashable for dishonest attestations. Real deterrent, real collateral at risk.
But slashing only fires once someone catches a bad outcome. It doesn't lower the odds of one slipping through first.

Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

An attestation proves a policy ran correctly.
It doesn't prove the policy was the right one to run.
That gap doesn't go away. It just gets harder to see once the execution looks this clean.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

A locksmith can prove a lock is unpickable without showing you the mechanism.
Newton's attestations work the same way — only a hash and commitment go onchain, never the underlying data.
Proof and privacy were never actually opposites.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

A notary doesn't ask you to trust them. Their signature is the proof.
Most compliance today still runs on promise.
@NewtonProtocol replaces that with a BLS attestation: cryptographic proof, not a claim.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Spent three weeks proving a compliant transaction had been properly screened.
Couldn't. The vendor said it ran. No record existed.
Newton produces a signed onchain receipt for every evaluation. Automatically.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Honestly didn't expect this reaction: not skepticism, more like noticing what "no UX changes" is actually admitting.
If enforcement is invisible, the only people who'll ever notice it exists are the ones it blocks.
Paid Partnership #Newt $NEWT @newton_xyz

[.. @superfi000777]

Verification proves something once.
But when that proof moves across systems, timing and context start to matter.
That’s where “valid” stops feeling absolute.
@SignOfficial $SIGN #SignDigitalSovereignInfra