Skip to content

Commit 9bc1570

Browse files
committed
Merge pull request 'develop' (#7) from develop into master
Reviewed-on: https://git.blaize.tech/Celo/celo-sdk-python/pulls/7
2 parents c4fe79f + df19e63 commit 9bc1570

File tree

83 files changed

+1859
-382
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

83 files changed

+1859
-382
lines changed

LICENSE

Lines changed: 201 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,201 @@
1+
Apache License
2+
Version 2.0, January 2004
3+
http://www.apache.org/licenses/
4+
5+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6+
7+
1. Definitions.
8+
9+
"License" shall mean the terms and conditions for use, reproduction,
10+
and distribution as defined by Sections 1 through 9 of this document.
11+
12+
"Licensor" shall mean the copyright owner or entity authorized by
13+
the copyright owner that is granting the License.
14+
15+
"Legal Entity" shall mean the union of the acting entity and all
16+
other entities that control, are controlled by, or are under common
17+
control with that entity. For the purposes of this definition,
18+
"control" means (i) the power, direct or indirect, to cause the
19+
direction or management of such entity, whether by contract or
20+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
21+
outstanding shares, or (iii) beneficial ownership of such entity.
22+
23+
"You" (or "Your") shall mean an individual or Legal Entity
24+
exercising permissions granted by this License.
25+
26+
"Source" form shall mean the preferred form for making modifications,
27+
including but not limited to software source code, documentation
28+
source, and configuration files.
29+
30+
"Object" form shall mean any form resulting from mechanical
31+
transformation or translation of a Source form, including but
32+
not limited to compiled object code, generated documentation,
33+
and conversions to other media types.
34+
35+
"Work" shall mean the work of authorship, whether in Source or
36+
Object form, made available under the License, as indicated by a
37+
copyright notice that is included in or attached to the work
38+
(an example is provided in the Appendix below).
39+
40+
"Derivative Works" shall mean any work, whether in Source or Object
41+
form, that is based on (or derived from) the Work and for which the
42+
editorial revisions, annotations, elaborations, or other modifications
43+
represent, as a whole, an original work of authorship. For the purposes
44+
of this License, Derivative Works shall not include works that remain
45+
separable from, or merely link (or bind by name) to the interfaces of,
46+
the Work and Derivative Works thereof.
47+
48+
"Contribution" shall mean any work of authorship, including
49+
the original version of the Work and any modifications or additions
50+
to that Work or Derivative Works thereof, that is intentionally
51+
submitted to Licensor for inclusion in the Work by the copyright owner
52+
or by an individual or Legal Entity authorized to submit on behalf of
53+
the copyright owner. For the purposes of this definition, "submitted"
54+
means any form of electronic, verbal, or written communication sent
55+
to the Licensor or its representatives, including but not limited to
56+
communication on electronic mailing lists, source code control systems,
57+
and issue tracking systems that are managed by, or on behalf of, the
58+
Licensor for the purpose of discussing and improving the Work, but
59+
excluding communication that is conspicuously marked or otherwise
60+
designated in writing by the copyright owner as "Not a Contribution."
61+
62+
"Contributor" shall mean Licensor and any individual or Legal Entity
63+
on behalf of whom a Contribution has been received by Licensor and
64+
subsequently incorporated within the Work.
65+
66+
2. Grant of Copyright License. Subject to the terms and conditions of
67+
this License, each Contributor hereby grants to You a perpetual,
68+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69+
copyright license to reproduce, prepare Derivative Works of,
70+
publicly display, publicly perform, sublicense, and distribute the
71+
Work and such Derivative Works in Source or Object form.
72+
73+
3. Grant of Patent License. Subject to the terms and conditions of
74+
this License, each Contributor hereby grants to You a perpetual,
75+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76+
(except as stated in this section) patent license to make, have made,
77+
use, offer to sell, sell, import, and otherwise transfer the Work,
78+
where such license applies only to those patent claims licensable
79+
by such Contributor that are necessarily infringed by their
80+
Contribution(s) alone or by combination of their Contribution(s)
81+
with the Work to which such Contribution(s) was submitted. If You
82+
institute patent litigation against any entity (including a
83+
cross-claim or counterclaim in a lawsuit) alleging that the Work
84+
or a Contribution incorporated within the Work constitutes direct
85+
or contributory patent infringement, then any patent licenses
86+
granted to You under this License for that Work shall terminate
87+
as of the date such litigation is filed.
88+
89+
4. Redistribution. You may reproduce and distribute copies of the
90+
Work or Derivative Works thereof in any medium, with or without
91+
modifications, and in Source or Object form, provided that You
92+
meet the following conditions:
93+
94+
(a) You must give any other recipients of the Work or
95+
Derivative Works a copy of this License; and
96+
97+
(b) You must cause any modified files to carry prominent notices
98+
stating that You changed the files; and
99+
100+
(c) You must retain, in the Source form of any Derivative Works
101+
that You distribute, all copyright, patent, trademark, and
102+
attribution notices from the Source form of the Work,
103+
excluding those notices that do not pertain to any part of
104+
the Derivative Works; and
105+
106+
(d) If the Work includes a "NOTICE" text file as part of its
107+
distribution, then any Derivative Works that You distribute must
108+
include a readable copy of the attribution notices contained
109+
within such NOTICE file, excluding those notices that do not
110+
pertain to any part of the Derivative Works, in at least one
111+
of the following places: within a NOTICE text file distributed
112+
as part of the Derivative Works; within the Source form or
113+
documentation, if provided along with the Derivative Works; or,
114+
within a display generated by the Derivative Works, if and
115+
wherever such third-party notices normally appear. The contents
116+
of the NOTICE file are for informational purposes only and
117+
do not modify the License. You may add Your own attribution
118+
notices within Derivative Works that You distribute, alongside
119+
or as an addendum to the NOTICE text from the Work, provided
120+
that such additional attribution notices cannot be construed
121+
as modifying the License.
122+
123+
You may add Your own copyright statement to Your modifications and
124+
may provide additional or different license terms and conditions
125+
for use, reproduction, or distribution of Your modifications, or
126+
for any such Derivative Works as a whole, provided Your use,
127+
reproduction, and distribution of the Work otherwise complies with
128+
the conditions stated in this License.
129+
130+
5. Submission of Contributions. Unless You explicitly state otherwise,
131+
any Contribution intentionally submitted for inclusion in the Work
132+
by You to the Licensor shall be under the terms and conditions of
133+
this License, without any additional terms or conditions.
134+
Notwithstanding the above, nothing herein shall supersede or modify
135+
the terms of any separate license agreement you may have executed
136+
with Licensor regarding such Contributions.
137+
138+
6. Trademarks. This License does not grant permission to use the trade
139+
names, trademarks, service marks, or product names of the Licensor,
140+
except as required for reasonable and customary use in describing the
141+
origin of the Work and reproducing the content of the NOTICE file.
142+
143+
7. Disclaimer of Warranty. Unless required by applicable law or
144+
agreed to in writing, Licensor provides the Work (and each
145+
Contributor provides its Contributions) on an "AS IS" BASIS,
146+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147+
implied, including, without limitation, any warranties or conditions
148+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149+
PARTICULAR PURPOSE. You are solely responsible for determining the
150+
appropriateness of using or redistributing the Work and assume any
151+
risks associated with Your exercise of permissions under this License.
152+
153+
8. Limitation of Liability. In no event and under no legal theory,
154+
whether in tort (including negligence), contract, or otherwise,
155+
unless required by applicable law (such as deliberate and grossly
156+
negligent acts) or agreed to in writing, shall any Contributor be
157+
liable to You for damages, including any direct, indirect, special,
158+
incidental, or consequential damages of any character arising as a
159+
result of this License or out of the use or inability to use the
160+
Work (including but not limited to damages for loss of goodwill,
161+
work stoppage, computer failure or malfunction, or any and all
162+
other commercial damages or losses), even if such Contributor
163+
has been advised of the possibility of such damages.
164+
165+
9. Accepting Warranty or Additional Liability. While redistributing
166+
the Work or Derivative Works thereof, You may choose to offer,
167+
and charge a fee for, acceptance of support, warranty, indemnity,
168+
or other liability obligations and/or rights consistent with this
169+
License. However, in accepting such obligations, You may act only
170+
on Your own behalf and on Your sole responsibility, not on behalf
171+
of any other Contributor, and only if You agree to indemnify,
172+
defend, and hold each Contributor harmless for any liability
173+
incurred by, or claims asserted against, such Contributor by reason
174+
of your accepting any such warranty or additional liability.
175+
176+
END OF TERMS AND CONDITIONS
177+
178+
APPENDIX: How to apply the Apache License to your work.
179+
180+
To apply the Apache License to your work, attach the following
181+
boilerplate notice, with the fields enclosed by brackets "[]"
182+
replaced with your own identifying information. (Don't include
183+
the brackets!) The text should be enclosed in the appropriate
184+
comment syntax for the file format. We also recommend that a
185+
file or class name and description of purpose be included on the
186+
same "printed page" as the copyright notice for easier
187+
identification within third-party archives.
188+
189+
Copyright 2020 BlaizeTech
190+
191+
Licensed under the Apache License, Version 2.0 (the "License");
192+
you may not use this file except in compliance with the License.
193+
You may obtain a copy of the License at
194+
195+
http://www.apache.org/licenses/LICENSE-2.0
196+
197+
Unless required by applicable law or agreed to in writing, software
198+
distributed under the License is distributed on an "AS IS" BASIS,
199+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200+
See the License for the specific language governing permissions and
201+
limitations under the License.

Readme.md

Lines changed: 173 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,173 @@
1+
# Python ContractKit
2+
3+
Celo's ContractKit is a library to help developers and validators to interact with the celo-blockchain.
4+
5+
ContractKit supports the following functionality:
6+
7+
- Connect to a node
8+
- Access web3 object to interact with node's Json RPC API
9+
- Send Transaction with celo's extra fields: (feeCurrency)
10+
- Simple interface to interact with CELO and cUSD
11+
- Simple interface to interact with Celo Core contracts
12+
- Utilities
13+
14+
## User Guide
15+
16+
### Getting Started
17+
18+
To install:
19+
20+
```bash
21+
pip install .
22+
```
23+
24+
You need in Python version 3.8 or higher.
25+
26+
To start working with python contractkit you need a `Kit` instance:
27+
28+
```python
29+
from celo_sdk.kit import Kit
30+
31+
kit = Kit('https://alfajores-forno.celo-testnet.org')
32+
```
33+
34+
To access web3:
35+
36+
```python
37+
kit.w3.eth.getBalance(some_address)
38+
```
39+
40+
### Setting Default Tx Options
41+
42+
`Kit` allows you to set default transaction options:
43+
44+
```python
45+
from celo_sdk.kit import Kit
46+
47+
kit = Kit('https://alfajores-forno.celo-testnet.org')
48+
currency_address = kit.base_wrapper.registry.load_contract_by_name('StableToken')['address']
49+
kit.wallet_fee_currency = currency_address
50+
```
51+
52+
### Interacting with CELO & cUSD
53+
54+
celo-blockchain has two initial coins: CELO and cUSD (stableToken).
55+
Both implement the ERC20 standard, and to interact with them is as simple as:
56+
57+
```python
58+
gold_token = kit.base_wrapper.create_and_get_contract_by_name('GoldToken')
59+
balance = gold_token.balance_of(address)
60+
```
61+
62+
To send funds:
63+
64+
```python
65+
one_gold = kit.w3.toWei(1, 'ether')
66+
tx_hash = gold_token.transfer(address, one_gold)
67+
```
68+
69+
To interact with cUSD, is the same but with a different contract:
70+
71+
```python
72+
stable_token = kit.base_wrapper.create_and_get_contract_by_name('StableToken')
73+
```
74+
75+
If you would like to pay fees in cUSD, set the gas price manually:
76+
77+
```python
78+
stable_token = kit.base_wrapper.create_and_get_contract_by_name('StableToken')
79+
gas_price_contract = kit.base_wrapper.create_and_get_contract_by_name('GasPriceMinimum')
80+
gas_price_minimum = gas_price_contract.get_gas_price_minimum(stable.address)
81+
gas_price = gas_price_minimum * 1.3 # Wiggle room if gas price minimum changes before tx is sent
82+
kit.wallet_fee_currency = stable_token.address # Default to paying fees in cUSD
83+
kit.wallet_gas_price = gas_price
84+
85+
tx = stable_token.transfer(recipient, wei_transfer_amount)
86+
```
87+
88+
### Interacting with Other Contracts
89+
90+
Apart from GoldToken and StableToken, there are many core contracts.
91+
92+
For the moment, we have contract wrappers for:
93+
94+
- Accounts
95+
- Attestations
96+
- BlockchainParameters
97+
- DoubleSigningSlasher
98+
- DowntimeSlasher
99+
- Election
100+
- LockedGold
101+
- Escrow
102+
- Exchange
103+
- Freezer
104+
- GasPriceMinimum
105+
- GoldToken
106+
- Governance
107+
- MultiSig
108+
- Reserve
109+
- ReleaseGold
110+
- SortedOracles
111+
- StableToken
112+
- Validators
113+
114+
To create object of contract wrapper you shold set one of those contract names as a parameter to function `BaseWrapper.create_and_get_contract_by_name(...)`
115+
116+
## A Note About Contract Addresses
117+
118+
Celo Core Contracts addresses, can be obtained by looking at the `Registry` contract.
119+
That's actually how `BaseWrapper` obtain them.
120+
121+
We expose the registry api, which can be accessed by:
122+
123+
```python
124+
gold_token_address = kit.base_wrapper.registry.load_contract_by_name('GoldToken')['address']
125+
```
126+
127+
## Adding new keys to the wallet
128+
129+
Wallet object by defaut generate some private key
130+
131+
But of course you can add your own already generated private key or generate new one
132+
133+
To add your own:
134+
135+
```python
136+
from celo_sdk.kit import Kit
137+
138+
kit = Kit('https://alfajores-forno.celo-testnet.org')
139+
kit.wallet_add_new_key = '0xf2f48ee19680706196e2e339e5da3491186e0c4c5030670656b0e0164837257d'
140+
```
141+
142+
To generate new one:
143+
144+
```python
145+
new_key = kit.generate_new_key()
146+
kit.wallet_add_new_key = new_key
147+
```
148+
149+
To see all the wallet accounts:
150+
151+
```python
152+
accounts = kit.wallet.accounts
153+
```
154+
155+
And to switch between accounts:
156+
157+
```python
158+
kit.wallet_change_account = existing_account_address # address of account has to be in wallet.__accounts dict
159+
```
160+
161+
## Signing messages with wallet
162+
163+
In addition to signing the transaction, the wallet can sign messages:
164+
165+
```python
166+
from celo_sdk.kit import Kit
167+
from celo_sdk.celo_account.messages import encode_defunct
168+
169+
kit = Kit('https://alfajores-forno.celo-testnet.org')
170+
message = self.kit.w3.soliditySha3(['address'], [signer]).hex() # For example we want to sign someones address
171+
message = encode_defunct(hexstr=message)
172+
signature = self.kit.wallet.active_account.sign_message(message)
173+
```
Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
1-
from sdk import (
1+
from celo_sdk import (
22
registry,
33
wallet,
44
tests,
5+
kit,
56
)

celo_sdk/celo_account/__init__.py

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
from celo_sdk.celo_account.account import ( # noqa: F401
2+
Account,
3+
)
File renamed without changes.

sdk/celo_account/_utils/signing.py renamed to celo_sdk/celo_account/_utils/signing.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
to_int,
77
)
88

9-
from sdk.celo_account._utils.transactions import (
9+
from celo_sdk.celo_account._utils.transactions import (
1010
ChainAwareUnsignedTransaction,
1111
UnsignedTransaction,
1212
encode_transaction,

0 commit comments

Comments
 (0)