scispace - formally typeset
N

Nikhil Swamy

Researcher at Microsoft

Publications -  80
Citations -  3755

Nikhil Swamy is an academic researcher from Microsoft. The author has contributed to research in topics: Compiler & Semantics (computer science). The author has an hindex of 29, co-authored 77 publications receiving 3333 citations. Previous affiliations of Nikhil Swamy include University of Maryland, College Park.

Papers
More filters
Proceedings ArticleDOI

Formal Verification of Smart Contracts: Short Paper

TL;DR: This paper outlines a framework to analyze and verify both the runtime safety and the functional correctness of Ethereum contracts by translation to F*, a functional programming language aimed at program verification.
Proceedings ArticleDOI

Defeating script injection attacks with browser-enforced embedded policies

TL;DR: This paper proposes a simple alternative mechanism for preventing script injection called Browser-Enforced Embedded Policies (BEEP), which is that a web site can embed a policy in its pages that specifies which scripts are allowed to run.
Proceedings ArticleDOI

Dependent types and multi-monadic effects in F*

TL;DR: A new, completely redesigned, version of F*, a language that works both as a proof assistant as well as a general-purpose, verification-oriented, effectful programming language that confirms F*'s pay-as-you-go cost model.
Journal ArticleDOI

Secure distributed programming with value-dependent types

TL;DR: This work presents F*, a full-fledged design and implementation of a new dependently typed language for secure distributed programming that provides arbitrary recursion while maintaining a logically consistent core, and proves type soundness (with proofs mechanized in Coq) and logical consistency for F*.
Proceedings ArticleDOI

Verified Security for Browser Extensions

TL;DR: This paper presents \ibex, a new framework for authoring, analyzing, verifying, and deploying secure browser extensions based on using type-safe, high-level languages to program extensions against an API providing access to a variety of browser features, and proposes using Data log to specify fine-grained access control and dataflow policies.