jerry/apex-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use slot number (not POSIX ms) for activity datum last_proposal_slot

Browse Source 
The on-chain validator checks slot_mismatch against the tx validity range.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
david
2026-04-09 15:31:36 +02:00
parent a1b06ecf3f
commit 422d336257
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/vector/governance.ts
View File

@@ -557,7 +557,9 @@ Each batch UTxO holds ~30 AP3X for adoption rewards.`,
const propTokenUnit = GOV_PROPOSAL_MINT_HASH + propTokenName;
const actTokenUnit = GOV_PROPOSAL_MINT_HASH + actTokenName;
// Validity range: Lucid .validFrom/.validTo expect POSIX time in ms
// Get current slot + POSIX time for validity range and datum
const tip2 = await provider.getNetworkTip();
const spendSlot = tip2.slot;
const nowMs = Date.now();
const validFromMs = nowMs - 60_000; // 60 seconds ago
const validToMs = nowMs + 360_000; // 6 minutes from now
@@ -568,7 +570,7 @@ Each batch UTxO holds ~30 AP3X for adoption rewards.`,
agentDid, // agent_did
new Constr(0, [vkeyHash]), // agent_credential
1n, // active_proposal_count
BigInt(nowMs), // last_proposal_slot (POSIX ms)
BigInt(spendSlot), // last_proposal_slot
]));
// Redeemer: SubmitProposal = Constructor 0