feat: submit agent-wallet transactions#152
Conversation
|
Warning Review limit reached
More reviews will be available in 11 minutes and 59 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Time Submission Status
Submit or update total time with: Add time on top of previous submission with: See available commands to help comply with our Guidelines. |
|
@holdex pr submit-time 4h |
|
Caution Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted. Error details |
|
@coderabbitai full review |
✅ Action performedFull review finished. |
resolves: https://github.com/truflation/website/issues/4085
Adds the
maa_exectransaction to kwil-js so a developer can run one allow-listed action as an agent wallet (Modular Agent Address): the wallet's restricted agent or unrestricted owner signs the transaction, and the node looks up the rule, enforces the allow-list for the signer's role, and re-enters the engine with@callerrewritten to the wallet.maa_execis a distinct transaction payload, not an action call.What this adds
PayloadType.MAA_EXEC('maa_exec'),MAAExecPayload, andencodeMAAExec()— serialized byte-for-byte identically to kwil-db'score/types.MAAExec.MarshalBinary(the wire layout is a consensus contract: one divergent byte rewrites which action runs, or under whose identity).kwil.maaExec(body, signer)method on bothNodeKwilandWebKwil, mirroringexecSql/transfer. It normalizes the address (0x-hex or raw bytes), defaults an empty namespace tomain, validates the 20-byte length, and formats positional inputs through the same encoderexecuteuses.Utils.encodeMAAExecandTypes.MAAExecBodyexports.Testing
kwil-db core/types/payloads_maa_test.go), the single-call argument framing, and empty-namespace handling.tsc --noEmit, the full unit suite, and the CJS + ESM build pass; the builtdistreproduces the golden vector exactly.Context
This completes the kwil-js slice of MAA Problem #9. The sibling slices are already merged:
The sdk-js wrapper follows once a kwil-js version shipping this is published.