Search Results for "smart contracts"

A library for secure smart contract development. Build on a solid foundation of community-vetted code. OpenZeppelin Contracts uses semantic versioning to communicate backward compatibility of its API and storage layout. To keep your system secure, you should always use the installed code as-is, and neither copy-paste it from online sources nor modify it yourself.

FHEVM is a framework built by Zama to enable confidential smart contracts on EVM-compatible blockchains using Fully Homomorphic Encryption (FHE). It lets developers write Solidity contracts that handle encrypted inputs, encrypted state, arithmetic and logical operations on encrypted types, while maintaining privacy (data always encrypted), composability (encrypted state works alongside public state), and security (via threshold decryption, KMS, etc).

...Any user can stake and help to secure the network. There is no voting, master nodes, or minimum amount required. There have been transactions as small as 2 Qtum that have created blocks in the past. Staking from smart contracts is under development.

...It emphasizes reproducible benchmark claims, keyless operation, and a clear status table that separates stable capabilities from experimental or roadmap work. Its stated target areas include web apps, CTF challenges, source-code review, OSS vulnerability hunting, smart contracts, and embedded or robotics research. Because it automates offensive workflows, it must only be used on systems where the user has explicit written permission.

...The main usage of the ChainKit is to unify top blockchains interfaces into a single normalized API interface, therefore you can build blockchain dApps easily without digging into blockchain complex infrastructure. Bi-directional on-chain transactions (inbound and outbound). Build dApps connecting to smart contracts using chain kit agnostic connector. Quick intuitive code deployments by using a special mechanism that will deploy smart contracts and dApp services where code changed. Silent deployments, no interruption for the current functionality (really useful on production). One single command to simultaneously deploy all available functions on your project where code changed from the last deployment. ...

...Cross-device sync uses encrypted CRDTs (Automerge) with no server involved in the merge. Vault recovery is handled via Shamir Secret Sharing (3-of-5). Unique features include on-chain digital inheritance via smart contracts on Base L2 (gasless, ERC-4337), built-in TOTP authenticator, breach monitoring via HIBP k-anonymity, encrypted document vault with NFC scanning, and email alias generation. Available on Chrome, Firefox, and iOS. Android is in private beta. Built by a solo developer. Fully open-source, zero telemetry.

Open eSign allows software developers and technical parties in a company to create secure, online (web-based) forms and documents that follow a business process flow and enable legally recognized electronic signatures using digital signature technology.