This release is a pre-release and may not be stable for production use.
C++ Candid Library
The C++ Candid Library of icpp-pro
- API Reference
- The C++ Candid Library is extensively tested in our QA Canister.
- If you want to contribute, please reach out.
How to use
C++ Smart Contracts
To write a C++ smart contract that runs in a Canister, you do not use icpp-candid directly, but you install icpp-pro, which is a full-blown C++ Canister Development Kit.
Simply install & Get Started !
C++ Rich Clients
If you want to use the C++ Candid Library in your Rich Client, you need to include it in your application and then compile it to a native executable.
We already do this ourselves as part of icpp-pro to enable interactive debugging with VS Code, as described here.
The command we use is:
icpp build-native
Which uses the Clang++ compiler to create a native debug executable named mockic.exe
Support
For support, kindly create a GitHub Issue as outlined in the Support documentation page.
1 maintainer
Metadata
1 maintainer
Release files for icpp-candid 7.0.0rc3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| icpp_candid-7.0.0rc3.tar.gz | 111.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| icpp_candid-7.0.0rc3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 355.0 kB
Release files / icpp_candid-7.0.0rc3.tar.gz
| Download URL | icpp_candid-7.0.0rc3.tar.gz |
|---|---|
| Size | 111.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
935f81e9bb6b875d8cc11b92d9e8835e23a870f219681119d3be97fd78652363
|
|
BLAKE2b-256 checksum How to use checksums |
c3671ef6df6257d56cea7b3bcbf14f62b15bd9e1ac50ac27a9f3b20af75dcb08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / icpp_candid-7.0.0rc3-py3-none-any.whl
| Download URL | icpp_candid-7.0.0rc3-py3-none-any.whl |
|---|---|
| Size | 243.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fac318c7f660f8bafde76af49e08c5a46f30343e80eb1dc83745b9458729d253
|
|
BLAKE2b-256 checksum How to use checksums |
85aa5aab3647f1da3057ebf5b899c32f6f1511bfcbcbc3127a259777ae6c1fba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for icpp-candid 7.0.0rc3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for icpp_candid-7.0.0rc3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
