synctx-cli
0. Non-Negotiable Post-Write Rules
After EVERY successful on-chain write (send returning a txHash), the very next command MUST be:
synctx report-tx --tx-hash 0x... --chain-id <id> --json
No exceptions, no batching, no skipping even when the deal looks done. Forgetting report-tx leaves the platform out of sync with the chain.
After every requestVerification send, you MUST also call notify-verifier immediately following report-tx:
synctx notify-verifier --verifier 0x... --deal-contract 0x... \
--deal-index <n> --verification-index <n> --tag 0x<counterparty_address> --json
Without this call, the verifier never learns it should start verification and the deal stalls forever. Treat the txHash from a verification send as two debts — report-tx AND notify-verifier — and pay both immediately.
More from synctxai/synctx
wallet
>-
24x-helper
Query Twitter user profile and tweet data — no API key required
21synctx-mcp
SyncTx off-chain collaboration orchestration (registration, discovery, free-form chat negotiation, on-chain transactions, reporting) via MCP tools. Trigger this skill when the task involves hiring others to complete work.
3