Skip to content

fix(validation): pay the configured validation fee automatically - #97

Merged
paulgnz merged 1 commit into
mainfrom
fix/validation-fee-autopay
Oct 1, 2026
Merged

paulgnz merged 1 commit into
mainfrom
fix/validation-fee-autopay

Conversation

@paulgnz

@paulgnz paulgnz commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator

agentvalid's validation_fee is now 10 XPR on mainnet (msig paul123/valfee1, executed). It stops one staked account from filling agentvalid's contract RAM with unlimited validation rows (found in the October contract review).

xpr_submit_validation and the validators page called validate on its own, which the contract now rejects. Both now read the live config and add the valfee: deposit in the same transaction when the fee is above zero. The plugin still applies maxTransferAmount to the fee.

  • openclaw: auto-fee path + 3 tests (fee paid, no fee, fee above cap refused); 253 passing
  • frontend: typecheck clean, tests pass
  • openclaw bumped to 0.8.7 (publish after merge)

agentvalid now charges a 10 XPR validation fee (msig valfee1) to stop
unbounded validation rows filling contract RAM. The plugin's
xpr_submit_validation and the site's validate form sent validate() alone,
which the contract now rejects. Both read the live config and prepend the
valfee: deposit when the fee is set; the plugin keeps the transfer cap.

openclaw 0.8.7.
@paulgnz
paulgnz merged commit 614d88c into main Oct 1, 2026
7 checks passed
@paulgnz
paulgnz deleted the fix/validation-fee-autopay branch October 1, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant