battlechain-lib-py 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,27 @@
1
+ name: pypi-release
2
+
3
+ on:
4
+ release:
5
+ types: [released]
6
+ workflow_dispatch:
7
+
8
+ jobs:
9
+ build-and-publish:
10
+ runs-on: ubuntu-latest
11
+ environment: production
12
+ permissions:
13
+ id-token: write
14
+ steps:
15
+ - uses: actions/checkout@v4
16
+ - name: Set up Python
17
+ uses: actions/setup-python@v5
18
+ with:
19
+ python-version-file: "pyproject.toml"
20
+ - name: Install uv
21
+ uses: astral-sh/setup-uv@v6
22
+ - name: Install dependencies
23
+ run: uv sync
24
+ - name: Build package
25
+ run: uv build
26
+ - name: Publish package
27
+ uses: pypa/gh-action-pypi-publish@release/v1
@@ -0,0 +1,42 @@
1
+ name: PR Checks
2
+
3
+ on:
4
+ pull_request:
5
+ branches: [ main ]
6
+
7
+ jobs:
8
+ typecheck:
9
+ name: Run Typecheck
10
+ runs-on: ubuntu-latest
11
+ steps:
12
+ - uses: actions/checkout@v4
13
+ - name: Set up Python
14
+ uses: actions/setup-python@v5
15
+ with:
16
+ python-version-file: "pyproject.toml"
17
+ - name: Install uv
18
+ uses: astral-sh/setup-uv@v6
19
+ - name: Install dependencies
20
+ run: uv sync --dev
21
+ - name: Setup just
22
+ uses: extractions/setup-just@v3
23
+ - name: Run typecheck
24
+ run: just typecheck
25
+
26
+ format:
27
+ name: Run Format Check
28
+ runs-on: ubuntu-latest
29
+ steps:
30
+ - uses: actions/checkout@v4
31
+ - name: Set up Python
32
+ uses: actions/setup-python@v5
33
+ with:
34
+ python-version-file: "pyproject.toml"
35
+ - name: Install uv
36
+ uses: astral-sh/setup-uv@v6
37
+ - name: Install dependencies
38
+ run: uv sync --dev
39
+ - name: Setup just
40
+ uses: extractions/setup-just@v3
41
+ - name: Run format
42
+ run: just format-check
@@ -0,0 +1,46 @@
1
+ # Byte-compiled / cached
2
+ __pycache__/
3
+ *.py[cod]
4
+ *$py.class
5
+
6
+ # Build / distribution
7
+ build/
8
+ dist/
9
+ *.egg-info/
10
+ *.egg
11
+
12
+ # Virtual environments
13
+ .venv/
14
+ venv/
15
+ env/
16
+
17
+ # Tooling caches
18
+ .pytest_cache/
19
+ .ruff_cache/
20
+ .mypy_cache/
21
+ .ty_cache/
22
+ .tox/
23
+ .nox/
24
+ .coverage
25
+ .coverage.*
26
+ coverage.xml
27
+ htmlcov/
28
+
29
+ # Editors / IDEs
30
+ .vscode/
31
+ .idea/
32
+ *.swp
33
+ *.swo
34
+
35
+ # OS
36
+ .DS_Store
37
+ Thumbs.db
38
+
39
+ # Secrets — never commit these
40
+ .env
41
+ .env.*
42
+ !.env.example
43
+
44
+ # Boa / Moccasin artifacts (in case contributors run boa scripts here)
45
+ .moccasin/
46
+ out/
@@ -0,0 +1 @@
1
+ 3.13
@@ -0,0 +1,180 @@
1
+ # Contributing to battlechain-lib-py
2
+
3
+ Thanks for helping out. This doc covers the dev environment, the codegen flow
4
+ that keeps us in sync with the Solidity lib, and the test/lint workflow.
5
+
6
+ - [Prerequisites](#prerequisites)
7
+ - [Dev environment](#dev-environment)
8
+ - [Project layout](#project-layout)
9
+ - [Common tasks](#common-tasks)
10
+ - [Run tests](#run-tests)
11
+ - [Lint and format](#lint-and-format)
12
+ - [Type-check](#type-check)
13
+ - [Regenerate the ABI module](#regenerate-the-abi-module)
14
+ - [Keeping in sync with battlechain-lib (Solidity)](#keeping-in-sync-with-battlechain-lib-solidity)
15
+ - [Conventions](#conventions)
16
+ - [Filing issues / PRs](#filing-issues--prs)
17
+
18
+ ## Prerequisites
19
+
20
+ | Tool | Why |
21
+ | ----------------------------------------------- | -------------------------------------------------- |
22
+ | [`uv`](https://docs.astral.sh/uv/) | Python toolchain (env, deps, runner) |
23
+ | [`just`](https://github.com/casey/just) | Task runner — the `justfile` wraps common commands |
24
+ | [Foundry](https://book.getfoundry.sh/) | Required to regenerate `abi.py` from forge artifacts |
25
+
26
+ Python ≥ 3.11 is required (the project pins 3.13 via `.python-version`).
27
+
28
+ ## Dev environment
29
+
30
+ ```bash
31
+ # Clone alongside battlechain-lib (the codegen looks for ../battlechain-lib by default)
32
+ git clone https://github.com/Cyfrin/battlechain-lib-py
33
+ cd battlechain-lib-py
34
+
35
+ # Install deps + the package in editable mode
36
+ uv sync
37
+ ```
38
+
39
+ That's it — `uv sync` resolves dependencies from `uv.lock`, creates `.venv/`,
40
+ and installs the package in editable mode so your changes are picked up
41
+ immediately.
42
+
43
+ Use `uv run <cmd>` to run anything in the project env (`uv run pytest`,
44
+ `uv run python -c "..."`).
45
+
46
+ ## Project layout
47
+
48
+ ```
49
+ battlechain/ ← the library
50
+ __init__.py public API re-exports
51
+ _boa.py internal: boa contract loaders
52
+ abi.py AUTO-GENERATED — see codegen flow below
53
+ builders.py agreement builders (mirrors BCSafeHarbor builders)
54
+ config.py chain IDs, addresses, overrides (mirrors BCConfig.sol)
55
+ createx_chains.py CreateX-supported chain registry
56
+ deploy.py bcDeployCreate/2/3 + tracked deployments (BCDeploy.sol)
57
+ errors.py typed exceptions mirroring Solidity custom errors
58
+ query.py isAttackable + on-chain primitives (BCQuery.sol)
59
+ safe_harbor.py create/adopt/attack-mode helpers (BCSafeHarbor.sol)
60
+ types.py agreement dataclasses + AgreementState enum
61
+ verify.py block-explorer source verification
62
+
63
+ tests/ pytest test suite (no RPC required)
64
+ tools/
65
+ gen_abi.py regenerates battlechain/abi.py from forge artifacts
66
+ justfile common commands wrapped for `just`
67
+ pyproject.toml project metadata + tool config (ruff, hatchling)
68
+ ```
69
+
70
+ ## Common tasks
71
+
72
+ The `justfile` wraps the everyday flow. Run `just` with no args to list targets.
73
+
74
+ ### Run tests
75
+
76
+ ```bash
77
+ just test
78
+ # or:
79
+ uv run pytest -v
80
+ ```
81
+
82
+ The smoke tests don't require an RPC or boa environment — they stub the
83
+ explorer and verify pure-Python correctness (constants, dataclass shapes,
84
+ builders, `is_attackable` against the BCQuery test fixtures).
85
+
86
+ ### Lint and format
87
+
88
+ ```bash
89
+ just format # ruff: organize imports + auto-fix
90
+ just format-check # ruff: report only, no writes
91
+ ```
92
+
93
+ Lint rules are configured in `pyproject.toml` under `[tool.ruff]`. Line length
94
+ is 100; selected rule sets are `E`, `F`, `I`, `UP`, `B`, `SIM`.
95
+
96
+ ### Type-check
97
+
98
+ ```bash
99
+ just ty
100
+ # or:
101
+ uvx ty check
102
+ ```
103
+
104
+ We use [`ty`](https://github.com/astral-sh/ty), Astral's static type checker.
105
+
106
+ ### Regenerate the ABI module
107
+
108
+ `battlechain/abi.py` is auto-generated from forge build artifacts in the
109
+ sibling `battlechain-lib` Solidity repo. Whenever the Solidity interfaces
110
+ change, regenerate:
111
+
112
+ ```bash
113
+ # Defaults to ../battlechain-lib
114
+ uv run python tools/gen_abi.py
115
+
116
+ # Or point at a specific working copy
117
+ uv run python tools/gen_abi.py /path/to/battlechain-lib
118
+
119
+ # Skip `forge build` if you've already built (faster iteration)
120
+ uv run python tools/gen_abi.py --no-build
121
+ ```
122
+
123
+ The script:
124
+ 1. Runs `forge build` inside the Solidity repo (unless `--no-build`).
125
+ 2. Reads `out/<Iface>.sol/<Iface>.json` for each interface (`IAgreementFactory`,
126
+ `IAgreement`, `IAttackRegistry`, `IBCSafeHarborRegistry`, `IBCDeployer`).
127
+ 3. Extracts the `.abi` field from each artifact.
128
+ 4. Renders `battlechain/abi.py` with the standard ABI list-of-dicts shape that
129
+ boa and web3.py both accept.
130
+
131
+ Commit the regenerated `abi.py` alongside any code changes that motivated it.
132
+
133
+ ## Keeping in sync with battlechain-lib (Solidity)
134
+
135
+ This library mirrors the public surface of
136
+ [`cyfrin/battlechain-lib`](https://github.com/Cyfrin/battlechain-lib). When the
137
+ Solidity lib changes, here's what to update:
138
+
139
+ | Solidity change | Python update |
140
+ | ---------------------------- | --------------------------------------------------------------------- |
141
+ | `BCConfig.sol` addresses | `battlechain/config.py` constants + `bc_testnet` |
142
+ | `AgreementTypes.sol` | `battlechain/types.py` dataclasses/enums |
143
+ | Interface methods | Run `tools/gen_abi.py` to refresh `battlechain/abi.py` |
144
+ | `BCSafeHarbor.sol` builders | `battlechain/builders.py` + corresponding `safe_harbor.py` actions |
145
+ | `BCDeploy.sol` helpers | `battlechain/deploy.py` |
146
+ | `BCQuery.sol` predicates | `battlechain/query.py` (Python uses HTTP directly instead of FFI) |
147
+ | `CreateXChains.sol` chain list | `battlechain/createx_chains.py` `PRODUCTION_CHAIN_IDS` / `TEST_CHAIN_IDS` |
148
+ | New custom errors | `battlechain/errors.py` |
149
+
150
+ Add a test in `tests/test_smoke.py` that pins the new behavior to a value from
151
+ the Solidity source — that's the cheapest way to catch silent drift.
152
+
153
+ ## Conventions
154
+
155
+ - **Boa-first.** Action helpers (`deploy.py`, `safe_harbor.py`, `query.py`)
156
+ use boa for contract calls. They go through the `_boa` module, which
157
+ centralizes ABI loading. If you need a non-boa client, import `abi` and
158
+ `config` directly and load contracts yourself.
159
+ - **Address case matches Solidity.** When serializing addresses into agreement
160
+ details, we use lowercase 0x-hex (matching `vm.toString(address)` from
161
+ forge-std), not EIP-55 checksum. Don't use `to_checksum_address` in the
162
+ builders — it produces different bytes than the Solidity lib.
163
+ - **Frozen dataclasses for value types.** `AgreementDetails`, `BountyTerms`,
164
+ `BcChain`, etc. are immutable. Each exposes a `to_tuple()` method that
165
+ produces the positional shape boa's `loads_abi` expects.
166
+ - **No premature abstractions.** If a function is used only by the Solidity
167
+ lib in one place, it's used in one place here too. Mirror first, refactor
168
+ later.
169
+ - **Auto-generated files have a header.** Anything generated by `tools/`
170
+ must start with a comment pointing to the generator, so a future contributor
171
+ doesn't hand-edit it.
172
+
173
+ ## Filing issues / PRs
174
+
175
+ - Open issues at <https://github.com/Cyfrin/battlechain-lib-py/issues>.
176
+ - For PRs, please include:
177
+ - A test that fails before your change (when adding a feature or fix).
178
+ - `just format-check` and `just test` passing locally.
179
+ - If you regenerated `abi.py`, mention the `battlechain-lib` commit you
180
+ pulled from.
@@ -0,0 +1,200 @@
1
+ Version 2.0, January 2004
2
+ http://www.apache.org/licenses/
3
+
4
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
5
+
6
+ 1. Definitions.
7
+
8
+ "License" shall mean the terms and conditions for use, reproduction,
9
+ and distribution as defined by Sections 1 through 9 of this document.
10
+
11
+ "Licensor" shall mean the copyright owner or entity authorized by
12
+ the copyright owner that is granting the License.
13
+
14
+ "Legal Entity" shall mean the union of the acting entity and all
15
+ other entities that control, are controlled by, or are under common
16
+ control with that entity. For the purposes of this definition,
17
+ "control" means (i) the power, direct or indirect, to cause the
18
+ direction or management of such entity, whether by contract or
19
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
20
+ outstanding shares, or (iii) beneficial ownership of such entity.
21
+
22
+ "You" (or "Your") shall mean an individual or Legal Entity
23
+ exercising permissions granted by this License.
24
+
25
+ "Source" form shall mean the preferred form for making modifications,
26
+ including but not limited to software source code, documentation
27
+ source, and configuration files.
28
+
29
+ "Object" form shall mean any form resulting from mechanical
30
+ transformation or translation of a Source form, including but
31
+ not limited to compiled object code, generated documentation,
32
+ and conversions to other media types.
33
+
34
+ "Work" shall mean the work of authorship, whether in Source or
35
+ Object form, made available under the License, as indicated by a
36
+ copyright notice that is included in or attached to the work
37
+ (an example is provided in the Appendix below).
38
+
39
+ "Derivative Works" shall mean any work, whether in Source or Object
40
+ form, that is based on (or derived from) the Work and for which the
41
+ editorial revisions, annotations, elaborations, or other modifications
42
+ represent, as a whole, an original work of authorship. For the purposes
43
+ of this License, Derivative Works shall not include works that remain
44
+ separable from, or merely link (or bind by name) to the interfaces of,
45
+ the Work and Derivative Works thereof.
46
+
47
+ "Contribution" shall mean any work of authorship, including
48
+ the original version of the Work and any modifications or additions
49
+ to that Work or Derivative Works thereof, that is intentionally
50
+ submitted to Licensor for inclusion in the Work by the copyright owner
51
+ or by an individual or Legal Entity authorized to submit on behalf of
52
+ the copyright owner. For the purposes of this definition, "submitted"
53
+ means any form of electronic, verbal, or written communication sent
54
+ to the Licensor or its representatives, including but not limited to
55
+ communication on electronic mailing lists, source code control systems,
56
+ and issue tracking systems that are managed by, or on behalf of, the
57
+ Licensor for the purpose of discussing and improving the Work, but
58
+ excluding communication that is conspicuously marked or otherwise
59
+ designated in writing by the copyright owner as "Not a Contribution."
60
+
61
+ "Contributor" shall mean Licensor and any individual or Legal Entity
62
+ on behalf of whom a Contribution has been received by Licensor and
63
+ subsequently incorporated within the Work.
64
+
65
+ 2. Grant of Copyright License. Subject to the terms and conditions of
66
+ this License, each Contributor hereby grants to You a perpetual,
67
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
68
+ copyright license to reproduce, prepare Derivative Works of,
69
+ publicly display, publicly perform, sublicense, and distribute the
70
+ Work and such Derivative Works in Source or Object form.
71
+
72
+ 3. Grant of Patent License. Subject to the terms and conditions of
73
+ this License, each Contributor hereby grants to You a perpetual,
74
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
75
+ (except as stated in this section) patent license to make, have made,
76
+ use, offer to sell, sell, import, and otherwise transfer the Work,
77
+ where such license applies only to those patent claims licensable
78
+ by such Contributor that are necessarily infringed by their
79
+ Contribution(s) alone or by combination of their Contribution(s)
80
+ with the Work to which such Contribution(s) was submitted. If You
81
+ institute patent litigation against any entity (including a
82
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
83
+ or a Contribution incorporated within the Work constitutes direct
84
+ or contributory patent infringement, then any patent licenses
85
+ granted to You under this License for that Work shall terminate
86
+ as of the date such litigation is filed.
87
+
88
+ 4. Redistribution. You may reproduce and distribute copies of the
89
+ Work or Derivative Works thereof in any medium, with or without
90
+ modifications, and in Source or Object form, provided that You
91
+ meet the following conditions:
92
+
93
+ (a) You must give any other recipients of the Work or
94
+ Derivative Works a copy of this License; and
95
+
96
+ (b) You must cause any modified files to carry prominent notices
97
+ stating that You changed the files; and
98
+
99
+ (c) You must retain, in the Source form of any Derivative Works
100
+ that You distribute, all copyright, patent, trademark, and
101
+ attribution notices from the Source form of the Work,
102
+ excluding those notices that do not pertain to any part of
103
+ the Derivative Works; and
104
+
105
+ (d) If the Work includes a "NOTICE" text file as part of its
106
+ distribution, then any Derivative Works that You distribute must
107
+ include a readable copy of the attribution notices contained
108
+ within such NOTICE file, excluding those notices that do not
109
+ pertain to any part of the Derivative Works, in at least one
110
+ of the following places: within a NOTICE text file distributed
111
+ as part of the Derivative Works; within the Source form or
112
+ documentation, if provided along with the Derivative Works; or,
113
+ within a display generated by the Derivative Works, if and
114
+ wherever such third-party notices normally appear. The contents
115
+ of the NOTICE file are for informational purposes only and
116
+ do not modify the License. You may add Your own attribution
117
+ notices within Derivative Works that You distribute, alongside
118
+ or as an addendum to the NOTICE text from the Work, provided
119
+ that such additional attribution notices cannot be construed
120
+ as modifying the License.
121
+
122
+ You may add Your own copyright statement to Your modifications and
123
+ may provide additional or different license terms and conditions
124
+ for use, reproduction, or distribution of Your modifications, or
125
+ for any such Derivative Works as a whole, provided Your use,
126
+ reproduction, and distribution of the Work otherwise complies with
127
+ the conditions stated in this License.
128
+
129
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
130
+ any Contribution intentionally submitted for inclusion in the Work
131
+ by You to the Licensor shall be under the terms and conditions of
132
+ this License, without any additional terms or conditions.
133
+ Notwithstanding the above, nothing herein shall supersede or modify
134
+ the terms of any separate license agreement you may have executed
135
+ with Licensor regarding such Contributions.
136
+
137
+ 6. Trademarks. This License does not grant permission to use the trade
138
+ names, trademarks, service marks, or product names of the Licensor,
139
+ except as required for reasonable and customary use in describing the
140
+ origin of the Work and reproducing the content of the NOTICE file.
141
+
142
+ 7. Disclaimer of Warranty. Unless required by applicable law or
143
+ agreed to in writing, Licensor provides the Work (and each
144
+ Contributor provides its Contributions) on an "AS IS" BASIS,
145
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
146
+ implied, including, without limitation, any warranties or conditions
147
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
148
+ PARTICULAR PURPOSE. You are solely responsible for determining the
149
+ appropriateness of using or redistributing the Work and assume any
150
+ risks associated with Your exercise of permissions under this License.
151
+
152
+ 8. Limitation of Liability. In no event and under no legal theory,
153
+ whether in tort (including negligence), contract, or otherwise,
154
+ unless required by applicable law (such as deliberate and grossly
155
+ negligent acts) or agreed to in writing, shall any Contributor be
156
+ liable to You for damages, including any direct, indirect, special,
157
+ incidental, or consequential damages of any character arising as a
158
+ result of this License or out of the use or inability to use the
159
+ Work (including but not limited to damages for loss of goodwill,
160
+ work stoppage, computer failure or malfunction, or any and all
161
+ other commercial damages or losses), even if such Contributor
162
+ has been advised of the possibility of such damages.
163
+
164
+ 9. Accepting Warranty or Additional Liability. While redistributing
165
+ the Work or Derivative Works thereof, You may choose to offer,
166
+ and charge a fee for, acceptance of support, warranty, indemnity,
167
+ or other liability obligations and/or rights consistent with this
168
+ License. However, in accepting such obligations, You may act only
169
+ on Your own behalf and on Your sole responsibility, not on behalf
170
+ of any other Contributor, and only if You agree to indemnify,
171
+ defend, and hold each Contributor harmless for any liability
172
+ incurred by, or claims asserted against, such Contributor by reason
173
+ of your accepting any such warranty or additional liability.
174
+
175
+ END OF TERMS AND CONDITIONS
176
+
177
+ APPENDIX: How to apply the Apache License to your work.
178
+
179
+ To apply the Apache License to your work, attach the following
180
+ boilerplate notice, with the fields enclosed by brackets "[]"
181
+ replaced with your own identifying information. (Don't include
182
+ the brackets!) The text should be enclosed in the appropriate
183
+ comment syntax for the file format. We also recommend that a
184
+ file or class name and description of purpose be included on the
185
+ same "printed page" as the copyright notice for easier
186
+ identification within third-party archives.
187
+
188
+ Copyright 2024 Cyfrin Inc
189
+
190
+ Licensed under the Apache License, Version 2.0 (the "License");
191
+ you may not use this file except in compliance with the License.
192
+ You may obtain a copy of the License at
193
+
194
+ http://www.apache.org/licenses/LICENSE-2.0
195
+
196
+ Unless required by applicable law or agreed to in writing, software
197
+ distributed under the License is distributed on an "AS IS" BASIS,
198
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
199
+ See the License for the specific language governing permissions and
200
+ limitations under the License.
@@ -0,0 +1,7 @@
1
+ Copyright 2024 Cyfrin Inc
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
4
+
5
+ The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
6
+
7
+ THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.