Skip to content
master
Switch branches/tags
Code

Latest commit

* refactor and support array types in EIP-712 encoding

* add domain and request types

* start adding tests for eip712 function with encodeType

* update encodeType to throw an error when an unrecognized type is encountered

* add array support for encodeType and typeHash test

* add basic data example and fix edge case with string encoding

* use the `keccak` alias instead of `sha3`

* handle ints and uints outside of uint256

* add Transaction example and structHash test

* add BigNumber to EIP-712 value type definition

* fix and add test for array encoding

* add Optional type to make Domain types EIP-712 compliant

* make DomainRestrictedSignatureRequest EIP-712 compatible

* add comment and compile-time test

* add EIP-712 type for SequentialDelayDomain

* fix the build and add compile test

* add zero value handling with EIP-712 objects

* add request types and remove unused zero default code

* fix a couple of linter errors

* add and use OmitIfNever to simplify declarations

* move compile tests into separate file

* format comment

* add example to type comment

* use updated SequentialDelayDomain in rate limit code

* fix input-validaton-test types

* fix phone-number-privacy-common tests

* specify default for first type param in requests

* add domainHash function for easier use of hashing

* utilize new types in odis signer and minor refactorings

* fix remaining linter errors

* make disable domain request idempotent and allow disabling previously unknown domains

* fix build error

* refactor and add EIP712 type for domain options

* modify spec to include name and version in EIP-712 message

* add EIP-712 types for domain signature request

* add EIP-712 types for quota and disable request types

* rename the publicKey field to address

* Apply suggestions from Alec's code review

Co-authored-by: Alec Schaefer <alec@cLabs.co>

* Use more description names for EIP-712 optional type functions

* fix usage of renamed field publicKey -> address

* Add option to use unpublished dependency code to the Docker build

* fix missing comma in cloudbuild.yaml

* fix dependency refrence in signer package.json

* update yarn.lock

Co-authored-by: Alec Schaefer <alec@cLabs.co>
f4dd249

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time

celo logo

Celo Monorepo - Official repository for core projects comprising the Celo platform

This repository contains the source code for the Celo core projects including the smart contracts, contractKit, and other packages. The source code for the Celo Blockchain which operates a node on the Celo Network is kept in a separate repo here.

CircleCI Codecov GitHub contributors GitHub commit activity GitHub Stars GitHub repo size GitHub

Website celo.org Blog docs Youtube forum Discord Twitter CeloDevs Twitter CeloOrg Subreddit subscribers

GitHub pull requests by-label GitHub Issues GitHub issues by-label GitHub issues by-label GitHub issues by-label

Contents:

🥅 Celo's Mission - Prosperity for All

Celo, pronounced /ˈtselo/, means ‘purpose’ in Esperanto. In a similar spirit, we are aiming to create a new platform to connect people globally and bring financial stability to those who need it most. We believe blockchain technology is one of the most exciting innovations in recent history and as a community we look to push the boundaries of what is possible with it today. More importantly, we are driven by purpose -- to solve real-world problems such as lack of access to sound currency, or friction for cash-transfer programs aimed to alleviate poverty. Our mission is to build a monetary system that creates the conditions for prosperity for all.

Play on Youtube - What if money were beautiful
What if money were beautiful?

🧱 The Celo Stack

Celo is oriented around providing the simplest possible experience for end users, who may have no familiarity with cryptocurrencies, and may be using low cost devices with limited connectivity. To achieve this, the project takes a full-stack approach, where each layer of the stack is designed with the end user in mind whilst considering other stakeholders (e.g. operators of nodes in the network) involved in enabling the end user experience.

The Celo stack is structured into the following logical layers:

Celo protocol
The Celo Blockchain and Celo Core Contracts together comprise the Celo Protocol

  • Celo Blockchain: An open cryptographic protocol that allows applications to make transactions with and run smart contracts in a secure and decentralized fashion. The Celo Blockchain has shared ancestry with Ethereum, and maintains full EVM compatibility for smart contracts. However it uses a Byzantine Fault Tolerant (BFT) consensus mechanism rather than Proof of Work, and has different block format, transaction format, client synchronization protocols, and gas payment and pricing mechanisms. The network’s native asset is Celo Gold, exposed via an ERC-20 interface.

  • Celo Core Contracts: A set of smart contracts running on the Celo Blockchain that comprise much of the logic of the platform features including ERC-20 stable currencies, identity attestations, Proof of Stake and governance. These smart contracts are upgradeable and managed by the decentralized governance process.

Celo network
Topology of a Celo Network

  • Applications: Applications for end users built on the Celo platform. The Celo Wallet app, the first of an ecosystem of applications, allows end users to manage accounts and make payments securely and simply by taking advantage of the innovations in the Celo protocol. Applications take the form of external mobile or backend software: they interact with the Celo Blockchain to issue transactions and invoke code that forms the Celo Core Contracts’ API. Third parties can also deploy custom smart contracts that their own applications can invoke, which in turn can leverage Celo Core Contracts. Applications may use centralized cloud services to provide some of their functionality: in the case of the Celo Wallet, push notifications and a transaction activity feed.

📚 Documentation

Follow the instructions in SETUP.md to get a development environment set up.

See Developer's Guide for full details about the design of the Celo protocol and other information about running these projects.

🙋 Issues

See the issue backlog for a list of active or proposed tasks. Feel free to create new issues to report bugs and/or request features.

📂 Repo Structure

The repository has the following packages (sub projects):

  • attestation-service - service run by validators on the Celo network to send SMS messages, enabling attestations of user phone numbers and their accounts on the Celo network
  • blockchain-api - service that uses Blockscout to present view of transactions by account for Celo Wallet activity feed
  • celotool - scripts for deploying and managing testnets
  • cli - tool that uses ContractKit to interact with the Celo protocol (docs)
  • contractkit - library to help developers and validators interact with the protocol and it's smart contracts (docs)
  • dappkit - set of functions for mobile DApps to work with the wallet app (ex. sign transactions and access the user's account) (docs)
  • dev-utils - a utils package for use as a dev dependency
  • docs - technical documentation for the Celo project (live)
  • faucet - faucet deployment configuration (live)
  • helm-charts - templatized deployments of entire environments to Kubernetes clusters
  • mobile - Android wallet app for the Celo platform (docs, live)
  • notification-service - service for managing push notifications for Celo Wallet
  • protocol - identity, stability and other smart contracts for the Celo protocol (docs)
  • react-components - generalized react native components
  • reserve-site - website for (Celo Reserve.org)
  • terraform-modules - templatized deployments of entire VM-based testnets for Google Cloud Platform
  • typescript - no README available (improve?)
  • utils - no README available (improve?)

Code owners for each package can be found in .github/CODEOWNERS.

✍️ Contributing

Feel free to jump on the Celo 🚂🚋🚋🚋. Improvements and contributions are highly encouraged! 🙏👊

See the contributing guide for details on how to participate. GitHub issues by-label

All communication and contributions to the Celo project are subject to the Celo Code of Conduct.

Not yet ready to contribute but do like the project? Support Celo with a or share the love in a Twitter URL

💬 Ask Questions, Find Answers, Get in Touch

📜 License

All packages are licensed under the terms of the Apache 2.0 License unless otherwise specified in the LICENSE file at package's root.