
About
Token vesting with a cross-VM ledger on QoreChain: QVEST vests on a cliff + linear schedule enforced by the EVM contract, and every claim atomically calls the bridge precompile to increase the beneficiary's allowance on the allowlisted Native cw20 contract — the Native contract holds a verifiable cross-VM vesting ledger (allowance equals total claimed), proven on-chain after every claim, including a forced revert proving atomicity.
How it's made
QoreVest is a Solidity contract (QVEST token, 6 decimals, 1M supply) deployed on the QoreChain Diana testnet. It enforces token vesting schedules with a cliff plus linear release. Every claim atomically calls the cross-VM bridge precompile to increase the beneficiary's allowance on the allowlisted Native cw20 contract, so the Native contract holds a verifiable cross-VM vesting ledger (allowance equals total claimed). A forced revert test proves the atomicity: if the Native leg fails, the whole claim reverts and no QVEST moves. We first investigated the cross-VM allowlist and found it holds only three targets and no vesting contract, so the schedule is enforced on the EVM side and the Native leg serves as the ledger and attestation — this limitation is documented honestly in the README. Transactions run inside post-quantum authorisation windows opened by hybrid-signed messages. The demo is a React app, the contract has 9 passing tests, and all on-chain evidence (3 schedules, 5 claims, 1 forced revert) is recorded in the repo.
Timeline
Comments and questions
- No comments yet.