AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Maya2C is a post-quantum layer-1 blockchain in Rust. Every transaction carries two NIST post-quantum signatures, ML-DSA and SLH-DSA. DAG-BFT finality.
Developer toolsRust · PythonGitHub @EricWijesingheOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Maya2C: a post-quantum Layer-1 blockchain in Rust. Every transaction carries two NIST post-quantum signatures (ML-DSA-65 + SLH-DSA), with DAG-BFT finality. Public testnet live at maya2c.dev.
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Help run the network — one line
Paste one line and your computer becomes a node of the test network. No
technical background is needed. Full steps, with a section for each OS:
maya2c.dev/guides/help-run.
Every transaction carries two signatures — ML-DSA-65 (FIPS 204) and
SLH-DSA-SHA2-128s (FIPS 205) — and both must verify. That is 11,165 bytes per
transaction, which is the price of not betting the chain on one lattice
assumption. Transport is libp2p with an ML-KEM-768 layer over Noise, and an
optional HQC-192 second KEM behind a flag.Read the full README ↗The full README is unavailable right now. Read it at the original link. The saved excerpt is shown below.
Help run the network — one line
Paste one line and your computer becomes a node of the test network. No
technical background is needed. Full steps, with a section for each OS:
maya2c.dev/guides/help-run.
Every transaction carries two signatures — ML-DSA-65 (FIPS 204) and
SLH-DSA-SHA2-128s (FIPS 205) — and both must verify. That is 11,165 bytes per
transaction, which is the price of not betting the chain on one lattice
assumption. Transport is libp2p with an ML-KEM-768 layer over Noise, and an
optional HQC-192 second KEM behind a flag.Read the full README ↗