<feed xmlns='http://www.w3.org/2005/Atom'>
<title>blocksense/zkVMs-benchmarks/zkvms/zkm, branch main</title>
<subtitle>Setups and programs for zero-knowledge virtual machine benchmarking</subtitle>
<id>https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/atom?h=main</id>
<link rel='self' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/'/>
<updated>2025-05-02T12:32:54Z</updated>
<entry>
<title>chore: cargo fmt</title>
<updated>2025-05-02T12:32:54Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-05-02T07:24:47Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=1a2ad5528f7a61390c40c0b6f56fa507923d09f5'/>
<id>urn:sha1:1a2ad5528f7a61390c40c0b6f56fa507923d09f5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat(zkvms_guest_io): Output proof size</title>
<updated>2025-05-02T12:32:54Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-30T14:25:15Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=eefb57f2c035be1a398f630dd8cfed8b4ccbe348'/>
<id>urn:sha1:eefb57f2c035be1a398f630dd8cfed8b4ccbe348</id>
<content type='text'>
In each zkVM we'll write the size to /tmp/proof_size and then guest_io
will read that value and place it inside our metrics output. This is not
the most elegant, and in certain zkVMs the file output is a part of the
benchmark timing, but it will have to do.
</content>
</entry>
<entry>
<title>feat(zkvms_host_io): Implement new output format for zkvm/guest</title>
<updated>2025-05-02T12:32:54Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-29T12:48:34Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=1112cce22f81341dfd0553034ca927e823bb36bf'/>
<id>urn:sha1:1112cce22f81341dfd0553034ca927e823bb36bf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat(zkvms_host_io): Add json dependency</title>
<updated>2025-05-02T12:32:54Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-03-28T10:38:04Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=c8505d63fcc46df5ec5e2f3e99517408d95bc8a6'/>
<id>urn:sha1:c8505d63fcc46df5ec5e2f3e99517408d95bc8a6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chore: Update mcl-blockchain dependency</title>
<updated>2025-04-24T13:48:24Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-24T12:01:35Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=b9a899d95ae2a661859fcdca2b27d15931d0e2a8'/>
<id>urn:sha1:b9a899d95ae2a661859fcdca2b27d15931d0e2a8</id>
<content type='text'>
There are no package version updates. The primary difference is that
RISC0 is now compiled with the unstable feature. All other hash updates
come from the switch from rust-bin to fenix.
</content>
</entry>
<entry>
<title>fix(zkvms/zkm): Include string in guest wrapper</title>
<updated>2025-04-23T14:28:22Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-16T06:46:36Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=8b7eae6c78bab4632b87003de0672b792a8046a5'/>
<id>urn:sha1:8b7eae6c78bab4632b87003de0672b792a8046a5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat(guests/keccak): Add ZKM precompile function call</title>
<updated>2025-04-14T10:40:57Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-14T08:51:36Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=c87a637465126176ae361e0b9ce7893e279e86ce'/>
<id>urn:sha1:c87a637465126176ae361e0b9ce7893e279e86ce</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix(zkvms): Fix non-braced usages of grouped methods</title>
<updated>2025-04-07T14:41:20Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-07T14:40:13Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=1f3ca1f4455c4dd98680ede689bbcfba2c8e4225'/>
<id>urn:sha1:1f3ca1f4455c4dd98680ede689bbcfba2c8e4225</id>
<content type='text'>
Before grouping transformed vec![a,b,...] into "(a,b,...)", but with
FunctionDefinition, grouping transforms vec![a,b,...] into "a,b,...".
This change wasn't reflected in Nexus and ZKM
</content>
</entry>
<entry>
<title>feat(zkvms/zkm): Update to use FunctionDefinition</title>
<updated>2025-04-07T14:41:20Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-07T13:55:22Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=ef33084183298d15c7a957ed959246fbc9c810fe'/>
<id>urn:sha1:ef33084183298d15c7a957ed959246fbc9c810fe</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix(zkvms/zkm): Update SDK and remove hack</title>
<updated>2025-04-04T08:03:00Z</updated>
<author>
<name>Kamen Mladenov</name>
<email>kamen@syndamia.com</email>
</author>
<published>2025-04-04T07:59:34Z</published>
<link rel='alternate' type='text/html' href='https://git.syndamia.com/work/blocksense/zkVMs-benchmarks/commit/?id=7498d604be92a0b1a7a5603e0295f194aa8b05e7'/>
<id>urn:sha1:7498d604be92a0b1a7a5603e0295f194aa8b05e7</id>
<content type='text'>
Recently ZKM introduced a bug, where SNARK_SETUP would crash, but the
witness would be generated. So we introduced a hack where we would run
SNARK_SETUP, ignore the crash and rerun the program again, without
SNARK_SETUP.

Now they fixed it, so with SNARK_SETUP, the witnesses would be generated
and the proving process will be done directly after.
</content>
</entry>
</feed>
