Block or report davidsemakula
Block user
Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.
You must be logged in to block users.
Close all issues, pull requests, and discussions opened by this user
Content in all repositories owned by your account will be closed.
Add an optional note
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abuseI'm currently working on:
Program analysis, compilers and programming languages
- 🚧 pallet-verifier (creator): a tool for detecting common security vulnerabilities and insecure patterns in FRAME pallets using static program analysis techniques like data-flow analysis, abstract interpretation and symbolic execution. (Funded by the Web3 Foundation).
- rust-analyzer (independent contributor): a Rust compiler front-end for IDEs.
- MIRAI (independent contributor): an abstract interpreter for the Rust compiler's mid-level intermediate representation (MIR).
Cryptographic protocols and libraries
- 🚧 wamu (creator): a protocol and library for computation of threshold signatures by multiple cryptographic identities. (Funded by the Ethereum Foundation).
I've previously worked on/contributed to:
- ink! analyzer (creator): A collection of modular and reusable libraries and tools for semantic analysis of ink! smart contracts. (Funded by the Web3 Foundation).
- tangle-network/cggmp-threshold-ecdsa (independent contributor): an implementation of the CGGMP21 threshold ECDSA protocol.
- ink! (contributor): a Rust DSL (Domain Specific Language) for writing smart contracts for Substrate-based blockchains.
- cargo-contract (contributor): a build and deployment tool for ink! smart contracts.
⚡ I hold a B.Sc. in Computer Science.
Pinned Loading
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.