Skip to content

Project notice

1.28.1 — Contract qualification and reproducible verification

This maintenance release makes contract build and verification evidence easier to check, documents which compiler belongs to each deployment, and corrects bounded defects in the separate legacy v2 contracts. Start with the contract warning and verification guide. For the installed agent, use the operator start guide.

What changes

  • Keep the current Solidity 0.8.37/Cancun build separate from the immutable October 11 Solidity 0.8.24/Paris deployment archive. Both use via IR and optimizer 200; their dependency versions also differ. Verification must use the exact sources, settings and constructor arguments of its address.
  • Add npm run compile:strict: compile every shipped production source and its dependencies, check fixture copies for drift, then force a fresh fixture build with the npm-locked Solidity compiler and reject every Solidity warning. The baseline fixture compilation already emitted no Solidity warnings; this prevents regressions. Hardhat debugging notices, dependency advisories and explorer verification status remain distinct checks.
  • Add mainnet:verification-package for either the recorded deployment or an exact reviewed new plan. Export all five Standard JSON inputs, ABI-encoded constructor arguments, Etherscan V2 request parameters and file digests without credentials, explorer submissions or transactions.
  • Correct legacy v2 job admission for zero rewards and expired deadlines/applications; retain the actual client in cancellation/delist events; bound combined fees/burn; clear certificate sale listings when ownership changes. Disable unsupported legacy NFT bonus registration until a separately funded design exists; retain the historical ABI selectors/getters with an explicit rejection of registration.
  • Add targeted legacy regressions and preserve the existing Ascension settlement, historical deployment, read-only verification, source-preservation and release-publication gates.
  • Synchronize active release/version guides and browser caches while retaining the SUCCESSOR Ω workshop, bilingual onboarding, every historical release note, original research and flowcharts.

Existing Ethereum contracts

The five recorded Ascension contracts remain at the same addresses, with the same deployed code, immutable bindings and ownership. This release does not deploy a contract, send a transaction, transfer funds, change a governor, migrate state or replace the canonical external $AGIALPHA token.

The archived deployment predates the current payout/burn balance checks and rejection-quorum safeguards. Those differences still require an explicit operational decision. Explorer notices about an old compiler can remain on historical addresses; changing the repository cannot remove their deployed compiler provenance. The exact explorer warning text must be examined before attributing any specific notice. See the deployed owner guide and the separate new-deployment guide.

The contracts/v2 suite is retained legacy material, separate from those five Ascension addresses. Its bounded fixes do not establish a commissioned end-to-end v2 system: the legacy registry/validation integration has additional interface gaps. Do not treat that suite as deployment-ready.

Legacy StakeManager.addAGIType rejects every bonus registration with NFT bonuses disabled. The former bonus model could pay more than a job's escrow by consuming other users' collateral. Settlement uses the funded escrow reward, and the unsupported bonus multiplier has been removed. Historical ABI selectors/getters remain for compatibility; an independently reviewed, separately funded bonus design is required before that feature can be enabled.

Evidence, upgrade and remaining qualification

A build without Solidity warnings establishes the diagnostics of the exact tested compilation, not a proof of flawless behavior. Exact-bytecode checks do not replace independent security/economic review, a real-token mainnet-fork lifecycle or the operator's commissioning decision. Hardhat debugging-support notices and separately reported dependency findings must remain visible.

Publication requires the full existing acceptance gates on the exact integrated commit. Read the release manifest and matching validation archive for actual accepted results, commit and producer identity; this source document does not record a future CI pass. Mainnet commissioning and any future signed deployment or migration remain separate, unresolved operations.

No native journal migration is introduced. Follow the backup and recovery procedure. The 1.28.0 workshop release and earlier deployment archive remain intact.

En français. Cette version améliore les contrôles de compilation et la reproduction des fichiers à vérifier, et corrige des défauts circonscrits de l'ancien module v2. Elle ne modifie aucun contrat sur Ethereum. Les cinq adresses existantes conservent leur code du 11 octobre et leurs paramètres historiques. Les bonus NFT de l’ancien module v2 sont explicitement désactivés tant qu’un financement séparé n’est pas conçu et vérifié. La validation indépendante et la mise en service restent à effectuer séparément.