Skip to content

Releases: AInima-Collective/trustgraphs

v0.1.5

Choose a tag to compare

@github-actions github-actions released this 14 Sep 22:16
40e945d

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.1.5

Digest: sha256:43d04f3a21e56764bf2df14928e60c5fbef550d9ae1b70ddcc01644d030c6570

Built by this workflow run
from 40e945d2a58efdc3512257f473bf3b337f39616f, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.1.5 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 446d12fab5a9cde882ca7d07499e2db750915c21696c3945f8fcb061b6435f6e 0x00bbf3b3cc5efe71ced29517bd09edac2720bcc795b7094a314db17c224dcea3
trust-graph-weighted 12e658843d2719b246f2898e3375610e65c255326a11df8ec16e57ae40142d95 0x0095b1a77a841e434307acdc8cd2340c3a82beda37cde4498170db3cdcc6eb80
trust-compose d74643d1a62bf5951dcc3e3caee4e0d558a61f4fc0d8664509da277b31f0e082 0x00c6868afdf506311dcb1393a74f3c033ad0620ec25602b65d079227c88d9dfc
signer-sync 73ca7d5e2fd1516a83645aefe3ce8541fe76007d7416267a5169ff5dd6bbb912 0x00f8ad1fd05ff8c894a1e8906b3e1a1f9fba968d14ef8a121d3107d3c57df7fb
contributions 48603c146a0d7100f5a2a6e92ba518b6b7f9ca0d55816be1742d70f70e5a2480 0x0098fb1266d6ca97c12c529c29ef59b45dae9bede0cbe0990a2fbb1b4394d798
hypercerts 00cdda54fb2eccffed8b393cad91926a9560faa1341c0b7ae05248565b9222f0 0x0072790ce927dab3afab201f8517b7b0ac36764c825825f6a23d9ed3c080c8d2
nostr-workspace 3238e0ef525febdc094ed7d3fe1958ef93ddeddbb31599cd3d0d615d8ea121b7 0x00a8e5183dbdab1ff521c068ff2d2d8ed840f5beef4f516964d345a16bc302af

v0.1.4

Choose a tag to compare

@github-actions github-actions released this 14 Sep 18:53
249466e

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.1.4

Digest: sha256:3834588af5769e935445fbbcd8dce904958063d228c59292a16cc357e4315053

Built by this workflow run
from 249466e71d0493649ed16a1bfb0d8e7411640502, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.1.4 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 446d12fab5a9cde882ca7d07499e2db750915c21696c3945f8fcb061b6435f6e 0x00bbf3b3cc5efe71ced29517bd09edac2720bcc795b7094a314db17c224dcea3
trust-graph-weighted 12e658843d2719b246f2898e3375610e65c255326a11df8ec16e57ae40142d95 0x0095b1a77a841e434307acdc8cd2340c3a82beda37cde4498170db3cdcc6eb80
trust-compose d74643d1a62bf5951dcc3e3caee4e0d558a61f4fc0d8664509da277b31f0e082 0x00c6868afdf506311dcb1393a74f3c033ad0620ec25602b65d079227c88d9dfc
signer-sync 73ca7d5e2fd1516a83645aefe3ce8541fe76007d7416267a5169ff5dd6bbb912 0x00f8ad1fd05ff8c894a1e8906b3e1a1f9fba968d14ef8a121d3107d3c57df7fb
contributions 48603c146a0d7100f5a2a6e92ba518b6b7f9ca0d55816be1742d70f70e5a2480 0x0098fb1266d6ca97c12c529c29ef59b45dae9bede0cbe0990a2fbb1b4394d798
hypercerts 00cdda54fb2eccffed8b393cad91926a9560faa1341c0b7ae05248565b9222f0 0x0072790ce927dab3afab201f8517b7b0ac36764c825825f6a23d9ed3c080c8d2
nostr-workspace 3238e0ef525febdc094ed7d3fe1958ef93ddeddbb31599cd3d0d615d8ea121b7 0x00a8e5183dbdab1ff521c068ff2d2d8ed840f5beef4f516964d345a16bc302af

v0.1.3

Choose a tag to compare

@github-actions github-actions released this 11 Sep 00:37
5902d7e

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.1.3

Digest: sha256:645944e4ed08277bdbd1a9efc8e841af621565b02f82acaf251e39fdea301092

Built by this workflow run
from 5902d7eb2622f2be1aa349ae2823bad167680227, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.1.3 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 446d12fab5a9cde882ca7d07499e2db750915c21696c3945f8fcb061b6435f6e 0x00bbf3b3cc5efe71ced29517bd09edac2720bcc795b7094a314db17c224dcea3
trust-graph-weighted 12e658843d2719b246f2898e3375610e65c255326a11df8ec16e57ae40142d95 0x0095b1a77a841e434307acdc8cd2340c3a82beda37cde4498170db3cdcc6eb80
trust-compose d74643d1a62bf5951dcc3e3caee4e0d558a61f4fc0d8664509da277b31f0e082 0x00c6868afdf506311dcb1393a74f3c033ad0620ec25602b65d079227c88d9dfc
signer-sync 73ca7d5e2fd1516a83645aefe3ce8541fe76007d7416267a5169ff5dd6bbb912 0x00f8ad1fd05ff8c894a1e8906b3e1a1f9fba968d14ef8a121d3107d3c57df7fb
contributions 48603c146a0d7100f5a2a6e92ba518b6b7f9ca0d55816be1742d70f70e5a2480 0x0098fb1266d6ca97c12c529c29ef59b45dae9bede0cbe0990a2fbb1b4394d798
hypercerts 00cdda54fb2eccffed8b393cad91926a9560faa1341c0b7ae05248565b9222f0 0x0072790ce927dab3afab201f8517b7b0ac36764c825825f6a23d9ed3c080c8d2
nostr-workspace 3238e0ef525febdc094ed7d3fe1958ef93ddeddbb31599cd3d0d615d8ea121b7 0x00a8e5183dbdab1ff521c068ff2d2d8ed840f5beef4f516964d345a16bc302af

v0.1.2

Choose a tag to compare

@github-actions github-actions released this 10 Sep 02:40

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.1.2

Digest: sha256:d37fad30f3007a1f0f515ffec1f8a1542248296d71b796705146f086e94f22e6

Built by this workflow run
from 6a9e2d789c8cdc9ff73804e328f06f3467667341, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.1.2 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 446d12fab5a9cde882ca7d07499e2db750915c21696c3945f8fcb061b6435f6e 0x00bbf3b3cc5efe71ced29517bd09edac2720bcc795b7094a314db17c224dcea3
trust-graph-weighted 12e658843d2719b246f2898e3375610e65c255326a11df8ec16e57ae40142d95 0x0095b1a77a841e434307acdc8cd2340c3a82beda37cde4498170db3cdcc6eb80
trust-compose d74643d1a62bf5951dcc3e3caee4e0d558a61f4fc0d8664509da277b31f0e082 0x00c6868afdf506311dcb1393a74f3c033ad0620ec25602b65d079227c88d9dfc
signer-sync 73ca7d5e2fd1516a83645aefe3ce8541fe76007d7416267a5169ff5dd6bbb912 0x00f8ad1fd05ff8c894a1e8906b3e1a1f9fba968d14ef8a121d3107d3c57df7fb
contributions 48603c146a0d7100f5a2a6e92ba518b6b7f9ca0d55816be1742d70f70e5a2480 0x0098fb1266d6ca97c12c529c29ef59b45dae9bede0cbe0990a2fbb1b4394d798
hypercerts 00cdda54fb2eccffed8b393cad91926a9560faa1341c0b7ae05248565b9222f0 0x0072790ce927dab3afab201f8517b7b0ac36764c825825f6a23d9ed3c080c8d2
nostr-workspace 3238e0ef525febdc094ed7d3fe1958ef93ddeddbb31599cd3d0d615d8ea121b7 0x00a8e5183dbdab1ff521c068ff2d2d8ed840f5beef4f516964d345a16bc302af

v0.1.1

Choose a tag to compare

@github-actions github-actions released this 09 Sep 22:15

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.1.1

Digest: sha256:1ff3b817174ba6b8540aa661095a6278007602c5c379ba43347ca5ba955c75e2

Built by this workflow run
from 6d3e272eef46ee9e06ab7caedb03fa733594c4ce, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.1.1 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 446d12fab5a9cde882ca7d07499e2db750915c21696c3945f8fcb061b6435f6e 0x00bbf3b3cc5efe71ced29517bd09edac2720bcc795b7094a314db17c224dcea3
trust-graph-weighted 12e658843d2719b246f2898e3375610e65c255326a11df8ec16e57ae40142d95 0x0095b1a77a841e434307acdc8cd2340c3a82beda37cde4498170db3cdcc6eb80
trust-compose d74643d1a62bf5951dcc3e3caee4e0d558a61f4fc0d8664509da277b31f0e082 0x00c6868afdf506311dcb1393a74f3c033ad0620ec25602b65d079227c88d9dfc
signer-sync 73ca7d5e2fd1516a83645aefe3ce8541fe76007d7416267a5169ff5dd6bbb912 0x00f8ad1fd05ff8c894a1e8906b3e1a1f9fba968d14ef8a121d3107d3c57df7fb
contributions 48603c146a0d7100f5a2a6e92ba518b6b7f9ca0d55816be1742d70f70e5a2480 0x0098fb1266d6ca97c12c529c29ef59b45dae9bede0cbe0990a2fbb1b4394d798
hypercerts 00cdda54fb2eccffed8b393cad91926a9560faa1341c0b7ae05248565b9222f0 0x0072790ce927dab3afab201f8517b7b0ac36764c825825f6a23d9ed3c080c8d2
nostr-workspace 3238e0ef525febdc094ed7d3fe1958ef93ddeddbb31599cd3d0d615d8ea121b7 0x00a8e5183dbdab1ff521c068ff2d2d8ed840f5beef4f516964d345a16bc302af

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 09 Sep 19:33

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.1.0

Digest: sha256:a9ec758820c2d43f1b979a1eb5c3e7f5a5a7ebc45ea7078bf611f350bacbcac4

Built by this workflow run
from b880300977dfde0a058c4009f9936109a08e0dd7, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.1.0 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 446d12fab5a9cde882ca7d07499e2db750915c21696c3945f8fcb061b6435f6e 0x00bbf3b3cc5efe71ced29517bd09edac2720bcc795b7094a314db17c224dcea3
trust-graph-weighted 12e658843d2719b246f2898e3375610e65c255326a11df8ec16e57ae40142d95 0x0095b1a77a841e434307acdc8cd2340c3a82beda37cde4498170db3cdcc6eb80
trust-compose d74643d1a62bf5951dcc3e3caee4e0d558a61f4fc0d8664509da277b31f0e082 0x00c6868afdf506311dcb1393a74f3c033ad0620ec25602b65d079227c88d9dfc
signer-sync 73ca7d5e2fd1516a83645aefe3ce8541fe76007d7416267a5169ff5dd6bbb912 0x00f8ad1fd05ff8c894a1e8906b3e1a1f9fba968d14ef8a121d3107d3c57df7fb
contributions 48603c146a0d7100f5a2a6e92ba518b6b7f9ca0d55816be1742d70f70e5a2480 0x0098fb1266d6ca97c12c529c29ef59b45dae9bede0cbe0990a2fbb1b4394d798
hypercerts 00cdda54fb2eccffed8b393cad91926a9560faa1341c0b7ae05248565b9222f0 0x0072790ce927dab3afab201f8517b7b0ac36764c825825f6a23d9ed3c080c8d2
nostr-workspace 3238e0ef525febdc094ed7d3fe1958ef93ddeddbb31599cd3d0d615d8ea121b7 0x00a8e5183dbdab1ff521c068ff2d2d8ed840f5beef4f516964d345a16bc302af

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 25 Aug 16:29

Operator image

docker pull ghcr.io/ainima-collective/trustgraphs-operator:v0.0.5

Digest: sha256:347345b440a143509106b9ed42182b1a3921865fcf59366f49bdb577ddf1b22a

Built by this workflow run
from f64a4c7c9b5e552e2392894a2e0d6f6c40973549, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/ainima-collective/trustgraphs-operator:v0.0.5 --repo AInima-Collective/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 1ad727e35139b7db669430052a376b6850352c2fc5792a0f6815c7da21b7059d 0x003c8e19b8e12c260e5450a068c61460180b5cf93f03dc1214187a9ad3bdde5e
trust-graph-weighted 9c8d1d52b503bbbdf50f778521ab6391114a2107b293040403b98c814286eab8 0x0027625a41e9d165ab50ca4ff9afbc134385b99688a5fd69cdf03d5056f5abb2
trust-compose d3947c0640498acc42ae4a292d8e65abccc833d9ff2f6791e749e3fc57fc8879 0x00e2847cc257d916a6422283094e8764296045e5f9ed8805b7aaa9b3dd6f7aed
signer-sync 9e4c6757fdfbf6e4f2ace056e902379f7fb362d3f0de6a79dcacc0827f40c715 0x00d1b981df6bee1682be2b212151d2ac74c30108215d8e949a84a604ae4baadb
contributions 1d6f6ce22e97c1be65a6a142dc238449c57f0eebef6e303217276d1d78d3fdd0 0x0083cb62532a5c855c0c1b61a1eb7b7d5d6d924784342ea661c80baf79cfa243
hypercerts b70743d700464b31df81f87b73b653e38e58c0a1a0c600038eb98015dd0e491e 0x009890d8fed8be4836e060c25ad267049efbe79ce929b0e63c1e086007008d40
nostr-workspace 1dbe149fe811693397aac371e90a75552f8bb5d778074c838a1aa9e0daca2d42 0x003a7984610aa854a8daa012d2d78846ba663781c8fe3aa74fed99be047b6566

v0.0.4

Choose a tag to compare

@github-actions github-actions released this 25 Aug 02:51

Operator image

docker pull ghcr.io/jakehartnell/trustgraphs-operator:v0.0.4

Digest: sha256:1656285b28c526016ce259bb84528d04fce3b544edbb9e1ca89fe59e256141bd

Built by this workflow run
from 95faa6ff1fe99a40c4b485d6d3a61319687a5703, with a build-provenance attestation you can check without
an account:

gh attestation verify oci://ghcr.io/jakehartnell/trustgraphs-operator:v0.0.4 --repo JakeHartnell/trustgraphs

Guest programs

Every guest was built inside the pinned SP1 builder image, twice, on two cold
runners that share no state, and produced identical bytes before this release
was cut. Two cold builds rather than two architectures: the pinned SP1 builder
image is amd64-only, so an arm64 runner would run that same container under
emulation and compare a build against itself. guest-manifest.json is
attached; the same values are reproducible from source with:

sh scripts/build-guests.sh && sh scripts/guest-elf-digests.sh
program ELF sha256 vkey
trust-graph 1ad727e35139b7db669430052a376b6850352c2fc5792a0f6815c7da21b7059d 0x003c8e19b8e12c260e5450a068c61460180b5cf93f03dc1214187a9ad3bdde5e
trust-graph-weighted 9c8d1d52b503bbbdf50f778521ab6391114a2107b293040403b98c814286eab8 0x0027625a41e9d165ab50ca4ff9afbc134385b99688a5fd69cdf03d5056f5abb2
trust-compose d3947c0640498acc42ae4a292d8e65abccc833d9ff2f6791e749e3fc57fc8879 0x00e2847cc257d916a6422283094e8764296045e5f9ed8805b7aaa9b3dd6f7aed
signer-sync 9e4c6757fdfbf6e4f2ace056e902379f7fb362d3f0de6a79dcacc0827f40c715 0x00d1b981df6bee1682be2b212151d2ac74c30108215d8e949a84a604ae4baadb
contributions 1d6f6ce22e97c1be65a6a142dc238449c57f0eebef6e303217276d1d78d3fdd0 0x0083cb62532a5c855c0c1b61a1eb7b7d5d6d924784342ea661c80baf79cfa243
hypercerts b70743d700464b31df81f87b73b653e38e58c0a1a0c600038eb98015dd0e491e 0x009890d8fed8be4836e060c25ad267049efbe79ce929b0e63c1e086007008d40
nostr-workspace 1dbe149fe811693397aac371e90a75552f8bb5d778074c838a1aa9e0daca2d42 0x003a7984610aa854a8daa012d2d78846ba663781c8fe3aa74fed99be047b6566