Project Introduction
ReviveCheck helps token-list maintainers and applications verify a release before accepting it. It connects finalized Portaldot V3 checks, retrievable reports, on-chain approval and an application policy. The demo follows a pUSD listing from a failed check to an approved release that a separate application can use.
Problem Solved
The demo starts with a candidate pUSD entry that declares 18 decimals, while the Portaldot V3 testnet reports 6. The wrong precision can misstate token amounts. Approval also needs to follow the exact release. ReviveCheck binds a decision to the checked report and its revision, so the application can withhold an entry when the revision changes, approval is revoked or the evidence expires.
Link
- Demo Video · ReviveCheck Demo Day (2:33)
- GitHub · Source and reproduction instructions
- Pitch Deck · ReviveCheck final deck (PDF)
Technical Highlights
- Compare the native and EVM views. ReviveApi aligns the finalized checkpoint and account mapping. The verifier compares pUSD precision, supply and balance through the Assets pallet and its ERC-20 precompile. The 18-decimal entry was refused in a real contract dry run.
- Replay the evidence that was approved. Remark stores the sealed report on-chain, and the Solidity registry records approval for its exact fingerprint. The video verifies that fingerprint and reproduces 13 of 13 observations at the original checkpoint.
- Follow the full release lifecycle. The Portaldot V3 testnet record contains 12 steps and 10 finalized receipts. They cover approval, listing, revision invalidation, explicit rebinding, revocation and restoration. The revision-2 pUSD listing finalized at block 187205 with matching native and EVM readbacks. Release record and receipts
- Put the decision in a consumer. A separate application built by the project installs the open-source package and checks its own policy before accepting a token. The report shown in the recording reached its seven-day freshness limit on November 1. The policy requires fresh approved evidence for continued acceptance. The demo runs on testnet, with both signer accounts controlled by the project.
Team
Duning Ouyang, solo developer. ReviveCheck is entered in Modular Cloud & Middleware. DoraHacks Build 50176
Judges & Voting Fit
For Judges. The video and linked receipts trace one token through a failed precision check, a corrected release, on-chain approval and the consumer’s admission decision. The repository includes the contracts, verification package and steps to reproduce the checks.
For Community Voters. The demo shows why a token list should check what the chain actually reports. When the catalog disagrees or the evidence expires, the application withholds the token until the release meets its policy again.