keep-core
The core contracts and reference client implementation behind the Keep network, a privacy, interoperability, and censorship-resistance toolkit for developers on Ethereum.
What’s a keep?
The network offers application developers keeps, small off-chain data containers for private storage and computation that can be opened, closed, and managed by smart contracts autonomously.
Keeps are maintained by stakers, actors who run nodes and have skin in the game, and collect fees for operating the network. When a new keep is opened, the requisite number of stakers are chosen via a BLS-based random beacon to maintain the keep, using a process called sortition.
The first type of keep launching with the network is the BondedECDSAKeep,
allowing smart contracts to generate private keys and sign messages without
endangering key material. ECDSA keeps mean decentralized signing, cross-chain
applications, and new tools for custodial applications — from Solidity. This
capability is used heavily by tBTC.
To learn more about ECDSA keeps, check out keep-ecdsa.
Getting Started
A good place to start is the the docs directory.
Running a Node
To run your own node in the Keep network, follow the run Random Beacon doc. Feedback on this process and the documentation is appreciated!
Moving to a new random beacon
The legacy core contracts of the random beacon are moved to the solidity-v1/
directory which can be referred as "v1". The newest "v2" random beacon contracts can
be found in solidity/random-beacon directory.
The full specification of the "v2" random beacon is written in rfc-19-random-beacon-v2.adoc.
dApp Developers
dApp developers will be most interested in the smart contracts exposing Keep’s on-chain facilities.
The core contracts can be found in the solidity-v1/ directory.
They can be used to request
miner-resistant random numbers, as
well as creating and managing keeps. To generate new ECDSA key material and
request signatures, the contracts can be found in
keep-ecdsa.
Client Developers
Client developers will be most interested in the reference Keep
Go client and CONTRIBUTORS file, as well as the
RFCs and repo directory structure
Directory structure
The directory structure used in this repository is very similar to that used in other Go projects:
keep-core/
Dockerfile
main.go, *.go
docs/
solidity/ (1)
ecdsa/
random-beacon/
solidity-v1/ (2)
cmd/ (3)
pkg/ (4)
net/
net.go, *.go (5)
libp2p/
chain/
chain.go, *.go (5)
ethereum/
gen/
gen.go (6)
relay/
relay.go, *.go-
Core contracts of the Keep contracts. Random beacon contracts are stored under
/solidity/random-beaconwhereas ECDSA under/solidity/ecdsa. -
Legacy core contracts of the random beacon (v1). While the Keep network only uses Solidity at the moment, the directory structure allows for other contract languages.
-
Keep client subcommands are implemented here, though they should be minimal and deal solely with user interaction. The meat of the commands should exist in a package fit for the appropriate purpose.
-
All additional packages live in
pkg/. -
The high-level interfaces for a package
mypackagelive inmypackage.go.netandchainare interface packages that expose a common interface to network and blockchain layers. Their subpackages provide particular implementations of these common interfaces. Onlycmd/and the main package should interact with the implementations directly. -
When a package requires generated code, it should have a subpackage named
gen/. This subpackage should contain a single file,gen.go, with a// go:generateannotation to trigger appropriate code generation. All code generation is done with a single invocation ofgo generateat build time.