rns_engine
Fast, exact integer arithmetic on a four-rail Residue Number System.
No floating point. No approximation. Arithmetic is exact modulo the engine's fixed dynamic range.
Recent Colab benchmark: https://colab.research.google.com/drive/18RIQSLf4Vf5xUnwEmDwYNPJDLSM_Stqa?usp=sharing
What it does
rns_engine decomposes each integer across four coprime rails:
127819165536524287
Arithmetic runs independently on the rails, then Garner-style CRT reconstructs the canonical result.
M = 127 × 8191 × 65536 × 524287
= 35,742,890,181,197,824
Unsigned results live in:
[0, M)
The centered signed interpretation lives in:
[-M/2, M/2 - 1]
=
[-17,871,445,090,598,912, 17,871,445,090,598,911]
Install
pip install rns_engine
Supported Python versions: 3.10–3.13.
AVX2 note
HAS_AVX2 is a build-time property of the compiled extension, not runtime CPU detection. Supported x86-64 wheels can use AVX2 acceleration. macOS wheels intentionally avoid an external OpenMP dependency.
Unsigned quick start
import numpy as np
import rns_engine as rns
x = np.array([123456789, 999999999], dtype=np.uint64)
y = np.array([987654321, 111111111], dtype=np.uint64)
ex = rns.encode(x)
ey = rns.encode(y)
out_add = rns.decode(*rns.add(*ex, *ey))
out_mul = rns.decode(*rns.mul(*ex, *ey))
# Stay in residue space across several exact operations and decode once.
s1 = rns.add(*ex, *ey)
s2 = rns.mul(*s1, *ey)
s3 = rns.sub(*s2, *ex)
out = rns.decode(*s3)
Session API
import numpy as np
import rns_engine as rns
session = rns.Session(cache_capacity=32)
x = np.array([1, 2, 3, 4], dtype=np.uint64)
encoded = session.encode(x)
result = session.mul(session.add(encoded, encoded), encoded)
out = session.decode(result)
one_step = session.one_shot_affine(
x,
multiplier=1_000_003,
addend=7,
)
hot_loop = session.hot_loop_affine(
x,
multiplier=1_000_003,
addend=7,
iterations=1000,
)
Centered signed arithmetic
import numpy as np
import rns_engine as rns
values = np.array([-5, 0, 7], dtype=np.int64)
rails = rns.encode_signed(values)
round_trip = rns.decode_signed(*rails)
assert np.array_equal(round_trip, values)
encode_signed(...) accepts only integers in [-M/2, M/2 - 1]. It rejects out-of-range inputs instead of silently wrapping them modulo M.
decode_signed(...) returns the canonical centered representative. That representation alone does not prove that an unknown mathematical result did not wrap. Unique signed reconstruction requires independent range evidence:
|result| < M/2
certificate = rns.certify_signed_bound(max_abs_bound=1_000_000)
certificate.require_unique()
print(certificate.headroom)
print(certificate.minimum_required_modulus)
For a signed dot product—or one output entry of a GEMM—the engine can construct the conservative exact bound directly:
certificate = rns.certify_signed_dot_bound(
inner_dimension=5120,
left_abs_bound=127,
right_abs_bound=127,
)
assert certificate.max_abs_bound == 82_580_480
assert certificate.unique
certificate.require_unique()
The law is:
output bound
=
inner_dimension × left bound × right bound + addend bound
SignedSession exposes the existing rail arithmetic with signed external values:
session = rns.SignedSession()
a = session.encode_signed([-5, 7])
b = session.encode_signed([3, -10])
out = session.decode_signed(session.add(a, b))
Weighted INT32 partial accumulation
Version 0.6 adds the first direct bridge for digit-plane, chunked-GEMM, and Tensor Core pipelines.
Give the engine signed INT32 partial outputs with shape:
(terms, *output_shape)
and one exact integer positional weight per term:
import numpy as np
import rns_engine as rns
partials = np.array(
[
[[1, -2], [3, -4]],
[[5, 6], [-7, -8]],
[[-9, 10], [11, -12]],
],
dtype=np.int32,
)
receipt = rns.accumulate_weighted_int32(
partials,
weights=[1, -3, 8],
require_unique=True,
)
exact = receipt.decode_signed()
print(receipt.certificate.max_abs_bound)
print(receipt.certificate.headroom)
For partials P[t] and full integer weights w[t], the receipt uses the exact conservative law:
max_abs_bound
=
sum(abs(w[t]) × max_abs(P[t]))
Important details:
- The original arbitrary-precision Python weights are retained in the proof receipt.
- Only the execution weights are reduced modulo
M, which is lawful for rail arithmetic. - Negative weights and weights wider than
uint64are supported. INT32_MINis measured with its correct magnitude,2,147,483,648.decode_signed()requires a unique range certificate by default.decode_modular()always returns the canonical residue in[0, M).- Empty term sets produce an exact zero result.
The current implementation is an evidence-first baseline. Python schedules terms, while each per-element encode, scalar-weight multiply, and rail addition runs through the compiled native kernels. It is not yet one fused C++ weighted-accumulation kernel, and no fused-kernel speed claim is made.
A precomputed receipt can also be created without materializing partial arrays:
certificate = rns.certify_weighted_sum_bound(
weights=[1, 128, 128**2],
term_abs_bounds=[100, 200, 300],
)
certificate.require_unique()
Core API
Rail operations
encode(x)/decode(r0, r1, r2, r3)encode_signed(x)/decode_signed(r0, r1, r2, r3)add(...),sub(...),mul(...),div_(...),fma(...)op(..., code)where0=add,1=mul,2=sub,3=div
Signed range receipts
certify_signed_bound(max_abs_bound)certify_signed_dot_bound(inner_dimension, left_abs_bound, right_abs_bound, addend_abs_bound=0)SignedRangeCertificate.uniqueSignedRangeCertificate.headroomSignedRangeCertificate.minimum_required_modulusSignedRangeCertificate.require_unique()
Weighted partial reconstruction
accumulate_weighted_int32(partials, weights, require_unique=False)certify_weighted_sum_bound(weights, term_abs_bounds, addend_abs_bound=0)WeightedInt32Result.decode_signed(require_unique=True)WeightedInt32Result.decode_modular()
Scalar-broadcast encoded operations
mul_u64(...)fma_u64(...)affine_repeat_u64(...)
Fused raw uint64 operations
add_u64_io(...)sub_u64_io(...)mul_u64_io(...)fma_u64_io(...)affine_repeat_u64_io(...)
OpenMP forms use the _omp suffix. Auto-dispatch forms use the _auto suffix.
High-level objects
SessionSignedSessionSessionCacheEncodedArrayWeightedInt32Result
Division constraint
Division requires the divisor to be invertible on every rail:
b % 127 != 0b % 8191 != 0bis odd for modulus65536b % 524287 != 0
Data model
- Unsigned
encode(...)treats inputs asuint64and reduces values moduloM. encode_signed(...)accepts only integers in the centered interval and refuses silent wrapping.decode_signed(...)returns the canonical centeredint64representative.accumulate_weighted_int32(...)requires an array whose dtype is exactlyint32.- Encoded rails use:
r0:uint16r1:uint16r2:uint16r3:uint32
EncodedArraystores four read-only rails.
Existing verified benchmark
Verified on Google Colab Linux x86-64 with AVX2=True, two OpenMP processors, and two OpenMP threads. Workloads used the installed wheel.
Median throughput over five runs on 1,000,000 uint64 values:
Fused single-step affine
Workload: fma_u64_io(x, 1_000_003, 7)
fma_u64_io: 47.8 million values/secfma_u64_io_ompwith one thread: 80.7 million values/secfma_u64_io_ompwith two threads: 84.6 million values/sec
Repeated affine loop
Workload: affine_repeat_u64_io(x, 1_000_003, 7, iterations=1000)
- scalar fused path: 61.19 billion ops/sec
- OpenMP with one thread: 82.80 billion ops/sec
- OpenMP with two threads: 94.86 billion ops/sec
These measurements cover the existing affine kernels, not the new weighted INT32 orchestration path.
Build from source
git clone https://github.com/playfularchitect/rns_engine.git
cd rns_engine
pip install -e .
python -m pytest tests/ -v
Requirements:
- Python 3.10–3.13
- C++17 compiler
- Access to the build dependencies declared in
pyproject.toml
The release workflow compiles and tests the package on Linux, macOS, and Windows, then installs and tests every produced wheel before publication.
Introspection
import rns_engine as rns
rns.info()
rns.M
rns.HALF_M
rns.SIGNED_MIN
rns.SIGNED_MAX
rns.M0
rns.M1
rns.M2
rns.M3
rns.HAS_AVX2
Current release
v0.6.0
- weighted signed INT32 partial accumulation
- exact arbitrary-precision positional weights
- per-term magnitude receipts and strict no-wrap certification
- canonical modular and uniqueness-gated signed decode paths
- canonical centered signed encoding and decoding
- exact dot-product and GEMM output-bound receipts
SignedSessionhigh-level API- four-rail native engine (
127 × 8191 × 65536 × 524287) - AVX2, OpenMP, and auto-dispatch kernel families
License
AGPL-3.0-only
If this software is used in a network service, the AGPL requires modified source to be made available to users. Commercial licensing for proprietary or closed-source use is available. Inquiries: ewesley541@gmail.com
Copyright 2026 Evan Wesley
Metadata
Release files for rns-engine 0.6.0
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 | Actions |
|---|---|---|---|---|
| rns_engine-0.6.0.tar.gz | 42.3 kB | With provenance | Details for rns_engine-0.6.0.tar.gz |
Built distributions (wheels)
Total release size: 9.9 MB
Release files / rns_engine-0.6.0.tar.gz
| Download URL | rns_engine-0.6.0.tar.gz |
|---|---|
| Size | 42.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b327f418cf6d1f57035ab28b381e3fa513193e727a32df2465c0ae3694e5ef2c
|
|
BLAKE2b-256 checksum How to use checksums |
068acbc277f4957c3aeceb3a8f7b480a8e2c37d2015da96a126d46cd43ba7f55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp313-cp313-win_amd64.whl
| Download URL | rns_engine-0.6.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 144.4 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8a481cbc230dd50755ef46fdfa7d6e09887926a6c65fc8790d8c7c7f92210546
|
|
BLAKE2b-256 checksum How to use checksums |
6455aae115bd9718a51e928db276a243664e7cabf4c588f6c408c9ecaa3fc3f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rns_engine-0.6.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
6e35111695b75c10dafe305747406f7f811bd31032ac69cda8f4b59e84d78bd7
|
|
BLAKE2b-256 checksum How to use checksums |
e4031277641f7787cf8f7cc4f12029401c139595f8f39840a5d3b057258dea4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp313-cp313-macosx_11_0_x86_64.whl
| Download URL | rns_engine-0.6.0-cp313-cp313-macosx_11_0_x86_64.whl |
|---|---|
| Size | 176.7 kB |
| Tags | CPython 3.13 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
a9ded46b089c8393feb47b84ddb45aa9d77acbb5543ae66f0c17f3847c7bd7d2
|
|
BLAKE2b-256 checksum How to use checksums |
2398cef65f302534b1916a6155b1a48b33491d4e7fa5d337d3b3a0c536e48848
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | rns_engine-0.6.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 177.0 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a491e9f9496ef2fcde57c4d1da8b4962dbdd8a1f26d3f461ab696bf7a79f1395
|
|
BLAKE2b-256 checksum How to use checksums |
6d03785b03292281e7d598ee3d1b34a9deeccc59277701cf9ce7db15a2d13764
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp312-cp312-win_amd64.whl
| Download URL | rns_engine-0.6.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 144.4 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c049ae400f583b45ff276bc9ab3982f4339555d665e171900cffd8e1cc8dbf59
|
|
BLAKE2b-256 checksum How to use checksums |
d5eefc40083465f64a8fa57b8bae08b8c29bca0f6923ce35e742d1998b1e88a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rns_engine-0.6.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
910ba1a9ce9c902558af1cabb18363bb1650f8f4ba9cb8825d65793d52f6face
|
|
BLAKE2b-256 checksum How to use checksums |
2335f8f55c1b8083f0b58ecf744bdac62e1c3f028901204244ca92471b85d05c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp312-cp312-macosx_11_0_x86_64.whl
| Download URL | rns_engine-0.6.0-cp312-cp312-macosx_11_0_x86_64.whl |
|---|---|
| Size | 176.7 kB |
| Tags | CPython 3.12 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
c6c0b676a26dabf09dfc3da0dbd44122240e9d9e2b994b43fab4ed037d2a1012
|
|
BLAKE2b-256 checksum How to use checksums |
b67b101e240b68ee2d9fdde3b7634590c7d56e8f9d3fc50cdd5bd9a8a495f063
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | rns_engine-0.6.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 176.9 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d700bcaef1852d50ca9ad38b53262f1129bb59f8be49725c7a2320e31c4526f6
|
|
BLAKE2b-256 checksum How to use checksums |
40cb53e2dccd0c6c29cab36893d389b88420840696c63048057b5e052dddeade
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp311-cp311-win_amd64.whl
| Download URL | rns_engine-0.6.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 142.4 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0b87e4c03dda47cc7ba81c21fb621a0628561e03b407e80ef195c804f32567c9
|
|
BLAKE2b-256 checksum How to use checksums |
23eb9f9625db4dfe2f80699e918c8da41495485e5e6311a4c945a887acbf19a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rns_engine-0.6.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
98fae3bc79e1c35a371fe3824a7abfb9cb5fd68fbbbcf88fd3033a2f79aea377
|
|
BLAKE2b-256 checksum How to use checksums |
4d683ae1d3e1967129a1e40a4dfd37fa5121414bdc57f32f6175f47904e6372a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp311-cp311-macosx_11_0_x86_64.whl
| Download URL | rns_engine-0.6.0-cp311-cp311-macosx_11_0_x86_64.whl |
|---|---|
| Size | 173.5 kB |
| Tags | CPython 3.11 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
02708d396586b4ba8e0e7d8b7345f1c2cc497e1fb816863b9e8acf0fae7dbf42
|
|
BLAKE2b-256 checksum How to use checksums |
70502a7912dff672085378ef600ab9d1a85622272e43c385913e53ee67daa0b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | rns_engine-0.6.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 174.9 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
5c8b5c21f8c3fa4c81e923c95865f4dee7251223388685b11fb3c3d10d33641a
|
|
BLAKE2b-256 checksum How to use checksums |
2c777f534c0b672f38a05158590e035cde07e743907096886d25f7e2a975232d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp310-cp310-win_amd64.whl
| Download URL | rns_engine-0.6.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 141.9 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4a23726159e8160f1fcccd46edeb5288c05257e796471e3d291add37b3484ba5
|
|
BLAKE2b-256 checksum How to use checksums |
5b1d086cc74b3bc1b4c9dc7f0ee31735b681d9b22e3945eb2a8414cc653c8bf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rns_engine-0.6.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
d614820e4a9c33e937013d6a43d7e458dedc620b6fe6437d3e9feb29e7aec31e
|
|
BLAKE2b-256 checksum How to use checksums |
e6524dc7409b3928755e6aca41d1e1f613c7702f60180fe81e63980f7985f6e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp310-cp310-macosx_11_0_x86_64.whl
| Download URL | rns_engine-0.6.0-cp310-cp310-macosx_11_0_x86_64.whl |
|---|---|
| Size | 172.2 kB |
| Tags | CPython 3.10 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
a6e08f542eaac79bd86a962a9078e273192e73574fece3c6735b44b22a3af72a
|
|
BLAKE2b-256 checksum How to use checksums |
68f0ed51e4747ccb16fd246ff2579d27c62bab4814a01207ff436a42116f1838
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logRelease files / rns_engine-0.6.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | rns_engine-0.6.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 173.4 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
be385606b8aaf520cff81f0b456af24ab96f27cb7b341d6d57999173950e654a
|
|
BLAKE2b-256 checksum How to use checksums |
5c059b23a6aa85a14ec99d00fab5bc6489c5c5fc29f0f2b32096102239e13d57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 2, 2026.
Transparency logSecurity for rns-engine 0.6.0
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 17 files in this release have been uploaded with provenance metadata.
Attestation for rns_engine-0.6.0.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 Aug 2, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.