Browse / Other
qorechain/qorechain-rdk
Rollup Development Kit for launching and operating application-specific rollups on the QoreChain network.
Works.Tested on 2026-10-28. From the README alone, on Linux with Haiku.
What we checked
Does it run from the README?Yes. Running in 17:21 on a clean Linux box.The run
Tested Oct 28, 2026, rev 2abe19b.
Does it do what the README says?3 of 3 claims held up.Evidence
“The RDK defaults to testnet, so live module parameters are read from testnet”
Expected live testnet module parameters are printed, including maxRollups 200. Got "maxRollups": 200.
“Rollup creation shows the stake and burn cost before submitting”
Expected dry run reports a 10,000 QOR stake (10000000000 uqor). Got "stakeUqor": "10000000000".
“keygen generates an operator key”
Expected a new qor1 operator address is printed. Got "address": "qor1.
Which checks were skipped?1 check skipped.Reasons
Skipped checks count as neither passes nor failures.
Cycles: 1 skipped
- watchtower polls a rollup's batches on a timer: missing prerequisite: a live rollup on qorechain-diana; creating one needs a funded signer (stake 10,000 QOR)
Which setups did we try?Works with Haiku.Setups
Linux / Haiku: works, Oct 28, rev 2abe19b.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?Made outbound HTTPS connections: yes (hosts not recorded) by <guest-path>What we saw
Review signals across current setups: connection review. 262 listed items (named-host connections, static matches, dependency advisories) are below and do not change this verdict. 8 static matches retained as context.
Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 2 distinct locations. 14 attributed processes.
Gitleaks found a possible hardcoded secret; value withheld. 2 distinct locations. 2 findings.
OSV reports a known vulnerability in this dependency version. 35 distinct locations. 104 findings.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written; resolver address lookups that send no data.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 6 commits in 90 days · 0 merged PRs in 90 days · 0 open issues · 0 open PRsActivity
actively maintained: last commit 0 days ago; 6 commits and 0 merged PRs in 90 days; 0 open issues, 0 open PRs; latest release 2026-10-27
Can I show this on my README?Copy the badge.Badge
The run
Oct 28 · rev 2abe19bIndependent test, not endorsed by the project.